Home » Adaptec Manuals » Network Storage Servers » Adaptec 5325301656 » Manual Viewer

Adaptec 5325301656 Administration Guide - Page 105

Setting File and Directory Access Permissions and Inheritance (Windows), GROUP, Users

UPC - 753253016563

Add to My Manuals
Save this manual to your list of manuals

Page 105 highlights

Windows ACLs Permissions are enforced for the specified users in the same manner for all client protocols, including non-SMB clients that normally have the UNIX security personality. However, if a non-SMB client changes permissions or ownership on a Windows personality file or directory (or deletes and recreates it), the personality will change to UNIX with the UNIX permissions specified by the client. Note Group membership of NFS clients is established by configuring the local client's user account or the NIS domain. Group membership of Snap Server local users or users ID-mapped to domain users is not observed by NFS clients. Therefore, ACL permissions applied to groups may not apply as expected to NFS clients. Default File and Folder Permissions When a file or directory is created by an SMB client, the owner of the file will be the user who created the file (except for files created by local or domain administrators, in which case the owner will be the "Administrators" group, mapped to the local admingrp), and the ACL will be inherited per the inheritance ACEs on the parent directory's ACL. The owner of a file or directory always implicitly has the ability to change permissions, regardless of the permissions established in the ACL. In addition, members of the Snap Server's local admin group, as well as members of Domain Admins (if the server is configured to belong to a domain) always implicitly have take ownership and change ownership permissions. Setting File and Directory Access Permissions and Inheritance (Windows) Access permissions for files and directories with the Windows security personality are set using standard Windows NT, 2000, 2003, XP, or Vista security tools. GuardianOS supports: • All standard generic and advanced access permissions that can be assigned by Windows clients. • All levels of inheritance that can be assigned to an ACE in a directory ACL from a Windows client. • Automatic inheritance from parent directories, as well as the ability to disable automatic inheritance from parents. • Special assignment and inheritance of the CREATOR OWNER, CREATOR GROUP, Users, Authenticated Users, and Administrators built-in users and groups. Chapter 6 Share and File Access 91

