Veritas replication - Volume in RVG is in DETACHED DETACH state
It may happen in following cases:
- Either one of disk used in disk group has failed
- Or one of disk has lost all path at DMP level
In this case, volume has been detached from RVG and status will be something like below:
# vxprint | grep DETACHED
v product_vol product_rvg DETACHED DETACH 2306777088 SELECT - fsgen
>> Resolve underlying disk issue
>> Stop replication on problematic system/site
# vradmin -g product_dg stoprep product_rvg secondary-vvr-host
>> On , remove 'DETACHED DETACH' volume from the rvg ( if it fails, proceed to next steps)
# vradmin -g product_dg -f delvol product_rvg product_vol
>> Remove the DCM log from the removed volume
# vxassist -g product_dg remove log product_vol
>> If VVR running under VCS, offline RVGLogOwner and RVGShredGroup from all nodes
# hagrp -offline RVGLogOwner -sys node-a
# hagrp -offline RVGLogOwner -sys node-b
# hagrp -offline RVGShredGroup -sys node-a
# hagrp -offline RVGShredGroup -sys node-b
>>Else, stop RVG and VVR
# vxrvg -g product_dg stop product_rvg
>> start volume
# vxvol -g product_dg -f start product_vol
>> On secondary, add DCM log back
# vxassist -g disk_group addlog vol_name logtype=dcm nlog=1
>> Add the volume to the RVG on secondary
# vradmin -g product_dg addvol product_rvg product_vol
>> On primary, start the autoresynchronization (UNFORTUNATELY, you need to sync whole volume !)
# vradmin -g product_dg -a startrep product_rvg secondary-vvr-host
# vradmin -g product_dg pauserep product_rvg
>> Restrict bandwidth limit if you are replicaton across DC
# vradmin -g product_dg set product_rvg secondary-vvr-host bandwidth_limit=50mbps
>> Resume replication
# vradmin -g product_dg resumerep product_rvg
>> Monitor replication status
# vxrlink -g product_dg status -i 5 rlk_secondary-vvr-host
Reference :
-Symantec tech note
- Description of important fields displayed by the
It may happen in following cases:
- Either one of disk used in disk group has failed
- Or one of disk has lost all path at DMP level
In this case, volume has been detached from RVG and status will be something like below:
# vxprint | grep DETACHED
v product_vol product_rvg DETACHED DETACH 2306777088 SELECT - fsgen
Solution
>> Check /var/log/message and 'vxdisk list' output to check which disks is causing problem.>> Resolve underlying disk issue
>> Stop replication on problematic system/site
# vradmin -g product_dg stoprep product_rvg secondary-vvr-host
>> On , remove 'DETACHED DETACH' volume from the rvg ( if it fails, proceed to next steps)
# vradmin -g product_dg -f delvol product_rvg product_vol
>> Remove the DCM log from the removed volume
# vxassist -g product_dg remove log product_vol
>> If VVR running under VCS, offline RVGLogOwner and RVGShredGroup from all nodes
# hagrp -offline RVGLogOwner -sys node-a
# hagrp -offline RVGLogOwner -sys node-b
# hagrp -offline RVGShredGroup -sys node-a
# hagrp -offline RVGShredGroup -sys node-b
>>Else, stop RVG and VVR
# vxrvg -g product_dg stop product_rvg
# /etc/init.d/vras-vradmind.sh stop
>> start volume
# vxvol -g product_dg -f start product_vol
>> On secondary, add DCM log back
# vxassist -g disk_group addlog vol_name logtype=dcm nlog=1
>> Add the volume to the RVG on secondary
# vradmin -g product_dg addvol product_rvg product_vol
>> On primary, start the autoresynchronization (UNFORTUNATELY, you need to sync whole volume !)
# vradmin -g product_dg -a startrep product_rvg secondary-vvr-host
# vradmin -g product_dg pauserep product_rvg
>> Restrict bandwidth limit if you are replicaton across DC
# vradmin -g product_dg set product_rvg secondary-vvr-host bandwidth_limit=50mbps
>> Resume replication
# vradmin -g product_dg resumerep product_rvg
>> Monitor replication status
# vxrlink -g product_dg status -i 5 rlk_secondary-vvr-host
Reference :
-Symantec tech note
- Description of important fields displayed by the
vradmin
repstatus
command
No comments:
Post a Comment