Setting up VVR configuration that uses different diskgroup, or volume, names on each node

book

Article ID: 100039010

calendar_today

Updated On:

Description

This article discusses a procedure for setting up a VVR (Veritas Volume Replicator) configuration that uses different diskgroup, or volume, names on each node.

Site 1:
Location/Server name: sydney / Server101

Attribute	Value
DGName	sydneydg
Primary RVG	sydney_rvg
Primary RLINK to melbourne	to_melbourne
Primary Data Volume	sydneyvol
Primary SRL for sydney_rvg	sydnesrl
IP	192.168.10.101

Site 2:
Location/Server name: melbourne / Server102

Attribute	Value
DGName	melbournedg
Primary RVG	melbourn_rvg
Primary RLINK to melbourne	to_sydney
Primary Data Volume	melbournevol
Primary SRL for sydney_rvg	melbournesrl
IP	192.168.10.102

1. From Server102:

[Server102 sbin]# vxdisk list
DEVICE TYPE DISK GROUP STATUS
disk_4 auto:cdsdisk - - online
disk_5 auto:cdsdisk - - online
disk_6 auto:cdsdisk - - online
disk_7 auto:cdsdisk - - online
disk_8 auto:cdsdisk - - online
disk_9 auto:cdsdisk - - online
disk_10 auto:cdsdisk - - online
sda auto:none - - online invalid
[Server102 sbin]# vxdg init melbournedg melbournedg01=disk_4 melbournedg02=disk_5 melbournedg03=disk_6
[Server102 sbin]# vxassist -g melbournedg make melbournevol 300m layout=mirror logtype=dcm mirror=2
[Server102 sbin]# vxassist -g melbournedg make melbournesrl 200m mirror=2
[Server102 sbin]# vradmin -g melbournedg createpri melbourn_rvg melbournevol melbournesrl
[Server102 sbin]# vxedit -g melbournedg set primary=false melbourn_rvg
[Server102 sbin]# vxprint -htg melbournedg
.......
dg melbournedg default default 0 1482448745.21.Server102

dm melbournedg01 disk_4 auto 65536 2027264 -
dm melbournedg02 disk_5 auto 65536 2027264 -
dm melbournedg03 disk_6 auto 65536 2027264 -

rv melbourn_rvg 0 ENABLED ACTIVE secondary 1 melbournesrl
v melbournevol melbourn_rvg ENABLED ACTIVE 614400 SELECT - fsgen
pl melbournevol-01 melbournevol ENABLED ACTIVE 614400 CONCAT - RW
sd melbournedg01-01 melbournevol-01 melbournedg01 32 614400 0 disk_4 ENA
pl melbournevol-02 melbournevol ENABLED ACTIVE 614400 CONCAT - RW
sd melbournedg02-01 melbournevol-02 melbournedg02 32 614400 0 disk_5 ENA
pl melbournevol-03 melbournevol ENABLED ACTIVE LOGONLY CONCAT - RW
sd melbournedg01-02 melbournevol-03 melbournedg01 0 32 LOG disk_4 ENA
pl melbournevol-04 melbournevol ENABLED ACTIVE LOGONLY CONCAT - RW
sd melbournedg02-02 melbournevol-04 melbournedg02 0 32 LOG disk_5 ENA
v melbournesrl melbourn_rvg ENABLED ACTIVE 409600 SELECT - SRL
pl melbournesrl-01 melbournesrl ENABLED ACTIVE 409600 CONCAT - RW
sd melbournedg03-01 melbournesrl-01 melbournedg03 0 409600 0 disk_6 ENA
pl melbournesrl-02 melbournesrl ENABLED ACTIVE 409600 CONCAT - RW
sd melbournedg01-03 melbournesrl-02 melbournedg01 614432 409600 0 disk_4 ENA

2. From Server101:

