12.5: ESXI Configuration backup shows wrong agent
I'm using two ESXi hosts, each with a separate agent
Looking at the ESXi configuration backup of my two ESXi hosts shows
The red one should be AcronisESXAppliance-2!
As a result I do NOT see the second configuration backup in my history!
Martin

- Log in to post comments

Acronis: Where can I change the wrong assignment? It seems that I can only change the agent for virtual machines but not for the host?
- Log in to post comments

Hi Martin,
First thing to note is that the agent (appliance) assignment to an ESXi host is used only when you back up ESXi configuration from this host, which can be done by any agent (appliance). The agent binding algorithm is not applied automatically to ESXi hosts instances currently (that's a known bug which will be fixed in future updates: internal ID ABR-119914).
However what matters most is assignment of agent to VMs hosted on the ESXi hosts - the VMs by default should be bind to appliance running on the same ESXi host. You can check it from Devices list by selecting a VM and checking its Details tab.
The appliance renaming should work and we were not able to reproduce similar behavior - the changes you make to the name in appliance console should be reflected in the web console after short time (1-2 minutes). Please double-check and try rebooting the appliance if the changes are still not shown.
Thank you.
- Log in to post comments
In reply to Acronis: Where can I change… by truwrikodrorow…

The assignment of agent to ESXi host instances cannot be changed currently (problem as described in my previous comment). But again note that it does not make much sense. The ESXi host configuration backups take ~300-500MB of space and are completed nearly instantly in comparison with VM backups, so there is no practical sense to distribute ESXi host configuration backups between different agents, but we will still address the bug in future updates.
- Log in to post comments

Vasily, thanks for your explanation. After restarting and cleanup, the scheduled configuration backup now seems to work on both hosts.
Regards
Martin
- Log in to post comments

After a reboot of the management server, the renamed name is now correct.
Martin
- Log in to post comments