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
Exporting the same file system/directory as a different CIFS share
In ctdb clustering mode, you can export the same file system or directory as a different CIFS share with different available CIFS options. This features allows you more granular control over CIFS shares for different sets of users.
If the same file system is exported as different shares in ctdb clustering mode, then after switching to normal clustering mode only one share out of these is available.
Note:
If the same file system or directory is exported as different shares, then the fs_mode value is the same for all of these shares; that is, the last modified fs_mode value is applicable for all of those shares. This applies to fs_mode, owner, and group.
Note:
This feature is only supported in the ctdb clustering mode.
To export a directory with read access to everyone, but write access to the limited set of users who need to be authenticated
- To export a directory with read access to everyone, but write access to the limited set of users who need to be authenticated, enter the following:
CIFS> share add "fs1/Veritas isa" share1 rw,noguest CIFS> share add "fs1/Veritas isa" share2 ro,guest CIFS> share show
The above example illustrates that the same directory is exported as a different CIFS share for guest and noquest users with different sets of permissions.