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
About failover parent / parallel child
With a failover parent and parallel child, no hard dependencies are supported.
Table: Service group dependency configurations: Failover parent / Parallel child shows service group dependency configurations for Failover parent / Parallel child.
Table: Service group dependency configurations: Failover parent / Parallel child
Link | Failover parent depends on ... | Failover parent is online if ... | If parallel child faults on a system, then ... | If failover parent faults, then ... |
---|---|---|---|---|
online local soft | Instance of parallel Child group on same system. | Instance of Child is online on same system. | If Child instance fails over to another system, the Parent also fails over to the same system. If Child instance cannot failover to another system, Parent remains online. | Parent fails over to other system and depends on Child instance there. Child Instance remains online where the Parent faulted. |
online local firm | Instance of parallel Child group on same system. | Instance of Child is online on same system. | Parent is taken offline. Parent fails over to other system and depends on Child instance there. | Parent fails over to other system and depends on Child instance there. Child Instance remains online where Parent faulted. |
online global soft | All instances of parallel Child group online in the cluster. | At least one instance of Child group is online somewhere in the cluster. | Parent remains online if Child faults on any system. If Child cannot fail over to another system, Parent remains online. | Parent fails over to another system, maintaining dependence on all Child instances. |
online global firm | One or more instances of parallel Child group remaining online | An instance of Child group is online somewhere in the cluster. | Parent is taken offline. If another Child instance is online or Child fails over, Parent fails over to another system or the same system. If no Child instance is online or Child cannot fail over, Parent remains offline. | Parent fails over to another system, maintaining dependence on all Child instances. |
online remote soft | One or more instances parallel Child group remaining online on other systems. | One or more instances of Child group are online on other systems. | Parent remains online. If Child fails over to the system on which Parent is online, Parent fails over to another system. | Parent fails over to another system, maintaining dependence on the Child instances. |
online remote firm | All instances parallel Child group remaining online on other systems. | All instances of Child group are online on other systems. | Parent is taken offline. If Child fails over to the system on which Parent is online, Parent fails over to another system. If Child fails over to another system, Parent is brought online on its original system. | Parent fails over to another system, maintaining dependence on all Child instances. |
online site soft | One or more instances of parallel Child group in the same site. | At least one instance of Child is online in same site. | Parent stays online if child is online on any system in the same site. If Child fails over to a system in another site, Parent stays in the same site. If Child cannot fail over, Parent remains online. | Child stays online. Parents fails over to a system with Child online in the same site. If the parent group cannot failover, child group remains online |
online site firm | One or more instances of parallel Child group in the same site. | At least one instance of Child is online in same site. | Parent stays online if any instance of child is online in the same site. If Child fails over to another system, Parent migrates to a system in the same site. If Child cannot fail over, Parent remains offline. | Child stays online. Parents fails over to a system with Child online in the same site. If the parent group cannot failover, child group remains online. |
offline local | Parallel Child offline on same system. | No instance of Child is online on same system. | Parent remains online if Child fails over to another system. If Child fails over to the system on which Parent is online, Parent fails over. | Child remains online and parent fails over to another system where child is not online. If the parent group cannot failover, child group remains offline. |