Pre-Check for update VEEAM to Version 12 using VMware



Show first post

33 comments

Userlevel 7
Badge +7

Ouch! 😮

Thanks for sharing Martin..

Userlevel 4

Inside the forum there is a workaround to change transport mode to NBD (network) - https://forums.veeam.com/post479533.html#p479533

But this is not a workaround for us - because we have a separate Backup VLAN/Network/Uplink

 

I created a Powershell script to Change Disk UUIDs without to reboot a vm - https://github.com/claranet/ClaranetHub/tree/main/VMware/Change-DiskUUID

Currently we test it on some vms with failed backups

Userlevel 4
Badge +2

Watching….

Userlevel 4

I found a blogpost - I will review it and test it… If it work, i will reply the result here

 

https://blog.milla-online.de/duplicate-disk-uuids-and-how-to-get-rid-of-it-hopefully

Userlevel 4

@vAdmin You said it :(

I found over 300VMs over across multiple customers with duplicate UUIDs.

I understand that the main problem comes from VMware - but VMware has no problems with that at the moment, only VEEAM in Version 12 has it.

Userlevel 7
Badge +2

@vAdminNo, this will not work - I tested it

 

You have to identify the Disk, shutdown the VM and change UUID over the shell

vmkfstools -J setuuid <vmname>.vmdk

 

Wow, that’s massive outage :-| for a big and busy VM.

Thank you for the sharing @Martin Weber 

Userlevel 4

@vAdmin No, this will not work - I tested it

 

You have to identify the Disk, shutdown the VM and change UUID over the shell

vmkfstools -J setuuid <vmname>.vmdk

 

Userlevel 7
Badge +2

Hi @Martin Weber , 
Thank you for sharing.

So, the work around is to do the Storage vMotion after Deploying the VM from the Template.

What if the VM has already been deployed from Template and running as Production VM?

Comment