Cluster Server 7.4.1 Administrator's Guide - Linux
- 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
- About resource monitoring
- Agent classifications
- About cluster control, communications, and membership
- About security services
- Components for administering VCS
- About cluster topologies
- VCS configuration concepts
- Introducing Cluster Server
- Section II. Administration - Putting VCS to work
- About the VCS user privilege model
- Administering the cluster from the command line
- About administering VCS from the command line
- About installing a VCS license
- Administering LLT
- Starting VCS
- Stopping the VCS engine and related processes
- Logging on to VCS
- 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
- Enabling and disabling IMF for agents by using script
- Linking and unlinking resources
- About administering resource types
- About administering clusters
- Configuring applications and resources in VCS
- VCS bundled agents for UNIX
- Configuring NFS service groups
- About NFS
- Configuring NFS service groups
- Sample configurations
- About configuring the RemoteGroup agent
- About configuring Samba service groups
- About testing resource failover by using HA fire drills
- Predicting VCS behavior using VCS Simulator
- Section III. VCS communication and operations
- About communications, membership, and data protection in the cluster
- About cluster communications
- About cluster membership
- About membership arbitration
- About membership arbitration components
- About server-based I/O fencing
- About majority-based fencing
- About the CP server service group
- About secure communication between the VCS cluster and CP server
- About data protection
- Examples of VCS operation with I/O fencing
- About cluster membership and data protection without I/O fencing
- Examples of VCS operation without I/O fencing
- Administering I/O fencing
- About the vxfentsthdw utility
- Testing the coordinator disk group using the -c option of vxfentsthdw
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- About administering the coordination point server
- About configuring a CP server to support IPv6 or dual stack
- About migrating between disk-based and server-based fencing configurations
- Migrating between fencing configurations using response files
- Controlling VCS behavior
- VCS behavior on resource faults
- About controlling VCS behavior at the service group level
- About AdaptiveHA
- Customized behavior diagrams
- About preventing concurrency violation
- VCS behavior for resources that support the intentional offline functionality
- VCS behavior when a service group is restarted
- About controlling VCS behavior at the resource level
- VCS behavior on loss of storage connectivity
- Service group workload management
- Sample configurations depicting workload management
- The role of service group dependencies
- About communications, membership, and data protection in the cluster
- Section IV. Administration - Beyond the basics
- VCS event notification
- VCS event triggers
- Using event triggers
- List of event triggers
- Virtual Business Services
- Section V. Veritas High Availability Configuration wizard
- Introducing the Veritas High Availability Configuration wizard
- Administering application monitoring from the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Section VI. 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
- 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 the command line
- About global querying in a global cluster setup
- Administering clusters in global cluster setup
- Setting up replicated data clusters
- Setting up campus clusters
- Connecting clusters–Creating global clusters
- Section VII. Troubleshooting and performance
- VCS performance considerations
- How cluster components affect performance
- How cluster operations affect performance
- VCS performance consideration when a system panics
- About scheduling class and priority configuration
- VCS agent statistics
- About VCS tunable parameters
- Troubleshooting and recovery for VCS
- VCS message logging
- Gathering VCS information for support analysis
- Troubleshooting the VCS engine
- Troubleshooting Low Latency Transport (LLT)
- Troubleshooting Group Membership Services/Atomic Broadcast (GAB)
- Troubleshooting VCS startup
- Troubleshooting issues with systemd unit service files
- Troubleshooting service groups
- Troubleshooting resources
- Troubleshooting sites
- Troubleshooting I/O fencing
- Fencing startup reports preexisting split-brain
- Troubleshooting CP server
- Troubleshooting server-based fencing on the VCS cluster nodes
- Issues during online migration of coordination points
- Troubleshooting notification
- Troubleshooting and recovery for global clusters
- Troubleshooting licensing
- Licensing error messages
- Troubleshooting secure configurations
- Troubleshooting wizard-based configuration issues
- Troubleshooting issues with the Veritas High Availability view
- VCS message logging
- VCS performance considerations
- Section VIII. Appendixes
About failover parent / failover child
Table: Service group dependency configurations: Failover parent / Failover child shows service group dependencies for failover parent / failover child.
Table: Service group dependency configurations: Failover parent / Failover child
Link | Failover parent depends on ... | Failover parent is online If ... | If failover child faults, then ... | If failover parent faults, then ... |
---|---|---|---|---|
online local soft | Failover Child online on same system. | Child is online on same system. | Parent stays online. If Child fails over to another system, Parent migrates to the same system. If Child cannot fail over, Parent remains online. | Child stays online. |
online local firm | Failover Child online on same system. | Child is online on same system. | Parent taken offline. If Child fails over to another system, Parent migrates to the same system. If Child cannot fail over, Parent remains offline. | Child stays online. |
online local hard | Failover Child online on same system. | Child is online on same system. | Parents taken offline before Child is taken offline. If Child fails over to another system, Parent migrates to the same system. If Child cannot fail over, Parent remains offline. | Child taken offline. If Child fails over, Parent migrates to the same system. If Child cannot fail over, Parent remains offline. |
online global soft | Failover Child online somewhere in the cluster. | Child is online somewhere in the cluster. | Parent stays online. If Child fails over to another system, Parent remains online. If Child cannot fail over, Parent remains online. | Child stays online. Parent fails over to any available system. If no failover target system is available, Parent remains offline. |
online global firm | Failover Child online somewhere in the cluster. | Child is online somewhere in the cluster. | Parent taken offline after Child is taken offline. If Child fails over to another system, Parent is brought online on any system. If Child cannot fail over, Parent remains offline. | Child stays online. Parent fails over to any available system. If no failover target system is available, Parent remains offline. |
online remote soft | Failover Child online on another system in the cluster. | Child is online on another system in the cluster. | If Child fails over to the system on which Parent was online, Parent migrates to another system. If Child fails over to another system, Parent continues to run on original system. If Child cannot fail over, Parent remains online. | Child stays online. Parent fails over to a system where Child is not online. If the only system available is where Child is online, Parent is not brought online. If no failover target system is available, Child remains online. |
online remote firm | Failover Child online on another system in the cluster. | Child is online on another system in the cluster. | If Child fails over to the system on which Parent was online, Parent switches to another system. If Child fails over to another system, Parent restarts on original system. If Child cannot fail over, VCS takes the parent offline. | Parent fails over to a system where Child is not online. If the only system available is where Child is online, Parent is not brought online. If no failover target system is available, Child remains online. |
online site soft | Failover Child online on same site. | Child is online in the same site. | Parent stays online. If another Child instance is online or Child fails over to a system within the same site, Parent stays online. If Child fails over to a system in another site, parent migrates to another site where Child is online and depends on Child instance(s) in that site. If Child cannot fail over, Parent remains online. | Child remains online. Parent fails over to another system in the same site maintaining dependency on Child instances in the same site. If Parent cannot failover to a system within the same site, then Parent fails over to a system in another site where at least one instance of child is online in the same site. |
online site firm | Failover Child online in the same site | Child is online in the same site. | Parent taken offline. If another instance of child is online in the same site or child fails over to another system in the same site, Parent migrates to a system in the same site. If no Child instance is online or Child cannot fail over, Parent remains offline. | Child remains online. Parent fails over to another system in same site maintaining dependence on Child instances in the same site. If Parent cannot failover to a system within same site, then Parent fails over to a system in another site where at least one instance of child is online. |
offline local | Failover Child offline on the same system | Child is offline on the same system. | If Child fails over to the system on which parent in not running, parent continues running. If child fails over to system on which parent is running, parent switches to another system, if available. If no failover target system is available for Child to fail over to, Parent continues running. | Parent fails over to system on which Child is not online. If no failover target system is available, Child remains online. |