Cluster Server 7.3.1 Administrator's Guide - Linux
- Section I. Clustering concepts and terminology
- Introducing Cluster Server
- About Cluster Server
- About cluster control guidelines
- About the physical components of VCS
- Logical components of VCS
- Types of service groups
- About resource monitoring
- Agent classifications
- About cluster control, communications, and membership
- Components for administering VCS
- About cluster topologies
- VCS configuration concepts
- Introducing Cluster Server
- Section II. Administration - Putting VCS to work
- About the VCS user privilege model
- Administering the cluster from the command line
- About administering VCS from the command line
- About installing a VCS license
- Administering LLT
- Starting VCS
- Stopping the VCS engine and related processes
- Logging on to VCS
- About managing VCS configuration files
- About managing VCS users from the command line
- About querying VCS
- About administering service groups
- Modifying service group attributes
- About administering resources
- Enabling and disabling IMF for agents by using script
- Linking and unlinking resources
- About administering resource types
- About administering clusters
- Configuring applications and resources in VCS
- VCS bundled agents for UNIX
- Configuring NFS service groups
- About NFS
- Configuring NFS service groups
- Sample configurations
- About configuring the RemoteGroup agent
- About configuring Samba service groups
- About testing resource failover by using HA fire drills
- HA and DR configurations using InfoScale Enterprise in AWS
- HA and DR configurations in Azure environment
- Predicting VCS behavior using VCS Simulator
- Section III. VCS communication and operations
- About communications, membership, and data protection in the cluster
- About cluster communications
- About cluster membership
- About membership arbitration
- About membership arbitration components
- About server-based I/O fencing
- About majority-based fencing
- About the CP server service group
- About secure communication between the VCS cluster and CP server
- About data protection
- Examples of VCS operation with I/O fencing
- About cluster membership and data protection without I/O fencing
- Examples of VCS operation without I/O fencing
- Administering I/O fencing
- About the vxfentsthdw utility
- Testing the coordinator disk group using the -c option of vxfentsthdw
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- About administering the coordination point server
- About migrating between disk-based and server-based fencing configurations
- Migrating between fencing configurations using response files
- Controlling VCS behavior
- VCS behavior on resource faults
- About controlling VCS behavior at the service group level
- About AdaptiveHA
- Customized behavior diagrams
- About preventing concurrency violation
- VCS behavior for resources that support the intentional offline functionality
- VCS behavior when a service group is restarted
- About controlling VCS behavior at the resource level
- VCS behavior on loss of storage connectivity
- Service group workload management
- Sample configurations depicting workload management
- The role of service group dependencies
- About communications, membership, and data protection in the cluster
- Section IV. Administration - Beyond the basics
- VCS event notification
- VCS event triggers
- Using event triggers
- List of event triggers
- Virtual Business Services
- Section V. Veritas High Availability Configuration wizard
- Introducing the Veritas High Availability Configuration wizard
- Administering application monitoring from the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Section VI. Cluster configurations for disaster recovery
- Connecting clusters–Creating global clusters
- VCS global clusters: The building blocks
- About global cluster management
- About serialization - The Authority attribute
- Prerequisites for global clusters
- Setting up a global cluster
- About cluster faults
- About setting up a disaster recovery fire drill
- Test scenario for a multi-tiered environment
- Administering global clusters from the command line
- About global querying in a global cluster setup
- Administering clusters in global cluster setup
- Setting up replicated data clusters
- Setting up campus clusters
- Connecting clusters–Creating global clusters
- Section VII. Troubleshooting and performance
- VCS performance considerations
- How cluster components affect performance
- How cluster operations affect performance
- VCS performance consideration when a system panics
- About scheduling class and priority configuration
- VCS agent statistics
- About VCS tunable parameters
- Troubleshooting and recovery for VCS
- VCS message logging
- Gathering VCS information for support analysis
- Troubleshooting the VCS engine
- Troubleshooting Low Latency Transport (LLT)
- Troubleshooting Group Membership Services/Atomic Broadcast (GAB)
- Troubleshooting VCS startup
- Troubleshooting issues with systemd unit service files
- Troubleshooting service groups
- Troubleshooting resources
- Troubleshooting sites
- Troubleshooting I/O fencing
- Fencing startup reports preexisting split-brain
- Troubleshooting CP server
- Troubleshooting server-based fencing on the VCS cluster nodes
- Issues during online migration of coordination points
- Troubleshooting notification
- Troubleshooting and recovery for global clusters
- Troubleshooting licensing
- Licensing error messages
- Troubleshooting secure configurations
- Troubleshooting wizard-based configuration issues
- Troubleshooting issues with the Veritas High Availability view
- VCS message logging
- VCS performance considerations
- Section VIII. Appendixes
DR across AWS regions or VPCs and from on-premises to AWS
InfoScale Enterprise lets you use the global cluster option (GCO) for DR configurations. You can use a DR configuration to fail over applications across different regions or VPCs in AWS. The cluster nodes can be in the same AZ or in different AZs.
The following information is required:
VPN tunnel information between regions or VPCs
The IP address to be used for cross-cluster communication:
Virtual private IP for cluster the nodes that exist in the same subnet
Overlay IP for cluster the nodes that exist in different subnets
You can also use GCO to configure applications for DR from an on-premises site to AWS.
Note:
If you use an Amazon VPN tunnel in a global cluster configuration between an on-premises site and AWS, the cluster nodes in the cloud must be in the same subnet.
The following graphic depicts a sample DR configuration across AWS regions:
The sample configuration includes the following elements:
VPN tunnel between Region A and Region B
The primary site has the following elements:
A virtual private cloud, VPC 1, is configured in Region A of the AWS cloud.
An application is configured for HA using an InfoScale cluster that comprises two nodes, Node 1 and Node 2, which are EC2 instances.
Node 1 exists in Subnet 1 and Node 2 exists in Subnet 2.
The overlay IP allows the private IP of a node to be fail over from one subnet to another in an AZ during failover or failback.
The secondary site has the following elements:
A virtual private cloud, VPC 2, is configured in Region B of the AWS cloud.
The same application is configured for HA on Node 3 and Node 4, which exist in Subnet 3 and Subnet 4 respectively.
The overlay IP allows the private IP of a node to fail over from one subnet to another in an AZ.
The following snippet is a service group configuration from a sample VCS configuration file (main.cf) at the primary site (Region A):
include "types.cf" cluster sitever ( ClusterAddress = "172.32.1.2" SecureClus = 1 ) remotecluster sitecal ( ClusterAddress = "172.35.1.2" ConnectTimeout = 3000 SocketTimeout = 3000 ) heartbeat Icmp ( ClusterList = { sitecal } Arguments @sitecal = { "172.35.1.2" } ) system ip-172-31-21-156 ( ) system ip-172-31-61-106 ( ) group ClusterService ( SystemList = { ip-172-31-21-156 = 0, ip-172-31-61-106 = 1 } AutoStartList = { ip-172-31-21-156, ip-172-31-61-106 } OnlineRetryLimit = 3 OnlineRetryInterval = 120 ) AWSIP Aws_Ipres ( OverlayIP = "172.32.1.2/32" Device = eth0 AWSBinDir = "/usr/local/bin" ) Application wac ( StartProgram = "/opt/VRTSvcs/bin/wacstart -secure" StopProgram = "/opt/VRTSvcs/bin/wacstop" MonitorProcesses = { "/opt/VRTSvcs/bin/wac -secure" } RestartLimit = 3 ) IP Ipres ( Device = eth0 Address = "172.32.1.2" NetMask = "255.255.255.0" ) NIC gconic ( Device = eth0 ) Aws_Ipres requires Ipres Ipres requires gconic wac requires Ipres
The following snippet is a service group configuration from a sample VCS configuration file (main.cf) at the secondary site (Region B):
include "types.cf" cluster sitecal ( ClusterAddress = "172.35.1.2" SecureClus = 1 ) remotecluster sitever ( ClusterAddress = "172.32.1.2" ConnectTimeout = 3000 SocketTimeout = 3000 ) heartbeat Icmp ( ClusterList = { sitever } Arguments @sitever = { "172.32.1.2" } ) system ip-172-34-20-109 ( ) system ip-172-34-30-231 ( ) group ClusterService ( SystemList = { ip-172-34-20-109 = 0, ip-172-34-30-231 = 1 } AutoStartList = { ip-172-34-20-109, ip-172-34-30-231 } OnlineRetryLimit = 3 OnlineRetryInterval = 120 ) AWSIP Aws_Ipres ( OverlayIP = "172.35.1.2/32" Device = eth0 AWSBinDir = "/usr/local/bin" ) Application wac ( StartProgram = "/opt/VRTSvcs/bin/wacstart -secure" StopProgram = "/opt/VRTSvcs/bin/wacstop" MonitorProcesses = { "/opt/VRTSvcs/bin/wac -secure" } RestartLimit = 3 ) IP Ipres ( Device = eth0 Address = "172.35.1.2" NetMask = "255.255.255.0" ) NIC gconic ( Device = eth0 ) Aws_Ipres requires Ipres Ipres requires gconic wac requires Ipres