This section describes how to use the vradmin addvol command to add a volume to a RDS. The vradmin addvol command can also be used to add a volume set to a RDS, or to add a component volume to a volume set that is associated to an RDS. A component volume of a volume set cannot be added to the RDS directly.
You can use the vradmin addvol command to add a volume to a RDS even when replication is in progress. This command associates a volume to all the RVGs of the RDS. Note that volumes of the same name and same length must exist on all Secondaries and the Primary of the RDS. You must create volumes of the required layout on the Secondary and Primary hosts before issuing the vradmin addvol command. If necessary, the vradmin addvol command can be used to add a volume to an RDS that only has a Primary RVG. In this case, there are no Secondary volumes.
By default, the vradmin addvol command adds DCM logs to the data volumes being added to the RDS, if they have not already been added. If any of the data volumes contains a DRL log, the vradmin addvol command removes the DRL log before adding the DCM to the data volume.
The -nodcm option with the vradmin addvol command adds data volumes to the RDS without adding DCMs to the data volumes. If any of the data volumes has a DRL, the DRL is removed before the data volume is associated with the RVG. If -nodcm is issued when any of the RLINKs has srlprot set to dcm or autodcm, and any of the data volumes being added to the RDS does not already have a DCM log, the command will fail.
Before adding a volume, the vradmin addvol command displays a warning and prompts the user to confirm whether or not the Primary and Secondary volumes contain the same data. Verify that the Primary and Secondary volumes contain the same data before adding a volume.
Prerequisites for adding a volume to an RDS:
# vradmin -g diskgroup addvol local_rvgname volume_name