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
Administering global service groups in a global cluster setup
Operations for the VCS global clusters option are enabled or restricted depending on the permissions with which you log on. The privileges associated with each user role are enforced for cross-cluster, service group operations.
This topic includes commands to administer global service groups.
See the hagrp (1M) manual page for more information.
To administer global service groups in a global cluster setup
- Depending on the administrative task you want to perform on global service groups, run the hagrp command as follows:
To bring a service group online across clusters for the first time
hagrp -online -force
To bring a service group online across clusters
hagrp -online service_group -sys system [-clus cluster | -localclus]
The option -clus brings the service group online on the system designated in the cluster. If a system is not specified, the service group is brought online on any node within the cluster. The option -localclus brings the service group online in the local cluster.
To bring a service group online on any node
hagrp -online [-force] service_group -any [-clus cluster | -localclus]
The option -any specifies that HAD brings a failover group online on the optimal system, based on the requirements of service group workload management and existing group dependencies. If bringing a parallel group online, HAD brings the group online on each system designated in the SystemList attribute.
To display the resources for a service group
hagrp -resources service_group [-clus cluster_name | -localclus]
The option -clus displays information for the cluster designated by the variable cluster_name; the option -localclus specifies the local cluster.
To take a service group offline across clusters
hagrp -offline [-force] [-ifprobed] service_group -sys system [-clus cluster | -localclus]
The option -clus takes offline the service group on the system designated in the cluster.
To take a service group offline anywhere
hagrp -offline [-ifprobed] service_group -any [-clus cluster | -localclus]
The option -any specifies that HAD takes a failover group offline on the system on which it is online. For a parallel group, HAD takes the group offline on each system on which the group is online. HAD adheres to the existing group dependencies when taking groups offline.
To switch a service group across clusters
hagrp -switch service_group -to system [-clus cluster | -localclus [-nopre]]
The option -clus identifies the cluster to which the service group will be switched. The service group is brought online on the system specified by the -to system argument. If a system is not specified, the service group may be switched to any node within the specified cluster.
The option -nopre indicates that the VCS engine must switch the service group regardless of the value of the PreSwitch service group attribute.
To switch a service group anywhere
hagrp -switch service_group -any [-clus cluster | -localclus]
The -any option specifies that the VCS engine switches a service group to the best possible system on which it is currently not online, based on the value of the group's FailOverPolicy attribute. The VCS engine switches a global service group from a system to another system in the local cluster or a remote cluster.
If you do not specify the -clus option, the VCS engine by default assumes -localclus option and selects an available system within the local cluster.
The option -clus identifies the remote cluster to which the service group will be switched. The VCS engine then selects the target system on which to switch the service group.
To switch a parallel global service group across clusters
hagrp -switch
VCS brings the parallel service group online on all possible nodes in the remote cluster.