Veritas NetBackup™ for SAP Administrator's Guide

To configure the volume replicator primary (production database host)

1. Attach the external primary disk D1 to the volume replicator primary, and create a VM disk group using the following command:

   root@primary# vxdg init diskgroup [cds=on|off] diskname=devicename

2. Create a data volume in primary disk D1 using the following command:

   root@primary# vxassist -g diskgroup make volume size

   By default, it creates two copies that require two disks in one group. To override the default, enter the following command:

   root@primary # vxassist -g diskgroup addlog volume logtype=dcm nlog=1

3. Create the VxFS file system on this volume and mount it using the following commands:

   root@primary# mkfs -F vxfs /dev/vx/rdsk/diskgroup/volume 
   root@primary# mount -F vxfs /dev/vx/dsk/diskgroup/volume mnt

4. Create the SAP production database on this volume.
5. Create a Storage Replicator Log (SRL) volume in primary disk D1 using the following command:

   root@primary# vxassist -g diskgroup make volume_srl size

To configure the volume replicator secondary (alternate client off-host)

1. Attach the external replication disk D2 to the volume replicator secondary and create the VM disk group using the following command:

   root@secondary# vxdg init diskgroup [cds=on|off] diskname=devicename

2. Create a data volume in replication disk D2 using the following command:

   root@secondary # vxassist -g diskgroup make volume size

   By default, it creates two copies that require two disks in one group. To override the default, enter the following command:

   root@secondary# vxassist -g diskgroup addlog volume logtype=dcm nlog=1

3. Create a Storage Replicator Log (SRL) volume in the replication disk D2 using the following command:

   root@secondary# vxassist -g diskgroup make volume_srl size

4. Create the primary replicated volume group (RVG) specifying the data volume(s) and the SRL volume. On the volume replicator primary (production database host), run the following command:

   The names of the disk group and volumes must be same as on the primary host.

   root@primary# vradmin -g diskgroup createpri rvg_name data_volumes(s) srl_volume

5. Ensure that authentication can complete.

   Before you add a new secondary host (by using the addsec) or overwrite data on a remote host (by using the syncvol), vradmin performs some authentication. This process checks that the /etc/vx/vras/.rdg file on the remote host contains an entry for the primary disk group ID. The vradmin addsec or syncvol command fails if the /etc/vx/vras/.rdg file on the remote host does not have such an entry.

   If authentication cannot complete, do the following:

   • Add the primary disk group ID to the /etc/vx/vras/.rdg file on the remote host.

   • To find disk group ID, run the vxprint -l diskgroup_name command on the primary.

   • Ensure that the /etc/hosts file has entries of primary and secondary host names in both hosts.

6. Add the secondary RVG to form the replicated data set (RDS) using the following command:

   root@primary# vradmin -g diskgroup addsec rvg_name primary_hostname secondary_hostname

7. Start replication between the volume replicator primary and secondary using the following command:

   root@primary# vradmin -g group_1 -a startrep v1_rvg

8. Attach the external mirror disk D3 to the alternate client for taking a snapshot mirror.
9. On the volume replicator secondary (alternate client off-host), start the snap for the data volume using the following command:

   root@secondary# vxassist  - g diskgroup -b snapstart volume