We recommend that you use the same name for a data volume in a Primary RVG and the corresponding data volume in a Secondary RVG. However, each Secondary data volume can have a different name from that of the corresponding Primary data volume. The Primary does not know whether the name is mapped to a different name at any given Secondary. The name mapping information is maintained entirely at the Secondary. To facilitate name-mapping, each data volume associated to an RVG has a
primary_datavol field. This field can be set to the name of the corresponding data volume on the Primary.
By default, global mapping is in effect, that is, the
primary_datavol field is not used on any Secondary data volumes. This requires that all the Secondary data volumes have the same names as used on the Primary.
One of the prerequisites for adding a Secondary using the
addsec command is that data volumes of the same names and lengths as the Primary must exist on the Secondary. When adding a Secondary using the
addsec command, the Secondary data volumes cannot have different names from that of the corresponding Primary data volumes.
If you use different names for the Secondary data volumes and their corresponding Primary data volumes, the
migrate command does not set the
primary_datavol field on the new Primary after transferring the Primary role. To facilitates seamless transfer of the Primary role, make sure you set the
primary_datavol field of the Primary data volumes, in addition to the Secondary. Note that you can use the
vradmin command to perform all other VVR operations in a configuration containing differently named volumes on the Primary and Secondary.
There are two ways to set the
primary_datavol field on a Secondary data volume. In the examples that follow, the commands are executed only on the Secondary. The Secondary data volume is called
secondaryname-dv_name, and the corresponding Primary data volume name is
vxedit -g diskgroup
-moption on the
vxvol -g diskgroup
-m assoc rvg_name
primary_datavolfield for a volume using
vxprint -g diskgroup -l secondaryname-dv_name
If any volume (on the Primary or a Secondary) is associated with an RVG (as an SRL or a data volume), the
-l listing for that volume will indicate the RVG name on the output line beginning with
assoc:, as shown above.