Testing Potential Shadow Migration using the CLI

Before attempting a complete migration, it is important to test the migration to make sure that Oracle ZFS Storage Appliance has appropriate permissions and security attributes are translated correctly. After you are confident that the basic setup is functional, the filesystems can be set up 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.

1. 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).
2. Create a share on the local filesystem with the shadow attribute set to nfs://<host>/<snapshotpath> in the CLI, or <host>/<snapshotpath> in the BUI (with the NFS protocol selected). The snapshot should be a read-only copy of the source. If no snapshots are available, a read-write source can be used, but may result in undefined errors.
3. Validate that file contents and identity mapping are correctly preserved by traversing the file structure.
4. 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.