Migrating Data from an Active NFS Server
Schedule downtime during which clients can be quiesced and reconfigured
to point to a new server.
Configure the source so that the ZFSSA 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
Configure the source to be read-only. This step is technically optional,
but it is much easier to guarantee compliance if it's impossible for
misconfigured clients to write to the source while migration is in
Create a share on the local filesystem with the shadow attribute set to
'nfs://<host>/<path>' in the CLI or just
'<host>/<path>' in the BUI (with the protocol selected as
Reconfigure clients to point at the local share on the SS7000.
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 above. Multiple shares can be created during a single
scheduled downtime through scripting the CLI.