Veritas Access Appliance Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Configuring the network
- Configuring authentication services
- Configuring user authentication using digital certificates or smart cards
- Section III. Managing Access Appliance storage
- Configuring storage
- Managing disks
- Access Appliance as an iSCSI target
- Configuring storage
- Section IV. Managing Access Appliance file access services
- Configuring the NFS server
- Setting up Kerberos authentication for NFS clients
- Using Access Appliance as a CIFS server
- About configuring CIFS for Active Directory (AD) domain mode
- About setting trusted domains
- About managing home directories
- About CIFS clustering modes
- About migrating CIFS shares and home directories
- About managing local users and groups
- Using Access Appliance as an Object Store server
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Section VI. Monitoring and troubleshooting
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- Configuring event notifications and audit logs
- Section VII. Provisioning and managing Access Appliance file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- About managing application I/O workloads using maximum IOPS settings
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Provisioning and managing Access Appliance shares
- Creating shares for applications
- Creating and maintaining NFS shares
- About the NFS shares
- Creating and maintaining CIFS shares
- About the CIFS shares
- About managing CIFS shares for Enterprise Vault
- Integrating Access Appliance with Data Insight
- Section IX. Managing Access Appliance storage services
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Access Appliance continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring episodic replication
- Section X. Reference
About mapping user names for CIFS/NFS sharing
The CIFS server uses user name mapping to translate login names sent by a Windows client to local or remote UNIX user names. The CIFS server uses file lookup for mapping, and this mapping is unidirectional. You can map a CIFS user to an NFS user, but the reverse operation is not possible.
This functionality can be used for the following purposes:
CIFS and NFS sharing by mapping CIFS users to NFS users
File sharing among CIFS users by mapping multiple CIFS users to a single UNIX user
Mapping between two UNIX users by using the CIFS> mapuser add <CIFSusername> LOCAL <NFSusername> command, where both the CIFS user and the NFS user are UNIX users
User name mapping is stored in a configuration file.
When user name mapping takes place, it is dependent on the current security configurations. If security is set to user, mapping is done prior to authentication, and a password must be provided for the mapped user name. For example, if there is a mapping between the users CIFSuser1 and NFSuser1. If CIFSuser1 wants to connect to the Access Appliance server, then CIFSuser1 needs to provide a password for NFSuser1. In this case, NFSuser1 must be the CIFS local user.
If security is set to ads, user name mapping is done after authentication with the domain controller. This means, the actual password must be supplied for the login user CIFSuser1 in the example cited above. In this case, NFSuser1 may not be the CIFS local user.
The domain you specify for CIFS user name mapping must be the netbios domain name (instead of the Active Directory DNS domain name) for the user. For example, a netbios domain name might be listed as VERITASDOMAIN instead of VERITASDOMAIN.COM (without the .com extension).
To determine the netbios domain name, login to your Active Directory Server and type the following in a command window:
set | findstr DOMAIN
The results will include:
USERDOMAIN netbios_domain_name USERDNSDOMAIN Active_Directory_DNS_domain_name
Use the value of USERDOMAIN (the netbios domain name) when you map user names.
Note:
When setting quotas on home directories and using user name mapping, make sure to set the quota on the home directory using the user name to which the original name is mapped.
Note:
For mapped Active Directory users to access their home directory CIFS shares, use the following convention: \\access\realADuser
instead of \\access\homes
.
Note:
For UNIX users (LDAP/NIS/local) users, make sure to set up these users properly, so that these users are recognized by Samba. User mapping can work properly only after these users are recognized by Samba.