I've done a bit more testing with a 100 GB backup.
Source = HD1
Destination = HD2
I monitored the Disk acces with Windows Resource Monitor while the backup was running and I saw reads from HD1 and writes to HD2 but no reads from HD2.
Then while the backup was still running I tried continually (every few secounds) to clear the Windows Standby RAM with the microsoft util RAM MAP http://technet.microsoft.com/en-us/sysi ... 00229.aspx for a period of about 1-2 minutes and then I suddenly started to see reads from HD2.
When I stopped clearing the Windows standby memory the reads from HD2 faded out and stopped again.
The problem for me is that the corruption of files happens on the written files on the destination HD2 in the write process and not in the read process from the source HD1.
So it seems like SyncBackPro in the verification process just uses the file from Windows Standby RAM and doesn't read back the file from the destination HD which then defeats the purpose of the check?
Source = HD1
Destination = HD2
I monitored the Disk acces with Windows Resource Monitor while the backup was running and I saw reads from HD1 and writes to HD2 but no reads from HD2.
Then while the backup was still running I tried continually (every few secounds) to clear the Windows Standby RAM with the microsoft util RAM MAP http://technet.microsoft.com/en-us/sysi ... 00229.aspx for a period of about 1-2 minutes and then I suddenly started to see reads from HD2.
When I stopped clearing the Windows standby memory the reads from HD2 faded out and stopped again.
The problem for me is that the corruption of files happens on the written files on the destination HD2 in the write process and not in the read process from the source HD1.
So it seems like SyncBackPro in the verification process just uses the file from Windows Standby RAM and doesn't read back the file from the destination HD which then defeats the purpose of the check?