Subscribe

SnapLock Compliance clock @ destination

Implementing SnapLock Compliance solution with VSM replication.  Currently the destination (DST) system is in a DC that will be moved.  The current DC is in EST and New DC will be MST.  We want to start replicaitons ASAP to mainatain DR soltion, but worried about not only changing the timezone, but also having the DST system powered off for two weeks while we move it.   What affect will this have on the drift of the compliance clock and Mirror relationships?   Seems that drift correction went away in 8.1, and the compliance volume clock is set by the source (SRC) updates to the DST.   Does this mean all will be fine or will the compliance clock on the DST system be skewed even as compared to that of the volume clock?