Skip to main content

failed to backup VM while powered on

Thread needs solution
Beginner
Posts: 1
Comments: 0

I recently using vmprotect 7 trial version.
It always failed to backup VM while it's online (powered on), but no issues when I shutdown it.
below the errors from the logs.
please help.

Task 'Back up bbciti' failed: 'Failed to create a backup.
Additional info:
--------------------
Error code: 3
Module: 435
LineInfo: 555b5abba09500ab
Fields:
Message: Failed to create a backup.
--------------------
Error code: 32786
Module: 114
LineInfo: 28314c961de7d3b2
Fields:
Message: Failed to prepare for backing up.
--------------------
Error code: 353
Module: 149
LineInfo: a71592046cb2c5f8
Fields:
Message: Failed to back up the group.
--------------------
Error code: 2
Module: 218
LineInfo: 338a407ad20e0987
Fields:
Message: Error occurred while running the backup and recovery engine.
--------------------
Error code: 1080
Module: 1
LineInfo: 145a191bfe9050e5
Fields:
Message: Failed to execute the operation.
--------------------
Error code: 372
Module: 149
LineInfo: 8e1d384601b2ab81
Fields:
Message: Failed to download additional file from 'https://192.168.0.57/folder/BBCITI/BBCITI.nvram?dcPath=BB%20Group%20Dat…'.
--------------------
Error code: 500
Module: 0
LineInfo: 3a807318633ed716
Fields:
Message: Failed to download 'https://192.168.0.57/folder/BBCITI/BBCITI.nvram?dcPath=BB%20Group%20Dat…'.
--------------------'.

0 Users found this helpful
Beginner
Posts: 1
Comments: 1

I'm experiencing the exact same problem using VMprotect 7 in my company's SAN. We have a two-host infrastructure running Vsphere Enterprise version 4.0; most of the VM's are stored on a ISCSI EMC AX-4 disk array.

The backup always fails when the VMs are running; no issue at all is experienced if they've been shutted down. The strange thing is also that the backup still works if the VM is running AND the vmdk is stored on a host's local storage.

Any suggestion about how to fix this issue would be hugely appreciated.

Forum Star
Posts: 24
Comments: 3268

Hello all,

Thank you for your comments, and for finding time to report about the issue.

There are several possible causes of this failure.

In general it happens since the URL mentioned in the log file is not working,i.e. it’s not possible to download the files from vCenter/ESX host using the HTTPS access:

So far we have found the following possible causes:

1) The datacenters in vSphere are located under folders which are not parsed in the URL:
If the Datacenter is under a folder in vCenter then the backup won’t work with Failed to download error. Here’s an example:

However if the Datacenter is under vCenter (as it should be by default) then everything works properly:

2) This is a vCenter 4.0 Update 1 based installation where there is a known issue that vCenter does not properly handle the download requests. Solution is to upgrade the vCenter to Update 2 or to 4.1 version.

See these instructions.

If the above doesn’t help then we need to check more details, such as the vCenter version, what is registered in vmProtect (vCenter or ESXi host directly), does the download via https://[vcenterIP]/folder work?

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you.

Attachment Size
96972-100582.png 115.79 KB
96972-100585.png 18.52 KB
96972-100588.png 11.02 KB
Beginner
Posts: 7
Comments: 15

Just an FYI I had your issues when I was on 4.0 with ISCSI storage. We updated to 4.1 U2 and all issues at this point have completely resolved.

Interesting on VMP6 we didnt have the issue but when we went to VMP7 we started seeing the problem.

Last note: 4.1 U2 runs much better and smoother than 4.0 particularly when related to snapshots.

Forum Member
Posts: 0
Comments: 92

I got this exact issue. Later did I realized as well that it was out ISCSI storage.