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
- About resources and resource dependencies
- Categories of resources
- About resource types
- About service groups
- Types of service groups
- About the ClusterService group
- About agents in VCS
- About agent functions
- Agent classifications
- VCS agent framework
- About cluster control, communications, and membership
- About security services
- Components for administering VCS
- Putting the pieces together
- 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
- Starting VCS
- 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
- Adding and deleting service groups
- Modifying service group attributes
- Bringing service groups online
- Taking service groups offline
- Switching service groups
- Freezing and unfreezing service groups
- Enabling and disabling priority based failover for a service group
- Enabling and disabling service groups
- Clearing faulted resources in a service group
- Linking and unlinking service groups
- Administering agents
- About administering resources
- About administering resource types
- Administering systems
- About administering clusters
- Using the -wait option in scripts that use VCS commands
- About administering simulated clusters from the command line
- 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
- Shared storage - if you use NetApp filers
- Shared storage - if you use SFW to manage cluster dynamic disk groups
- Shared storage - if you use Windows LDM to manage shared disks
- Non-shared storage - if you use SFW to manage dynamic disk groups
- Non-shared storage - if you use Windows LDM to manage local disks
- Non-shared storage - if you use VMware storage
- About storage configuration
- About configuring network resources
- About configuring file shares
- Before you configure a file share service group
- Configuring file shares using the wizard
- Modifying a file share service group using the wizard
- Deleting a file share service group using the wizard
- Creating non-scoped file shares configured with VCS
- Making non-scoped file shares accessible while using virtual server name or IP address if NetBIOS and WINS are disabled
- About configuring IIS sites
- About configuring services
- About configuring a service using the GenericService agent
- Before you configure a service using the GenericService agent
- Configuring a service using the GenericService agent
- About configuring a service using the ServiceMonitor agent
- Before you configure a service using the ServiceMonitor agent
- Configuring a service using the ServiceMonitor agent
- About configuring processes
- About configuring Microsoft Message Queuing (MSMQ)
- Before you configure the MSMQ service group
- Configuring the MSMQ resource using the command-line utility
- Configuring the MSMQ service group using the wizard
- Modifying an MSMQ service group using the wizard
- Configuring MSMQ agent to check port bindings more than once
- Binding an MSMQ instance to the correct IP address
- Checking whether MSMQ is listening for messages
- About configuring the infrastructure and support agents
- About configuring applications using the Application Configuration Wizard
- Before you configure service groups using the Application Configuration wizard
- Adding resources to a service group
- Configuring service groups using the Application Configuration Wizard
- Modifying an application service group
- Deleting resources from a service group
- Deleting an application 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
- About the AutoRestart attribute
- About controlling failover on service group or system faults
- About defining failover policies
- About system zones
- Load-based autostart
- About freezing service groups
- About controlling Clean behavior on resource faults
- Clearing resources in the ADMIN_WAIT state
- About controlling fault propagation
- Customized behavior diagrams
- VCS behavior for resources that support the intentional offline functionality
- About controlling VCS behavior at the resource level
- Changing agent file paths and binaries
- Service group workload management
- Sample configurations depicting workload management
- The role of service group dependencies
- VCS event notification
- VCS event triggers
- About VCS event triggers
- Using event triggers
- List of event triggers
- About the dumptunables trigger
- About the injeopardy event trigger
- About the loadwarning event trigger
- About the nofailover event trigger
- About the postoffline event trigger
- About the postonline event trigger
- About the preonline event trigger
- About the resadminwait event trigger
- About the resfault event trigger
- About the resnotoff event trigger
- About the resrestart event trigger
- About the resstatechange event trigger
- About the sysoffline event trigger
- About the unable_to_restart_agent event trigger
- About the unable_to_restart_had event trigger
- About the violation event trigger
- Controlling VCS behavior
- Section IV. Cluster configurations for disaster recovery
- Connecting clusters–Creating global clusters
- How VCS global clusters work
- VCS global clusters: The building blocks
- Visualization of remote cluster objects
- About global service groups
- About global cluster management
- About serialization - The Authority attribute
- About resiliency and "Right of way"
- VCS agents to manage wide-area failover
- About the Steward process: Split-brain in two-cluster global clusters
- Secure communication in global clusters
- Prerequisites for global clusters
- Setting up a global cluster
- Preparing the application for the global environment
- Configuring the ClusterService group
- Configuring replication resources in VCS
- Linking the application and replication service groups
- Configuring the second cluster
- Linking clusters
- Configuring the Steward process (optional)
- Stopping the Steward process
- Configuring the global service group
- About IPv6 support with global clusters
- About cluster faults
- About setting up a disaster recovery fire drill
- Multi-tiered application support using the RemoteGroup agent in a global environment
- Test scenario for a multi-tiered environment
- Administering global clusters from Cluster Manager (Java console)
- Administering global clusters from the command line
- About administering global clusters from the command line
- About global querying in a global cluster setup
- Administering global service groups in a global cluster setup
- Administering resources in a global cluster setup
- Administering clusters in global cluster setup
- Administering heartbeats in a 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 booting a cluster system
- VCS performance consideration when a resource comes online
- VCS performance consideration when a resource goes offline
- VCS performance consideration when a service group comes online
- VCS performance consideration when a service group goes offline
- VCS performance consideration when a resource fails
- VCS performance consideration when a system fails
- VCS performance consideration when a network link fails
- VCS performance consideration when a system panics
- VCS performance consideration when a service group switches over
- VCS performance consideration when a service group fails over
- Monitoring CPU usage
- VCS agent statistics
- About VCS performance with non-HA products
- About VCS performance with SFW
- Troubleshooting and recovery for VCS
- VCS message logging
- Handling network failure
- Troubleshooting VCS startup
- Troubleshooting secure clusters
- Troubleshooting service groups
- Troubleshooting resources
- Troubleshooting notification
- Troubleshooting and recovery for global clusters
- Troubleshooting the steward process
- 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