onlineforums
Explorer
- Joined
- Oct 1, 2017
- Messages
- 56
Friends,
I need some reassurance of the process to not screw up my configurations, settings, jails, etc!
I recently upgraded from Freenas to Truenas-13.0-U3.1 (CORE) on an Freenas-mini-xl. Everything went totally fine.
My pool (tank01) uses legacy encryption which requires a passphrase to unlock after locking or after a reboot. This works totally fine.
I recently backed my photos, documents and jails (both the dataset and the jails export command tarbar method) from tank01 to an external hard drive using zfs send|receive and verified the data on the external drive contains the irreplaceable photos, documents and jails data. I have disconnected this external hard drive and connected it back in, unlocked it and everything is this looks fine.
I believe now would be a great time to upgrade the tank01 main pool to use the latest and likely the only foreseeable future supported encryption method. My understanding is in doing so I would need to destroy the tank01 pool, upgrade the zfs feature flags and then create the tank01 pool fresh with zfs encryption enabled. If this understanding is incorrect please correct it.
Here are my concerns:
1. System Dataset -> On this page it has the System Dataset Pool as my tank01 (not freenas-boot). Is this the correct setup method? Wouldn't this mean that when I destroy tank01 that I'll also destroy everything about my configurations in Truenas? For example, I have a few simple cron jobs, periodic snapshot tasks, scrub tasks, users accounts, etc. Will this all get destroyed when I destroy tank01 or is all of that data found in the freenas-boot drive/pool? Help me understand the pros and cons of having the "system dataset pool" on the main pool which I believe is common practice since I can have multiple hard drive failures on the main pool but not the freenas-boot pool.
2. Jails and configurations: Right now I have a few jails that run some services that I use internally on my local network. I recursively backed up the iocage dataset and used the jails export command which created a tarball. My concern is that destroying the tank01 pool that the Jails will still show up in the web interface and when i import the jails from the backup to the new zfs encrypted tank01 pool that it will duplicate or cause some problems within the Jails section of the web interface.
Should I just bag the whole idea and keep everything the way it is and forego the zfs encryption? I just want to future proof myself just incase the team decides to totally deprecate, not support and actually remove GUI interfaces to work with legacy encryption created during the FreeNAS era.
I need some reassurance of the process to not screw up my configurations, settings, jails, etc!
I recently upgraded from Freenas to Truenas-13.0-U3.1 (CORE) on an Freenas-mini-xl. Everything went totally fine.
My pool (tank01) uses legacy encryption which requires a passphrase to unlock after locking or after a reboot. This works totally fine.
I recently backed my photos, documents and jails (both the dataset and the jails export command tarbar method) from tank01 to an external hard drive using zfs send|receive and verified the data on the external drive contains the irreplaceable photos, documents and jails data. I have disconnected this external hard drive and connected it back in, unlocked it and everything is this looks fine.
I believe now would be a great time to upgrade the tank01 main pool to use the latest and likely the only foreseeable future supported encryption method. My understanding is in doing so I would need to destroy the tank01 pool, upgrade the zfs feature flags and then create the tank01 pool fresh with zfs encryption enabled. If this understanding is incorrect please correct it.
Here are my concerns:
1. System Dataset -> On this page it has the System Dataset Pool as my tank01 (not freenas-boot). Is this the correct setup method? Wouldn't this mean that when I destroy tank01 that I'll also destroy everything about my configurations in Truenas? For example, I have a few simple cron jobs, periodic snapshot tasks, scrub tasks, users accounts, etc. Will this all get destroyed when I destroy tank01 or is all of that data found in the freenas-boot drive/pool? Help me understand the pros and cons of having the "system dataset pool" on the main pool which I believe is common practice since I can have multiple hard drive failures on the main pool but not the freenas-boot pool.
2. Jails and configurations: Right now I have a few jails that run some services that I use internally on my local network. I recursively backed up the iocage dataset and used the jails export command which created a tarball. My concern is that destroying the tank01 pool that the Jails will still show up in the web interface and when i import the jails from the backup to the new zfs encrypted tank01 pool that it will duplicate or cause some problems within the Jails section of the web interface.
Should I just bag the whole idea and keep everything the way it is and forego the zfs encryption? I just want to future proof myself just incase the team decides to totally deprecate, not support and actually remove GUI interfaces to work with legacy encryption created during the FreeNAS era.