Learn about DokuWiki
Learn about DokuWiki
FreeNAS is built with Samba as a default. It is not activated by default but is already installed making using the Samba features very simple.
|This column is wider||than||others!|
FreeNAS can be installed on almost any hardware but to best suit the requirements of B-C-D it must meet the following:
Samba, once set up is very low maintenance. One big thing, however, is if a new user has been created in the domain FreeNAS will not automatically update right away so this must be done manually.
What should be monitored and all the alerts that could be generated. Who should get the alerts and what to do to resolve each.
If one machine delivering service of multiple what is the plan.
The SMB shared provided by FreeNAS are critical to the success of B-C-D. All digital documentation and paperwork is stored there. Down time is very damaging to the company.
Due to the importance of up time with this service the uptime goal is 2 days a year or 99.9955% of the time. FreeNAS is very stable but Active Directory can move forwards faster at times than Samba can keep up leading to issues authenticating. This leaves computers unable to connect to the server which is a large issue. Knowing this downtime is possible we can not commit to a higher up time.
Samba failure does not result in any direct data loss due to it denying access during a failure. The only predicted data loss is from changes that are not being updated on the file server. Most of these changes however are fixed by Windows automatically on re-connection. Despite this though the company can not afford to lose more than one hour of data due to this issue. It should be detected within the hour to prevent further data loss.
FreeNAS uses ZFS which allows for easy import of disks and import of a configuration file. With both of those features a full recovery can take no more than 5 hours. This along with at least 2 hours of trouble shooting bring the RPO to a total of 5 hours for full Samba recovery.