Unable to verify disk

[nigejn]

Hi All

I'm just copied over my full backups to our offsite server, I've mapped the files on from source to destination with WAN Accelerator. When I started the job I got the following

Code: Select all

24/08/2013 20:49:57 :: Job started at 24/08/2013 20:49:56
24/08/2013 20:50:00 :: New copy interval started
24/08/2013 20:50:04 :: Building VM list
24/08/2013 20:51:05 :: Some disks were not verified
24/08/2013 20:51:06 :: Unable to verify disk BAKDCSERVER.-flat.vmdk
24/08/2013 20:51:06 :: Unable to verify disk ACTSERVER-flat.vmdk
24/08/2013 20:51:06 :: Unable to verify disk SBSSERVER-flat.vmdk
24/08/2013 20:51:06 :: Unable to verify disk SBSSERVER_1-flat.vmdk
24/08/2013 20:51:06 :: Unable to verify disk SBSSERVER_3-flat.vmdk
24/08/2013 20:51:06 :: Unable to verify disk SBSSERVER_2-flat.vmdk
24/08/2013 20:51:07 :: Unable to verify disk DDMSERVER-flat.vmdk
24/08/2013 20:51:07 :: Unable to verify disk TS1-flat.vmdk
24/08/2013 20:51:07 :: Unable to verify disk APPSERVER-flat.vmdk
24/08/2013 20:51:07 :: Unable to verify disk APPSERVER_1-flat.vmdk
24/08/2013 20:51:10 :: Waiting for new restore points

What does unable to to verify disk mean?

Thanks

Nigel

[foggy]

Nigel, in your particular case, where you get those warnings right after mapping the backup copy job to a fresh backup, you can safely ignore them. Those warnings are logged when Veeam B&R cannot perform digests verification between disks stored in source and target backups and in this case this is due to the fact that there are simply no digests yet.

Just for the future, with all technical issues it's always better to contact technical support directly (as it is advised when you click New Topic, as most likely job debug logs review is required to investigate the reasons of the observed behavior.

Thanks!

[Wihan]

Thanks for using the forum instead, because then other people can also see the response.
I had the same issue and this answered my question.