Veritas Access 7.3.0.1 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
- 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
- About scale-out 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
- Configuring the cloud gateway
- Configuring cloud as a tier
- About policies for scale-out file systems
- 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 replication
- Replication job failover and failback
- Using snapshots
- Using instant rollbacks
- Configuring Veritas Access with the NetBackup client
- Section XI. Reference
Creating CIFS shares for a scale-out file system
Veritas Access provides support for creating CIFS shares for a scale-out file system. Unlike a standard clustered file system, a scale-out file system can scale linearly and you can grow the file system up to 3 PB.
See About scale-out file systems.
The CIFS integration with scale-out file system works in the same manner as the standard clustered file system except for the following differences:
In a standard clustered file system, the load for a CIFS share is distributed across virtual IPs hosted on different nodes by using the DFS referral. But the scale-out file system works in active/passive mode. Hence, irrespective of the virtual IP from which the request comes, it is always served from the virtual IP to which the scale-out file system is attached. You are not required to configure the system in any way for this functionality.
A scale-out file system is a stitched file system. It is built on top of multiple file systems. The additional layering has an effect on performance.
The exact numbers are available at reference architecture.
The following limitations apply when you create a CIFS share for a scale-out file system:
In CTDB mode:
As the scale-out file system is in active/passive mode, the CTDB mode does not have any advantage over the normal clustering mode.
If the CIFS server is in normal mode, you can add shares to both clustered file system and scale-out file system.
If the CIFS server is in CTDB mode, you can add shares to clustered file system but you cannot add shares to a scale-out file system.
If clustered filed system shares as well as scale-out file system shares exist, you cannot switch the CIFS server from normal mode to CTDB mode.
When setting the home directory file systems:
You cannot have a home directory file system which is a combination of scale-out file system and clustered file system.
You can set multiple clustered file systems as a home directory file system.
When setting quotas:
The CIFS> homedir set command is usually used along with the Storage> quota functionality. Since a scale-out file system does not support quota, a CIFS home directory which is based on a scale-out file system does not have the quota functionality.