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
Joining Veritas Access to Active Directory (AD)
To join Veritas Access to Active Directory (AD)
- To stop the CIFS server, enter the following command.
CIFS> server stop
- To set the domain, enter the following command:
CIFS> set domain accesstest-ad2.local
In this example, it is the same as the DNS domain name.
This is the domain name of Active Directory.
- To set the domain controller, enter the following command:
CIFS> set domaincontroller <IP address>
The IP address can be the IP address of the Active Directory Domain Controller. The DNS server and Active Directory can run on different servers, and hence this IP address may be different from the IP address of the DNS server.
- To set the domain user, enter the following command:
CIFS> set domainuser newuser
This is a user whose credentials are used to join the Active Directory domain. The domainuser must have Domain Join privilege into the Active Directory domain. The domainuser need not be Administrator.
- To set the CIFS security mode, enter the following command:
CIFS> set security ads
The other CIFS security mode is user for local users. For authenticating to Active Directory, use the ads CIFS security mode.
- To start the CIFS server, enter the following command:
CIFS> server start
Veritas Access displays the time on the cluster as well as the time on the Active Directory Domain Controller.
If NTP has been configured correctly, then there will be no time skew.
Otherwise, you will need to reconfigure NTP correctly.
You will be prompted to enter the password of domainuser.
- To set the workgroup name if the WORKGROUP or NetBIOS domain name is different from the domain name, enter the following:
CIFS> set workgroup workgroup
where
workgroup
sets the WORKGROUP name. If the name of the WORKGROUP or NetBIOS domain name is different from the domain name, use this command to set the WORKGROUP name.For example, if SIMPLE is the name of the WORKGROUP you want to set, you would enter the following:
CIFS> set workgroup SIMPLE
Though the following symbols $,( ), ', and & are valid characters for naming a WORKGROUP, the Veritas Access CIFS implementation does not allow using these symbols.