[EFAULT] Re-encrypting already encrypted source dataset ‘zpool/yy’ while preserving its properties is not supported

[Olivia]

Hi

I get this error on latest stable TrueNAS:

* [EFAULT] Re-encrypting already encrypted source dataset ‘zpool/yy’ while preserving its properties is not supported.

Source System (datasets not automatically unlocked at boot, I need manual passhrase)

Remote system (unecrypted pool)

my replication task:

thank you very much for help

[Apollo]

I think you need to uncheck the “Encryption” box under the “Destination” section.

[winnielinnie]

Do you want the destination dataset to be encrypted or unencrypted? If encrypted, do you want it to be with the same key/passphrase that the source requires?

[Olivia]

@winnielinnie

If encrypted, do you want it to be with the same key/passphrase that the source requires?

Yes. Same passphrase. Thanks.

[Olivia]

@Apollo

I think you need to uncheck the “Encryption” box under the “Destination” section.

now this error

[EFAULT] Unable to send encrypted dataset 'zpool/timemachine' to existing unencrypted or unrelated dataset 'zfs-replication'.

[winnielinnie]

@Olivia

now this error

It’s trying to overwrite a root dataset. This is unsupported and dangerous if allowed.

You need to manually type /siri as the destination dataset.

Make sure no “zfs-replication/siri” dataset already exists on the destination pool.

You would do the same thing for the “timemacine” replication. Manually add /timemachine as the destination.

[Olivia]

thank you. It’s working.
Just to be sure: the destination is also encrypted? Same passhrase as source?

[winnielinnie]

@Olivia

Just to be sure: the destination is also encrypted? Same passhrase as source?

It should be. If the source dataset is encrypted, then enabling “Include Dataset Properties” or “Full Filesystem Replication” will invoke a “raw stream”. This sends the data untouched: same properties, same compression, same encryption.

[Olivia]

thanks. How-To verify it? CLI command is OK

[winnielinnie]

Five memtests before bed and two memtests in the morning. Doctor’s orders.

It can be tested in the UI or command-line without actually unlocking the dataset.

zfs load-key -n zfs-replication/siri

It’s sill good practice to occasionally check that the backup data is accessible, since you don’t want to be in an emergency where you cannot retrieve data that you thought could be relied on. (Don’t write or modify anything on the destination filesystem, since it will break future incremental replications.)

[Olivia]

Enter passphrase for 'zfs-replication/siri':
1 / 1 key(s) successfully verified

thank you guys for help

You guys better than ChatGPT and Claude, because I asked the same question but no correct answer