Please enter search query.
Search <book_title>...
Cluster Server 7.4.1 Administrator's Guide - Linux
Last Published:
2019-10-17
Product(s):
InfoScale & Storage Foundation (7.4.1)
Platform: 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
Sample configuration for a multiple NFS environment with lock recovery
include "types.cf" cluster clus1 ( UseFence = SCSI3 ) system sys1 ( ) system sys2 ( ) group nfs_sg ( SystemList = { sys1 = 0, sys2 = 1 } Parallel = 1 AutoStartList = { sys1, sys2 } )
NFS n1 ( Nproc = 6 )
Phantom ph1 ( ) group sg11 ( SystemList = { sys1 = 0, sys2 = 1 } AutoStartList = { sys1 } ) DiskGroup vcs_dg1 ( DiskGroup = dg1 StartVolumes = 0 StopVolumes = 0 ) DNS dns_11 ( Domain = "oradb.sym" TSIGKeyFile = "/Koradb.sym.+157+13021.private" StealthMasters = { "10.198.90.202" } ResRecord @sys1 = { sys1 = "10.198.90.198" } ResRecord @sys2 = { sys2 = "10.198.90.198" } CreatePTR = 1 OffDelRR = 1 ) IP ip_sys1 ( Device @sys1 = eth0 Device @sys2 = eth0 Address = "10.198.90.198" NetMask = "255.255.248.0" ) Mount vcs_dg1_r01_2 ( MountPoint = "/testdir/VITA_dg1_r01_2" BlockDevice = "/dev/vx/dsk/dg1/dg1_r01_2" FSType = vxfs FsckOpt = "-y" ) Mount vcs_dg1_r0_1 ( MountPoint = "/testdir/VITA_dg1_r0_1" BlockDevice = "/dev/vx/dsk/dg1/dg1_r0_1" FSType = vxfs FsckOpt = "-y" ) NFSRestart NFSRestart_sg11_L ( NFSRes = n1 Lower = 1 LocksPathName = "/testdir/VITA_dg1_r01_2" NFSLockFailover = 1 ) NFSRestart NFSRestart_sg11_U ( NFSRes = n1 LocksPathName = "/testdir/VITA_dg1_r01_2" NFSLockFailover = 1 ) NIC nic_sg11_eth0 ( Device @sys1 = eth0 Device @sys2 = eth0 NetworkHosts = { "10.198.88.1" } ) Proxy p11 ( TargetResName = n1 ) Share share_dg1_r01_2 ( PathName = "/testdir/VITA_dg1_r01_2" Options = rw ) Share share_dg1_r0_1 ( PathName = "/testdir/VITA_dg1_r0_1" Options = rw ) Volume vol_dg1_r01_2 ( Volume = dg1_r01_2 DiskGroup = dg1 ) Volume vol_dg1_r0_1 ( Volume = dg1_r0_1 DiskGroup = dg1 ) requires group nfs_sg online local firm NFSRestart_sg11_L requires p11 NFSRestart_sg11_L requires vcs_dg1_r01_2 NFSRestart_sg11_L requires vcs_dg1_r0_1 NFSRestart_sg11_U requires dns_11 dns_11 requires ip_sys1 ip_sys1 requires nic_sg11_eth0 ip_sys1 requires share_dg1_r01_2 ip_sys1 requires share_dg1_r0_1 share_dg1_r01_2 requires NFSRestart_sg11_L share_dg1_r0_1 requires NFSRestart_sg11_L vcs_dg1_r01_2 requires vol_dg1_r01_2 vcs_dg1_r0_1 requires vol_dg1_r0_1 vol_dg1_r01_2 requires vcs_dg1 vol_dg1_r0_1 requires vcs_dg1