VVR - Data status inconsistent - DCM (autosync)

Question

Hi!

I’ve configured&nbsp;VVR &nbsp;5.1_SP1RP4&nbsp;(Veritas Storage Foundation) on a RHEL 5.9 server.

I’ve started yesterday the replication and today (19 hours later) the state of Data Status still is&nbsp;Inconsistent.

It’s only 1 RVG of 1000 GB.

Looks like never ends Autosync, network looks fine, I've copy files between the two hosts and time was normal.

I saw that Readback in PROD server is always filled up. I've increased to 256M and still filled up, looks like never flush!

[root @ latlap-prd4917 ~]

# vxmemstat

Fri 12 Dec 2014 06:38:47 PM BRST
	&nbsp;Pool &nbsp; &nbsp; &nbsp; DG &nbsp; &nbsp; &nbsp; Min &nbsp; &nbsp; &nbsp; Max &nbsp; &nbsp; &nbsp; &nbsp; In &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Allocated &nbsp; Max &nbsp; &nbsp; &nbsp; Waiting
	&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Size &nbsp; &nbsp; &nbsp;Size &nbsp; &nbsp; &nbsp; &nbsp;Use &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Used
	---------- &nbsp;------- &nbsp;-------- &nbsp;---------- &nbsp;---------- &nbsp;---------- &nbsp;--------- &nbsp;-------
	Voliomem &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1024 &nbsp; &nbsp;131072 &nbsp; &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp;1024 &nbsp; &nbsp; &nbsp; &nbsp;0 &nbsp; &nbsp;no
	NMCOM-latambpmvvr_rvg &nbsp;vvrdg01 &nbsp; &nbsp; &nbsp;1024 &nbsp; &nbsp; 16384 &nbsp; &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp;1024 &nbsp; &nbsp; &nbsp; &nbsp;0 &nbsp; &nbsp;no
	RViomem &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1024 &nbsp; &nbsp;131072 &nbsp; &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp;1024 &nbsp; &nbsp; &nbsp; &nbsp;0 &nbsp; &nbsp;no
	Readback &nbsp; &nbsp;- &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1024 &nbsp; &nbsp;262144 &nbsp; &nbsp;236080 &nbsp; &nbsp; &nbsp;236576 &nbsp; 236080 &nbsp; &nbsp;no
	Other &nbsp; &nbsp; &nbsp; - &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1024 &nbsp; &nbsp;131072 &nbsp; &nbsp; &nbsp; &nbsp; 0 &nbsp; &nbsp; &nbsp; &nbsp;1024 &nbsp; &nbsp; &nbsp; &nbsp;0 &nbsp; &nbsp;no

&nbsp;

Source server: latlap-prd4917

Replica server: latlap-cob4917

&nbsp;

# vxdisk list

DEVICE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TYPE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DISK&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GROUP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; STATUS

sda&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; auto:none&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; online invalid

sdb&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; auto:cdsdisk&nbsp;&nbsp;&nbsp; vvrdisk01&nbsp;&nbsp;&nbsp; vvrdg01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; online

sdc&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; auto:cdsdisk&nbsp;&nbsp;&nbsp; vvrdisk02&nbsp;&nbsp;&nbsp; vvrdg01&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; online

sdd&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; auto:none&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; online invalid

&nbsp;

# vxprint -Pl

Disk group: vvrdg01

&nbsp;

Rlink:&nbsp;&nbsp;&nbsp; rlk_latlap-cob4917_latambpmvvr

info:&nbsp;&nbsp;&nbsp;&nbsp; timeout=500 rid=0.1068

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; latency_high_mark=10000 latency_low_mark=9950

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bandwidth_limit=none

state:&nbsp;&nbsp;&nbsp; state=ACTIVE

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; synchronous=off latencyprot=off srlprot=autodcm

assoc:&nbsp;&nbsp;&nbsp; rvg=latambpmvvr_rvg

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; remote_host=latlap-cob4917 IP_addr=153.40.227.102 port=4145

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; remote_dg=vvrdg01

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; remote_dg_dgid=1418321601.11.latlap-cob4917

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; remote_rvg_version=30

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; remote_rlink=rlk_latlap-prd4917_latambpmvvr

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; remote_rlink_rid=0.1065

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; local_host=latlap-prd4917 IP_addr=144.215.151.70 port=4145

protocol: TCP/IP

flags:&nbsp;&nbsp;&nbsp; write enabled attached inconsistent cant_sync connected asynchronous autosync resync_started

&nbsp;

[root @ latlap-prd4917 ~]

# df -h

&nbsp;

Filesystem&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;Size&nbsp; &nbsp;&nbsp;Used &nbsp;&nbsp;Avail Use% Mounted on

[…]

/dev/vx/dsk/vvrdg01/latambpmvvr&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1000G&nbsp; 536M&nbsp; 938G&nbsp;&nbsp; 1% /latambpm/vvr

&nbsp;

[root @ latlap-prd4917 ~]

#&nbsp; vradmin -g vvrdg01 -l repstatus latambpmvvr_rvg

Replicated Data Set: latambpmvvr_rvg

Primary:

&nbsp; Host name:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; latlap-prd4917

