Unable to restore VM
Hello,
AB12.5, new backup job + archive, ESX 5.5 + vcenter. When we try to do the restore to new VM it fail after 10 secs of running with below error message ... there are more servers with such problem. No resizing done .. ran restore job with default settings.
Tried to log a call for 2 hours via chat but received just "Your chat request has been canceled because no agents are available.".
Resizing is unavailable.
MODULE309
MESSAGECommand has failed. Command=Preparing for recovery of virtual machine; tenantID=00000000-0000-0000-0000-000000000000
Additional info:------------------------
Error code: 61
Module: 309
LineInfo: 0x4A8728DC8A1C95A1
Fields: {"$module":"service_process_glxa64_7048"}
Message: Command has failed. Command=Preparing for recovery of virtual machine; tenantID=00000000-0000-0000-0000-000000000000
------------------------
Error code: 32868
Module: 114
LineInfo: 0x2B2C9ED481007BCD
Fields: {"$module":"disk_bundle_tape_off_glxa64_7048"}
Message: Failed to recover the entire virtual machine.
------------------------
Error code: 32871
Module: 114
LineInfo: 0xFDE974FD2EBCFE15
Fields: {"$module":"disk_bundle_tape_off_glxa64_7048"}
Message: Failed to copy source disks to a new virtual machine.
------------------------
Error code: 75
Module: 149
LineInfo: 0x253B4FA68B9FF6B9
Fields: {"$module":"disk_bundle_tape_off_glxa64_7048"}
Message: Cannot recover the volume from the disk backup. There is insufficient free space on the target disk.
------------------------
Error code: 5
Module: 534
LineInfo: 0xC75257350CE0F755
Fields: {"$module":"disk_bundle_tape_off_glxa64_7048"}
Message: Cannot calculate the file system limits.
------------------------
Error code: 17
Module: 534
LineInfo: 0xC75257350CE0F8E4
Fields: {"$module":"disk_bundle_tape_off_glxa64_7048"}
Message: Invalid parameters are passed to the format/resize command.
------------------------
Error code: 17
Module: 534
LineInfo: 0xC75257350CE0F8D6
Fields: {"$module":"disk_bundle_tape_off_glxa64_7048"}
Message: Invalid parameters are passed to the format/resize command.
------------------------
Error code: 8
Module: 7
LineInfo: 0xE1FA52E6D1A0F3A0
Fields: {"$module":"disk_bundle_tape_off_glxa64_7048"}
Message: Resizing is unavailable.
Also a quick workaround for recovery would be by using the bootable media:
- Prepare an empty VM on the host with required disks sizes
- Boot this VM from Acronis Backup bootable media
- In the bootable media interface start the Recovery, browse the previously created backup and allocate the volumes from the backup to the disks
Hello Vasily,
i logged a call as had a request to do the restore from VM fast ... to see if this is may be some known bug and you can provide me with some workaround how to do the restore .. however this didn't happen.
It is quite unfortunate that it can happen that you released a product in such state. We have another 3-4 bugs that are preventing backups/restore or are interfering in some other way with backups - posted this in forum as well in some other topics.
I have no other option just to continue with investigation with your support and hope it will be fixed soon (we have a call open for 8 months for some other issue without resolution)
Lubos
Can't do the restore with bootable media as well .....
Lubos
Hi Lubos,
I've reviewed your submitted support case and found that the problems with recovery are related to specifics of the backed up system and to the archive which is being restored. There are low-level errors there which we've not seen before. Most likely we'll need a sample archive from you (you willl be requested for that in the support ticket) in order to figure out what the problem is.
Thank you.
Vasily,
i just received reply from support:
"There is no Linux agent on xxxxx, but there are volume groups and LVMs on the system.
Backing up and restoring of such machines by using virtual appliance is not supported, because it doesn't back up / re-create LVM metadata which makes bare metal restore or restore to a VM impossible."
I really don't understand why this is so ??? ... as in agentless mode it should not matter what OS is inside the VM. Also this was working fine with Acronis backup for vmware (version 9) ... also with same OS and filesystem config just different number of virtual disks it is working fine in AB12.5 as well.
BR,
Lubos
Hi Lubos,
Apparently you were misleaded - backup and recovery of VMs with LVMs inside is supported by Acronis Backup 12.5 - we've even made special adjustments to also enable files/folders recovery from such backups (which was not supported in v9), e.g. we parse the LVM volumes inside these backups despite the fact that they created in special sector-by-sector mode which is in turn required to preserve the LVM structure upon entire VM recovery. The entire VM recovery should also work properly.
The main point is that if it doesn't work with some specific VM configurations then this problem has to be investigated, bug reproduced and fixed after that. I've asked our support team managers to review your support ticket and make proper actions upon it.
Thank you.
This is for whole week without any activity .... is this the way how the support should work?
Hi Lubos,
We were able to reproduce the issue using on the archive you provided and will continue the investigation on our side (internal bug ID: ABR-133747). The investigation will likely take time since the problem is specific to particular machine internal partitions structure and currently we aim to finish it and prepare the fix to be included in Acronis Backup 12.5 Update 2 pending for September.
Edit: we will surely try to find some applicable workaround before September and in any case we will let you know once we make some progress (so likely you'll get some news before that time).
Thank you.
Vasily,
i'm not sure if you understand how critical is this issue for us. We payed for the solution that is suppose to do the backup (~60-80% success rate - there are other cases open for other issues) and restore. Now we came to point where we are not to do the restore under any circumstances and after 3 weeks the only answer is that likely you will receive some good news? Are you joking ??? This should be P1 with resolution time in hours !!! we are not able to do the restore !!!! You get it??????
We have payed for something that is not working at all .... Tell me what should we do ... hmm?
Lubos
Lubos, my point is that we'll do whatever is possible to deliver the solution ASAP, but I don't want to make promises we can't keep. The issue is technically complicated, affects only specific machine and thus requires not only time to investigate, but also time to properly fix it. To make it more clear: September is the timeline when the fix will become available in public (to address the problem in future for anyone who potentially runs into it), while in the meantime we will try to deliver some alternative (custom) solution earlier - when that happens I can't tell right now - we need time for investigation (1-2 weeks). Once it completes we will update you on the status. I totally understand your frustration, but that's the best I can tell you right now.