In this short video, you will learn how to ensure the resilience of Veritas Clusters by using AvailabilityGuard. As part of its nightly process, AvailabilityGuard collects the configuration of VCS clusters, disk arrays, and more. This configuration data is analyzed to identify issues that can cause Veritas Cluster Server outages, failover or switchover problems, and other VCS issues.
Veritas Cluster Server (VCS) Failover Issue
One of the examples featured in this video showcases a two-node, active-passive VCS cluster. The active node is correctly mapped to the NetApp LUN, but the passive node is not. The affected service group and its resources will not be able to failover successfully. Thus, if the active node goes down, the cluster users will experience a serious outage.
Veritas Cluster Server (VCS): Additional Risks
AvailablityGuard’s risk-detection engine checks for a large number of Veritas Cluster Server misconfigurations and issues that are beyond the scope of this introductory video. These include: missing mount points, resource dependency correctness, service group and resource states, I/O fencing and heartbeat best practices, GCO validation (communication, replication agents, storage device groups and more), recommendations for specific VCS resources (LVMVG, Mount, IP, NIC, NFSV4, DNS and more), campus cluster mirroring guidelines, Storage Foundation best practices (vxvm, vxfs, vxdmp and more).
VCS Global Cluster Option (GCO)
The examples in this video do not cover the VCS Global Cluster Option (GCO). However, detection of errors and misconfigurations in the GCO environment are supported by AvailablityGuard.