I cannot tell what your secondary is from the output - you need to show

vxprint -VPl

Rlink rlk_192.168.253.32_DG-RVG is just a name and it may represent replicating TO or FROM IP 192.168.253.32 or technically may not involve 192.168.253.32 at all.  Normally for vradmin commands you don't need to specify the secondary if you only have 1 secondary, but from the manual it does appear that sechost is required, but you could try without.  You could also try using hostnames if "vxprint -VPl" shows the hostnames.

Mike

# vxprint -VPl
Disk group: DG

Rlink:    rlk_192.168.253.32_DG-RVG
info:     timeout=500 rid=0.1065
          latency_high_mark=10000 latency_low_mark=9950
          bandwidth_limit=none
state:    state=ACTIVE
          synchronous=off latencyprot=off srlprot=autodcm
assoc:    rvg=DG-RVG
          remote_host=192.168.253.32 IP_addr=192.168.253.32 port=4145
          remote_dg=DG
          remote_dg_dgid=1354266201.11.node2
          remote_rvg_version=40
          remote_rlink=rlk_192.168.253.31_DG-RVG
          remote_rlink_rid=0.1062
          local_host=192.168.253.31 IP_addr=192.168.253.31 port=4145
protocol: TCP/IP
flags:    write enabled attached consistent connected

Rvg:      DG-RVG
info:     rid=0.1058 version=2 rvg_version=40 last_tag=1
state:    state=CLEAN kernel=DISABLED
assoc:    datavols=DATA-VOL
          srl=DATA-VOL-SRL
          rlinks=rlk_192.168.253.32_DG-RVG
          exports=(none)
          vsets=(none)
att:      rlinks=rlk_192.168.253.32_DG-RVG
flags:    closed secondary disabled detached logging
device:   minor=23002 bdev=199/23002 cdev=199/23002 path=/dev/vx/dsk/DG/DG-RVG
perms:    user=root group=root mode=0600
 

========================================================

Without Secondary:

# vradmin -g DG verifydata DG-RVG cache=vvrcacheobj
VxVM VVR vradmin ERROR V-5-52-19 Incorrect number of arguments
VxVM VVR vradmin INFO V-5-52-183
Usage: vradmin [-g diskgroup] [-k {snap | cache}] verifydata rvg sechost {cache=cacheobj | cachesize=size}
 

The output of vxprint -VPl, shows the rlink is detached and is using logging.  I think the command should work when the rlink is detached as the man page says it can be used while replication is running (rlink attached) or stopped (rlink detached) so your problem, is probably "logging" as I think this means the DCM is being used (use vradmin repstatus to confirm DCM is been used) and if DCM is being used, then you would expect volumes to be different.

Also, the advanage of "vradmin verifydata" is that is can be used when replication is running, but if replication is stopped, you can use "vradmin -verify syncrvg", but I guess this may also have problems if the DCM is active.

Mike

Command ran:

Actually for some reason the DR was primary and Primary was DR. Thats why the secondary IP should be 192.168.253.32

=================================

But now one question :

After verifying the data should the below part be remove from the vxprint result ? OR we need to remove this manually ?

v  DATA-VOL_dcl gen          ENABLED  67840    -        ACTIVE   -       -
pl DATA-VOL_dcl-01 DATA-VOL_dcl ENABLED 67840  -        ACTIVE   -       -
sd DG01-03      DATA-VOL_dcl-01 ENABLED 67840  0        -        -       -
pl DATA-VOL_dcl-02 DATA-VOL_dcl ENABLED 67840  -        ACTIVE   -       -
sd DG02-03      DATA-VOL_dcl-02 ENABLED 67840  0        -        -       -

co vvrcacheobj  -            ENABLED  -        -        ACTIVE   -       -
v  cachevol     vvrcacheobj  ENABLED  10485760 -        ACTIVE   -       -
pl cachevol-01  cachevol     ENABLED  10485760 -        ACTIVE   -       -
sd DG03-01      cachevol-01  ENABLED  10485760 0        -        -       -

