vmProtect7 ESXi 5 - Disk Is Skipped
I'm trialling vmProtect 7, running as a Windows agent on the vCenter host.
When attempting to backup several Linux VMs the backup logs an information message saying that GRUB was detected. It then logs a warning message; "The disk is skipped". There is no indication as to which disk is skipped.
There is no reason provided or error codes. The job continues on and appears to complete normally, but with this warning. The resulting .tib file is too small and I suspect that it is skipping my main data volume/disk. If it matters this disk(vmdk) contains a large LVM volume with several EXT3 formatted partitions.
When going through file recovery for this VM, a C: and D: drive are displayed. C: shows the grub folder and a few grub files. Clicking the D: "drive" gives
Error code: 1 Module: 432
LineInfo: da004ef1034b5b1
Fields: Message: Failed to get backed up file list.
---------------------
Error code: 11
Module: 161
LineInfo: af9c3bafc04e3b8
Fields: IsReturnCode: 1
Message: Cannot get File Iterator.
I have not yet tried a whole VM restore or running the VM from backup. That's next, but since the .tib is so small(100GB smaller than expected), I don't expect success.
Any help is appreciated.
Thanks for your feedback.
Further testing:
VMs that display the warning "The disk is skipped" are indeed skipping the most important data disk. So, these VMs are further unable to be restored or Run VM from Backup.
The C: and D: drives that vmProtect displays in the backup are the non-LVM boot partition C: (grub) and the swap partition D:. These both reside on a single vmdk along with a third LVM partition that does not show up at all. There is also a second vmdk containing only an LVM volume with most of the VM's data. This is the disk that is skipped.
This would seem to point to an issue with LVM. However, I have another VM on the same ESXi5 host that also has similar LVM volumes. That machine does backup successfully.
File Recovery on this, successfully backed up, machine is not possible because as you and the documentation state, LVM is not a supported file system for that feature. However, I can successfully Run VM from Backup as well as restore the entire VM.
But, the issue remains for several critical VMs that all fail to backup properly with only the warning "The disk is skipped".
Forgot to add - I'd also check if the disk is independent/persistent, see http://forum.acronis.com/forum/24954 . But it most likely not the case as it is skipped at all in this case.
i today have also this error strangely for me it only says
"timedate/ taskname / message" the disk is skipped.. nothing more no reference to what vm
i also have an linux vm with an extended LVM volume with a second disk and this this is also skipped.
Hello Just Sayin, Dev-anon, and Jan,
Thank you for your comments.
We investigated, and discussed this with the Development team. Even if the disk is independent/persistent, it shouldn't be skipped. Developers are already implementing the fix into the future build, and meantime Developers suggest to use an appliance from the 6th version. It won't skip the disks, but will back them up in sector-by-sector mode. Please contact any Forum moderator for the fix via Private message.
If the fix doesn't help, please gather the diagnostic information from this comment.
This issue's important for us, we need to have all the information stored in one place. So we would highly appreciate if you could refer to this thread for future reference.
Let us know if you have any additional questions or concerns, we will be glad to help.
Thank you.