Section	Page
Contents	7
Administrative Overview	15
GuardianOS Specifications	16
What’s New in GuardianOS	19
Snap Server Manager	23
Connecting to the Server for the First Time	26
Using the Initial Setup Wizard	28
Determining Capacity	29
Scheduling Data Protection Tasks	30
Migrating Data from Legacy Servers to the Snap Server	30
Configuring the Snap Server as a Print Server	31
Configuring an APC-Brand UPS	31
SnapExtensions	31
Network Access to the Server	33
Viewing Current Network Settings	34
TCP/IP Options	35
Configuring TCP/IP Settings	37
Default Network Protocol Settings	39
Windows Networking Configuration	40
Support for Windows Networking (SMB)	40
Support for Windows Network Authentication	41
NFS Access	44
Apple Networking Configuration	45
FTP Access	47
HTTP/HTTPS Access (Web View)	47
DHCP Server	48
Print Server	48
User & Group Management	51
Default User and Group Settings	52
UID and GID Assignments	52
Local Users and Groups	53
NIS Domain	54
Storage Configuration and Expansion	55
Default Storage Configuration	56
Changing the Default Storage Configuration	56
RAIDs	57
RAID Groups	59
Volumes	61
Quotas	63
Setting User Quotas	64
Data Migration	64
Preserving Permissions	65
Expansion Arrays	66
The SANbloc S50	66
Managing Expansion Array Storage	67
Disks and Units	69
Replacing Disk Drives on a RAID	69
Adding Disk Drives to a RAID	70
Hot Swapping Disk Drives	70
iSCSI Disks	77
Configuring iSCSI Initiators	78
iSCSI Configuration for Microsoft Windows using MS Initiator	79
Configuring the QLogic QLA4010 and QLA4050 iSCSI Initiators for Microsoft Windows	84
iSCSI Configuration for Linux and UNIX	84
iSCSI Configuration for Novell NetWare	86
iSCSI Configuration for VMware	86
iSCSI Configuration on the Snap Server	87
Creating iSCSI Disks	90
Share and File Access	93
Configuring Share and Folder Security Overview	94
Components and Options	96
SnapTrees and Security Models	98
ID Mapping	100
Creating Shares	101
Configuring Share Access	102
Share Access Behaviors	102
Setting Share Access Permissions	103
Creating Home Directories	104
Windows ACLs	104
Setting File and Directory Access Permissions and Inheritance (Windows)	105
Security Guides	106
Snapshots	109
Snapshot Management and Usage	110
Estimating Snapshot Pool Requirements	111
Adjusting Snapshot Pool Size	112
Accessing Snapshots	112
Coordinating Snapshot and Backup Operations	113
Disaster Recovery	115
Backing Up Server and Volume Settings	115
Backing Up the NetVault Database Directory	118
Recovering the NetVault Database	119
Disaster Recovery Procedural Overview	121
CA eTrust Antivirus Software	123
Antivirus Dependencies	124
Launching the CA eTrust Antivirus GUI	125
The Local Scanner View	126
Scan Job Configuration and Scheduling	127
Defining Scan Jobs	127
Running a Manual Scan Job	128
Scheduling a Scan Job	128
Signature Updates	129
Updating Snap Servers that have Internet Access	130
Updating a Snap Server that does not have Internet Access	131
Distributing Updates from One Server to Another	131
Verifying Download Events	133
Alert Options	134
The Move Directory	134
Log View	135
Unicode	137
What is Unicode?	137
Converting to Unicode	137
Unicode and Protocol Interaction	139
How Snapshots Interact with Unicode	141
Backing Up Unicode Servers	141
Unicode and Expansion Arrays	143
Backup and Replication Solutions	145
Integrated Backup Solutions for the Snap Server	146
BakBone Netvault	146
Snap Enterprise Data Replicator (Snap EDR)	147
Off-the-Shelf Backup Solutions for the Snap Server	149
Preparing to Install a Backup Solution	149
Preinstallation Tasks	150
Installing the CA BrightStor ARCserve Agent	151
Installing the Symantec Backup Exec RALUS Agent	154
Installing the Symantec NetBackup v6.5 Client	157
Installing the EMC Legato NetWorker Client	159
Command Line Interface	165
SnapCLI Syntax	165
Scripts in SnapCLI	168
Troubleshooting Snap Servers	173
The Meaning of LED Indicators	174
Snap Server 110/210 Status and Drive Light Behavior	174
Snap Server 410 Status and Drive Light Behavior	176
Snap Server 500 Series/600 Series Status and Drive Light Behavior	177
Snap Server 4200/4500 Status and Drive Light Behavior	180
Snap Server 18000 Status and Drive Light Behavior	182
SANbloc S50 Enclosure, Disk Drive, APC Module, and Controller Behavior	185
Snap Disk 10 Disk Drive and Power Supply Module LEDs	188
Snap Disk 30SA Disk Drive and Power/Fan Module Behavior	189
System Reset Options	192
Resetting the Snap Server to Factory Defaults	192
Performing System Resets Without Network Access	193
Networking Issues	194
Miscellaneous Issues	198
Phone Home Support	200
GuardianOS Ports	201
Glossary	207

Match case Limit results 1 per page

Windows ACLs

Chapter 6

Share and File Access

Permissions are enforced for the specified users in the same manner for all client

protocols, including non-SMB clients that normally have the UNIX security

personality. However, if a non-SMB client changes permissions or ownership on a

Windows personality file or directory (or deletes and recreates it), the personality

will change to UNIX with the UNIX permissions specified by the client.

Note

Group membership of NFS clients is established by configuring the local

client’s user account or the NIS domain. Group membership of Snap Server local

users or users ID-mapped to domain users is not observed by NFS clients.

Therefore, ACL permissions applied to groups may not apply as expected to NFS

clients.

Default File and Folder Permissions

When a file or directory is created by an SMB client, the owner of the file will be the

user who created the file (except for files created by local or domain administrators,

in which case the owner will be the “Administrators” group, mapped to the local

admingrp), and the ACL will be inherited per the inheritance ACEs on the parent

directory’s ACL. The owner of a file or directory always implicitly has the ability to

change permissions, regardless of the permissions established in the ACL. In

addition, members of the Snap Server’s local admin group, as well as members of

Domain Admins (if the server is configured to belong to a domain) always

implicitly have

take ownership

and

change ownership

permissions.

Setting File and Directory Access Permissions and Inheritance

(Windows)

Access permissions for files and directories with the Windows security personality

are set using standard Windows NT, 2000, 2003, XP, or Vista security tools.

GuardianOS supports:

•

All standard generic and advanced access permissions that can be assigned by

Windows clients.

•

All levels of inheritance that can be assigned to an ACE in a directory ACL from a

Windows client.

•

Automatic inheritance from parent directories, as well as the ability to disable

automatic inheritance from parents.

•

Special assignment and inheritance of the CREATOR OWNER, CREATOR

GROUP, Users, Authenticated Users, and Administrators built-in users and

groups.