< Previous  | TOC | Index | Next  >

Errors during an RLINK attach

During an RLINK attach, VVR checks for errors in the configuration of data volumes. VVR also checks for errors in the configuration of volume sets, if the RDS has a volume set associated to the RVG.

Data volume errors

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:

The Secondary has the following configuration:

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-0 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

To fix the problem, issue the following commands on the Secondary:

1. Resize the data volume hr_dv01:

   # vradmin -g hrdg resizevol hr_rvg hr_dv01 12800

2. Rename the data volume hr_dv2 to hr_dv02:

   # vxedit -g hrdg rename hr_dv2 hr_dv02

3. Associate a new volume, hr_dv03, of the same size as the Primary data volume hr_dv03.

   # vxassist -g hrdg make hr_dv03 12800

   # vxvol -g hrdg assoc hr_rvg hr_dv03

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 INFO V-5-1-3614 Secondary data volumes detected with rvg hr_rvg as parent:

VxVM VVR vxrlink INFO V-5-1-0 vol1: len=12800 primary_datavol=hr_dv01

VxVM VVR vxrlink INFO V-5-1-0 vol1: len=12800 primary_datavol=hr_dv02

VxVM VVR vxrlink INFO V-5-1-0 vol1: len=12800 primary_datavol=hr_dv03

Volume set errors

If a volume set is associated to an RDS, the name of the volume set on the Primary must have the same name as the volume set on the Secondary, and the volume sets must have the same configuration of component volumes.

When an RLINK is attached, VVR checks whether for each volume set associated to the Primary RVG, the Secondary RVG has an associated volume set of the same name. Also, VVR checks whether the volume sets on the Primary and on the Secondary have the same component volumes with the same names, lengths, and indices. (The volume names of the component volumes can be different on the Primary and Secondary if they are mapped, as for independent volumes.) If any of the component volumes do not exist on the Secondary or have a mismatched name, length, or index, the RLINK attach command fails with the appropriate error message. For details about each of these errors, see the section Volume set configuration errors.

If the volume set does not exist on the Secondary, but all the component volumes exist on the Secondary with the correct names and lengths, VVR creates the volume set on the Secondary and associates it to the RDS. This does not cause a configuration error.