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
- 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
- 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
- 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
- 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
- Appendix G. InfoScale event logging
VCS environment variables
Table: VCS environment variables
Environment Variable | Definition and Default Value |
|---|---|
PERL5LIB | Root directory for Perl executables. (applicable only for Windows) Default: Install Drive:\Program Files\VERITAS\cluster server\lib\perl5. |
VCS_CONF | Root directory for VCS configuration files. Default: Install Drive:\Program Files\VERITAS\cluster server\conf\config Note: You cannot modify this variable. |
VCS_CONN_INIT_QUOTA | Maximum number of simultaneous connections accepted by the VCS engine (HAD) per client host that has not completed the handshake. |
VCS_CONN_HANDSHAKE_TIMEOUT | Timeout in seconds after which the VCS engine (HAD) closes the client connection that has not completed the handshake. |
VCS_DEBUG_LOG_TAGS | Enables debug logs for the VCS engine, VCS agents, and HA commands. You must set VCS_DEBUG_LOG_TAGS before you start HAD or before you execute HA commands. To make sure that the debug logging persists even after HAD or the cluster node is restarted, set this environment variable as follows: VCS_DEBUG_LOG_TAGS="DBG_POLICY DBG_IPM DBG_TRACE DBG_INTERNAL DBG_SECURITY DBG_AGTRACE DBG_AGINFO DBG_AGDEBUG" Alternatively, run the following command to add these debug logs: halog -addtags DBG_POLICY DBG_IPM DBG_TRACE DBG_INTERNAL DBG_SECURITY DBG_AGTRACE DBG_AGINFO DBG_AGDEBUG Note that the debug logs added using the CLI do not persist if HAD or the cluster node is restarted. |
VCS_DOMAIN | The Security domain in which users are configured. The Security domain to which the VCS users belong. The VCS Authentication Service uses this environment variable to authenticate VCS users on a remote host. Default: Fully qualified host name of the remote host as defined in the VCS_HOST environment variable or in the .vcshost file. |
VCS_DOMAINTYPE | Type of domain: unixpwd, nt, nis, nisplus, or vx. The type of Security domain such as unixpwd, nt, nis, nisplus, ldap, or vx. The VCS Authentication Service uses this environment variable to authenticate VCS users on a remote host. Default: unixpwd |
VCS_DIAG | Directory where VCS dumps HAD cores. |
VCS_ENABLE_LDF | Designates whether or not log data files (LDFs) are generated. If set to 1, LDFs are generated. If set to 0, they are not. |
VCS_HOME | Root directory for VCS executables. Default: Install Drive:\Program Files\VERITAS\cluster server\ Note: You cannot modify this variable. |
VCS_HOST | VCS node on which ha commands will be run. |
VCS_GAB_PORT | GAB port to which VCS connects. Default: h |
VCS_GAB_TIMEOUT | Timeout in milliseconds for HAD to send heartbeats to GAB. Default: 30000 (denotes 30 seconds) Range: 30000 to 300000 (denotes 30 seconds to 300 seconds) If you set VCS_GAB_TIMEOUT to a value outside the range, the value is automatically reset to 30000 or 300000, depending on the proximity of the value to the lower limit or upper limit of the range. For example, the value is reset to 30000 if you specify 22000 and to 300000 if you specify 400000. Irrespective of the values set, VCS_GAB_TIMEOUT_SECS overrides VCS_GAB_TIMEOUT if both are specified. Note: If the specified timeout is exceeded, GAB kills HAD, and all active service groups on the system are disabled. |
VCS_GAB_TIMEOUT_SECS | Timeout in seconds for HAD to send heartbeats to GAB under normal system load conditions. Default: 30 seconds Range: 30 seconds to 300 seconds If you set VCS_GAB_TIMEOUT_SECS to a value outside the range, the value is automatically reset to 30 or 300, depending on the proximity of the value to the lower limit or upper limit of the range. For example, the value is reset to 30 if you specify 22 and to 300 if you specify 400. Irrespective of the values set, VCS_GAB_TIMEOUT_SECS overrides VCS_GAB_TIMEOUT if both are specified. Note: If the specified timeout is exceeded, GAB kills HAD, and all active service groups on the system are disabled. |
VCS_GAB_PEAKLOAD_TIMEOUT_SECS | Timeout in seconds for HAD to send heartbeats to GAB under peak system load conditions. Default: 30 seconds Range: 30 seconds to 300 seconds To set the GAB tunables in adaptive mode, you must set VCS_GAB_PEAKLOAD_TIMEOUT_SECS to a value that exceeds VCS_GAB_TIMEOUT_SECS. If you set VCS_GAB_PEAKLOAD_TIMEOUT_SECS to a value that is lower than VCS_GAB_TIMEOUT_SECS, it is reset to VCS_GAB_TIMEOUT_SECS. Note: If the specified timeout is exceeded, GAB kills HAD, and all active service groups on the system are disabled. |
VCS_GAB_RMTIMEOUT | Timeout in milliseconds for HAD to register with GAB. Default: 200000 (denotes 200 seconds) If you set VCS_GAB_RMTIMEOUT to a value less than 200000, the value is automatically reset to 200000. |
VCS_GAB_RMACTION | Controls the GAB behavior when VCS_GAB_RMTIMEOUT exceeds. You can set the value as follows:
Default: SYSLOG |
VCS_HAD_RESTART_TIMEOUT | Set this variable to designate the amount of time the hashadow process waits (sleep time) before restarting HAD. Default: 0 |
VCS_LOG | Root directory for log files and temporary files. You must not set this variable to "" (empty string). Default: Install Drive:\Program Files\VERITAS\cluster server\ Note: If this variable is added or modified, you must reboot the system to apply the changes. |
VCS_SERVICE | Name of the configured VCS service. The VCS engine uses this variable to determine the external communication port for VCS. By default, the external communication port for VCS is 14141. The value for this environment variable is defined in the service file at the following location: C:\Windows\System32\drivers\etc\services Default value: vcs If a new port number is not specified, the VCS engine starts with port 14141. To change the default port number, you must create a new entry in the service file at: C:\Windows\System32\drivers\etc\services For example, if you want the external communication port for VCS to be set to 14555, then you must create the following entries in the services file: vcs 14555/tcp vcs 14555/udp Note: The cluster-level attribute OpenExternalCommunicationPort determines whether the port is open or not. See Cluster attributes. |
VCS_TEMP_DIR | Directory in which temporary information required by, or generated by, hacf is stored. Default: Install Drive:\Program Files\VERITAS\cluster server\ This directory is created in the
|