Acronis backups failed in VM's created manually with vmdks files restored from Acronis .tib file
Hi fellows, thanx for your support and time in advance. The Scenario is this:
AMS Acronis 11.5 (Virtualized on another vCenter and 1 layer up to the production network)
Vmware ESXi 5.1U1 (Different site and isolated, but with firewall rules allowing the AMS)
NetApp FAS storing the VM's via FC.
Acronis Backup Agent for Vmware (As a Virtual Applicance installed on the ESX's)
HP StorageWork D2D (configured as CIFS Share and personal Vault for store the backups)
The situation is this: There was a request of our customer to restore some VM's backed up on Acronis .tib files (those backups were succesfully and configured to backing up the full machine as a image). The first issue was the network is too slow to execute the process (i mean: Bring the backup file, read and processing throw the network to the AMS and perform the whole restore) it failed with the error of "Input/output error" sooo.... we workarounded picking the .tib file and restoring in a different location (locally) as a VM's folder. Next step was copy the disk files (.vmdk only) and linking to a new virtual machine configured exactly the same as the other one. But, when we tried to power on that new VM there was a error linking this restored Hard disks files. The error was associated to the compatibity of the vmdk file -- make no sense for me -- but Checking on internet , we solved this issue executing the import of the vmdk's with the command "vmkfstool -i /vmfs/volumes/../.." on ESXi console, and then, re configuring with this new files the VM. The VM power on without any issues and is stable so far.
Now those 2 VM's restored with that "alternative" process are having problem backing up with Acronis again. I've been checking on Acronis forums and google, but the scope of the error are too large and i need some guide. The backup job is configured exactly the same for all VM's. But it's failing only with this 2 VM's.
The Error Details are this one:
Fell free to asking me anything that would it help to identify the root cause. We need to fix this issue ASAP. Thank you guys again.
The problem is related to specifics of the VMs you're trying to back up. During attach of their disks to the backup agent (to appliance) the VMware doesn't allow to perform this operation ("The operation is not supported on this object" error). Why this happens is unclear and it is related to specifics of the problematic VMs, e.g. some details in their configuration which needs to be revealed with help from our support team.
The quick workaround would be to avoid using HotAdd backup method which can be done, by performing the VM backup via Agent for VMware (Windows) installed somewhere. In v11.5/11.7 this type of agent is capable to perform backups in network (NBD) mode without ability to use HotAdd mode (which uses "AttachScsiHardDisk" method which fails in your scenario).
Thanx Vasily! we 're contacting the support team of Acronis LATAM to help us on the troubleshooting of the problem. In the meantime it's seem that the only way to backup this machines sucessfully, is via Windows agent. Sadly, this isn't the request of the App Vendor, because they have a especific request to perform backup as images.
To clarify: there is still no need to install Agent for Windows inside the VMs in your case. The main point in my suggestion is to use Agent for VMware which will be unable to perform backup in HotAdd mode (where VM virtual disks are attached to Virtual Appliance). This can be either Virtual Appliance installed on a remote ESXi host or Agent for VMware (Windows) installed on some virtual or physical machine - both these agents will be capable for performing image backups of the VMs in agent-less mode without using HotAdd method (NBD method will be used instead).
Vaisly, please can u explain a little more detailed about what i have to do?.. cause i don't understand. Should i have to modify the configuration of the backup?.. or maybe execute another type of backup?..should i need the windows /vmware agents or not?.. sorry. But i read your post, and i can't get it straight the workaround suggested. Thanx for your replies and time!..
In essence you need to install Agent for VMware (Windows) type of agent. For example it can be installed alongside the Acronis Management Server machine.
- It's one of the choices on how to configure the Agent for VMware which is provided in 2 formats: 1) "Agent for VMware (Virtual Appliance)" and 2) "Agent for VMware (Windows)"
- The Agent for VMware (Windows) in v11.7 can be installed inside a Windows VM or on a physical machine. Regardless of where it is installed, it can connect to vSphere environment (via vCenter or ESXi host directly) in order to read the VM virtual disks data over NBD (Network Block Device protocol) - that's the main goal which needs to be achieved (e.g. NBD backup mode) in order to get successful backup.
- After that you should configure VM binding for the problematic VM(s), so that it is backed up by this newly installed "Agent for VMware (Windows)" instead of virtual appliance used before (which failed).
- As the result the backup plan (you can use some existing one) will be executed by Agent for VMware (Windows) without calling "AttachScsiHardDisk" function (which is known to fail in your case) and thus will succeed.
Hope this helps.