Modify vmdk UUID to work hotadd

[adam900331]

Hy!

Nowadays I noticed that some VMs cannot us the hotadd feature during backup. I checked the Veeam VMs log, and identify there are some VMs wihch has tha same disk UUID. I think these VMS deployed from template. What do you think, can I modify the disk UUID manually in VMware? Is it safe? Are there any impact for the runing VM?

https://kb.vmware.com/s/article/2006865

Thanks.

[Mildur]

Hi Adam

It's safe. But could it be, that you are affected by this known issue?
https://www.veeam.com/kb4460

If so, please disable multipath on your Linux proxies and the duplicated issue will not shown anymore in Veeam job session logs.

Best,
Fabian

[adam900331]

No. There is the following in during the backup: Unable to hot add source disk vmname.vmdk, failing over to network mode...

There isn't any error.

[Mildur]

Then it's a technical issue which must be investigated via a support case.
You can change the disk UUID on VMware side. But I expect Veeam to take a new full backup of this disk.

Best,
Fabian

[adam900331]

I am testing the Virtual Appliance mode with two VMs. I create these two VMs with template. I checked the vmdk file UUID:

Code: Select all

[root@node01:/vmfs/volumes/ee9ab993-c8b5b227] vmkfstools -J getuuid /vmfs/volumes/ee9ab993-c8b5b227/TST02/TST02.vmdk
UUID is 60 00 C2 99 fd 80 2f 62-00 ea 88 f1 67 f1 1e 93
[root@node01:/vmfs/volumes/ee9ab993-c8b5b227] vmkfstools -J getuuid /vmfs/volumes/ee9ab993-c8b5b227/TST01/TST01.vmdk
UUID is 60 00 C2 9d 72 28 45 a7-82 09 83 7b 6d 23 40 dd

The UUID is different, but even so the backup job say during backup:
2023. 09. 19. 13:42:46 :: Unable to hot add source disk TST02.vmdk, failing over to network mode...

I checked the TST02 VM logs:

Code: Select all

[TryInvoke] Invocation error;
[19.09.2023 13:31:10.125] <50> Error        Failed to get guest OS path for newly attached disk [SimplivityDS1] TST02/TST02.vmdk: there are 2 new disks with uuid 6000C299-fd80-2f62-00ea-88f167f11e93  (System.Exception)
[19.09.2023 13:31:10.125] <50> Error           at Veeam.Backup.Core.CSoapHotaddAttachAlg.RescanDisksAndGetAttachedDiskPath(CVirtualDisk disk, String diskPath, IEnumerable`1 diskUuidsAndPathsBeforeAttach)
[19.09.2023 13:31:10.125] <50> Error           at Veeam.Backup.Common.SFunctionExtensions.TryInvoke[TResult](Func`1 action, Int32 retryCount, TimeSpan timeout, Func`2 excFilter)

The Veeam can backup with hotadd the TST01 VMs. I don't idea which UUID is wrong so the two VMs disk UUID is different.

[adam900331]

Hi Adam

It's safe. But could it be, that you are affected by this known issue?
https://www.veeam.com/kb4460

If so, please disable multipath on your Linux proxies and the duplicated issue will not shown anymore in Veeam job session logs.

Best,
Fabian

Hy!

Meanwhile I turned off the multipath and my problem is resolved. Thanks!

[Mildur]

Hi Adam

You're welcome.
I'm glad the kb article worked in your case too.

Best,
Fabian