Validate appears to validate the image file cached in memory, and not on disk.

Scenario:

1. Make an Acronis v11.7 image of a small disk or partition, say a 16GB USB stick, using a PC with a larger amount of RAM, say 32GB.

2. Save the image to the PC's backup/work HDD as normal, and the resulting compressed image is 12GB.

3. Now manually validate that image, and amazingly the successful validation occurs in a couple of seconds, and you notice there's no disk LED activity on the PC's backup HDD.

4. That said, If you reboot that same PC that made the image, the validation takes a normal amount of time, maybe a couple minutes minutes.

The only reason I can think of why the initial validation (when run immediately after the image is made) runs so fast, is that the validation is validating the backup image file (ie. the tib) that's cached in the PC's memory. Likewise, when we reboot the PC, the memory is flushed, and we see the actual image stored on disk being validated this time around

Obviously, my concern here is that a "Validation Successful" is of little value if we're not validating the image on the long term storage. Who care tha a cached copy of the image in memory validated.

Anyone have any thoughts on this one?

Regards . . .