Extending Veritas Volume Replication Group and filesystem by adding a new disk

Let see how to add 1 TB disk in an existing Veritas RVG (Replicated Volume Group). Assume that there is only one secondary node.

(0) If you need to remove a volume to free up space, see article : 

Veritas VVR - removing a volume from VVR and deleting it from disk group

(1) Confirm Volume Group is replicating.

vradmin -g PrimaryHost_dg -l repstatus PrimaryHost_rvg # Check replication status

(2) Add 1 TB disk in dg on Primary host and confirm free space in dg

vxdisk scandisks  
vxdisk -e list     # Find new disk name - say it is new_disk1
vxdisk list new_disk1 # see detail of new disk
vxdisksetup -i new_disk1
vxdg -g PrimaryHost_dg adddisk PrimaryHost_disk_9=new_disk1  
vxdg -g PrimaryHost_dg  -u h free     # Check free space
vxassist -g PrimaryHost_dg maxsize     # Maximum possible extension (same as above)
vxprint -hrt -g SecondaryHost_dg -u g|grep -i ^v # Check RVG existing size


(3) Add 1 TB disk in dg on Secondary host and confirm free space in dg

vxdisk scandisks  
vxdisk -e list     # Find new disk name - say it is new_disk2
vxdisk list new_disk2 # see detail of new disk
vxdisksetup -i new_disk2
vxdg -g SecondaryHost_dg adddisk SecondaryHost_disk_9=new_disk2 
vxdg -g SecondaryHost_dg  -u h free # Check free space
vxassist -g SecondaryHost_dg maxsize # Maximum possible extension (same as above)
vradmin -g PrimaryHost_dg -l repstatus SecondaryHost_rvg # Check replication status
vxprint -hrt -g SecondaryHost_dg -u g|grep -i ^v # Check RVG existing size

(4) Pause replication, extend RVG and and filesystem, resume replication and verify it

vradmin -g PrimaryHost_dg pauserep PrimaryHost_rvg SecondaryHost-vvr.com   
vradmin -g PrimaryHost_dg resizevol PrimaryHost_rvg Volume_Name +g         
vradmin -g PrimaryHost_dg resumerep PrimaryHost_rvg SecondaryHost-vvr.com  
vradmin -g PrimaryHost_dg -l repstatus PrimaryHost_rvg # Check replication status
df -hP  # check filesystem size

Note: If you get following "WARNING: DCM log size is smaller than recommended due to increased volume size" in above step, you may do following:

  vxedit -g PrimaryHost_dg set srlprot=off  
  vxassist -g PrimaryHost_dg  remove log Volume_Nam
  vxassist -g PrimaryHost_dg remove log Volume_Name
  vxassist -g PrimaryHost_dg addlog Volume_Name logtype=dcm
  (vxassist will allocate the proper DCM size as per new volume size)

  vxedit -g PrimaryHost_dg set srlprt=dcm
Refer : https://support.symantec.com/en_US/article.TECH21427.html