Skip to main content

ESXi configuration backup not working

Thread needs solution

Hi,

Yesterday I've upgraded our Acronis backup 12 environment to version 12.5. It all went well, except for the plan we use to backup the ESXi configuration of both our VMware ESXi 6.0 hosts.

The existing backup plan started as scheduled, but failed with an error: "POR: Branch 'ProviderId' cannot be found."

I then tried to create a new backup plan for the ESXi configuration and this also fails with the same error.

 

Please advise.

Theo

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Theo,

There could be problems with ESXi root credentials migration to 12.5 after upgrade. Note that besides Acronis Management Server component, the agents must also be upgraded. If they were upgraded already - you can check it from Settings->Agents, then try to re-install the Agent for VMware (appliance or Windows Agent - whichever you use) by removing the agent from Settings->Agents (delete) and installing it back again either remotely (Devices->Add button) or by running the setup program.

If this doesn't help then please post the full error message - it should contain the additional details such as "Line:"/"Linetag" ID which would help us identify the problem.

Thank you.

Hi Vasily,

I reinstalled the vmware agent using setup (on the same Windows machine as the management server) and reconnected the agent to the vCenter server.

I then created a new plan for the ESXi configuration backup, specifying the root credentials of the VMware ESXi 6.0 host.

Running the plan the same error occurred:

 

POR: Branch 'ProviderId' cannot be found.

DATE AND TIME

Jun 05, 2017, 08:11:16 AM

CODE

0x01350016+0x01350016+0x01330029+0x01350035+0x01350016+0x01350016+0x01490003+0x01CA000D+0x00FA001B

MODULE

309

MESSAGE

Backup failed

Additional info:

------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"$module":"mms_vsa64_7048","CommandID":"D332948D-A7A9-4E07-B76C-253DCF6E17FB"}
Message: TOL: Failed to execute the command. Backup plan 'ESXi'
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"$module":"agent_protection_addon_vsa64_7048","CommandID":"D332948D-A7A9-4E07-B76C-253DCF6E17FB"}
Message: TOL: Failed to execute the command. Backup plan 'ESXi'
------------------------
Error code: 41
Module: 307
LineInfo: 0xE6792A5EE190DE2C
Fields: {"$module":"agent_protection_addon_vsa64_7048"}
Message: Failed to execute the command.
------------------------
Error code: 53
Module: 309
LineInfo: 0x2E7E9E174F1FB719
Fields: {"FailCount":"2","$module":"agent_protection_addon_vsa64_7048"}
Message: 2 activities have not succeeded. One of them is displayed.
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"$module":"service_process_vsa64_7048","CommandID":"8F01AC13-F59E-4851-9204-DE1FD77E36B4"}
Message: TOL: Failed to execute the command. Backing up
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"$module":"gtob_backup_command_addon_vsa64_7048","CommandID":"8F01AC13-F59E-4851-9204-DE1FD77E36B4"}
Message: TOL: Failed to execute the command. Backing up
------------------------
Error code: 3
Module: 329
LineInfo: 0xDB72A375111D804F
Fields: {"$module":"disk_bundle_vsa64_7048"}
Message: Failed to back up the configuration of ESXi host 'vmware02.drh.local'.
------------------------
Error code: 13
Module: 458
LineInfo: 0x60D54FE10D95ECF6
Fields: {"$module":"disk_bundle_vsa64_7048"}
Message: Failed to back up the configuration of ESXi host 'vmware02.drh.local'.
------------------------
Error code: 27
Module: 250
LineInfo: 0xBDB15D965E4D5DE3
Fields: {"TraceLevel":"1","$module":"mms_vsa64_7048"}
Message: POR: Branch 'ProviderId' cannot be found.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Theo,

Thank you for the additional details. The problem is that one property of some reported machine instance cannot be read from Acronis Management Server database. This problem will require further investigation by checking the full system report. After collecting the report please submit a ticket through our support team and send me a private message on the forum with the submitted ticket ID, so that I can followup with it.

Thank you.

Hi,

 

Because Acronis support was taking forever I decided to try installing agent virtual appliances on my VMware hosts instead of using an agent for VMware on my Windows server. The ESXi configuration now works.

Theo