Setting Up the VVR Configuration
This section details the procedure to set up the VVR configuration using the Sample VVR Configuration. The following table outlines the names that are used by the sample configuration. For more information on configuring VVR, refer to the VERITAS Volume Replicator Administrator's Guide.
Name of Cluster: Seattle
Disk group
|
hrdg
|
Primary RVG
|
hr_rvg
|
Primary RLINK to london1
|
rlk_london_hr_rvg
|
Primary data volume #1
|
hr_dv01
|
Primary data volume #2
|
hr_dv02
|
Primary SRL for hr_rvg
|
hr_srl
|
Cluster IP
|
192.2.40.74
|
Name of Cluster: London
Disk group
|
hrdg
|
Secondary RVG
|
hr_rvg
|
Secondary RLINK to seattle
|
rlk_seattle_hr_rvg
|
Secondary data volume #1
|
hr_dv01
|
Secondary data volume #2
|
hr_dv02
|
Secondary SRL for hr_rvg
|
hr_srl
|
Cluster IP
|
192.2.40.53
|
Note
The example assumes that each of the hosts seattle1 and london1 has a disk group named hrdg with enough free space to create the VVR objects mentioned in the example.
Checking the Deport and Import Operations
Perform the following steps to confirm whether the disk group hrdg can be successfully deported and imported.
-
On host seattle1 run the following command to deport the disk group:
# vxdg deport hrdg
-
On host seattle2 run the following commands to import and deport the disk group:
# vxdg -t import hrdg
# vxdg deport hrdg
-
On host seattle1 run the following command to import the disk group:
# vxdg -t import hrdg
Repeat the step 1 to step 3 on hosts london1 and london2 to ensure that the deport and import commands work correctly.
Note
Also ensure that the /etc/vx/vras/.rdg file on both the Secondary hosts london1 and london2 contains the disk group ID of the Primary's disk group hrdg.
Creating the Secondary Data Volumes
Perform the following steps on host london1:
-
Create the Secondary data volumes.
# vxassist -g hrdg make hr_dv01 4G \
layout=mirror logtype=dcm mirror=2
# vxassist -g hrdg make hr_dv02 4G \
layout=mirror logtype=dcm mirror=2
-
Create the Secondary SRL.
# vxassist -g hrdg make hr_srl 4G mirror=2
Creating the Primary Data Volumes
Perform the following steps on host seattle1:
-
Create the Primary data volumes.
# vxassist -g hrdg make hr_dv01 4G \
layout=mirror logtype=dcm mirror=2
# vxassist -g hrdg make hr_dv02 4G \
layout=mirror logtype=dcm mirror=2
-
Create the Primary SRL.
# vxassist -g hrdg make hr_srl 4G mirror=2
Creating the Primary and Secondary RVGs
Perform the following steps on host seattle1:
-
Create the Primary RVG.
# vradmin -g hrdg createpri hr_rvg \
hr_dv01,hr_dv02 hr_srl
-
Create the Secondary RVG.
# vradmin -g hrdg addsec hr_rvg 192.2.40.74 192.2.40.53 \
prlink=rlk_london_hr_rvg srlink=rlk_seattle_hr_rvg
Note
The RLINKs must point to the virtual IP address for failovers to succeed. The virtual IP address 192.2.40.74 must be able to ping virtual IP address 192.2.40.53 and vice versa.
Mounting the Volumes in the Primary RVG
Perform the steps given below to mount the volumes under the Primary RVG.
-
Create the mount points for the volumes by creating the following directories on seattle1 and seattle2. These directories will be used as mount points for volumes hr_dv01 and hr_dv02 on the VVR Seattle site.
# mkdir /hr_mount01
# mkdir /hr_mount02
-
Create the file system on the volumes under the Primary RVG by using the following command on seattle1:
# mkfs -F vxfs /dev/vx/rdsk/hrdg/hr_dv01
# mkfs -F vxfs /dev/vx/rdsk/hrdg/hr_dv02
-
Mount the volumes in the Primary RVG by using the following command on seattle1:
# mount /dev/vx/dsk/hrdg/hr_dv01 /hr_mount01
# mount /dev/vx/dsk/hrdg/hr_dv02 /hr_mount02
Starting Replication
To start replication run the following command on the host seattle1:
# vradmin -g hrdg -f startrep hr_rvg
Verifying the State of Replication
Verify the replication state between seattle1 and london1 to ensure that VVR is configured correctly. Type the following command on each of the nodes seattle1 and london1:
# vxprint -g hrdg hr_rvg
In the output of this command verify that:
The RVG hr_rvg is in the ENABLED/ACTIVE state.
The RLINKs rlk_london_hr_rvg and rlk_seattle_hr_rvg are in the CONNECT/ACTIVE state.
|