Migrating Data from an Active NFS Server using the CLI

Use the following procedure to migrate data from an active NFS server using the CLI. Note that shadow migration fails if it encounters files under procfs or the following special file types: doors, sockets, and event ports.

1. Schedule downtime during which clients can be quiesced and reconfigured to point to a new server.
2. Configure the source so that Oracle ZFS Storage 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).
3. Configure the source to be read-only. This step is technically optional, but it is much easier to guarantee compliance if it is impossible for misconfigured clients to write to the source while migration is in progress.
4. Create a share on the local filesystem with the shadow attribute set to nfs://<host>/<path> in the CLI, or <host>/<path> in the BUI (with the NFS protocol selected).
5. Reconfigure clients to point at the local share on the appliance.

   At this point, shadow migration should be running in the background, and client requests should be serviced as necessary. You can observe the progress as described earlier. Multiple filesystems can be created during a single scheduled downtime through scripting the CLI.