< Previous  | TOC | Index | Next  >

Starting replication of Oracle database volume

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:

• Mode of replication: synchronous=off
• Latency Protection: latencyprot=off
• SRL overflow protection: srlprot_autodcm
• Packet size: packet_size=8400
• Network protocol: protocol=UDP

Method of initial synchronization:

• Automatic synchronization
• Full synchronization with Checkpoint

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

Starting replication using automatic synchronization

 To start replication using automatic synchronization

From the primary site, automatically synchronize the RVG on the secondary site:

vradmin -g disk_group -a startrep pri_rvg sec_host

where:

• disk_group is the disk group on the primary site that VVR will replicate
• pri_rvg is the name of the RVG on the primary site
• sec_host is the virtual host name for the secondary site

For example:

# 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.

Starting replication using full synchronization with Checkpoint

 To start replication using full synchronization with Checkpoint

1. From the primary site, synchronize the RVG on the secondary site with full synchronization (using the -c checkpoint option):

   vradmin -g disk_group -full -c ckpt_name syncrvg pri_rvg sec_host

   where:

   • disk_group is the disk group on the primary site that VVR will replicate
   • ckpt_name is the name of the checkpoint on the primary site
   • pri_rvg is the name of the RVG on the primary site
   • sec_host is the virtual host name for the secondary site

     For example:

     # vradmin -g oradatadg -c rac1_ckpt syncrvg rac1_rvg rac_clus102_priv

2. To start replication after full synchronization, enter:

   # vradmin -g oradatadg -c rac1_ckpt startrep rac1_rvg rac_clus102_priv

Verifying replication status

Verify replication is functioning properly:

1. Use the vxprint command on the primary site:

   vxprint -g diskgroup -l rlink_name

2. Review the 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