i’ve built my esxi box (skynet) … find some additional info at the unraid forums something i wanted to document. the command sequence to share the encrypted zfs filesystem after boot is $ sudo zfs mount -a (asks for the passphrase) $ sudo zfs set share=name=export_backup,path=/export/backup,prot=nfs backup/data the latter command is based on my setup also, oracle recently published an article on How to manage ZFS Data Encryption, with more details about zfs data encryption.
well, i need to add a couple of comments after my last post i deliberately chose to create the zfs dataset with a passphrase encryption method. as per solaris docs, this means it can’t mount it at boot time. the best practice would be a boot time prompt (a la TrueCrypt in windows), but until that time comes, i will live with loading after booting, using the following: $ sudo zfs mount -a $ sudo zfs set share tank/backup here seems to be a better way by doing zfs set key -l, but docs are scarce
so the plan is as follows: build a zfs box, with a two drive mirror pool rsync data from blackeard (my hackintosh mac) to the zfs box snaphot the zfs filesystem (full and incrementals) crashplan the backup to the cloud this basically gives me a two factor backup scenario: time machine-like fast access (without all the storage wasting that time machine does, on the zfs box) and offsite more secure storage (crashplan pro on the cloud)
i’m currently running an unRaid server, which hosts my media collection (movies, tv series, music, pictures and data backups) but, i’m running out of space on the server (currently 31.69TB used out of 32.51TB available) so i started looking for options on how to expand my capacity and decided on adding a second unRaid server, virtualizing both unRaids in an ESXi 5 head server and putting the disks on two DAS boxes (discussions at two unraid servers, atlas: a virtualized unraid, building a jbod das