Performing offline data verification

VVR enables you to verify whether the data on the Secondary is identical to the data on the Primary data volumes when the application is inactive. The vradmin syncrvg command with the -verify option verifies and reports any differences between the data volumes associated with the Secondary RVG and the corresponding Primary RVG. If a volume set is associated to the RDS, the vradmin -verify syncrvg command verifies only the component volumes that are associated to the RVG. The vradmin -verify syncrvg command only reports whether the Primary and Secondary volumes are identical or not. It does not make them identical. As the command runs, it reports the progress every 10 seconds. An MD5 checksum is used to calculate the difference between the Primary and the Secondary data volumes.

See Using difference-based synchronization.

Prerequisites for using the vradmin -verify syncrvg command

Observe the following prerequisites:

  • All applications using the Primary data volumes must be stopped before running the vradmin -verify syncrvg command.

To verify the differences between the Primary and Secondary data volumes

  • Use the following command to verify the differences between the Primary and Secondary data volumes

    # vradmin -g diskgroup -verify syncrvg local_rvgname \
            sec_hostname...

    When this command is invoked, you are prompted to confirm that the Primary data volumes are not in use. You can use the -s option to skip this confirmation step.

    The argument local_rvgname is the name of the RVG on the local host and represents the RDS.

    The argument sec_hostname is a space-separated list of the names of the Secondary hosts as displayed in the output of the vradmin printrvg command.

    This command checks the status of the Primary RLINK to each of the Secondary RVGs being verified. If any of the RLINKs are not up-to-date, the vradmin -verify syncrvg command returns with a message to indicate that the RLINKs are not up-to-date. In this scenario, verification is not be performed. Use the vxrlink status command to determine the extent to which the Secondary is behind.

Example:

To verify the data differences between the Primary RVG hr_rvg on seattle and the Secondary RVG on host london, issue the following command from any host in the RDS:

# vradmin -g hrdg -verify syncrvg hr_rvg london
The output resembles the following if the Primary and Secondary data volumes
are identical:
Message from Primary:
VxVM VVR vxrsync INFO V-5-52-2210 Starting volume verification to remote
VxVM VVR vxrsync INFO V-5-52-2211    Source host: 10.182.136.192
VxVM VVR vxrsync INFO V-5-52-2212    Destination host(s): 10.182.136.193
VxVM VVR vxrsync INFO V-5-52-2213    Total volumes:       1
VxVM VVR vxrsync INFO V-5-52-2214    Total size:          4.000 G


Eps_time Dest_host       Src_vol     Dest_vol     F'shed/Tot_sz  Diff  Done
00:00:00 10.182.136.193    hr_dv       hr_dv                 0M/4096M     0%    0%
00:00:10 10.182.136.193    hr_dv       hr_dv               221M/4096M     0%    5%
Message from Primary:
00:00:20 10.182.136.193    hr_dv       hr_dv               468M/4096M     0%   11%
Message from Primary:
00:00:30 10.182.136.193    hr_dv       hr_dv               705M/4096M     0%   17%
Message from Primary:
00:00:40 10.182.136.193    hr_dv       hr_dv               945M/4096M     0%   23%
Message from Primary:
00:00:50 10.182.136.193    hr_dv       hr_dv              1184M/4096M     0%   29%
Message from Primary:
00:01:00 10.182.136.193    hr_dv       hr_dv              1419M/4096M     0%   35%
Message from Primary:
00:01:10 10.182.136.193    hr_dv       hr_dv              1655M/4096M     0%   40%
Message from Primary:
00:01:20 10.182.136.193    hr_dv       hr_dv              1886M/4096M     0%   46%
Message from Primary:
00:01:30 10.182.136.193    hr_dv       hr_dv              2124M/4096M     0%   52%
Message from Primary:
00:01:40 10.182.136.193    hr_dv       hr_dv              2356M/4096M     0%   58%
00:01:50 10.182.136.193    hr_dv       hr_dv              2590M/4096M     0%   63%
Message from Primary:
00:02:00 10.182.136.193    hr_dv       hr_dv              2838M/4096M     0%   69%
Message from Primary:
00:02:10 10.182.136.193    hr_dv       hr_dv              3091M/4096M     0%   75%
Message from Primary:
00:02:20 10.182.136.193    hr_dv       hr_dv              3324M/4096M     0%   81%
Message from Primary:
00:02:30 10.182.136.193    hr_dv       hr_dv              3564M/4096M     0%   87%
Message from Primary:
00:02:40 10.182.136.193    hr_dv       hr_dv              3809M/4096M     0%   93%
Message from Primary:
00:02:50 10.182.136.193    hr_dv       hr_dv              4070M/4096M     0%   99%
00:02:51 10.182.136.193    hr_dv       hr_dv              4096M/4096M     0%  100%
VxVM VVR vxrsync INFO V-5-52-2217 The volumes are verified as identical.


