CRC verify compares source with source?!?

[Gruff]

Hi,

I've run a few backups with ViceVersa mirroring one drive to another.

They've all run smoothly.

However one day I decided to look at the data transfer statistics.

There's a problem with your CRC verify module!

When mirroring one full 300GB drive to another blank 300GB with CRC verify the controller statistics note that:

Source: Written ~0GB, Read: 600GB
Destination: Written 300GB, Read ~0GB

The Source should have read either 300 or 600GB depending on whether the CRC is calculated during copying or separately during verify. So that might be OK.

However, the Destination MUST read 300GB or else a CRC cannot be calculated. It is not doing this!

Therefore I can only conclude that the Verify module is simply comparing source with source.

[TGRMN Software]

Hello

I wonder if some caching is happening on your system.

Can you try this test: compare source and target, then in the ViceVersa Comparison Window select a few target files, right click, and from the menu select calculate CRC.

What does the controller say?

thanks!
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[Gruff]

Hi,

when a straight compare of the 2 identical drives is done with CRC COMPARE then the controller reports 300GB read on BOTH drives.
So, yes, COMPARE works just fine.

It's when mirroring 300GB to a blank drive with CRC VERIFY that the issue occurs.

[Gruff]

[TGRMN Software]

Ok, thanks, please let us know what you find out
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com