Veritas Access Appliance 8.2 Administrator's Guide
- Section I. Introducing Access Appliance
- Section II. Configuring Access Appliance
- Managing users
- Managing licenses
- 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
- Using Access Appliance as an Object Store server
- Configuring the S3 server using GUI
- Configuring the NFS server
- Section V. Managing Access Appliance security
- Managing security
- Setting up FIPS mode
- Configuring STIG
- Setting the banner
- Setting the password policy
- Immutability in Access Appliance
- Deploying certificates on Access Appliance
- Single Sign-On (SSO)
- Configuring multifactor authentication
- Section VI. Monitoring and troubleshooting
- Monitoring the appliance
- Configuring event notifications and audit logs
- About alert management
- Appliance log files
- 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
- Configuring an episodic replication job using the GUI
- Episodic replication job failover and failback
- Configuring continuous replication
- How Access Appliance continuous replication works
- Configuring a continuous replication job using the GUI
- Continuous replication failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring episodic replication
- Section X. Reference
About configuring Access Appliance for CIFS
The Common Internet File System (CIFS), also known as the Server Message Block (SMB) protocol, is a network file sharing protocol that is widely used on Microsoft and other operating systems. Access Appliance supports the SMB3 protocol.
Access Appliance supports the following clustering modes:
Normal
Clustered Trivial Database (CTDB) - a cluster implementation of the TDB (Trivial database) based on the Berkeley database API
Note:
In case of network or node failover, the application which performs the I/O operation on the CIFS share needs to have a retry logic for a failed I/O to survive from an I/O failure.
Access Appliance supports the ADS CIFS security mode. All the clustering modes support the ADS CIFS security mode.
See About CIFS clustering modes.
Access Appliance can be integrated into a network that consists of machines running Microsoft Windows. You can control and manage the network resources by using Active Directory (AD) domain controllers.
Before you use Access Appliance with CIFS, you must have administrator-level knowledge of the Microsoft operating systems, Microsoft services, and Microsoft protocols (including AD and NT services and protocols).
You can find more information about them at: www.microsoft.com.
Note:
The IPs used by CIFS server should be different from the virtual IP used by the Veritas Data Deduplication server.
When serving the CIFS clients, Access Appliance can be configured to operate in one of the security mode environments described in Table: CIFS security mode environments.
Table: CIFS security mode environments
Mode | Definition |
---|---|
Active Directory (AD) | Access Appliance becomes a member of an AD security domain and is configured to use the services of the AD domain controller, such as DNS, LDAP, and NTP. Kerberos, NTLMv2, or NTLM authenticate users. When Access Appliance operates in the AD domain mode, it acts as a domain member server and not as the domain controller. |
Configuring CIFS as a standalone server is not supported in this release. Before upgrade, you must convert the CIFS server type from standalone to domain member and then try upgrade. Else, the upgrade pre-check fails. Even if the upgrade to completed successfully, the CIFS shares are inaccessible after upgrade.
Upgrade considerations
If CIFS is configured as domain member server in CTDB clustering mode, you are not required to make any changes. During upgrade, the CIFS services is brought offline and when upgrade completes, the CIFS services is brought online. This is required since Samba does not support rolling upgrade of CTDB for major version change. After upgrade, use the FQDN instead of the virtual IP address to perform the necessary steps to mount the shares.
If CIFS is configured as domain member server in normal clustering mode, the upgrade is completed successfully and the CIFS- related VCS group come online. However, as the shares use the virtual IP address for msdfs path, the share access after upgrade fails. Hence, you have to delete the shares that are already present and then, add them back. When you add the shares again, use the FQDN instead of the IP address of the virtual IPs.
You also have to perform the following steps:
For DNS server:
Add SPN entry for all the server IPs on AD server. SPNs are used by Kerberos authentication to associate a service instance with a service logon account.
For non-DNS server:
Add FQDN entry for the virtual IP addresses using the Access CLISH using the network host add ipaddr fqdn command.
Add FQDN entry in the
/etc/hosts
file for all the virtual IP addresses on the Windows client.Add SPN entry for all the virtual IP addresses on the Windows client.