Issues Restoring VMs (Seemingly Random?)

[CurtLeCaptain]

I've opened a case: 00932485

Some notes: We're on Veeam 8.0 Update 2a, we have one Veeam B&R interface server and five proxy/repository servers in our environment that backup in hotadd mode. Our production environment that we're backing up is the latest version of VMware 5.5, the Lab is another environment running VMware 5.5 (latest).

It seems that restoration from our production VMs into our Lab environment (for testing purposes on live VMs) fails without rhyme or reason. We will go to restore four VMs at a time that reside in a single job, and three of four will succeed, one will fail. The failing VM takes a crazy amount of time to restore any files (in order of VMX, VMXF, and NVRAM) - each takes about 5 minutes a piece. The properly working VMS restore those files in a second and instantly register the VM on the destination. Every time it fails, we see the following error:

Code: Select all

[08.06.2015 19:03:12] <01> Info     Failed to open VDDK disk [[SV-VOL3] DC2\DC2.vmdk] ( is read-only mode - [false] )
[08.06.2015 19:03:12] <01> Info     Failed to open virtual disk
[08.06.2015 19:03:12] <01> Info     Logon attempt with parameters [VC/ESX: [LAB.DOMAIN.LOCAL];Port: 443;Login: [DOMAIN\Veeam];VMX Spec: [moref=vm-1016];Snapshot mor: [snapshot-1018];Transports: [nbd];Read Only: [false]] failed because of the following errors:
[08.06.2015 19:03:12] <01> Info     Failed to open disk for write.
[08.06.2015 19:03:12] <01> Info     Failed to download disk.
[08.06.2015 19:03:12] <01> Info     Agent failed to process method {DataTransfer.SyncDisk}.
[08.06.2015 19:03:12] <01> Info     Failed to open VDDK disk [[SV-VOL3] DC2/DC2.vmdk] ( is read-only mode - [false] )'

Now - the logon attempt thing is odd, because we know we can log onto vCenter using that DOMAIN\Veeam account, and our backup jobs use that account every time. The restoration process works just fine on some of these VMs. I can't find a pattern. Any thoughts would help greatly.

[PTide]

Hi Curt,

Have you already seen this thread

[sewru]

Hi Curt,

I've got the same problem. How did you manage to solve the problem?

I've read through the other threads, but to no avail.

[foggy]

Ruben, I cannot see the resolution in Curt's case details, please contact technical support directly with this. Actually, such issues could have different causes, so logs review is definitely required to track it down in every particular case. Thanks.