Changing the listening IP address
Greetings,
I've got the windows version of vmprotect 9 installed on our physical backup server (made the most sense). This server has many IP addresses/Interfaces, and vmprotect currently binds to all of them. This has become particularly problematic when it has chosen one of the many addresses (I don't know why) when I enable vcenter integration that does not have a route back to the client.
Bottom line I want to make sure vmprotect runs only on a single address and I haven't been able to figure out how to do that. Has anyone run into this?
Thanks,
Roy

- Log in to post comments

Greetings,
Changing it to the IP address did not resolve the issue, despite the fact the backup and vcenter on the same subnet it seems to choose the last available network to use for this feature. Are you telling me there is no way to assign what address acronis is going to bind to on the system? I couldn't seem to find any configuration for this, or where you would change the port after the fact in an installation. If I choose the very disruptive method of disabling every interface on the backup server except the main system one and then starting everything I imagine it would for that one point in time but as soon as the server is restarted it will go back to the undesirable configuration. Being able to configure it to only bind to the single address I want it to use would be more ideal.
Thanks,
Roy
- Log in to post comments

Hi Roy,
The port used to connect to the vCenter can be defined when you add vCenter under Configure->ESXi hosts menu. After the vCenter is added you cannot change the port, i.e. you need to remove the vCenter and re-add it back specifying the proper port. Note that the address of vmProtect agent which is saved in vCenter plugin configuration is not changed in time, so it doesn't matter whether the vmProtect agent is rebooted. In other words you can temporarily disable the undesired network interfaces on vmProtect agent side, then enable vCenter integration and then re-enable the network interfaces. This will be a one-time only operation (to record proper vmProtect Agent address in vCenter plugin properties).
On our side we will check this issue with our QA team to see if we can reproduce similar behavior. Likely there are some specifics on routing where vCenter IP is accessible through multiple network interfaces from vmProtect Agent, so adding it by IP doesn't make difference since there is still wrong vmProtect Agent IP selected in vCenter plugin properties.
Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager
- Log in to post comments