Who are we?
We are digital librarians. Among us are represented the various reasons to keep data -- legal requirements, competitive requirements, uncertainty of permanence of cloud services, distaste for transmitting your data externally (e.g. government or corporate espionage), cultural and familial archivists, internet collapse preppers, and people who do it themselves so they're sure it's done right. Everyone has their reasons for curating the data they have decided to keep (either forever or For A Damn Long Time). Along the way we have sought out like-minded individuals to exchange strategies, war stories, and cautionary tales of failures.
We are one. We are legion. And we're trying really hard not to forget.
-- 5-4-3-2-1-bang from this thread
If you do a raw zfs send from the old to the temporary server, the zfs data should be completely replicated. Including all settings, pools, quotas, etc.
You however need to know how truenas detects pools, if it has anything to do with the physical disks you are going to have problems.
You however need to know how truenas detects pools, if it has anything to do with the physical disks you are going to have problems.
Yeah that part I am not sure of. My plan was to name the pool the same name as my old pool then do the zfs send from old to new.
I think a lot of the settings like shares and such just look at the pool name. As long as the new pool is name the same as the old pool it should be a drop in replacement once I import the pool. But I don't know if Truenas would like having two different pools that are named the same, even if the old pool was removed. Or if things like automatic snapshots or replication tasks would be ok with that.
I might need to ask this on the TrueNas forum