Stopping An Import Job; Recreating An Import Job; Preserving Permissions - Overland Storage SnapServer Administrator's Manual

SnapServer GuardianOS 7.2 Administrator's Guide

Stopping an Import Job

To stop the import at any time, click the Stop Import button on the Data Import page. If a file
was in the process of being copied, the partially-copied file on the target will be removed.

Recreating an Import Job

The Data Import log records all errors that occurred during import. You can import files and
folders that were not imported during the original job because of an error condition (for
example, the file was locked).
1. Review the Data Import errors log and correct all error conditions.
2. Reopen the Data Import page. All fields (except the password) for the last import will
still be visible on the page.
3. Click Start Import to run the import again. 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 any problematic
files during the first import are deleted from the target SnapServer so they will be re-
imported.
NOTE: If an import failed, it is strongly recommended that you enable the Verify imported data

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 Root Directory
If you are importing from a Windows server (or other type of server that follows the Windows
security model) to a Windows root directory on a SnapServer, permissions will be retained
exactly as they exist on the source. However, as is the case when moving files with
permissions between Windows servers, permissions for users that are unknown on the
target server will be retained but not enforced. This includes permissions for:
• Local users on the source machine.
• Domain users for domains unknown to the SnapServer (for example, trusted domains,
if the SnapServer is not configured to support trusted domains).
• Certain built-in Windows users and groups.
Importing from a UNIX Security Model to a UNIX Root directory
If you are importing from a UNIX server to a UNIX root directory, UNIX permissions for
UIDs/GIDs are copied exactly from source to target; thus, identities of the users and groups
will be best retained if the SnapServer belongs to the same NIS domain as the UNIX server.
Importing Between Conflicting Security Models
When importing from a UNIX source to a Windows root directory, UNIX permissions will be
retained and the security personality on the resulting files and directories will be UNIX.
However, when importing from a Windows source to a UNIX root directory, 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.
10400317-003 05/2012
option for the re-importation.
©2010-12 Overland Storage, Inc.
Data Import
 9-12