Virtual machine name change

[rgj]

Hi,

Our Windows group have a habit of not deciding the names theirs VMs when they're installed.
They can change them 2-3 times before going into production.

Our Veeam installation is based on the folder-structure we have in VC and the VMs are therefore included automagically in the backup.

Unfortunatly the changed name is not reflected in the Veeam backup, and makes it kinda hard to find the VMs again in Veeam. And they also show up in every cross reference done when checking the backup.
I'm guessing that Veeam uses the VM UUID from VC as a reference to the VM after it's been backed up the first time.

Is there some way of syncronising the names between VC and Veeam?

/René

[Alexey D.]

Hello René,

Are you using vSphere client to change VMs' names? Also, which version of B&R are you using?

[rgj]

Hi,

Yeah, all changes are done through VI client.

We're running B&R 5.0.1.198.

/René

[Alexey D.]

Huh, that's strange though..
We've just re-tried adding VMs based on folders (your case) and resource pools - name changes were updated smoothly.

Please open a support case and work with our support team. Thanks!

[rgj]

Hi,

Just to make sure we're talking about the same

I have a job which includes a folder called "Production". In this folder there is a VM called NAME.
This VM is then renamed to FINALNAME, and the job runs again.

If i go to Backups, and expand the backup for that job, i should see the VM as FINALNAME instead of NAME?

/René

[Alexey D.]

True. So, please send us the logs, we've never seen this behavior before.

[rgj]

Done.

Case id: 581087

[rgj]

Hi,

According to support - The behaviour we're seeing is how it works. So it seems they disagree

I've asked support to make a feature request.

/René

[pizzim13]

[merged into existing discussion]

I see that Veeam is able to backup the correct vm after the vm's name has changed in vCenter, because it is using the ManagedObjectReference and not the actual vm's name. What I am not seeing is the vm's new name being reflected in the job objects properties. Is it possible to update this property?

[Vitaliy S.]

Yes, this is expected behavior. You will not see any changes on the "Virtual Machines to backup" step of the wizard, however all other views (such as backups node etc.) will be updated accordingly.

[Gostev]

Try to remove and re-add the VM to the job.