[Server101 sbin]# vxdisk -o alldgs list
disk_4 auto:cdsdisk - - online
disk_5 auto:cdsdisk - - online
disk_6 auto:cdsdisk - - online
disk_7 auto:cdsdisk - - online
disk_8 auto:cdsdisk - - online
disk_9 auto:cdsdisk - - online
sda auto:none - - online invalid
[Server101 sbin]# vxdg init sydneydg sydneydg01=disk_4 sydneydg02=disk_5 sydneydg03=disk_6
[Server101 sbin]# vxassist -g sydneydg make sydneyvol 300m layout=mirror logtype=dcm mirror=2
[Server101 sbin]# vxassist -g sydneydg make sydneysrl 200m mirror=2
[Server101 sbin]# vradmin -g sydneydg createpri sydney_rvg sydneyvol sydneysrl
[Server101 sbin]# vxprint -htg sydneydg
.........
dg sydneydg default default 6000 1482448609.16.Server101

dm sydneydg01 disk_4 auto 65536 2027264 -
dm sydneydg02 disk_5 auto 65536 2027264 -
dm sydneydg03 disk_6 auto 65536 2027264 -

rv sydney_rvg 0 ENABLED ACTIVE primary 1 sydneysrl
v sydneyvol sydney_rvg ENABLED ACTIVE 614400 SELECT - fsgen
pl sydneyvol-01 sydneyvol ENABLED ACTIVE 614400 CONCAT - RW
sd sydneydg01-01 sydneyvol-01 sydneydg01 32 614400 0 disk_4 ENA
pl sydneyvol-02 sydneyvol ENABLED ACTIVE 614400 CONCAT - RW
sd sydneydg02-01 sydneyvol-02 sydneydg02 32 614400 0 disk_5 ENA
pl sydneyvol-03 sydneyvol ENABLED ACTIVE LOGONLY CONCAT - RW
sd sydneydg01-02 sydneyvol-03 sydneydg01 0 32 LOG disk_4 ENA
pl sydneyvol-04 sydneyvol ENABLED ACTIVE LOGONLY CONCAT - RW
sd sydneydg02-02 sydneyvol-04 sydneydg02 0 32 LOG disk_5 ENA
v sydneysrl sydney_rvg ENABLED ACTIVE 409600 SELECT - SRL
pl sydneysrl-01 sydneysrl ENABLED ACTIVE 409600 CONCAT - RW
sd sydneydg03-01 sydneysrl-01 sydneydg03 0 409600 0 disk_6 ENA
pl sydneysrl-02 sydneysrl ENABLED ACTIVE 409600 CONCAT - RW
sd sydneydg01-03 sydneysrl-02 sydneydg01 614432 409600 0 disk_4 ENA
[Server101 sbin]#

3. On each node, add the dgid for the other node to the /etc/vx/vras/.rdg file.

For this example:

Add the dgid for the melbournedg diskgroup (1482448745.21.Server102) to /etc/vx/vras/.rdg on Server101.
Add the dgid for the sydneydg diskgroup (1482448609.16.Server101) to /etc/vx/vras/.rdg on Server102.

4. Create, associate and edit the rlink. Then, set primary volume and attach it, on Server102.

[Server102 sbin]# vxmake -g melbournedg rlink to_sydney remote_host=Server101 remote_rlink=to_melbourne
[Server102 sbin]# vxrlink -g melbournedg assoc melbourn_rvg to_sydney
[Server102 sbin]# vxedit set -g melbournedg remote_host=Server101 local_host=Server102 remote_dg=sydneydg remote_rlink=to_melbourne remote_dg_dgid=1482448609.16.Server101 to_sydney
[Server102 sbin]# vxedit set -g melbournedg primary_datavol=sydneyvol melbournevol
[Server102 sbin]# vxrlink -g melbournedg -f att to_sydney

5. Create, associate and edit the rlink. Then, attach to to Server101.

