Im aware the answer to my question/topic is YES , IF the child dataset has "inherit (encrypted)" set to YES (ie checked off).
but my question / case is different. Im using pull-replication, and the pull-replication task is the one creating this dataset (and i dont see an option to set THAT DS to "inherit (encrypted)"=YES).
So my question is: is the dataset in this example "public8TBz2-pull" in fact encrypted? Meaning if i were to pull the physical drives from this machine, insert them into a new blank ZFS system, would one be able to access this data, without my encryption passphrase?
(i can confirm the obvious, if i LOCK the parent data set, ie " he8xZ2-PullReplc-8tbRD0" and then look inside of it, the "public8TBz2-pull" dataset is gone - GOOD)
(ofcourse, once i unlock parent data set, ie " he8xZ2-PullReplc-8tbRD0", the "public8TBz2-pull" dataset re-appears - also GOOD)
- but im wondering if its data on this child dataset is actually encrypted on disk, like any other encrypted zfs dataset, or is the parent DS JUST un-mounted and that is why lock hides, the child dataset.
see picts below please,
(why am i not just setting the Encryption setting , in the Replication task for the Destination dataset? BC ive used that setup before, and i end up with many datasets for each of my replication tasks that i have to unlock, anytime the system reboots or has a power issue- so my goal was to just have 1 or 2x parent datasets that i would need to unlock, in cases of reboots on this backup system).
but my question / case is different. Im using pull-replication, and the pull-replication task is the one creating this dataset (and i dont see an option to set THAT DS to "inherit (encrypted)"=YES).
So my question is: is the dataset in this example "public8TBz2-pull" in fact encrypted? Meaning if i were to pull the physical drives from this machine, insert them into a new blank ZFS system, would one be able to access this data, without my encryption passphrase?
(i can confirm the obvious, if i LOCK the parent data set, ie " he8xZ2-PullReplc-8tbRD0" and then look inside of it, the "public8TBz2-pull" dataset is gone - GOOD)
(ofcourse, once i unlock parent data set, ie " he8xZ2-PullReplc-8tbRD0", the "public8TBz2-pull" dataset re-appears - also GOOD)
- but im wondering if its data on this child dataset is actually encrypted on disk, like any other encrypted zfs dataset, or is the parent DS JUST un-mounted and that is why lock hides, the child dataset.
see picts below please,
(why am i not just setting the Encryption setting , in the Replication task for the Destination dataset? BC ive used that setup before, and i end up with many datasets for each of my replication tasks that i have to unlock, anytime the system reboots or has a power issue- so my goal was to just have 1 or 2x parent datasets that i would need to unlock, in cases of reboots on this backup system).