Starting replication of the primary site database volume to the secondary site using VVR


Starting replication of the primary site database volume to the secondary site using VVR
Prev	Configuring a global cluster with Volume Replicator and Storage Foundation Cluster File System High Availability or Storage Foundation for Oracle RAC	Next

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
Storage Replicator Log (SRL) overflow protection: srlprot=autodcm
Packet size: packet_size=8400
Network protocol: protocol=TCP

Method of initial synchronization:

Automatic synchronization
Full synchronization with Storage Checkpoint

For guidelines on modifying these settings and information on choosing the method of replication for the initial synchronization:

See the Veritas InfoScale™ Replication Administrator's Guide

Use the vradmin command to start replication or the transfer of data from the primary site to the secondary site over the network. Because the cluster on the secondary site uses only one host name, the command does not require the sec_host argument.

To start replication using automatic synchronization

From the primary site, use the following command to automatically synchronize the Replicated Volume Group (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 Replicated Volume Group (RVG) on the primary site
- sec_host is the virtual host name for the secondary site
For example:
```
# vradmin -g dbdatadg -a startrep dbdata_rvg clus2
```

Use the vradmin command with the Storage Checkpoint option to start replication using full synchronization with Storage Checkpoint.

To start replication using full synchronization with Storage Checkpoint

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 Storage 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 dbdatadg -c dbdata_ckpt syncrvg dbdata_rvg clus2
```
To start replication after full synchronization, enter the following command:
```
# vradmin -g dbdatadg -c dbdata_ckpt startrep dbdata_rvg clus2
```

Verify that replication is properly functioning.

To verify replication status

Check the status of VVR replication:

# vradmin -g disk_group_name repstatus rvg_name

Review the flags output for the status. The output may appear as connected and consistent. For example:

# vxprint -g dbdatadg -l rlk_clus2_dbdata_rvg
  Rlink: rlk_clus2_dbdata_rvg
  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: dbdata_ckpt
  flags: write enabled attached consistent connected
 asynchronous

Prev	Up	Next
Setting up the disk group on secondary site for replication	Home	Configuring Cluster Server to replicate the database volume using VVR