Pausing and Resuming RLINKs

Article:TECH10610  |  Created: 2001-01-12  |  Updated: 2004-01-21  |  Article URL http://www.symantec.com/docs/TECH10610
Article Type
Technical Solution

Environment

Issue



Pausing and Resuming RLINKs

Solution



Pausing an RLINK will prevent new and already-queued updates from reaching the primary or secondary RLINK. An RLINK that has been paused on the primary is referred to as primary-paused, and must be resumed from the primary.  An RLINK that has been paused on the secondary is referred to as secondary-paused, and must be resumed from the secondary.

The KSTATE of an attached and ACTIVE RLINK is CONNECT if the connection with the secondary is currently up. The connection may temporarily go down because of network outages, but will be restored automatically. Primary-pausing the RLINK changes the STATE of the RLINK from ACTIVE to PAUSE, and the KSTATE from CONNECT to ENABLED.

Unlike a primary PAUSE, a secondary PAUSE does not break the network connection between the primary and the secondary. The KSTATE of both the primary and secondary RLINKs will remain in the CONNECT state. The state of both the primary and the secondary RLINK will change from ACTIVE to PAUSE.

A secondary pause can be performed even if the secondary is disconnected from the primary. When the connection is restored, the primary detects that the secondary is paused and will not send updates. Likewise, a secondary resume can be done when the secondary is disconnected. When a connection is reestablished, the primary detects that the secondary is no longer paused and will resume replication.

A primary RLINK has a state of PAUSE if it is primary-paused, secondary-paused, or both. A secondary RLINK with a state of PAUSE must have its secondary_paused flag set.

Below is an example of an primary RLINK in a pause state:

# vxprint -Pl

Disk group: testdg
Rlink:     palday_rlk
info:       timeout=500 packet_size=8400 rid=0.2264
latency_high_mark=10000 latency_low_mark=9950
state:     state=PAUSE
synchronous=off latencyprot=off srlprot=dcm
assoc:   rvg=test_rvg
remote_host=palday IP_addr=10.140.10.22 port=1710
remote_dg=testdg
remote_dg_dgid=969905831.1779.palday
remote_rlink=honolulu_rlk
remote_rlink_rid=0.2938
local_host=honolulu IP_addr=10.140.10.11 port=1710
protocol: tcpip
flags:     write enabled attached primary_paused consistent disconnected

To pause and resume an RLINK

On the Primary:

1. Pause the RLINK.

# vxrlink pause rlink_name

For example,

# vxrlink pause palday_rlk

2. Check the state of the RLINK.

# vxprint rlink_name

For example,

# vxprint palday_rlk

Disk group: testdg
TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
rl palday_rlk   test_rvg     ENABLED  -        -        PAUSE    -       -

3. Resume the RLINK.

# vxrlink resume rlink_name

For example,

# vxrlink resume palday_rlk

vxvm:vxrlink: INFO: Secondary data volumes detected with rvg test_rvg as parent:
vxvm:vxrlink: INFO: test_dv01:    len=102400   primary_datavol=test_dv01

4. Check if the RLINK returns to the correct state.

# vxprint rlink_name

For example,

# vxprint palday_rlk

Disk group: testdg
TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
rl palday_rlk   test_rvg     CONNECT  -        -        ACTIVE   -       -

5. Check if the RLINK catches up.

# vxrlink status rlink_name

For example,

# vxrlink status palday_rlk

Rlink palday_rlk is up to date

To pause and resume a Secondary RLINK:

On the secondary:

1. Pause the RLINK

# vxrlink pause rlink_name

2. Check the status of the RLINK

# vxprint rlink_name

3. Resume the RLINK

# vxrlink resume rlink_name






Legacy ID



235871


Article URL http://www.symantec.com/docs/TECH10610


Terms of use for this information are found in Legal Notices