The man page says:

By default, this command destroys the snapshot volumes and the cache object after data verification has completed successfully.

To preserve the cache object, but not the snapshots that are configured on it, specify the -k cache option.

To preserve both the cache object and the snapshots, specify the -k snap option.

Thanks Mike for your kind reply:

I ran the below command and the DCO/DCL enteries removed from the vxprint result

• vxsnap unprepare vol_name

in my case # vxsnap -g DG unprepare DATA-VOL

---------------------------------------------------------------------------------------------------

Now I want to remove the cache object but could not understand howto remove cache object "CO" above the Volume(cachevol in my case)

Thanks Mike I did all things manual to remove the required things....Marking Solution +thumb :)

Below are the activities which I did at "both Sites"(Primary and DR) to create a Space Optimize Snap to verify the Data at DR Site:

# vxsnap -g disk_group prepare volume_name

# vxsnap -g DG prepare DATA-VOL

# vxassist -g disk_group make cache_volume_name cache_volume_size

# vxassist -g DG make cachevol 5g

# vxmake -g disk_group cache cache_object_name cachevolname=cache_volume_name autogrow=on

# vxmake -g DG cache vvrcacheobj cachevolname=cachevol autogrow=on

# vxcache -g disk_group start cache_object_name

# vxcache -g DG start vvrcacheobj

This command we need to run at Primary Site

# vradmin -g disk_group verifydata rvg_name secondary_host cache=cache_object_name

# vradmin -g DG verifydata DG-RVG 192.168.253.32 cache=vvrcacheobj

====================

To revert all the changes under vxprint which produced from the above activitiy of verifying the DR Site DATA. Below are the activities we need to perform at "both sites"

vxcache stop vvrcacheobj                
vxcache dis cachevol
vxedit rm vvrcacheobj
vxassist remove volume cachevol

• Example vxprint result

# vxprint
Disk group: DG

TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
dg DG           DG           -        -        -        -        -       -

dm DG01         sdb          -        20802640 -        -        -       -
dm DG02         sdc          -        20802640 -        -        -       -
dm DG03         sdd          -        20802640 -        -        -       -

rv DG-RVG       -            DISABLED -        -        CLEAN    -       -
rl rlk_192.168.253.31_DG-RVG DG-RVG CONNECT -  -        ACTIVE   -       -
v  DATA-VOL     DG-RVG       ENABLED  16777216 -        ACTIVE   -       -
pl DATA-VOL-01  DATA-VOL     ENABLED  16777216 -        ACTIVE   -       -
sd DG01-01      DATA-VOL-01  ENABLED  16777216 0        -        -       -
pl DATA-VOL-02  DATA-VOL     ENABLED  LOGONLY  -        ACTIVE   -       -
sd DG01-02      DATA-VOL-02  ENABLED  288      LOG      -        -       -
pl DATA-VOL-03  DATA-VOL     ENABLED  LOGONLY  -        ACTIVE   -       -
sd DG02-01      DATA-VOL-03  ENABLED  288      LOG      -        -       -
dc DATA-VOL_dco DATA-VOL     -        -        -        -        -       -
v  DATA-VOL_dcl gen          ENABLED  67840    -        ACTIVE   -       -
pl DATA-VOL_dcl-01 DATA-VOL_dcl ENABLED 67840  -        ACTIVE   -       -
sd DG01-03      DATA-VOL_dcl-01 ENABLED 67840  0        -        -       -
pl DATA-VOL_dcl-02 DATA-VOL_dcl ENABLED 67840  -        ACTIVE   -       -
sd DG02-03      DATA-VOL_dcl-02 ENABLED 67840  0        -        -       -
v  DATA-VOL-SRL DG-RVG       ENABLED  16777216 SRL      ACTIVE   -       -
pl DATA-VOL-SRL-01 DATA-VOL-SRL ENABLED 16777216 -      ACTIVE   -       -
sd DG02-02      DATA-VOL-SRL-01 ENABLED 16777216 0      -        -       -

