Unable to run VM from backup
We are trying to run VMs from backup. THe archives are stored on a WIndows file share. When I choose the archive, I can see the VMs and choose which ones I would like to mount in VMware.
The mount process begins but after registering all the VMs, the appliance quickly unregisters everything and reverses the process.
I can see that it appears to be an access issue to the share, I have tried all credential formats (e.g. DOMAIN\ADministrator, administrator@domain.local, administrator, password) but none seem to allow the mount to continue.
Frustratingly I have had this issue once before and managed to find the solution but didn't make a note of this!
Here are the error logs:
Failed to publish virtual machine.
Additional info:
--------------------
Error code: 9
Module: 405
LineInfo: 476adbf26d208b31
Fields:
Message: Failed to publish virtual machine.
--------------------
Error code: 6
Module: 405
LineInfo: 476adbf26d2088db
Fields:
Message: Failed to emulate virtual machine's disks.
--------------------
Error code: 30
Module: 386
LineInfo: 171b6cbf75a1e50b
Fields:
Message: Failed to perform IOCTL call of the virtual file '/share/exch2010_mount 1359388185/Disk_SCSI0_0-flat.vmdk'.
--------------------
Error code: 14
Module: 386
LineInfo: 3ee3bcd9fc27beca
Fields:
Message: An error has occurred while performing I/O operation.
--------------------
Error code: 27
Module: 386
LineInfo: 192f6237fb9ad20c
Fields:
Message: Failed to open the archive 'allservers-Archive.TIB' in location 'avfs:/smb?//hsf214/f$/allservers-dr/'.
--------------------
Error code: 2
Module: 64
LineInfo: 3f26773fab7bd94a
Fields: path : avfs:/smb?//hsf214/f$/allservers-dr/
Message: Failed to open the archive for reading.
--------------------
Error code: 20
Module: 4
LineInfo: 72bd8f1a411be0da
Fields:
Message: Access to the file is denied.
--------------------
Hi KCS Helpdesk,
From the description and the error code it looks like there were some non-closed connections to that Windows share which caused the issue (which explains why reboot fixed the issue). The "Access to the file is denied" is returned by 'asamba' Linux module which is used to access network by vmProtect Virtual Appliance and typically such symptoms either indicate general compatibility issues of the share with 'asamba' or problems with particular state of the network share (as it seemed to be in your case).
Additional tip: in order to reset the shares connections state in Windows it is usually enough to restart "Server" service instead of rebooting the whole machine. The same tip applies to implementing IrpStackSize workaround, but it's a different story unrelated to this topic.
Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager