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
Prerequisites for creating a Primary RVG of an RDS
Before creating a Primary RVG of an RDS, the following prerequisites must be met:
Ensure that the SRL volume and the data volumes are created on the primary.
Note:
All the volumes must either be encrypted or non-encrypted. A mixed set of volumes is not supported. The createpri command that is used to create a primary RVG fails, if the volume type is not same.
The SRL cannot be a volume set or a component volume of a volume set.
The data volumes and SRL are started, and its state is active.
The data volumes used by the application exist in the same RVG and the data volumes used by the application are in the same RVG.
In a SAN disk group environment, if the application resides on the volume client, all the Primary data volumes must be attached to the volume client or unattached from the volume client.
Make sure you include the appropriate loopback address(es) in the
/etc/hosts file
.If your environment only uses IPv4, you must include an IPv4 loopback address in the
/etc/hosts
file. The following is a sample entry:127.0.0.1 localhost loopback
If your environment only uses IPv6, you must include an IPv6 loopback address in the
/etc/hosts
file.::1 localhost6.localdomain6 localhost6 loopback
If your environment uses both IPv4 and IPv6, the
/etc/hosts
file must include both loopback addresses.127.0.0.1 localhost loopback ::1 localhost6.localdomain6 localhost6 loopback
To create a Primary RVG of an RDS
Run the following command on the host on which you want to create the Primary RVG:
# vradmin -g diskgroup createpri rvgname \ dv01_name,dv02_name... srl_name
The argument rvgname is the name of the RVG to be created.
The argument dv01_name,dv02_name,... is a comma-separated list of the names of the data volumes to be associated to the RVG. Each item can be an independent data volume name, or the name of a volume set. To associate a volume set to the RVG, specify the name of the volume set, not the names of the individual component volumes.
Note:
In previous releases, component volumes could be associated directly to an RVG. Beginning in release 5.0, the volume set itself is associated to the RVG, enabling VVR to verify consistency between the volume sets on the Primary and the Secondary RVGs. The vradmin createpri command fails if a component volume of the volume set and the volume set itself are each specified for an RVG.
The argument srl_name is the name of the SRL to be associated to the RVG.
Use -nodcm option if you do not want DCMs to be added to the data volumes. By default, DCMs are added automatically.