Help
ZFS server settings allow you to easily clone datasets for your students. This is helpfull for making student virtual machins and quickly cloning copies. You will need a source dataset to hold what you want cloned (one sub dataset for each folder), and a destination dataset where a dataset will be created for each student, as well as a sub dataset for each cloned item. It is intended that the student can access the folder from a mapped drive in windows. This script is written to interface specifically with a FreeNas based server.
Example:
dpool/source_vms (dataset)
-> win8 (sub datasets)
-> win7
dpool/dest_vms (This is a dataset)
-> bobsmith (dataset for each user)
-> win8 (cloned dataset)
ZPool Enabled: Turn on/off the the ZFS Server tools.
ZPool Server Address: Please enter the IP of the ZFS Server. NOTE: Using the IP is more reliable. Default options for DNS lookup does not allow this server to look back into your network to resolve names.
ZPool Login User: Use a LOCAL NOT DOMAIN admin account that is on the ZFS server. This account needs priviledges to create datasets and clone datasets. The account HAS to be LOCAL or it will not work!!!
ZPool Login Password: The password for the local account described above. Password is encypted using AES encryption.
ZPool Source Dataset: Choose the location of source datasets. This is where you will clone from. The system will grab sub datasets from this location and make them available to clone. Use the refresh link to get a current list of datasets from the server.
ZPool Dest Dataset: Choose the location of the home drives. A dataset will be created for each user (student or faculty). A dataset will be created in the home director for each source. These will be clones of the source dataset. Use the refresh link to get a current list of datasets from the server.
ZPool Sync Setting: You can set the default sync setting for cloned datasets. This will affect reliablity and performance. Standard -> use log device for sync writes, direct write to spinning drives for async writes, always -> use log device for all writes, disabled -> don't log any writes (fastest but can be unsafe!).