#snapmirror source and destination different sizes

1 messages · Page 1 of 1 (latest)

tight tiger
#

I am running a snapmirror in order to migrate volumes from one cluster to another in ONTAP 9.11.1P14. As an example, the volumes are mirrored but the source volume space is 7TB while the destination is only using about 3TB. Any thoughts on why the size difference between the two volumes?

static bane
#

A couple of things. Which policy did you use? Vault? Mirror? MirrorVault? Do a snap list of the source and destination. Are all the snapshots on both sides?

What about volume efficiency?
Look at the source and destination “volume efficiency show”. Look at the output of “volume show -fields space-guarantee “. Are both sides the same? Is one thin (none) and one thick (volume). Lastly, take a look at “df -S -h” on the source and destination. How different are they?

tight tiger
#

Using Snapmirror Policy Mirror-Vault, volume efficiency enabled on both, snap list on destination does not have all of the snaps, none of the destination snaps were created before today. Source has a snap from last year that is 4.71TB. Both Source and Destination are Thin Provisioned. df -S -h output source is 7171GB, destination is 2430GB.

humble arch
#

well there is your answer then