Silly question, renaming the VMWare server name?

[ceez]

Hello,
So we added our first vmware esxi server using the IP address instead of the name of the host server. The rest of the servers were added via name which are much easier to reference. How can I go about renaming the IP to hostname without breaking the backup jobs that are running off it?

This is under Virtual Machines>Infrastructure>VMware vSphere> serverIPaddress

thanks!

B&Rv7.0

[Vitaliy S.]

Hello Cesar,

I don't believe there is an easy way to rename the host in the GUI. You should re-add it via the name you need, as SQL configuration database should also be updated. BTW, why do you add individual hosts as opposed to vCenter Server?

Thank you!

[veremin]

Hi,

You can also open a ticket with our support team. I believe there should be a way how the references can be modified directly in SQL database.

Thanks.

[masonit]

Hi

We have a backup job that backup 2 vms from a esxi host. The esxi host is added to vbr with dns name. Lets say is is called : esxi.tomato.local
Now the dns name of the esxi host is changed to esxi.orange.local. Now there is a only a dns A-record for esxi.orange.local. How will I deal with this in Veeam? Doesn't look like I can rename the standalone host in Veeam. I would prefeer not too trick Veeam by adding old dns name to the host file...
Also I really would prefeer to be able to continue use the existing job and don't run a full backup. Esxi host is at a branch office with slow wan link...

\Masonit

[foggy]

Magnus, please contact support, probably they will be able to update the database without changing the host ID.

[veremin]

Install VB&R PS snap-in, if you haven't done it already, and leverage this script; should be helpful. Thanks.

[masonit]

Hi

I haven't yet changed the name in vbr. As a quick fix I added "esxi.tomato.local" to host file. But now I get "SOAP connection is not available". I did temporary add esxi.orange.local as stand alone host to vbr. Then I had 2 different dns names pointing to the same host. Could that be the reason why my job now get soap errors?

\Masonit

[veremin]

It might be indeed. You'd better raise this issue with our support team and let them fix the consequences of this manual re-configuration. Thanks.

[masonit]

It might be indeed. You'd better raise this issue with our support team and let them fix the consequences of this manual re-configuration. Thanks.

After a rename with PS soap error went away.

\Masonit

[veremin]

Once again PowerShell has saved the world.

Should the issue re-occur, don't hesitate to open a support ticket.

Thanks.