"VxVM vxvol ERROR V-5-1-7033 Volume <dv_name> is a snapshot volume" appears while running vradmin -g <diskgroup> addsec

book

Article ID: 100032322

calendar_today

Updated On:

Description

Error Message

VxVM vxvol ERROR V-5-1-7033 Volume is a snapshot volume    

Cause

The issue is that the "snap_rid" field of the volume on the secondary wasn't cleared after the disk group was split on the primary.

Steps to reproduce this issue: 
  1. # vxassist -g  snapstart 
  2. # vxrvg -g  -c checkpt_name checkstart 
  3. # vxrvg -g  snapshot 
  4. # vxrvg -g  checkend 
  5. # vxprint -g  -m  | grep snap_rid                           
        snap_rid=0.1033

    The "snap_rid" changed from the default value of 0.0 after taking a snapshot.  

Solution

Clear the "snap_rid" field for the split volume, immediately after the split action, on the primary side. 
  1. # vxdg split   
  2. # vxedit -g  rename  
  3. # vxassist -g  snapclear

    This clears the "snap_rid" field when it is imported on the primary side

Alternatively, clear the "snap_rid" field on the secondary side before running vradmin addsec. 
  1. # vxdg import 
  2. # vxassist -g  snapclear

    This clears the "snap_rid" field when it is imported on secondary side
 

Now, run the vradmin addsec command. 
# vradmin -g  addsec

Cause

The issue is that the "snap_rid" field of the volume on the secondary wasn't cleared after the disk group was split on the primary.

Steps to reproduce this issue: 
  1. # vxassist -g  snapstart 
  2. # vxrvg -g  -c checkpt_name checkstart 
  3. # vxrvg -g  snapshot 
  4. # vxrvg -g  checkend 
  5. # vxprint -g  -m  | grep snap_rid                           
        snap_rid=0.1033

    The "snap_rid" changed from the default value of 0.0 after taking a snapshot.  

Resolution

Clear the "snap_rid" field for the split volume, immediately after the split action, on the primary side. 
  1. # vxdg split   
  2. # vxedit -g  rename  
  3. # vxassist -g  snapclear

    This clears the "snap_rid" field when it is imported on the primary side

Alternatively, clear the "snap_rid" field on the secondary side before running vradmin addsec. 
  1. # vxdg import 
  2. # vxassist -g  snapclear

    This clears the "snap_rid" field when it is imported on secondary side
 

Now, run the vradmin addsec command. 
# vradmin -g  addsec

Issue/Introduction

While attempting to synchronize and start VVR (Veritas Volume Replicator) using the "Diskgroup Split and Join" feature, the vradmin addsec command returns an error, preventing VVR from re-establishing.
Powered by Wolken Software