Veritas InfoScale™ 8.0.2 Disaster Recovery Implementation Guide - AIX
- Section I. Introducing Storage Foundation and High Availability Solutions for disaster recovery
- About supported disaster recovery scenarios
- About disaster recovery scenarios
- About campus cluster configuration
- About replicated data clusters
- About global clusters
- How VCS global clusters work
- User privileges for cross-cluster operations
- VCS global clusters: The building blocks
- Visualization of remote cluster objects
- About global service groups
- About global cluster management
- About serialization - The Authority attribute
- About resiliency and "Right of way"
- VCS agents to manage wide-area failover
- About the Steward process: Split-brain in two-cluster global clusters
- Secure communication in global clusters
- Disaster recovery feature support for components in the Veritas InfoScale product suite
- Virtualization support for InfoScale 8.0.2 products in replicated environments
- Planning for disaster recovery
- About supported disaster recovery scenarios
- Section II. Implementing campus clusters
- Setting up campus clusters for VCS and SFHA
- About setting up a campus cluster configuration
- Preparing to set up a campus cluster configuration
- Configuring I/O fencing to prevent data corruption
- Configuring VxVM disk groups for campus cluster configuration
- Configuring VCS service group for campus clusters
- Setting up campus clusters for VxVM and VCS using Veritas InfoScale Operations Manager
- Fire drill in campus clusters
- About the DiskGroupSnap agent
- About running a fire drill in a campus cluster
- About setting up a campus cluster configuration
- Setting up campus clusters for SFCFSHA, SFRAC
- About setting up a campus cluster for disaster recovery for SFCFSHA or SF Oracle RAC
- Preparing to set up a campus cluster in a parallel cluster database environment
- Configuring I/O fencing to prevent data corruption
- Configuring VxVM disk groups for a campus cluster in a parallel cluster database environment
- Configuring VCS service groups for a campus cluster for SFCFSHA and SF Oracle RAC
- Tuning guidelines for parallel campus clusters
- Best practices for a parallel campus cluster
- Setting up campus clusters for VCS and SFHA
- Section III. Implementing replicated data clusters
- Configuring a replicated data cluster using VVR
- Configuring a replicated data cluster using third-party replication
- About setting up a replicated data cluster configuration using third-party replication
- About typical replicated data cluster configuration using third-party replication
- About setting up third-party replication
- Configuring the service groups for third-party replication
- Fire drill in replicated data clusters using third-party replication
- Section IV. Implementing global clusters
- Configuring global clusters for VCS and SFHA
- Installing and Configuring Cluster Server
- Setting up VVR replication
- About configuring VVR replication
- Best practices for setting up replication
- Creating a Replicated Data Set
- Creating a Primary RVG of an RDS
- Adding a Secondary to an RDS
- Changing the replication settings for a Secondary
- Synchronizing the Secondary and starting replication
- Starting replication when the data volumes are zero initialized
- Setting up third-party replication
- Configuring clusters for global cluster setup
- Configuring service groups for global cluster setup
- Fire drill in global clusters
- Configuring a global cluster with Storage Foundation Cluster File System High Availability or Storage Foundation for Oracle RAC
- About global clusters
- About replication for parallel global clusters using Storage Foundation and High Availability (SFHA) Solutions
- About setting up a global cluster environment for parallel clusters
- Configuring the primary site
- Configuring the secondary site
- Setting up replication between parallel global cluster sites
- Testing a parallel global cluster configuration
- Configuring a global cluster with Volume Replicator and Storage Foundation Cluster File System High Availability or Storage Foundation for Oracle RAC
- About configuring a parallel global cluster using Volume Replicator (VVR) for replication
- Setting up replication on the primary site using VVR
- Setting up replication on the secondary site using VVR
- Starting replication of the primary site database volume to the secondary site using VVR
- Configuring Cluster Server to replicate the database volume using VVR
- Replication use cases for global parallel clusters
- Configuring global clusters for VCS and SFHA
- Section V. Implementing disaster recovery configurations in virtualized environments
- Section VI. Reference
Securing communication between the wide-area connectors
Perform the following steps to configure secure communication between the wide-area connectors.
To secure communication between the wide-area connectors
- Verify that security is configured in both the clusters. You can use the installvcs -security command to configure security.
For more information, see the Cluster Server Configuration and Upgrade Guide.
- Establish trust between the clusters.
For example in a VCS global cluster environment with two clusters, perform the following steps to establish trust between the clusters:
On each node of the first cluster, enter the following command:
# export EAT_DATA_DIR=/var/VRTSvcs/vcsauth/data/WAC; /opt/VRTSvcs/bin/vcsat setuptrust -b IP_address_of_any_node_from_the_second_cluster:14149 -s high
The command obtains and displays the security certificate and other details of the root broker of the second cluster.
If the details are correct, enter y at the command prompt to establish trust.
For example:
The hash of above credential is b36a2607bf48296063068e3fc49188596aa079bb Do you want to trust the above?(y/n) y
On each node of the second cluster, enter the following command:
# export EAT_DATA_DIR=/var/VRTSvcs/vcsauth/data/WAC /opt/VRTSvcs/bin/vcsat setuptrust -b IP_address_of_any_node_from_the_first_cluster:14149 -s high
The command obtains and displays the security certificate and other details of the root broker of the first cluster.
If the details are correct, enter y at the command prompt to establish trust.
Alternatively, if you have passwordless communication set up on the cluster, you can use the installvcs -securitytrust option to set up trust with a remote cluster.
- On each cluster, take the
Skip the remaining steps in this procedure if you used the installvcs -security command after the global cluster was set up.
Complete the remaining steps in this procedure if you had a secure cluster and then used the gcoconfig command.
wacresource offline on the node where thewacresource is online. For each cluster, run the following command:# hares -offline wac -sys node_where_wac_is_online
- Update the values of the StartProgram and MonitorProcesses attributes of the
wacresource:# haconf -makerw hares -modify wac StartProgram \ "/opt/VRTSvcs/bin/wacstart -secure" hares -modify wac MonitorProcesses \ "/opt/VRTSvcs/bin/wac -secure" haconf -dump -makero
- On each cluster, bring the
wacresource online. For each cluster, run the following command on any node:# hares -online wac -sys systemname