co vvrcacheobj  -            ENABLED  -        -        ACTIVE   -       -
v  cachevol     vvrcacheobj  ENABLED  10485760 -        ACTIVE   -       -
pl cachevol-01  cachevol     ENABLED  10485760 -        ACTIVE   -       -
sd DG03-01      cachevol-01  ENABLED  10485760 0        -        -       -
 

• First command will disable the CO

example:

co vvrcacheobj  -            DISABLED -        -        ACTIVE   -       -

• Second command will diassociate the cachevol from the RVG

example:

v  cachevol     fsgen        ENABLED  10485760 -        ACTIVE   -       -
pl cachevol-01  cachevol     ENABLED  10485760 -        ACTIVE   -       -
sd DG03-01      cachevol-01  ENABLED  10485760 0        -        -       -

rv DG-RVG       -            ENABLED  -        -        ACTIVE   -       -
rl rlk_192.168.253.31_DG-RVG DG-RVG CONNECT -  -        ACTIVE   -       -
v  DATA-VOL     DG-RVG       ENABLED  16777216 -        ACTIVE   -       -
pl DATA-VOL-01  DATA-VOL     ENABLED  16777216 -        ACTIVE   -       -
sd DG01-01      DATA-VOL-01  ENABLED  16777216 0        -        -       -
pl DATA-VOL-02  DATA-VOL     ENABLED  LOGONLY  -        ACTIVE   -       -
sd DG01-02      DATA-VOL-02  ENABLED  288      LOG      -        -       -
pl DATA-VOL-03  DATA-VOL     ENABLED  LOGONLY  -        ACTIVE   -       -
sd DG02-01      DATA-VOL-03  ENABLED  288      LOG      -        -       -
dc DATA-VOL_dco DATA-VOL     -        -        -        -        -       -
v  DATA-VOL_dcl gen          ENABLED  67840    -        ACTIVE   -       -
pl DATA-VOL_dcl-01 DATA-VOL_dcl ENABLED 67840  -        ACTIVE   -       -
sd DG01-03      DATA-VOL_dcl-01 ENABLED 67840  0        -        -       -
pl DATA-VOL_dcl-02 DATA-VOL_dcl ENABLED 67840  -        ACTIVE   -       -
sd DG02-03      DATA-VOL_dcl-02 ENABLED 67840  0        -        -       -
v  DATA-VOL-SRL DG-RVG       ENABLED  16777216 SRL      ACTIVE   -       -
pl DATA-VOL-SRL-01 DATA-VOL-SRL ENABLED 16777216 -      ACTIVE   -       -
sd DG02-02      DATA-VOL-SRL-01 ENABLED 16777216 0      -        -       -

co vvrcacheobj  -            DISABLED -        -        ACTIVE   -       -
 

• Third command will remove the DISABLED object of CO

example

# vxedit -g DG rm vvrcacheobj
[root@node2 ~]# vxprint
Disk group: DG

TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
dg DG           DG           -        -        -        -        -       -

dm DG01         sdb          -        20802640 -        -        -       -
dm DG02         sdc          -        20802640 -        -        -       -
dm DG03         sdd          -        20802640 -        -        -       -

v  cachevol     fsgen        ENABLED  10485760 -        ACTIVE   -       -
pl cachevol-01  cachevol     ENABLED  10485760 -        ACTIVE   -       -
sd DG03-01      cachevol-01  ENABLED  10485760 0        -        -       -

