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
Removing nodes from a cluster
This topic describes how to remove nodes from a multiple node VCS cluster. To remove a node from a single-node cluster, you must delete the cluster.
To remove nodes from a cluster
- Verify that no service groups are online on the node to be removed.
- Remove the node from the SystemList of all service groups.
- Launch the Cluster Configuration Wizard from the Apps menu on the Start screen.
- Read the information on the Welcome panel and click Next.
- In the Configuration Options panel, click Cluster Operations and click Next.
- In the Domain Selection panel, select or type the name of the domain in which the cluster resides and select the domain discovery options.
To discover information about all the systems and users in the domain:
Uncheck the Specify systems and users manually check box.
Click Next.
Proceed to step 10.
To specify systems and user names manually (recommended for large domains):
Check the Specify systems and users manually check box.
Additionally, you may instruct the wizard to retrieve a list of systems and users in the domain by selecting appropriate check boxes.
Click Next.
If you checked Retrieve system list from domain, proceed to step 8. Otherwise proceed to the next step.
- In the System Selection panel, type the name of the system and click Add.
Proceed to step 10.
- In the System Selection panel, specify the systems for the cluster from which you will be removing the nodes.
Enter the system name and click Add to add the system to the Selected Systems list. Alternatively, you can select the systems from the Domain Systems list and click the right-arrow icon.
If you specify only one node of an existing cluster, the wizard discovers all nodes for that cluster.
- The System Report panel displays the validation status, whether Accepted or Rejected, of all the systems you specified earlier.
A system can be rejected for any of the following reasons:
The system does not respond to a ping request.
WMI access is disabled on the system.
The wizard is unable to retrieve information about the system's architecture or operating system.
VCS is either not installed on the system or the version of VCS is different from what is installed on the system on which you are running the wizard.
Click on a system name to see the validation details. If you wish to include a rejected system, rectify the error based on the reason for rejection and then run the wizard again.
Click Next to proceed.
- In the Cluster Configuration Options panel, click Edit Existing Cluster and then click Next.
- In the Cluster Selection panel, select the cluster to be edited and click Next.
If you chose to specify the systems manually in step 6, only the clusters configured with the specified systems are displayed.
- In the Edit Cluster Options panel, click Remove Nodes and then click Next.
In the Cluster User Information panel, enter the user name and password for a user with administrative privileges to the cluster and click OK.
The Cluster User Information dialog box appears only when you remove a node from a non-secure cluster.
- In the Cluster Details panel, select the check boxes next to the nodes to be removed and click Next.
- If you want to remove the VCS Helper service user account from the administrative group of the nodes being removed from the cluster, click Yes from the informational dialog box. Otherwise, click No.
- The wizard validates the selected nodes. After the nodes have been validated, click Next. If a node does not get validated, review the message associated with the failure and restart the wizard after rectifying the problem.
An informational dialog box appears if you are removing all but one nodes of a multiple node cluster. In the dialog box, specify whether you want to retain or remove the private link heartbeat.
- Review the summary information and click Remove.
The wizard starts running commands to remove the node from the cluster.
- After the commands have been successfully run, click Finish.