12.07.2015 Views

DataKeeper for Windows All Documentation - SIOS

DataKeeper for Windows All Documentation - SIOS

DataKeeper for Windows All Documentation - SIOS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Resync Elapsed TimeThis value is the number of total blocks that are dirty during mirror resynchronization. "Dirty" blocks are thosethat must be sent to the target machine be<strong>for</strong>e synchronization is complete. This value will be 0 <strong>for</strong> all statesother than EmMirrorStateResync.When a mirror synchronization is begun, this value will be initially equal to the value of Resync Total Blocks.Please note that during a mirror synchronization, Resync Dirty Blocks may actually increase if a large numberof incoming writes are made to the volume.Resync Elapsed TimeDefault Value: 0Range: 0 - MAX_ULONGWhile the mirror is being synchronized, this value represents the elapsed time in seconds that thesynchronization has been occurring. After a mirror is successfully resynchronized, the value represents thetotal amount of time the previous synchronization operation took since the last system boot. The value will be0 <strong>for</strong> volumes that either never have been synchronized or volumes that were not synchronized during the lastboot.Resync New WritesDefault: 0Range: 0 - MAX_ULONGThis value represents the number of writes that have occurred on the volume since a synchronizationoperation has begun. This value will directly affect the number of dirty blocks, the number of passes requiredto synchronize the mirror and the amount of time the synchronization takes to complete.Resync PassDefault Value: 10Range: 0 - MaxResyncPasses (Registry)This value is the number of passes that have currently been made through the volume during theresynchronization process to update the target. The number of passes required to complete thesynchronization process will increase based on the amount of writing that is being per<strong>for</strong>med duringsynchronization. While writing to the source volume is allowed during synchronization, heavy writes willcause the synchronization to take longer, thus resulting in a much longer time until it is finished.Resync Total BlocksDefault Value: 0<strong>DataKeeper</strong> <strong>for</strong> <strong>Windows</strong> Technical <strong>Documentation</strong>Page 23

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!