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 disk group on secondary site for replication
Create the replication objects on the secondary site from the master node of the primary site, using the vradmin command.
To set up the disk group on the secondary site for replication
- Issue the command in the following format from the cluster on the primary site:
# vradmin -g dg_pri addsec rvg_pri pri_host sec_host
where:
dg_pri is the disk group on the primary site that VVR will replicate. For example: dbdata_vol
rvg_pri is the Replicated Volume Group (RVG) on the primary site. For example: dbdata_rvg
pri_host is the virtual IP address or resolvable virtual host name of the cluster on the primary site.
For example: 10.10.9.101 or clus1
sec_host is the virtual IP address or resolvable virtual host name of the cluster on the secondary site.
For example: 10.11.9.102 or clus2
For example, the command to add the cluster on the primary site to the Replicated Data Set (RDS) is:
vradmin -g dbdatadg addsec dbdata_rvg clus1 clus2
or
vradmin -g dbdatadg addsec dbdata_rvg 10.10.9.101 10.11.9.102
On the secondary site, the above command performs the following tasks:
Creates an RVG within the specified disk group using the same name as the one for the primary site
Associates the data and Storage Replicator Log (SRL) volumes that have the same names as the ones on the primary site with the specified RVG
Adds a data change map (DCM) for the data volume
Creates cluster RLINKs for the primary and secondary sites with the default names; for example, the "primary" RLINK created for this example is rlk_dbdata_clus2_dbdata_rvg and the "secondary" RLINK created is rlk_dbdata_clus1_dbdata_rvg.
If you use 10.10.9.101 and 10.11.9.102, creates cluster RLINKs for the primary and secondary sites with the default names; for example, the "primary" RLINK created for this example is rlk_10.11.9.102_dbdata_rvg and the "secondary" RLINK created is rlk_10.10.9.101_dbdata__rvg.
- Verify the list of RVGs in the RDS by executing the following command.
# vradmin -g dbdatadg -l printrvg
For example:
Replicated Data Set: dbdata_rvg Primary: HostName: 10.180.88.187 <localhost> RvgName: dbdata_rvg DgName: dbdata_vol datavol_cnt: 1 vset_cnt: 0 srl: dbdata_srl RLinks: name=rlk_clus2_dbdata_rvg, detached=on, synchronous=off Secondary: HostName: 10.190.99.197 RvgName:dbdata_rvg DgName: dbdatadg datavol_cnt: 1 vset_cnt: 0 srl: dbdata_srl RLinks: name=rlk_clus1_dbdata_rvg, detached=on, synchronous=off
Note:
Once the replication is started the value of the detached flag will change the status from ON to OFF.