Please enter search query.
Search <book_title>...
Veritas Access Administrator's Guide
Last Published:
2021-04-15
Product(s):
Appliances (Version Not Specified)
Platform: 3340
- 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
Manually enabling and disabling majority fencing in a non-SSH environment
Enabling majority fencing in a non-SSH environment
The Storage> fencing on majority command is disabled in a non-SSH environment.
To enable majority fencing in a non-SSH environment
- Verify that fencing is not enabled.
# vxfenadm -d
- Copy
/etc/vxfen.d/vxfenmode_majority
to/etc/vxfenmode
.# cat /etc/vxfenmode # # vxfen_mode determines in what mode VCS I/O Fencing should work. # # available options: # scsi3 - use scsi3 persistent reservation disks # customized - use script based customized fencing # majority - use majority based fencing # disabled - run the driver but don't do any actual fencing # vxfen_mode=majority
- Set the MAJORITY string in
/opt/VRTSnas/conf/fencing_type
.# cat /opt/VRTSnas/conf/fencing_type MAJORITY
- Stop HAD on all the nodes.
# hastop -all
- Update the
/etc/VRTSvcs/con/config/main.cf
file to add the UseFence=SCSI3 attribute.# cat main.cf .... include "types.cf" include "CFSTypes.cf" include "CVMTypes.cf" include "SNASTypes.cf" cluster vacluster ( UserNames = { admin = eHIaHChEIdIIgQIcHF } ResourceLimit = 10000 GroupLimit = 1000 Administrators = { admin } HacliUserLevel = COMMANDROOT UseFence = SCSI3 ) ....
- Copy the
main.cf
file to all the cluster nodes. - Restart the fencing driver on all cluster nodes.
# service vxfen stop # service vxfen start
- Start HAD on all the cluster nodes.
# hastart
- Once HAD is up, verify that fencing is configured.
# vxfenadm -d Storage> fencing status
Disabling majority fencing in a non-SSH environment
The Storage> fencing off is disabled in a non-SSH environment.
To disable majority fencing in a non-SSH environment
- Stop HAD on all the nodes.
# hastop -all
- Stop the fencing driver on all the nodes.
# service vxfen stop
- Copy
/etc/vxfen.d/vxfenmode_disable
to/etc/vxfenmode
.# cat /etc/vxfenmode # # # vxfen_mode determines in what mode VCS I/O Fencing should work. # # available options: # scsi3 - use scsi3 persistent reservation disks # customized - use script based customized fencing # majority - use majority based fencing # disabled - run the driver but don't do any actual fencing # vxfen_mode=disabled
- Update the
/opt/VRTSnas/conf/fencing_type
to blank. - Update the
/etc/VRTSvcs/con/config/main.cf
file to remove the UseFence attribute.# cat main.cf .... include "types.cf" include "CFSTypes.cf" include "CVMTypes.cf" include "SNASTypes.cf" cluster vacluster ( UserNames = { admin = eHIaHChEIdIIgQIcHF } ResourceLimit = 10000 GroupLimit = 1000 Administrators = { admin } HacliUserLevel = COMMANDROOT ) ....
- Copy the
main.cf
file to all the cluster nodes. - Start the fencing driver on all cluster nodes.
# service vxfen start
- Start HAD on all the cluster nodes.
# hastart