Starting replication using the vxrds startrep command


Starting replication using the vxrds startrep command
Prev	Administering the RDS using the vxrds command	Next

Use the vxrds startrep to start the replication to the normal or Bunker Secondary host in the RDS, to which the RVG belongs. The sec_host parameter is the name of the Secondary host that is displayed in the output of the vxrds printrvg command.

The startrep command attaches the Secondary host to the Primary to establish a communication link and start replication.

If the Primary becomes unavailable due to a disaster, then use the

vxrds startrep command with the -b option to start replication from the Bunker Primary to the Secondary. In this scenario the vxrds startrep command also switches the RLINKs to point to the Bunker Primary instead of the original Primary.

Syntax for vxrds startrep command

vxrds [-g <diskgroup>] -c <checkpoint>| -f | -forceatt |-autosync|
|-a|-b startrep <local_rvg> <sec_host>

Example

vxrds -g vvrdg -forceatt startrep rvg sec_host

The following table describes the attributes that you can specify with the vxrds startrep command.

Table: Attributes for vxrds startrep command

Option

Description

-autosync or -a

Use this option to automatically synchronize the Secondary data volumes.

-b <startrep>

Use this option to replay pending updates from Bunker Primary to Secondary.

-c <checkpoint>

Use this option to attach the Secondary to the Primary with the specified checkpoint

Note:

This option is not supported when synchronizing a Bunker RVG with the Primary RVG.

-forceatt or -f

Use this option to start replication if the Secondary data volumes contain exactly the same data as the Primary data volumes and therefore there is no need to synchronize the Secondary data volumes.

If the data volumes are not synchronized then the -f option can cause data corruption as replication is started immediately and the Secondary may miss the writes that may have been present on the Replicator Log but did not reach the Secondary. Because there is no way of knowing whether the Replicator Log had some pending writes that have not yet been sent to the Secondary, use this option only if you know that the Secondary is completely up-to-date.

Note:

This option is not supported when synchronizing a Bunker RVG with the Primary RVG.

These attributes are mutually exclusive and only one of these options can be used with the startrep command. The function of these options is similar to the function of the same options available with the vxrlink att command.

Prev	Up	Next
Setting replication attributes	Home	Stopping replication using the vxrds stoprep command