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
Sample configuration: Server consolidation
The following configuration has a complex eight-node cluster running multiple applications and large databases. The database servers, LargeServer1, LargeServer2, and LargeServer3, are enterprise systems. The middle-tier servers running multiple applications are MedServer1, MedServer2, MedServer3, MedServer4, and MedServer5.
In this configuration, the database zone (system zone 0) can handle a maximum of two failures. Each server has Limits to support a maximum of three database service groups. The application zone has excess capacity built into each server.
The servers running the application groups specify Limits to support one database, even though the application groups do not run prerequisites. This allows a database to fail over across system zones and run on the least-loaded server in the application zone.
include "types.cf" cluster SGWM-demo ( ) system LargeServer1 ( Capacity = 200 Limits = { ShrMemSeg=15, Semaphores=30, Processors=18 } LoadWarningLevel = 80 LoadTimeThreshold = 900 ) system LargeServer2 ( Capacity = 200 Limits = { ShrMemSeg=15, Semaphores=30, Processors=18 } LoadWarningLevel=80 LoadTimeThreshold=900 ) system LargeServer3 ( Capacity = 200 Limits = { ShrMemSeg=15, Semaphores=30, Processors=18 } LoadWarningLevel=80 LoadTimeThreshold=900 ) system MedServer1 ( Capacity = 100 Limits = { ShrMemSeg=5, Semaphores=10, Processors=6 } ) system MedServer2 ( Capacity = 100 Limits = { ShrMemSeg=5, Semaphores=10, Processors=6 } ) system MedServer3 ( Capacity = 100 Limits = { ShrMemSeg=5, Semaphores=10, Processors=6 } ) system MedServer4 ( Capacity = 100 Limits = { ShrMemSeg=5, Semaphores=10, Processors=6 } ) system MedServer5 ( Capacity = 100 Limits = { ShrMemSeg=5, Semaphores=10, Processors=6 } ) group Database1 ( SystemList = { LargeServer1 = 0, LargeServer2 = 1, LargeServer3 = 2, MedServer1 = 3, MedServer2 = 4, MedServer3 = 5, MedServer4 = 6, MedServer5 = 6 } SystemZones = { LargeServer1=0, LargeServer2=0, LargeServer3=0, MedServer1=1, MedServer2=1, MedServer3=1, MedServer4=1, MedServer5=1 } AutoStartPolicy = Load AutoStartList = { LargeServer1, LargeServer2, LargeServer3 } FailOverPolicy = Load Load = { Units = 100 } Prerequisites = { ShrMemSeg=5, Semaphores=10, Processors=6 } ) group Database2 ( SystemList = { LargeServer1 = 0, LargeServer2 = 1, LargeServer3 = 2, MedServer1 = 3, MedServer2 = 4, MedServer3 = 5, MedServer4 = 6, MedServer5 = 6 } SystemZones = { LargeServer1=0, LargeServer2=0, LargeServer3=0, MedServer1=1, MedServer2=1, MedServer3=1, MedServer4=1, MedServer5=1 } AutoStartPolicy = Load AutoStartList = { LargeServer1, LargeServer2, LargeServer3 } FailOverPolicy = Load Load = { Units = 100 } Prerequisites = { ShrMemSeg=5, Semaphores=10, Processors=6 } ) group Database3 ( SystemList = { LargeServer1 = 0, LargeServer2 = 1, LargeServer3 = 2, MedServer1 = 3, MedServer2 = 4, MedServer3 = 5, MedServer4 = 6, MedServer5 = 6 } SystemZones = { LargeServer1=0, LargeServer2=0, LargeServer3=0, MedServer1=1, MedServer2=1, MedServer3=1, MedServer4=1, MedServer5=1 } AutoStartPolicy = Load AutoStartList = { LargeServer1, LargeServer2, LargeServer3 } FailOverPolicy = Load Load = { Units = 100 } Prerequisites = { ShrMemSeg=5, Semaphores=10, Processors=6 } ) group Application1 ( SystemList = { LargeServer1 = 0, LargeServer2 = 1, LargeServer3 = 2, MedServer1 = 3, MedServer2 = 4, MedServer3 = 5, MedServer4 = 6, MedServer5 = 6 } SystemZones = { LargeServer1=0, LargeServer2=0, LargeServer3=0, MedServer1=1, MedServer2=1, MedServer3=1, MedServer4=1, MedServer5=1 } AutoStartPolicy = Load AutoStartList = { MedServer1, MedServer2, MedServer3, MedServer4, MedServer5 } FailOverPolicy = Load Load = { Units = 50 } ) group Application2 ( SystemList = { LargeServer1 = 0, LargeServer2 = 1, LargeServer3 = 2, MedServer1 = 3, MedServer2 = 4, MedServer3 = 5, MedServer4 = 6, MedServer5 = 6 } SystemZones = { LargeServer1=0, LargeServer2=0, LargeServer3=0, MedServer1=1, MedServer2=1, MedServer3=1, MedServer4=1, MedServer5=1 } AutoStartPolicy = Load AutoStartList = { MedServer1, MedServer2, MedServer3, MedServer4, MedServer5 } FailOverPolicy = Load Load = { Units = 50 } ) group Application3 ( SystemList = { LargeServer1 = 0, LargeServer2 = 1, LargeServer3 = 2, MedServer1 = 3, MedServer2 = 4, MedServer3 = 5, MedServer4 = 6, MedServer5 = 6 } SystemZones = { LargeServer1=0, LargeServer2=0, LargeServer3=0, MedServer1=1, MedServer2=1, MedServer3=1, MedServer4=1, MedServer5=1 } AutoStartPolicy = Load AutoStartList = { MedServer1, MedServer2, MedServer3, MedServer4, MedServer5 } FailOverPolicy = Load Load = { Units = 50 } ) group Application4 ( SystemList = { LargeServer1 = 0, LargeServer2 = 1, LargeServer3 = 2, MedServer1 = 3, MedServer2 = 4, MedServer3 = 5, MedServer4 = 6, MedServer5 = 6 } SystemZones = { LargeServer1=0, LargeServer2=0, LargeServer3=0, MedServer1=1, MedServer2=1, MedServer3=1, MedServer4=1, MedServer5=1 } AutoStartPolicy = Load AutoStartList = { MedServer1, MedServer2, MedServer3, MedServer4, MedServer5 } FailOverPolicy = Load Load = { Units = 50 } ) group Application5 ( SystemList = { LargeServer1 = 0, LargeServer2 = 1, LargeServer3 = 2, MedServer1 = 3, MedServer2 = 4, MedServer3 = 5, MedServer4 = 6, MedServer5 = 6 } SystemZones = { LargeServer1=0, LargeServer2=0, LargeServer3=0, MedServer1=1, MedServer2=1, MedServer3=1, MedServer4=1, MedServer5=1 } AutoStartPolicy = Load AutoStartList = { MedServer1, MedServer2, MedServer3, MedServer4, MedServer5 } FailOverPolicy = Load Load = { Units = 50 } )