InfoScale™ 9.0 Disaster Recovery Implementation Guide - Linux
- Section I. Introducing Storage Foundation and High Availability Solutions for disaster recovery
- About supported disaster recovery scenarios
- About campus cluster configuration
- About replicated data clusters
- About global clusters
- VCS global clusters: The building blocks
- About global cluster management
- About serialization - The Authority attribute
- 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
- About running a fire drill in a campus cluster
- About setting up a campus cluster configuration
- Setting up campus clusters for SFCFSHA, SFRAC
- 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
- Section IV. Implementing global clusters
- Configuring global clusters for VCS and SFHA
- Setting up VVR 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
- Configuring clusters for global cluster setup
- Configuring service groups for global cluster setup
- Configuring a global cluster with Storage Foundation Cluster File System High Availability, Storage Foundation for Oracle RAC, or Storage Foundation for Sybase CE
- Configuring the secondary site
- Configuring global clusters with VVR and Storage Foundation Cluster File System High Availability, Storage Foundation for Oracle RAC, or Storage Foundation for Sybase CE
- Setting up replication on the primary site using VVR
- Setting up replication on the secondary site using VVR
- Configuring Cluster Server to replicate the database volume using VVR
- Configuring global clusters for VCS and SFHA
- Section V. Reference
- Appendix A. Sample configuration files
- Sample Storage Foundation for Oracle RAC configuration files
- About sample main.cf files for Storage Foundation (SF) for Oracle RAC
- About sample main.cf files for Storage Foundation (SF) for Sybase ASE CE
- Appendix A. Sample configuration files
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.
wac
resource offline on the node where thewac
resource 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
wac
resource:# 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
wac
resource online. For each cluster, run the following command on any node:# hares -online wac -sys systemname