Migrating data from TrueNAS ZFS pool to new native pool with zfs send | zfs recv

[Akshunhiro]

Hi all, just need a sanity check please.

 

I've had a ZFS pool in unRAID for a while but it was created in TrueNAS. I'm now in a position to create and move to a new native pool but wanted to check the correct command to migrate data across while hopefully retaining snapshots.

 

I was going to take one last snapshot and use zfs send | zfs receive e.g.

 

zfs send -Rcv chimera/data@migrate | zfs recv -s newchimera/data

 

The last time I attempted this (in unRAID before native ZFS support), the dataset wasn't automatically created (it was showing but had a 0 size, all data was in the root?).

 

I have a script to take a recursive snapshot so wondering if I should just use that instead of specifying the "data" dataset?

 

Here's what I'm working with;

 

zfs list
NAME           USED  AVAIL     REFER  MOUNTPOINT
chimera       34.2T  9.24T      224K  /mnt/chimera
chimera/data  34.2T  9.24T     31.1T  /mnt/chimera/data

 

zfs list -t filesystem -o space
NAME          AVAIL   USED  USEDSNAP  USEDDS  USEDREFRESERV  USEDCHILD
chimera       9.24T  34.2T        0B    224K             0B      34.2T
chimera/data  9.24T  34.2T     3.12T   31.1T             0B         0B

 

zfs get copies
NAME                           PROPERTY  VALUE   SOURCE
chimera                        copies    1       default
chimera@auto-July23            copies    -       -
chimera@auto-August23          copies    -       -
chimera@auto-September23       copies    -       -
chimera@auto-October23         copies    -       -
chimera@auto-November23        copies    -       -
chimera@auto-December23        copies    -       -
chimera@auto-January24         copies    -       -
chimera@auto-February24        copies    -       -
chimera@auto-March24           copies    -       -
chimera@auto-April24           copies    -       -
chimera@auto-May24             copies    -       -
chimera/data                   copies    1       local
chimera/data@auto-July23       copies    -       -
chimera/data@auto-August23     copies    -       -
chimera/data@auto-September23  copies    -       -
chimera/data@auto-October23    copies    -       -
chimera/data@auto-November23   copies    -       -
chimera/data@auto-December23   copies    -       -
chimera/data@auto-January24    copies    -       -
chimera/data@auto-February24   copies    -       -
chimera/data@auto-March24      copies    -       -
chimera/data@auto-April24      copies    -       -
chimera/data@auto-May24        copies    -       -

 

Trying to avoid bungling this given how long it'll take to move everything over.

 

TIA!

[JorgeB]

52 minutes ago, Akshunhiro said:

zfs send -Rcv chimera/data@migrate | zfs recv -s newchimera/data

Looks OK to me, compress may not help a lot, depending on the data, and if you are using large blocks use -L