InfoScale™ 9.0 Cluster Server 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 security services
- 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
- About application monitoring on single-node clusters
- Configuring the service group in a non-shared storage environment
- About the VCS Application Manager utility
- About testing resource failover using virtual fire drills
- 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
- Appendix G. Executive Order logging
Configuring the Steward process (optional)
In case of a two-cluster GCO, you can configure a Steward to prevent potential split-brain conditions, provided the proper network infrastructure exists.
To configure the Steward process for clusters not running in secure mode
- Identify a system that will host the Steward process.
Make sure both clusters can connect to the system through a ping command.
- Copy the file steward from a node in the cluster to the Steward system. The file resides at the following path:
%VCS_HOME%\bin
The variable %VCS_HOME% represents the VCS installation directory, typically
C:\Program Files\VERITAS\Cluster Server
. - In both clusters, set the Stewards attribute to the IP address of the system running the Steward process. For example:
cluster cluster1938 ( UserNames = { admin = gNOgNInKOjOOmWOiNL } ClusterAddress = "10.182.147.19" Administrators = { admin } CredRenewFrequency = 0 CounterInterval = 5 Stewards = {"10.212.100.165"} }
- On the system designated to host the Steward, start the Steward process:
steward.exe -start
To configure the Steward process for clusters running in secure mode
- Verify the prerequisites for securing Steward communication are met.
- Identify a system that will host the Steward process.
Make sure both clusters can connect to the system through a ping command.
- Copy the steward file from a node in the cluster to the Steward system. The file resides at the following path:
%VCS_HOME%\bin\
The variable %VCS_HOME% represents the VCS installation directory, typically .
- On the Steward system, run the following script to generate certificates for the steward:
"C:\Program Files\Veritas\VRTSPerl\bin\perl.exe" create_certs.pl
This script is located in the
%VCS_HOME%\bin
directory. - To establish trust, run the following script on these systems:
On the Steward system:
"C:\Program Files\Veritas\VRTSPerl\bin\perl.exe" setup_trust.pl virtualIP STEWARD
Here, virtualIP is the virtual IP address of the cluster.
On any node in a global cluster:
"C:\Program Files\Veritas\VRTSPerl\bin\perl.exe" setup_trust.pl
If it is multi-site cluster, run this script on any cluster node at each site.
On each node in the cluster:
"C:\Program Files\Veritas\VRTSPerl\bin\perl.exe" setup_trust.pl stewardNameOrIP WAC
Here, stewardNameOrIP is the system name or IP address of the Steward system.
This script is located in the
%VCS_HOME%\bin
directory. - On the Steward system, create a file called Steward.conf and populate it with the following information:
broker=system_name accountname=accountname domain=HA_SERVICES@FQDN_of_system_that_issued_the_certificate
- In both clusters, set the Stewards attribute to the IP address of the system that runs the Steward process. For example:
cluster cluster1938 ( UserNames = { admin = gNOgNInKOjOOmWOiNL } ClusterAddress = "10.182.147.19" Administrators = { admin } CredRenewFrequency = 0 CounterInterval = 5 Stewards = {"10.212.100.165"} }
- On the system designated to run the Steward, start the Steward process:
steward.exe -start -secure