Specifications

Data Migration
62 SnapServer Administrator Guide
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 (e.g., trusted domains, if
the SnapServer 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 SnapServer 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.
However, when migrating from a Windows source to a Unix SnapTree, permissions
cannot be retained (since Unix snaptrees are required to be Unix personality
throughout). Files and directories will inherit the Unix personality and will have a
set of default Unix permissions.
Migrating from a GuardianOS Server
When migrating from one GuardianOS server to another, it is recommended that
you maintain the same security model on the target server that you have on the
source.
• If your source server uses a Windows SnapTree and has permissions assigned to
Windows domain users, use a Windows connection for migration. Windows
permissions will be retained exactly as they are on the source, with the same
enforcement limitations for unknown users as for migration from Windows
servers (see Migrating from a Windows Security Model to a Windows SnapTree).
Note If migrating from a pre-5.0 GuardianOS server, Windows permissions will
be retained verbatim, but may have different meaning due to the differences
between the pre-5.0 POSIX ACL security model and the Windows security model
introduced in 5.0.