10400455-002
©2008-14 Overland Storage, Inc.
212
SnapScale/RAINcloudOS 4.1 Administrator’s Guide
8 - Maintenance
2.
Reopen the
Data Import
page. All fields (except the password) from the last import will
still be visible on the page.
By default, all files will be re-imported. If you want only to import those files that failed
to import the first time, you can disable the
Overwrite Existing Target Files
option.
However, make sure that all problematic files from the first import are deleted from the
target so they can be re-imported.
NOTE: If an import failed, it is strongly recommended that you enable the Verify imported data
option for the re-importation.
3.
Enter your password and click
Start Import
to run the import again.
Preserving Permissions
The types of permissions retained will differ, depending on which import scenario is applied.
Importing from a Windows Security Model to a Windows Personality Directory
If you are importing from a Windows server (or other type of server that follows the Windows
security model) to a Windows personality directory, permissions are retained exactly as they
exist on the source. However, as is the case when moving files with permissions between
Windows servers, permissions for users who are unknown on the target are retained but not
enforced. This includes permissions for:
•
Local users on the source machine.
•
Domain users for domains unknown to the cluster (for example, trusted domains, if the
cluster is not configured to support trusted domains).
•
Certain built-in Windows users and groups.
Importing from a Unix Security Model to a Unix Personality directory
If you are importing from a Unix server to a Unix personality directory, Unix permissions for
UIDs/GIDs are copied exactly from source to target; thus, identities of the users and groups
are best retained if the SnapScale cluster belongs to the same NIS domain as the Unix server.
Importing Between Conflicting Security Models
When importing from a Unix source to a Windows security model target, Unix permissions are
retained and the security personality on the resulting files and directories will be Unix.
However, when importing from a Windows source to a Unix security model target,
permissions cannot be retained (since Unix root directories are required to be Unix personality
throughout). Files and directories will inherit the Unix personality and will have a set of
default Unix permissions.
Importing from a SnapServer or SnapScale Cluster
When importing from a different SnapServer or SnapScale cluster, it is recommended that you
maintain the same security model on the target that you have on the source.
•
If your source uses a Windows security model and has permissions assigned to Windows
domain users, use a Windows (SMB) connection for import. Windows permissions are
retained exactly as they are on the source, with the same enforcement limitations for
unknown users as for importing from Windows servers (see
Security Model to a Windows Personality Directory on page 212
).
•
If your source server or cluster uses a Unix security model and has permissions assigned
to local or NIS users, use an NFS connection for import.
