Veritas InfoScale™ 7.3.1 Troubleshooting Guide - Solaris

Data volume errors during an RLINK attach

When an RLINK is attached, VVR checks whether for each data volume associated to the Primary RVG, the Secondary RVG has an associated data volume of the same size that is mapped to its counterpart on the Primary. The following example illustrates an attempted attach with every possible problem and how to fix it. Before the attach, the Primary has this configuration:

TY     Name               Assoc        KSTATE     LENGTH       STATE

rv     hr_rvg         -                DISABLED     -          EMPTY

rl     rlk_london_hr_rvg  hr_rvg       DETACHED     -          STALE

v      hr_dv01            hr_rvg       ENABLED    12800        ACTIVE

pl     hr_dv01-01         hr_dv01      ENABLED    12800        ACTIVE

sd     disk01-05          hr_dv01-01   ENABLED    12800         -

v      hr_dv02            hr_rvg       ENABLED    12800        ACTIVE

pl     hr_dv02-01         hr_dv02      ENABLED    12880        ACTIVE

sd     disk01-06          hr_dv02-01   ENABLED    12880

v      hr_dv03            hr_rvg       ENABLED    12880        ACTIVE

pl     hr_dv03-01         hr_dv03      ENABLED    12880        ACTIVE

sd     disk01-07          hr_dv03-01   ENABLED    12880        - 

v      hr_srl             hr_rvg       ENABLED    12880        ACTIVE

pl     hr_srl-01          hr_srl       ENABLED    12880        ACTIVE

sd     disk01-08          hr_srl-01    ENABLED    12880 0      -

The Secondary has the following configuration:

TY     Name               Assoc        KSTATE     LENGTH       STATE

rv     hr_rvg             -            ENABLED    -        -   ACTIVE

rl     rlk_seattle_hr_rvg hr_rvg       ENABLED    -        -   ACTIVE

v      hr_dv01            hr_rvg       ENABLED    12700    -   ACTIVE

pl     hr_dv01-01         hr_dv01      ENABLED    13005    -   ACTIVE

sd     disk01-17          hr_dv01-01   ENABLED    13005    0    -

v      hr_dv2             hr_rvg       ENABLED    12880    -   ACTIVE

pl     hr_dv02-01         vol2         ENABLED    13005    -   ACTIVE

sd     disk01-18          hr_dv02-01   ENABLED    13005    0    - 

v      hr_srl             hr_rvg       ENABLED    12880    -   ACTIVE

pl     hr_srl-01          hr_srl       ENABLED    13005    -   ACTIVE

sd     disk01-19          hr_srl-01    ENABLED    13005    0    -

Note that on the Secondary, the size of volume hr_dv01 is small, hr_dv2 is misnamed (must be hr_dv02), and hr_dv03 is missing. An attempt to attach the Primary RLINK to this Secondary using the attach command fails.

# vxrlink -g hrdg -f att rlk_london_hr_rvg

The following messages display:

VxVM VVR vxrlink INFO V-5-1-3614 Secondary data volumes detected
    with rvg hr_rvg as parent:
VxVM VVR vxrlink ERROR V-5-1-6789 Size of secondary datavol hr_dv01
    (len=12700) does not match size of primary (len=12800)
VxVM VVR vxrlink ERROR V-5-1-3504 primary datavol hr_dv02 is not
    mapped on secondary, yet
VxVM VVR vxrlink ERROR V-5-1-3504 primary datavol hr_dv03 is not
    mapped on secondary, yet

Alternatively, the problem can be fixed by altering the Primary to match the Secondary, or any combination of the two. When the Primary and the Secondary match, retry the attach.

On the Primary:

# vxrlink -g hrdg -f att rlk_london_hr_rvg
VxVM VVR vxrlink WARNING V-5-1-12397 This 
command should only be used if primary and all 
secondaries arealready 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 hr_rvg as parent:
VxVM VVR vxrlink INFO V-5-1-6183 vol1: len=12800 primary_datavol=hr_dv01 
VxVM VVR vxrlink INFO V-5-1-6183 vol1: len=12800 primary_datavol=hr_dv02
VxVM VVR vxrlink INFO V-5-1-6183 vol1: len=12800 primary_datavol=hr_dv03