10400328-001 02/2011
©2011 Overland Storage, Inc.
W
3-6
SnapServer GuardianOS 6.5 Setup Guide
Migrating Data to the SnapServer
specified security model, which indicates which file permission personality will be
present on files by default, and whether that personality can be changed by users
when changing permissions. All top level volume directories, as well as all directories
inside the first level of a volume, are considered SnapTrees.
NFS Share Access
When controlling share access for NFS clients, administrators can limit client access
to the shares independently of share level permissions that apply to other protocols.
Access is controlled on a per-share basis. To set the NFS access, open the
Shares
page
and click the appropriate
NFS Access
link in the Shares table. Changes made on this
screen affect the NFS “exports” file within GuardianOS.
Note:
If there are multiple shares to the same directory on the disk, and those shares
permit access via NFS, they must all have the same NFS export configuration.
This is enforced when configuring NFS access to the overlapping shares.
Migrating Data to the SnapServer
Once storage structure and data management configurations have been set, data can
be migrated from a legacy SnapServer or other computer that supports CIFS or NFS
to the new SnapServer. The Data Migration (DM) utility can be used to copy or move
files and folders from a server on the network (source) to a SnapServer (target).
Using the Data Migration Utility
Use the Data Migration utility to transport data directly from the source to the
SnapServer target.
The following migration options can be specified:
• Copy or move data
• Include subfolders
• Overwrite existing files
• Preserve the original permissions settings
Note:
Before selecting this option, be sure to read the Data Migration topic in the
Administrators Guide
for information about the migration behavior of
different permissions.
• Verify migrated data
Note:
If you select to verify migrated data, all data will be read from the source
twice, once to write to the SnapServer and once to perform a binary
comparison with the data written to the SnapServer. This could be a lengthy
process.
If an error or exception is encountered during migration (e.g., a file or folder is locked
and cannot be migrated), the DM utility records the exception in a log, and continues
the operation. When the migration is completed, the administrator can view the log of
migration errors.
Setting Up a Data Migration Job
1. To access the Data Migration utility, navigate to
Maintenance >
Data Migration
.
2. Provide the required information about the source server or workstation and the
target SnapServer.