&nbsp; RVG name:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; latambpmvvr_rvg

&nbsp; DG name:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; vvrdg01

&nbsp; RVG state:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; enabled for I/O

&nbsp; Data volumes:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1

&nbsp; VSets:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;0

&nbsp; SRL name:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; latambpmvvr_srl

&nbsp; SRL size:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;200.00 G

&nbsp; Total secondaries:&nbsp; &nbsp;1

&nbsp;

Secondary:

&nbsp; Host name:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;l atlap-cob4917

&nbsp; RVG name:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;latambpmvvr_rvg

&nbsp; DG name:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;vvrdg01

&nbsp; Rlink from Primary:&nbsp;&nbsp;&nbsp;&nbsp; rlk_latlap-cob4917_latambpmvvr

&nbsp; Rlink to Primary:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rlk_latlap-prd4917_latambpmvvr

&nbsp; Configured mode:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; asynchronous

&nbsp; Latency protection:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; off

&nbsp; SRL protection:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;autodcm

&nbsp; Data status:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;inconsistent

&nbsp; Replication status:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; resync in progress (autosync)

&nbsp; Current mode:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; asynchronous

&nbsp; Logging to:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DCM (contains 996786176 Kbytes) (autosync)

&nbsp; Timestamp Information:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; N/A

&nbsp; Bandwidth Limit:&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;N/A

&nbsp;

[root @ latlap-prd4917 ~]

# vxrlink -g vvrdg01 -T status rlk_latlap-cob4917_latambpmvvr

&nbsp;

Fri 12 Dec 2014 11:26:20 AM BRST

VxVM VVR vxrlink INFO V-5-1-4464 Rlink rlk_latlap-cob4917_latambpmvvr is in AUTOSYNC. 996797440 Kbytes remaining.

VxVM VVR vxrlink INFO V-5-1-9472 Timestamp is not available when rlink is using DCM

&nbsp;

# date

Fri Dec 12 11:29:28 BRST 2014

# vradmin -g vvrdg01 -l repstatus latambpmvvr_rvg

&nbsp; Logging to:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DCM (contains 996645888 Kbytes) (autosync)

&nbsp;

# date

Fri Dec 12 11:29:34 BRST 2014

&nbsp; Logging to:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DCM (contains 996641792 Kbytes) (autosync)

&nbsp;

# date

Fri Dec 12 11:29:39 BRST 2014

&nbsp; Logging to:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DCM (contains 996637696 Kbytes) (autosync)

&nbsp;

# date

Fri Dec 12 11:29:48 BRST 2014

&nbsp; Logging to:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DCM (contains 996631552 Kbytes) (autosync)

&nbsp;

# date

Fri Dec 12 11:31:19 BRST 2014

&nbsp; Logging to:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DCM (contains 996558848 Kbytes) (autosync)

&nbsp;

Thanks a lot for any clue about the issue.

MaC.

mcoulon · Answer

After 3 days, is consistent:

# vradmin -g vvrdg01 -l repstatus latambpmvvr_rvg

Replicated Data Set: latambpmvvr_rvg
	Primary:
	&nbsp; Host name: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;latlap-prd4917
	&nbsp; RVG name: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; latambpmvvr_rvg
	&nbsp; DG name: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;vvrdg01
	&nbsp; RVG state: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;enabled for I/O
	&nbsp; Data volumes: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 1
	&nbsp; VSets: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;0
	&nbsp; SRL name: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; latambpmvvr_srl
	&nbsp; SRL size: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 200.00 G
	&nbsp; Total secondaries: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;1

Secondary:
	&nbsp; Host name: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;latlap-cob4917
	&nbsp; RVG name: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; latambpmvvr_rvg
	&nbsp; DG name: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;vvrdg01
	&nbsp; Rlink from Primary: &nbsp; &nbsp; &nbsp; &nbsp; rlk_latlap-cob4917_latambpmvvr
	&nbsp; Rlink to Primary: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; rlk_latlap-prd4917_latambpmvvr
	&nbsp; Configured mode: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;asynchronous
	&nbsp; Latency protection: &nbsp; &nbsp; &nbsp; &nbsp; off
	&nbsp; SRL protection: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; autodcm
	&nbsp; Data status: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;consistent, up-to-date
	&nbsp; Replication status: &nbsp; &nbsp; &nbsp; &nbsp; replicating (connected)
	&nbsp; Current mode: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; asynchronous
	&nbsp; Logging to: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; SRL
	&nbsp; Timestamp Information: &nbsp; &nbsp; &nbsp;behind by 0h 0m 0s
	&nbsp; Bandwidth Limit: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;N/A

Forum Discussion

VVR - Data status inconsistent - DCM (autosync)

Related Content

Status 42 on VMware backups (somewhat inconsistent)

exit status 140

Error 229 Status Events out of sequence - image inconsistency

Netbackup 10-CDP Status: 4207 4726

Error 229 Status Events out of sequence - image inconsistency

Recent Discussions

DataDomain To StoreOnce Migration

VCS ERROR V-16-1-10205 Group Mediation_NFS is faulted on system com1em03

vxprivutil

URGENT disk oublic region recover

super block corrupt