Testing Potential Shadow Migration using the CLI
Before attempting a complete migration, it is important to test the migration to make
sure that the appliance has appropriate permissions and security attributes are
translated correctly. Once you are confident that the basic setup is functional, the
filesystems can be setup for the final migration.
Note -
As part of capacity planning, remember to take into account default/user group
quotas because the quotas could be exceeded if the source is larger than the
destination. Also, shadow migration will fail if the target runs out of disk
space.
-
Configure the source so that the appliance has root access to the share. This
typically involves adding an NFS host-based exception or setting the anonymous user
mapping (the latter having more significant security implications).
-
Create a share on the local filesystem with the shadow attribute set to
'nfs://<host>/<snapshotpath>' in the CLI or just
'<host>/<snapshotpath>' in the BUI (with the protocol selected as
'NFS'). The snapshot should be read-only copy of the source. If no snapshots are
available, a read-write source can be used, but may result in undefined
errors.
-
Validate that file contents and identity mapping are correctly preserved by
traversing the file structure.
-
If the data source is read-only (as with a snapshot), let the migration complete
and verify that there were no errors in the transfer.