InfoScale™ 9.0 Replication Administrator's Guide - AIX

The vradmin addsec command performs the following operations by default:

• Creates and adds a Secondary RVG of the same name as the Primary RVG to the specified RDS on the Secondary host. By default, the Secondary RVG is added to the disk group with the same name as the Primary disk group. Use the option -sdg with the vradmin addsec command to specify a different disk group on the Secondary.

• If any of the data volumes or the SRL on the Secondary has a DRL, the DRL is removed before the data volume is associated to the RVG. DRLs are not needed with VVR because VVR uses the SRL to recover volumes, not the DRLs.

• Automatically adds DCMs to the Primary and Secondary data volumes if they do not have DCMs. Use the -nodcm option to specify that DCMs are not to be added to the data volumes.

  The -dcmplex option, when used with the vradmin addsec command, changes the configuration to use DCM log plexes instead of DCM logging in DCO for new replication configurations.

  The vradmin addsec command creates the DCM of an appropriate default size based on the size of the volume and mirrors the DCM by default. To create and add a DCM of a size that is different from the default, associate the DCM of the required size to the data volumes before running the vradmin addsec command.

  See Associating a Data Change Map to a data volume in DCO.

• Associates to the Secondary RVG, existing data volumes of the same names and sizes as the Primary data volumes; it also associates an existing volume with the same name as the Primary SRL, as the Secondary SRL.

• If the Primary RVG includes a volume set, the vradmin addsec command associates the corresponding volume set to the Secondary, if the volume set exists on the Secondary. The volume set on the Secondary must include volumes of the same name, lengths and indices as the component volumes on the Primary. If the volume set exists on the Secondary and the volume set configuration is correct except that it does not include all of the component volumes corresponding to those in the volume set on the Primary, the vradmin addsec command attempts to add the remaining component volumes to the volume set on the Secondary and then associate the volume set to the Secondary RVG. This command succeeds if all of the remaining component volumes exist on the Secondary with the same names, lengths, and indices as the component volumes on the Primary. However, if any of the component volumes do not exist on the Secondary or have a mismatched name, length, or index, the vradmin addsec command fails with the appropriate error message.

  If the volume set does not exist on the Secondary, but the component volumes exist with the same names, lengths, and indices, the vradmin addsec command creates the volume set on the Secondary and then associates it to the Secondary RVG.

• Creates and associates to the Primary and Secondary RVGs respectively, the Primary and Secondary RLINKs with default RLINK names rlk_remotehost_rvgname. If you choose to use names other than the default, use the prlink and srlink attributes of the vradmin addsec command to specify the Primary and Secondary RLINK names. To create an encrypted Rlink between the primary and the secondary site, use the -encrypted option with vradmin addsec command. This Rlink transfers the encrypted data from primary to secondary site.

  See Example - Creating a Primary RVG containing a volume set.