VxVM VVR vxrsync INFO V-5-52-2219 VxRSync operation completed.
VxVM VVR vxrsync INFO V-5-52-2220 Total elapsed time: 0:02:51

If there are differences in the data volumes, the output looks similar to the one shown below:

Message from Primary:
VxVM VVR vxrsync INFO V-5-52-2210 Starting volume verification to remote
VxVM VVR vxrsync INFO V-5-52-2211    Source host:         10.182.136.192
VxVM VVR vxrsync INFO V-5-52-2212    Destination host(s): 10.182.136.193
VxVM VVR vxrsync INFO V-5-52-2213    Total volumes:       1
VxVM VVR vxrsync INFO V-5-52-2214    Total size:          4.000 G


Eps_time Dest_host       Src_vol     Dest_vol     F'shed/Tot_sz  Diff  Done
00:00:01 10.182.136.193    hr_dv       hr_dv                 0M/4096M     0%    0%
00:00:11 10.182.136.193    hr_dv       hr_dv               231M/4096M    48%    6%
Message from Primary:
00:00:21 10.182.136.193    hr_dv       hr_dv               476M/4096M    23%   12%
Message from Primary:
00:00:31 10.182.136.193    hr_dv       hr_dv               719M/4096M    15%   18%
Message from Primary:
00:00:41 10.182.136.193    hr_dv       hr_dv               954M/4096M    12%   23%
Message from Primary:
00:00:51 10.182.136.193    hr_dv       hr_dv              1202M/4096M     9%   29%
Message from Primary:
00:01:01 10.182.136.193    hr_dv       hr_dv              1438M/4096M     8%   35%
Message from Primary:
00:01:11 10.182.136.193    hr_dv       hr_dv              1680M/4096M     7%   41%
Message from Primary:
00:01:21 10.182.136.193    hr_dv       hr_dv              1924M/4096M     6%   47%
Message from Primary:
00:01:31 10.182.136.193    hr_dv       hr_dv              2165M/4096M     5%   53%
Message from Primary:
00:01:41 10.182.136.193    hr_dv       hr_dv              2418M/4096M     5%   59%
Message from Primary:
00:01:51 10.182.136.193    hr_dv       hr_dv              2668M/4096M     4%   65%
00:02:01 10.182.136.193    hr_dv       hr_dv              2906M/4096M     4%   71%
Message from Primary:
00:02:11 10.182.136.193    hr_dv       hr_dv              3140M/4096M     4%   77%
Message from Primary:
00:02:21 10.182.136.193    hr_dv       hr_dv              3386M/4096M     3%   83%
Message from Primary:
00:02:31 10.182.136.193    hr_dv       hr_dv              3630M/4096M     3%   89%
Message from Primary:
00:02:41 10.182.136.193    hr_dv       hr_dv              3881M/4096M     3%   95%
Message from Primary:
00:02:49 10.182.136.193    hr_dv       hr_dv              4096M/4096M     3%  100%
VxVM VVR vxrsync INFO V-5-52-2218 Verification of the remote volumes found
differences.


VxVM VVR vxrsync INFO V-5-52-2219 VxRSync operation completed.
VxVM VVR vxrsync INFO V-5-52-2220 Total elapsed time: 0:02:50