Cluster Server 7.4 Administrator's Guide - Windows
- 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
- Agent classifications
- About cluster control, communications, and membership
- About cluster topologies
- VCS configuration concepts
- Introducing Cluster Server
- Section II. Administration - Putting VCS to work
- About the VCS user privilege model
- Getting started with VCS
- Administering the cluster from the command line
- About administering VCS from the command line
- Stopping the VCS engine and related processes
- 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
- About administering resource types
- About administering clusters
- Configuring resources and applications in VCS
- About configuring resources and applications
- About Virtual Business Services
- About Intelligent Resource Monitoring (IMF)
- About fast failover
- How VCS monitors storage components
- About storage configuration
- About configuring network resources
- About configuring file shares
- About configuring IIS sites
- About configuring services
- Before you configure a service using the GenericService agent
- About configuring processes
- About configuring Microsoft Message Queuing (MSMQ)
- About configuring the infrastructure and support agents
- About configuring applications using the Application Configuration Wizard
- Adding resources to a service group
- Configuring the service group in a non-shared storage environment
- About the VCS Application Manager utility
- About testing resource failover using virtual fire drills
- HA and DR configurations using InfoScale in AWS
- HA and DR configurations in Azure environment
- Modifying the cluster configuration
- Section III. Administration - Beyond the basics
- Controlling VCS behavior
- VCS behavior on resource faults
- About controlling VCS behavior at the service group level
- Customized behavior diagrams
- VCS behavior for resources that support the intentional offline functionality
- About controlling VCS behavior at the resource level
- Service group workload management
- Sample configurations depicting workload management
- The role of service group dependencies
- VCS event notification
- VCS event triggers
- List of event triggers
- Controlling VCS behavior
- Section IV. 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
- Configuring replication resources in VCS
- About IPv6 support with global clusters
- About cluster faults
- About setting up a disaster recovery fire drill
- Test scenario for a multi-tiered environment
- Administering global clusters from Cluster Manager (Java console)
- 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
- Connecting clusters–Creating global clusters
- Section V. Troubleshooting and performance
- VCS performance considerations
- How cluster components affect performance
- How cluster operations affect performance
- VCS performance consideration when a system panics
- VCS agent statistics
- Troubleshooting and recovery for VCS
- VCS message logging
- Handling network failure
- Troubleshooting VCS startup
- Troubleshooting service groups
- Troubleshooting and recovery for global clusters
- VCS utilities
- VCS performance considerations
- Section VI. Appendixes
- Appendix A. VCS user privileges—administration matrices
- Appendix B. Cluster and system states
- Appendix C. VCS attributes
- Appendix D. Configuring LLT over UDP
- Appendix E. Handling concurrency violation in any-to-any configurations
- Appendix F. Accessibility and VCS
DR from on-premise cluster 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 from on-premise cluster to AWS.
The following information is required:
VPN tunnel information between regions or VPCs
The Virtual private IP address to be used for cross-cluster communication.
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 from on-premise cluster to AWS cloud:
The sample configuration includes the following elements:
VPN tunnel between on-premise data center and Region A
The primary site has the following elements:
Cluster nodes in the same subnet
Virtual private IP for cross-cluster communication
The secondary site has the following elements:
A virtual private cloud, VPC, is configured in Region Aof the AWS cloud
The same application is configured for HA on Node 3 and Node 4, which exist in the same subnet
The following snippet is a service group configuration from a sample VCS configuration file (main.cf) for a single node:
include "types.cf" cluster vvr_aws ( ClusterAddress = "10.239.3.96" SecureClus = 1 ) remotecluster vvr_cloud ( ClusterAddress = "10.209.57.98" ConnectTimeout = 30000 SocketTimeout = 30000 ) heartbeat Icmp ( ClusterList = { vvr_cloud } AYARetryLimit = 10 Arguments @vvr_cloud = { "10.209.57.98" } ) system WIN-38PNEVJSR2K ( ) group ClusterService ( SystemList = { WIN-38PNEVJSR2K = 0 } AutoStartList = { WIN-38PNEVJSR2K } ) AWSIP gcoawsip ( PrivateIP = "10.239.3.96" Device = 12-7F-CE-5B-E2-6E ) IP csg_ip ( Address = "10.239.3.96" SubNetMask = "255.255.254.0" MACAddress @WIN-38PNEVJSR2K = "12:7F:CE:5B:E2:6E" ) NIC csg_nic ( MACAddress @WIN-38PNEVJSR2K = "12:7F:CE:5B:E2:6E" ) Process wac ( StartProgram @WIN-38PNEVJSR2K = "\"C:\\Program Files\\ Veritas\\Cluster Server\\bin\\wac.exe\"" StopProgram @WIN-38PNEVJSR2K = "\"C:\\Program Files\\ Veritas\\Cluster Server\\bin\\wacstop.exe\"" MonitorProgram @WIN-38PNEVJSR2K = "\"C:\\Program Files\\ Veritas\\Cluster Server\\bin\\wacmonitor.exe\"" ) csg_ip requires csg_nic wac requires gcoawsip wac requires csg_ip group fileshare ( SystemList = { WIN-38PNEVJSR2K = 0 } ClusterList = { vvr_cloud = 1, vvr_aws = 0 } Authority = 1 ClusterFailOverPolicy = Auto ) AWSIP vvrawsip ( PrivateIP = "10.239.3.97" Device @WIN-38PNEVJSR2K = 12-7F-CE-5B-E2-6E ) FileShare fileshare-FileShare ( PathName = "\\" ShareName = testshare LanmanResName = fileshare-Lanman MountResName = mounvres UserPermissions = { Everyone = FULL_CONTROL } ) IP fileshare-IP ( Address = "10.239.3.97" SubNetMask = "255.255.254.0" MACAddress @WIN-38PNEVJSR2K = 12-7F-CE-5B-E2-6E ) Lanman fileshare-Lanman ( VirtualName = FILESHARE-DHAWA IPResName = fileshare-IP ) MountV mounvres ( MountPath = "e:" VolumeName = datavol VMDGResName = vmnsdg ) NIC fileshare_NIC ( MACAddress @WIN-38PNEVJSR2K = "12:7F:CE:5B:E2:6E" ) RVGPrimary rvgprimary_1 ( RvgResourceName = vvrsg-VvrRvg AutoResync = 1 ) requires group vvrsg online local hard vvrawsip requires fileshare_NIC fileshare-FileShare requires mounvres fileshare-FileShare requires fileshare-Lanman fileshare-IP requires vvrawsip fileshare-Lanman requires fileshare-IP mounvres requires rvgprimary_1 group vvrsg ( SystemList = { WIN-38PNEVJSR2K = 0 } AutoStartList = { WIN-38PNEVJSR2K } ) Proxy proxy_ip ( TargetResName = csg_ip ) Proxy proxy_nic ( TargetResName = csg_nic ) VMNSDg vmnsdg ( DiskGroupName = vvrdg DGGuid = 03d725b1-fca3-49b2-b722-38984835e6b0 ) VvrRvg vvrsg-VvrRvg ( RVG = rvg VMDgResName = vmnsdg IPResName = proxy_ip ) vvrsg-VvrRvg requires proxy_nic vvrsg-VvrRvg requires proxy_ip vvrsg-VvrRvg requires vmnsdg