Overland Storage SnapServer Administrator's Manual page 158

SnapServer 7.0 Administrator's Guide
Function
Security Model
File System
Permissions
Toggling
Security Models
Mixing security
models
At the Security Models page, click a volume name to manage the security model
(Windows/mixed or Unix) for the entire volume.
NOTE: In Traditional RAID, security models can also be applied to subdirectories of the volume.
10400317-001 10/2011
Description
Security model and permissions differ according to the method used to
create the security model directory:
• From the client: If SMB, permissions will either be according to ACL
inheritance (if the parent volume root directory has the Windows
security model) or Full Access to the owning user only. Permissions for
directories created by all other protocols will be set by the client (per the
client's umask).
• From the Web Management Interface: If created in a UNIX volume,
permissions will be 777 (rwxrwxrwx). If created in a Windows/Mixed
volume, permissions will allow all users to create, delete, and change
permissions on files created inside the security model, and will grant
full control to administrators.
Changes to a security model can optionally be propagated to the
corresponding personality with a default permission to all files and
directories underneath the security model.
When changing the security model:
• If changing from Windows to UNIX, all files and directories will be
changed to be owned by admin and admingrp, with UNIX permissions
of 777(rwxrwxrwx).
• If changing from UNIX to Windows, files and directories will be changed
to default permissions that allow all users the ability to create and
manage their own files and directories and to access other users' files
and directories.
You can create security models of different security models on the same
volume.
©2010-11 Overland Storage, Inc.
7 – Security Options
7-30