[Server101 sbin]# vxmake -g sydneydg rlink to_melbourne remote_host=Server102 remote_rlink=to_sydney
[Server101 sbin]# vxrlink -g sydneydg assoc sydney_rvg to_melbourne
[Server101 sbin]# vxedit set -g sydneydg remote_host=Server102 local_host=Server101 remote_dg=melbournedg remote_rlink=to_sydney remote_dg_dgid=1482448745.21.Server102 to_melbourne
[Server101 sbin]# vxrlink -g sydneydg -f att to_melbourne
VxVM VVR vxrlink WARNING V-5-1-12397 This command should only be used if primary and all secondaries are already synchronized. If this is not the case detach the rlink and use autosync or checkpoint options to attach.
VxVM VVR vxrlink INFO V-5-1-3614 Secondary data volumes detected with rvg melbourn_rvg as parent:
VxVM VVR vxrlink INFO V-5-1-6183 melbournevol: len=614400 primary_datavol=sydneyvol
[Server101 sbin]# vxprint -Pl -g sydneydg
Rlink: to_melbourne
info: timeout=500 rid=0.1074
latency_high_mark=10000 latency_low_mark=9950
bandwidth_limit=none
state: state=ACTIVE
synchronous=off latencyprot=off srlprot=autodcm
assoc: rvg=sydney_rvg
remote_host=Server102 IP_addr=192.168.10.102 port=4145
remote_dg=melbournedg
remote_dg_dgid=1482448745.21.Server102
remote_rvg_version=40
remote_rlink=to_sydney
remote_rlink_rid=0.1074
local_host=Server101 IP_addr=192.168.10.101 port=4145
protocol: TCP/IP
flags: write enabled attached consistent connected asynchronous

[Server101 sbin]# vradmin -g sydneydg repstatus sydney_rvg
Replicated Data Set: sydney_rvg
Primary:
Host name: Server101
RVG name: sydney_rvg
DG name: sydneydg
RVG state: enabled for I/O
Data volumes: 1
VSets: 0
SRL name: sydneysrl
SRL size: 200.00 M
Total secondaries: 1
Secondary:
Host name: Server102
RVG name: melbourn_rvg
DG name: melbournedg
Data status: consistent, up-to-date
Replication status: replicating (connected)
Current mode: asynchronous
Logging to: SRL
Timestamp Information: behind by 0h 0m 0s

6. Stop replication, and perform a full resynchronization, if it is needed.

[Server101 sbin]# vradmin -g sydneydg stoprep sydney_rvg
VxVM VVR vradmin WARNING V-5-52-285 Secondary or Bunker will become out-of-date.
vradmin: Continue with stoprep (y/n)? y
[Server101 sbin]# vradmin -g sydneydg -a startrep sydney_rvg
Message from Primary:
VxVM VVR vxrlink WARNING V-5-1-3359 Attaching rlink to non-empty rvg. Autosync will be performed.
VxVM VVR vxrlink INFO V-5-1-3614 Secondary data volumes detected with rvg melbourn_rvg as parent:
VxVM VVR vxrlink INFO V-5-1-6183 melbournevol: len=614400 primary_datavol=sydneyvol
VxVM VVR vxrlink INFO V-5-1-3365 Autosync operation has started
[Server101 sbin]# vradmin -g sydneydg repstatus sydney_rvg
Replicated Data Set: sydney_rvg
Primary:
Host name: Server101
RVG name: sydney_rvg
DG name: sydneydg
RVG state: enabled for I/O
Data volumes: 1
VSets: 0
SRL name: sydneysrl
SRL size: 200.00 M
Total secondaries: 1
Secondary:
Host name: Server102
RVG name: melbourn_rvg
DG name: melbournedg
Data status: inconsistent
Replication status: resync in progress (autosync)
Current mode: asynchronous
Logging to: DCM (contains 29440 Kbytes) (autosync)
Timestamp Information: N/A

Issue/Introduction

Setting up VVR configuration that uses different diskgroup, or volume, names on each node

Was this article helpful?

thumb_up Yes

thumb_down No

Welcome to "KB Articles"