Adaptec 5325301656 Administration Guide - Page 65

Data Migration • Preserve the original permissions settings Note If you elect to preserve original permissions settings, be sure to review Preserving Permissions. • Verify migrated data Note If you elect to verify migrated data, all data will be read twice, once for migration and once for comparison to the copied data. This could be a lengthy process. For details about setting up a migration job, see the online help. Note If a migration failed, it is strongly recommended that you enable the Verify migrated data option for the re-migration. Preserving Permissions The types of permissions retained will differ, depending on which of the following migration scenarios is applied: Migrating from a Windows Security Model to a Windows SnapTree If you are migrating from a Windows server (or other type of server that follows the Windows security model) to a Windows SnapTree on a Snap Server, 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 Snap Server (e.g., trusted domains, if the Snap Server is not configured to support trusted domains). • Certain built-in Windows users and groups. Migrating from a UNIX Security Model to a UNIX SnapTree If you are migrating from a UNIX server to a UNIX SnapTree, 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 Snap Server belongs to the same NIS domain as the UNIX server. Migrating Between Conflicting Security Models When migrating from a Unix source to a Windows SnapTree, Unix permissions will be retained and the security personality on the resulting files and directories will be Unix. Chapter 4 Storage Configuration and Expansion 51