dcm resynchronization does not start automatically
Created: 24 Jun 2013 | 1 comment
I am testing the vcs/vvr cluster . When I write a data which size exceeds the srl volume size, VVR goes to "logging to dcm" state.
# vradmin -g data_dg -l repstatus rvg_bReplicated Data Set: rvg_bPrimary:Host name: 192.168.100.111RVG name: rvg_bDG name: data_dgRVG state: enabled for I/OData volumes: 1VSets: 0SRL name: srl_bSRL size: 150.00 MTotal secondaries: 1Secondary:Host name: 192.168.100.112RVG name: rvg_bDG name: data_dgRlink from Primary: rlk_192.168.100.112_rvg_bRlink to Primary: rlk_192.168.100.111_rvg_bConfigured mode: asynchronousLatency protection: offSRL protection: autodcmData status: consistent, behindReplication status: logging to DCM (needs dcm resynchronization)Current mode: asynchronousLogging to: DCM (contains 5572672 Kbytes) (SRL protection logging)Timestamp Information: N/ABandwidth Limit: 100.00 MbpsCompression Mode: On
After writing, the vvr keeps in "needs dcm resync" status and the resynchronization does not start automatically. What should I set to let the resync start auto?
Btw:another question. If a new write operation on block operation coming in when the block is in dcm resync state, is the write action blocked or not?