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
Configuring disk-based I/O fencing
To use the disk-based I/O fencing feature, the minimum configuration must be a two-node cluster with Veritas Access software installed and more than three disks. Three disks are used as coordinator disks and the rest of the disks are used for storing data.
Enabling I/O fencing configures disk-based fencing if shared disks are present.
Note:
Enabling I/O fencing causes a disruption of Veritas Access services. When I/O fencing is enabled, some services such as NFS shares, CIFS shares, and S3 shares have to be stopped as the process of enabling 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 I/O fencing, and then resume Veritas Access services.
To configure I/O fencing
- To check the status of I/O fencing, enter the following:
Storage> fencing status
In the following example, I/O fencing is configured on the three disks Disk_0,Disk_1 and Disk_2 and the column header Coord Flag On indicates that these disks are in good condition. If you check the Storage> disk list output, it will be in the OK state.
- If there are not three coordinator disks, you must add coordinator disks. You can add disks and enable fencing at the same time with the following command:
Storage> fencing on disk disk1,disk2,disk3
You may still provide three disks for fencing if three coordinator disks already exist. This will, however, remove the three coordinator disks previously used for fencing, and configure I/O fencing on the new disks.