How to manually migrate a replicated volume group in Volume Replicator

book

Article ID: 100039011

calendar_today

Updated On:

Description

Description

This article describes how to manually migrate a replicated volume group (RVG) in Volume Replicator (VVR), without using the vradmin command (vradmin -g [dgname] migrate [rvgname] [remote_host]).

Note: The status of the replication must be consistent, and up-to-date, before a manual migration can take place. 

Reviewing the configuration

Example configuration:
 Primary DG : sydneydg 
 Server : Server101
 Primary RVG : sydney_rvg
 Rlink : to_melbourne

 Secondary DG : melbournedg
 Server : Server102
 Secondary RVG : melbourn_rvg
 Rlink : to_sydney
 

Vxprint output:
 
[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
 

 Checking the replication status:
 
[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

 

Performing the manual migration

1. From Server101:

[Server101 sbin]# vxrvg -g sydneydg stop sydney_rvg
[Server101 sbin]# vxrlink -g sydneydg det to_melbourne
[Server101 sbin]# vxvol -g sydneydg dis sydneysrl
[Server101 sbin]# vxedit -g sydneydg set primary=false sydney_rvg


2. From Server102:

[Server102 sbin]# vxrvg -g melbournedg stop melbourn_rvg
[Server102 sbin]# vxrlink -g melbournedg det to_sydney
[Server102 sbin]# vxvol -g melbournedg dis melbournesrl
[Server102 sbin]# vxedit -g melbournedg set primary=true melbourn_rvg
 

3. From Server101:

[Server101 sbin]# vxvol -g sydneydg aslog sydney_rvg sydneysrl
[Server101 sbin]# vxrvg -g sydneydg start sydney_rvg
[Server101 sbin]# vxrlink -g sydneydg -f att to_melbourne


4. From Server102:

[Server101 sbin]# vxvol -g melbournedg aslog melbourn_rvg melbournesrl
[Server101 sbin]# vxrvg -g melbournedg start melbourn_rvg
[Server101 sbin]# vxrlink -g melbournedg -f att to_sydney

Issue/Introduction

How to manually migrate a replicated volume group in Volume Replicator
Powered by Wolken Software