Table of Contents
Advertisement
Migrating Local File Systems
Migrating Local File Systems
In addition to its primary purpose of migrating data from remote sources, the same mechanism
can also be used to migrate data from local filesystem to another on the appliance. This can
be used to change settings that otherwise cannot be modified, such as creating a compressed
version of a filesystem or changing the recordsize for a filesystem after the fact. In this model,
the old share (or subdirectory within a share) is made read-only or moved aside, and a new
share is created with the shadow property set using the file protocol. Clients access this new
share, and data is written using the settings of the new share.
Using Shadow Migration Analytics
In addition to standard monitoring on a per-share basis, it is also possible to monitor shadow
migration system-wide through Analytics. The shadow migration analytics are available under
the "Data Movement" category. There are three basic statistics available:
Shadow Migration Requests - This statistic tracks requests for files or directories that are
■
not cached and known to be local to the filesystem. It does account for both migrated and
unmigrated files and directories, and it can be used to track the latency incurred as part of
shadow migration, as well as track the progress of background migration. It can be broken
down by file, share, project, or latency. It currently encompasses both synchronous and
asynchronous (background) migration, so it is not possible to view only latency visible to
clients.
Shadow Migration Bytes - This statistic tracks bytes transferred as part of migrating file
■
or directory contents. This does not apply to metadata (extended attributes, ACLs, etc). It
gives a rough approximation of the data transferred, but source datasets with a large amount
of metadata will show a disproportionally small bandwidth. The complete bandwidth can
be observed by looking at network analytics. This statistic can be broken down by local
filename, share, or project.
Shadow Migration Operations - This statistic tracks operations that require going to
■
the source filesystem. This can be used to track the latency of requests from the shadow
migration source. It can be broken down by file, share, project, or latency.
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.
434
Oracle ZFS Storage Appliance Administration Guide, Release OS8.6.x • September 2016
Advertisement
Table of Contents
