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
Setting up the Replicated Volume Group on the primary site
Before creating the Replicated Volume Group (RVG) on the primary site, make sure the volumes and Cluster Volume Manager (CVM) group are active and online.
To review the status of replication objects on the primary site
- Verify the volumes you intend to include in the group are active.
- Review the output of the hagrp -state cvm command to verify that the CVM group is online.
- On each site, verify vradmin is running:
# ps -ef |grep vradmin root 536594 598036 0 12:31:25 0 0:00 grep vradmin
If vradmin is not running start it:
# vxstart_vvr VxVM VVR INFO V-5-2-3935 Using following ports: heartbeat: 4145 vradmind: 8199 vxrsyncd: 8989 data: Anonymous-Ports To change, see vrport(1M) command # ps -ef |grep vradmin root 536782 1 0 12:32:47 - 0:00 /usr/sbin/vradmind root 1048622 598036 0 12:32:55 0 0:00 grep vradmin # netstat -an |grep 4145 tcp4 0 0 *.4145 *.* LISTEN udp4 0 0 *.4145 *.*
After reviewing the status of replication objects on the primary site, you can create the primary RVG.
The command to create the primary RVG takes the form:
vradmin -g disk_group createpri rvg_name data_volume srl_volume
where:
disk_group is the name of the disk group containing the database
rvg_name is the name for the RVG
data_volume is the volume that VVR replicates
srl_volume is the volume for the Storage Replicator Log (SRL)
To create the primary RVG
- Determine which node is the CVM master node by entering:
# vxdctl -c mode
- To create the dbdata_rvg RVG, you must run the following on the master node:
# vradmin -g dbdatadg createpri dbdata_rvg dbdata_vol dbdata_srl
The command creates the RVG on the primary site and adds a Data Change Map (DCM) for each data volume. In this case, a DCM exists for dbdata_vol.