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 the 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 an FTP server
- Using Veritas Access as an Object Store server
- Configuring the NFS server
- Section V. Monitoring and troubleshooting
- Section VI. 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 VII. Configuring cloud storage
- Section VIII. 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
- Integrating Veritas Access with Data Insight
- Section IX. Managing Veritas Access storage services
- 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
- Compressing files
- Section X. Reference
Storing user and group accounts
To set idmap_backend to rid
- If the server is running, enter the following:
CIFS> server stop
- To store information about user and group accounts locally, enter the following:
CIFS> set idmap_backend rid [uid_range]
where uid_range represents the range of identifiers that are used by Veritas Access when mapping domain users and groups to local users and groups. The default range is 10000-1000000.
- To start the CIFS server, enter the following:
CIFS> server start
To set idmap_backend to LDAP
- To make sure that you have first configured LDAP, enter the following:
Network> ldap show
- If the CIFS server is running, enter the following:
CIFS> server stop
- To use the remote LDAP store for information about the user and group accounts, enter the following:
CIFS> set idmap_backend ldap [idmap_ou]
where idmap_ou represents the CIFS idmap Organizational Unit Name (OU) configured on the LDAP server, which is used by Veritas Access when mapping users and groups to local users and groups. The default value is cifsidmap.
- To start the CIFS server, enter the following:
CIFS> server start
To set idmap_backend to a hash algorithm
- If the CIFS server is running, enter the following:
CIFS> server stop
- To store information about user and group accounts locally, enter the following:
CIFS> set idmap_backend hash
- To start the CIFS server, enter the following:
CIFS> server start
To set idmap_backend to ad
- If the CIFS server is running, enter the following:
CIFS> server stop
- To obtain the unique UID/GID from domains by reading ID mappings from an Active Directory (AD) server, enter the following:
CIFS> set idmap_backend ad [uid_range]
where uid_range represents the range of identifiers that are used by Veritas Access when mapping domain users and groups to local users and groups. The default range is 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 start the CIFS server, enter the following:
CIFS> server start