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
Using majority-based fencing
For Flexible Storage Sharing (FSS), only majority-based fencing is supported. Majority-based fencing does not require configuring a coordinator pool or coordinator disks. Enabling I/O fencing configures majority-based fencing if no shared disks are present.
Note:
Enabling or disabling I/O fencing causes a disruption of Veritas Access services. When I/O fencing is enabled or disabled, some services such as NFS shares, CIFS shares, and S3 shares have to be stopped as the process of enabling or disabling fencing halts the VCS and cluster services. If any I/O is going on, then the cluster cannot be stopped. Veritas suggests that you bring down the Veritas Access services, enable or disable I/O fencing, and then resume Veritas Access services.
To check the status of I/O fencing
- Check the status of I/O fencing while I/O fencing is not enabled.
Storage> fencing status
To enable majority-based fencing
- Enable majority-based I/O fencing.
Storage> fencing on majority
- Check the status of I/O fencing after enabling I/O fencing.
Storage> fencing status
To disable majority-based I/O fencing
- Disable majority-based I/O fencing.
Storage> fencing off