Please enter search query.
Search <book_title>...
InfoScale™ 9.0 Cluster Server Administrator's Guide - Windows
Last Published:
2025-05-23
Product(s):
InfoScale & Storage Foundation (9.0)
Platform: 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
Verifying the cluster
To verify cluster operation, type the following command as Administrator on any node:
Drive:\>hasys -display #System Attribute Value HOUWIN201 AgentsStopped 0 HOUWIN201 AvailableCapacity 100 HOUWIN201 CPUUsage 0 HOUWIN201 CPUUsageMonitoring Enable 0 ActionThreshold 0 ActionTimeLimit 0 Action NONE NotifyThreshold 0 NotifyTimeLimit 0 HOUWIN201 Capacity 100 HOUWIN201 ConfigBlockCount 84 HOUWIN201 ConfigCheckSum 18907 HOUWIN201 ConfigDiskState CURRENT HOUWIN201 ConfigFile C:\Program Files\VERITAS\Cluster Server\conf\config HOUWIN201 ConfigInfoCnt 0 HOUWIN201 ConfigModDate Tue Dec 03 15:13:58 2001 HOUWIN201 CurrentLimits HOUWIN201 DiskHbStatus HOUWIN201 DynamicLoad 0 HOUWIN201 Frozen 0 HOUWIN201 GUIIPAaddr HOUWIN201 LLTNodeId 0 HOUWIN201 Limits HOUWIN201 LinkHbStatus Adapter0 UP Adapter1 UP HOUWIN201 LoadTimeCounter 0 HOUWIN201 LoadTimeThreshold 600 HOUWIN201 LoadWarningLevel 80 HOUWIN201 MajorVersion 2 HOUWIN201 MinorVersion 0 HOUWIN201 NodeID 0 HOUWIN201 OnGrpCnt 1 HOUWIN201 ShutdownTimeout 60 HOUWIN201 SourceFile .\main.cf HOUWIN201 SysInfo WINNT:HOUWIN201,5.0,2195, Service Pack 2, INTEL,1 HOUWIN201 SysName HOUWIN201 HOUWIN201 SysState RUNNING HOUWIN201 SystemLocation HOUWIN201 SystemOwner HOUWIN201 TFrozen 0 HOUWIN201 TRSE 0 HOUWIN201 UpDownState Up HOUWIN201 UserInt 0 HOUWIN201 UserStr # HOUWIN202 AgentsStopped 0 HOUWIN202 AvailableCapacity 100 HOUWIN202 CPUUsage 0 HOUWIN202 CPUUsageMonitoring Enable 0 ActionThreshold 0 ActionTimeLimit 0 Action NONE NotifyThreshold 0NotifyTimeLimit 0 HOUWIN202 Capacity 100 HOUWIN202 ConfigBlockCount 84 HOUWIN202 ConfigCheckSum 18907 HOUWIN202 ConfigDiskState CURRENT HOUWIN202 ConfigFile C:\Program Files\VERITAS\ Cluster Server\conf\config HOUWIN202 ConfigInfoCnt 0 HOUWIN202 ConfigModDate Tue Dec 03 15:15:58 2001 HOUWIN202 CurrentLimits HOUWIN202 DiskHbStatus HOUWIN202 DynamicLoad 0 HOUWIN202 Frozen 0 HOUWIN202 GUIIPAaddr HOUWIN202 LLTNodeIdHOUWIN202 Limits HOUWIN202 LinkHbStatus Adapter0 UP Adapter1 UP HOUWIN202 LoadTimeCounter 0 HOUWIN202 LoadTimeThreshold 600 HOUWIN202 LoadWarningLevel 80 HOUWIN202 MajorVersion 2 HOUWIN202 MinorVersion 0 HOUWIN202 NodeID 1 HOUWIN202 OnGrpCnt 1 HOUWIN202 ShutdownTimeout 60 HOUWIN202 SourceFile .\main.cf HOUWIN202 SysInfo WINNT:HOUWIN202,5.0,2195, Service Pack 2, INTEL,1 HOUWIN202 SysName HOUWIN202 HOUWIN202 SysState RUNNING HOUWIN202 SystemLocation HOUWIN202 SystemOwner HOUWIN202 TFrozen 0 HOUWIN202 TRSE 0 HOUWIN202 UpDownState Up HOUWIN202 UserInt 0 HOUWIN202 UserStr
Note the value for the attribute ConfigFile is an empty file created by default to enable VCS to start. Also note the value of the attribute SysState is RUNNING, which indicates VCS is started. This output indicates VCS was successfully installed on both nodes in the cluster.