Veritas Access Administrator's Guide
- Section I. Introducing Veritas Access
- Section II. Configuring Veritas Access
- Adding users or roles
- Configuring the network
- Configuring authentication services
- Section III. Managing Veritas Access storage
- Configuring storage
- Configuring data integrity with I/O fencing
- Configuring ISCSI
- Veritas Access as an iSCSI target
- Configuring storage
- Section IV. Managing Veritas Access file access services
- Configuring your NFS server
- Setting up Kerberos authentication for NFS clients
- Using Veritas Access as a CIFS server
- About Active Directory (AD)
- 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
- Configuring Veritas Access to work with Oracle Direct NFS
- Configuring an FTP server
- Configuring your NFS server
- Section V. Managing the Veritas Access Object Store server
- Section VI. Monitoring and troubleshooting
- Section VII. Provisioning and managing Veritas Access file systems
- Creating and maintaining file systems
- Considerations for creating a file system
- Modifying a file system
- Managing a file system
- Creating and maintaining file systems
- Section VIII. Configuring cloud storage
- Section IX. Provisioning and managing Veritas Access shares
- Creating shares for applications
- Creating and maintaining NFS shares
- Creating and maintaining CIFS shares
- Using Veritas Access with OpenStack
- Section X. Managing Veritas Access storage services
- Deduplicating data
- Compressing files
- About compressing files
- Compression tasks
- Configuring SmartTier
- Configuring SmartIO
- Configuring episodic replication
- Episodic replication job failover and failback
- Configuring continuous replication
- How Veritas Access continuous replication works
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring Veritas Access with the NetBackup client
- Section XI. Reference
Allowing trusted domains access to CIFS when setting an IDMAP backend to hash
To allow trusted domains access to CIFS when setting an IDMAP backend to hash
- If the CIFS server is running, enter the following:
CIFS> server stop
- To set idmap_backend to hash, enter the following:
CIFS> set idmap_backend hash
You can obtain unique user IDs (UIDs) or group IDs (GIDs) from domains by reading ID mappings from an Active Directory server that uses RFC2307/SFU schema extensions. This is a read-only idmap backend. Trusted domains are allowed if set allow_trusted_domains is set to yes. A valid user from a domain or trusted domain should have a UID as well as a GID for the user's primary group.
By default, the uid_range is set to 10000-1000000. Change it in cases where there are more than 1,000,000 users existing on a local Veritas Access cluster where there are joined Active Directory domains or trusted domains.
Note:
The uid_range is adjusted automatically according to the search results of the defined UNIX IDs from the domain after a CIFS server restart.
- To set allow_trusted_domains to yes, enter the following:
CIFS> set allow_trusted_domains yes
- To verify the CIFS server status when there are trusted domains, enter the following:
CIFS> server status