When you have both the primary and secondary sites set up for replication, you can start replication from the primary site to the secondary site.
Start with the default replication settings:
Method of initial synchronization:
For for guidelines on modifying these settings and information on choosing the method of replication for the initial synchronization, see the Veritas Volume Replicator Administrator's Guide.
To start replication using automatic synchronization
vradmin -g disk_group -a startrep pri_rvg sec_host
# vradmin -g oradatadg -a startrep rac1_rvg rac_clus102_priv
Because the cluster on the secondary site uses only one host name, the command does not require the sec_host argument. The command starts replication or the transfer of data from the primary site to the secondary site over the network.
To start replication using full synchronization with Checkpoint
-c checkpoint
option):
vradmin -g disk_group -full -c ckpt_name syncrvg pri_rvg sec_host
# vradmin -g oradatadg -c rac1_ckpt syncrvg rac1_rvg rac_clus102_priv
# vradmin -g oradatadg -c rac1_ckpt startrep rac1_rvg rac_clus102_priv
You must verify that replication is functioning properly.
vxprint
command on the primary site:
flags
output for the status. The output may appear as connected
and consistent
. For example:
# vxprint -g oradatadg -l rlk_10.182.13.221_oradatadg
Rlink: rlk_10.182.13.221_oradatadg
info: timeout=500 packet_size=8400 rid=0.1078
latency_high_mark=10000 latency_low_mark=9950
bandwidth_limit=none
state: state=ACTIVE
synchronous=off latencyprot=off srlprot=autodcm
.
protocol: UDP/IP
checkpoint: rac1_ckpt
flags: write enabled attached consistent connected asynchronous