Volume set configuration errors during modification of an RVG


Volume set configuration errors during modification of an RVG
Prev	Errors during modification of an RVG	Next

If a volume set is associated to the RDS, the name of the volume set on the Secondary must have the same name as the volume set on the Primary in order for replication to occur. In addition, the volume set on the Secondary must have the same component volumes, with the same names, lengths and indices as on the Primary.

If a component volume is resized on the Primary but not on the Secondary, a data volume mismatch error results. Resize the volume and resume replication.

See Data volume mismatch error during modification of an RVG.

The configuration of the Secondary is checked for configuration errors, when an RLINK is attached for the first time. If any errors are found, the vradmin startrep command fails and prints error messages indicating the problem. Correct the configuration error, and then retry the command.

Configuration errors may also occur when you modify a volume set or its component volumes. Run the vxrlink verify rlink command at either node to check whether this has occurred. Correct the configuration error, and then resume the RLINK.

Volume set name mismatch error

If the volume set name differs on the Primary and the Secondary, the following error displays:

VxVM VVR vxrlink ERROR V-5-1-0 VSet name vset_name of secondary datavol
vol_name does not match VSet name vset_name of primary datavol
vol_name

To correct the problem, rename the volume set on either the Primary or the Secondary, using the following command:

# vxedit -g diskgroup rename vset_name new_vset_name

Volume index mismatch error

If the indices for the component volumes on the Primary volume set and the Secondary volume set are different, the following error displays:

VxVM VVR vxrlink ERROR V-5-1-0 VSet index (index_name) of secondary datavol 
vol_name does not match VSet index (index_name) of primary datavol
vol_name

To correct the problem, perform the following steps on the Secondary:

Dissociate each volume from the volume set using the following command:
```
# vxvset -g diskgroup rmvol vset_name compvol_name
```
When you remove the last volume, the volume set is also removed.

Create the volume set using the following command:

# vxvset -g diskgroup -o index make vset_name \ 
  compvol_name index

Associate each of the remaining volumes to the volume set, specifying the index of the corresponding volumes on the Primary using the following command:
```
# vxvset -g diskgroup -o index addvol vset_name  \
  compvol_name index
```

Component volume mismatch error

If a data volume is removed from the volume set on the Primary RVG only or added to the volume set on the Secondary RVG only, the following error displays:

    Secondary datavol vol_name is associated to VSet vol_name
    whereas primary datavol is not associated to any Vset

Similarly, if a data volume is removed from the volume set on the Secondary RVG only or added to the volume set on the Primary RVG only, the following error displays:

    Primary datavol vol_name is associated to VSet whereas secondary
    datavol vol_name is not associated to any Vset

To correct the problem, add or remove data volumes from either the Secondary or the Primary volume sets. The volume sets on the Primary and the Secondary should have the same component volumes.

To add a data volume to a volume set, do one of the following:

To add a data volume to a volume set in an RVG:

# vradmin -tovset vset_name addvol rvg_name vol_name

To remove a data volume in a volume set in an RVG:

# vradmin -fromvset vset_name delvol rvg_name vol_name

Prev	Up	Next
Data volume name mismatch error during modification of an RVG	Home	Recovery on the Primary or Secondary