rv DG-RVG       -            ENABLED  -        -        ACTIVE   -       -
rl rlk_192.168.253.31_DG-RVG DG-RVG CONNECT -  -        ACTIVE   -       -
v  DATA-VOL     DG-RVG       ENABLED  16777216 -        ACTIVE   -       -
pl DATA-VOL-01  DATA-VOL     ENABLED  16777216 -        ACTIVE   -       -
sd DG01-01      DATA-VOL-01  ENABLED  16777216 0        -        -       -
pl DATA-VOL-02  DATA-VOL     ENABLED  LOGONLY  -        ACTIVE   -       -
sd DG01-02      DATA-VOL-02  ENABLED  288      LOG      -        -       -
pl DATA-VOL-03  DATA-VOL     ENABLED  LOGONLY  -        ACTIVE   -       -
sd DG02-01      DATA-VOL-03  ENABLED  288      LOG      -        -       -
dc DATA-VOL_dco DATA-VOL     -        -        -        -        -       -
v  DATA-VOL_dcl gen          ENABLED  67840    -        ACTIVE   -       -
pl DATA-VOL_dcl-01 DATA-VOL_dcl ENABLED 67840  -        ACTIVE   -       -
sd DG01-03      DATA-VOL_dcl-01 ENABLED 67840  0        -        -       -
pl DATA-VOL_dcl-02 DATA-VOL_dcl ENABLED 67840  -        ACTIVE   -       -
sd DG02-03      DATA-VOL_dcl-02 ENABLED 67840  0        -        -       -
v  DATA-VOL-SRL DG-RVG       ENABLED  16777216 SRL      ACTIVE   -       -
pl DATA-VOL-SRL-01 DATA-VOL-SRL ENABLED 16777216 -      ACTIVE   -       -
sd DG02-02      DATA-VOL-SRL-01 ENABLED 16777216 0      -        -       -
 

• Last command will remove the cachevol from the vxprint result

example

# vxprint
Disk group: DG

TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
dg DG           DG           -        -        -        -        -       -

dm DG01         sdb          -        20802640 -        -        -       -
dm DG02         sdc          -        20802640 -        -        -       -
dm DG03         sdd          -        20802640 -        -        -       -

rv DG-RVG       -            ENABLED  -        -        ACTIVE   -       -
rl rlk_192.168.253.31_DG-RVG DG-RVG CONNECT -  -        ACTIVE   -       -
v  DATA-VOL     DG-RVG       ENABLED  16777216 -        ACTIVE   -       -
pl DATA-VOL-01  DATA-VOL     ENABLED  16777216 -        ACTIVE   -       -
sd DG01-01      DATA-VOL-01  ENABLED  16777216 0        -        -       -
pl DATA-VOL-02  DATA-VOL     ENABLED  LOGONLY  -        ACTIVE   -       -
sd DG01-02      DATA-VOL-02  ENABLED  288      LOG      -        -       -
pl DATA-VOL-03  DATA-VOL     ENABLED  LOGONLY  -        ACTIVE   -       -
sd DG02-01      DATA-VOL-03  ENABLED  288      LOG      -        -       -
dc DATA-VOL_dco DATA-VOL     -        -        -        -        -       -
v  DATA-VOL_dcl gen          ENABLED  67840    -        ACTIVE   -       -
pl DATA-VOL_dcl-01 DATA-VOL_dcl ENABLED 67840  -        ACTIVE   -       -
sd DG01-03      DATA-VOL_dcl-01 ENABLED 67840  0        -        -       -
pl DATA-VOL_dcl-02 DATA-VOL_dcl ENABLED 67840  -        ACTIVE   -       -
sd DG02-03      DATA-VOL_dcl-02 ENABLED 67840  0        -        -       -
v  DATA-VOL-SRL DG-RVG       ENABLED  16777216 SRL      ACTIVE   -       -
pl DATA-VOL-SRL-01 DATA-VOL-SRL ENABLED 16777216 -      ACTIVE   -       -
sd DG02-02      DATA-VOL-SRL-01 ENABLED 16777216 0      -        -       -

========================================================

Now you are back to the state where you stand before taking the snap.

========================================================

Thanks Mike for your kind support in doing this all activity

You could have replaced all this by:

# vxsnap -g disk_group prepare volume_name
# vradmin -g disk_group verifydata rvg_name secondary_host cache_size=cache_volume_size

i.e if you use "cache_size" rather than "cache" attribute, the vradmin command will create the cache object for you and remove it after data verification has completed successfully.  But doing the manual steps means you get a better understanding of what is going on and learn something in the process.

Mike