Chat now with support
Chat mit Support

DR Series Software 4.0.0.3 - Administration Guide

Introducing the DR Series system documentation Introducing the DR Series system Setting up the DR Series system Configuring the DR Series system settings Managing containers Managing replications Monitoring the DR Series system Using GlobalView Configuring and using Rapid NFS and Rapid CIFS Configuring and using Rapid Data Access with NetVault Backup and with vRanger Configuring and using RDA with OST
Understanding RDA with OST Guidelines Terminology Supported RDA with OST software and components Best Practices: RDA with OST and the DR Series System Setting client-side optimization Configuring an LSU Installing the RDA with OST plug-in Configuring DR Series system information using NetBackup Backing Up Data From a DR Series System (NetBackup) Using Backup Exec with a DR Series system (Windows) Understanding the OST CLI commands Understanding RDA with OST Plug-In Diagnostic Logs Collecting Diagnostics Using a Linux Utility Guidelines for Gathering Media Server Information
Configuring and using VTL Configuring and Using Encryption at Rest Support, maintenance, and troubleshooting Supported Ports in a DR Series System

Access control list support in containers

Access control list support in containers

All new containers apply a default Access Control List (ACL) at the root of the container. This default ACL is the same as that which would be created by a Microsoft Windows 2003 Server. Therefore, these new containers with the default ACL support the following permission types:

 
NOTE: Any user that is part of BUILTIN\Administrators can edit ACLs on CIFS shares. The local DR Series system administrator is included in the BUILTIN\Administrators group. To add additional domain groups to the BUILTIN\Administrators group, you can use the Computer Manager tool on a Windows client to connect to the DR Series system as Domain administrator and add any groups you want. This capability allows users other than the Domain administrator to modify an ACL as needed.
•
BUILTIN\Administrators:
Allows
Full access, object inherit, and container inherit.
Applies to
This folder, subfolders, and files.
•
CREATOR OWNER:
Allows
Full access, inherit only, object inherit, and container inherit.
Applies to
Subfolders and files only.
•
EVERYONE:
Allows
Traverse folders, execute files, list folders, read data, read attributes, and read extended attributes.
Applies to
This folder only.
•
NT AUTHORITY\SYSTEM:
Allows
Full access, object inherit, and container inherit.
Applies to
This folder, subfolders, and files.
•
BUILTIN\Users:
Allows
Create folders and append data, inherit-only, and container inherit.
Applies to
This folder, subfolders, and files.
•
BUILTIN\Users:
Allows
Read and execute, and container inherit.
Applies to
This folder, subfolders, and files.
•
BUILTIN\Users:
Allows
Create files and write data, object inherit, and container inherit.
Applies to
Subfolders only.
 
NOTE: If these permissions are unsuitable for your needs, you can modify the default ACL to suit your own requirement using the Windows ACL Editor (for example, using Properties → Security from Windows Explorer).
 
NOTE: The system does not understand the Owner Rights permission and sets the owner of new files/folders created by the Domain Administrators as DOM\Administrator rather than as BUILTIN\Administrators.
Parent topic 

Unix permissions guidelines

Unix permissions guidelines

For a user to create, delete, or rename a file or a directory requires Write access to the parent directory that contains these files. Only the owner of a file (or the root user) can change permissions.

Permissions are based on the user IDs (UIDs) for the file Owner and group IDs (GIDs) for the primary group. Files have owner IDs and group owner IDs. To enable Unix access, the DR Series system supports three levels of users:

•
Owner (of the file)
•
Group (group in which the owner belongs)
•
Other (other users with an account on the system)

Each of these three user types support the following access permissions:

•
Read (read access that allows user to read files)
•
Write (write access that allows user to create or write to a file)
•
Execute (access that allows user to execute files or traverse directories in the filesystem)
 
NOTE: A root user has all levels of permission access, and a user can be a member of a single group or of multiple groups (up to 32 groups are allowed in Unix).
Parent topic 

Windows permissions guidelines

Windows permissions guidelines

To enable Windows access, the DR Series system supports access control lists (ACLs) that contain zero or more access control entries (ACEs), and an empty ACE list grants all access requests. The Windows New Technology File System (NTFS) uses ACLs as part of the security descriptor (SD) process, which requires permissions to access such filesystem objects as files and directories. ACLs support two levels of users:

•
Owners
•
Groups

Both Owners and Groups have Security IDs (SIDs) that define and identify an object owner or the group owning an object. ACEs in an ACL consist of a SID, a specific permission that either allows or denies access and also defines which of the following inheritance settings apply:

•
IO—inherit-only: not used for access checking.
•
OI—object inherit: new files get this ACE added.
•
CI—container inherit: new directories get this ACE added.

Windows NTFS ACLs include the following read, write, append, execute, and delete permissions that allow users to:

•
Synchronize access
•
Read data or list the directory
•
Write data or add a file
•
Append data or add a folder
•
Read Extended Attributes (EAs)
•
Write EAs
•
Execute file or traverse folders
•
Delete child or delete folders
•
Delete a file

The Owner user type has two default permissions:

•
Write discretionary ACL
•
Read control
Parent topic 

Rapid NFS and Rapid CIFS

Rapid NFS and Rapid CIFS

Rapid NFS and Rapid CIFS enable write operation acceleration on clients that use DR replication and NFS or CIFS file system protocols. Similar to OST and RDS, these accelerators allow for better coordination and integration between DR Series system backup, restore, and optimized deduplication operations with Data Management Applications (DMAs) such as CommVault, EMC Networker, and Tivoli Storage Manager. For the current list of qualified DMAs, see the DR Series System Interoperability Guide.

Rapid NFS is a new client file system type that ensures that only unique data is written to the DR Series system. It uses user space components and file system in user space (FUSE) to accomplish this. Metadata operations such as file creates and permission changes go through the standard NFS protocol, whereas write operations go through RDNFS.

Rapid CIFS is a Windows-certified filter driver that also ensures that only unique data is written to the DR Series system.

All chunking and hash computations are done at the media or client server level.

Rapid NFS and Rapid CIFS require you to install a plug-in on the client or media server, depending on your DMA and configuration. For details, see the Configuring and Using Rapid NFS and Rapid CIFS chapter.

Parent topic 
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen