Skip to main content
commvault.com commvault.com
Question

Full vm In-place restore not restoring original vm UUID, categories, or vm description

  • April 15, 2026
  • 5 replies
  • 26 views
A
Novice
Forum|alt.badge.img

Hi all. 

 

When I tried to do a full vm restore of a Nutanix VM with inPlaceRestore and overwriteVM set to True (tried from both command center UI and API), The expected behavior in my mind is that the vm’s metadata (vm description, categories, and UUID) is kept after the restore, just like how a VMware full vm restore has been working for us.

 

In our testing, the vm is deleted and then re-created, causing the VM UUID to change, at the same time, all the other vm metadata fields like description and categories are not restored; Guest Tool connection is broken because of the new UUID as well.

 

Is this expected behavior? Could this have been caused by misconfiguration on VM Group/Hypervisor side? 

 

Commvault 11.40

Nutanix AHV 7.5

 

Thanks in advance!

5 replies

J
Vaulter
Forum|alt.badge.img+9
  • Jace RossVaulter
  • Vaulter
  • April 16, 2026

Hi Aaron,

Deleting and recreating the VM is intended behaviour.
Commvault does collect and note your UUID during a backup (and restore), however Nutanix will always create a new UUID with a “new” VM.

https://portal.nutanix.com/page/documents/details?targetId=AHV-Admin-Guide-v10_0:ahv-vm-generation-id-bios-id-support-c.html

Hopefully this is of some assistance.

Jace Ross, Senior Technical SME
Sureshkumar S
Vaulter
Forum|alt.badge.img+12

Hi ​@Aaron Y ,

Good day!

Ideally in inplace restore we should retain the GUID

We  may need to look into the logs to see the reason for this 

can you attach vsbkkp.log or raise a case ?

Regards,
Sureshkumar S

 

A
Novice
Forum|alt.badge.img
  • Aaron YNovice
  • Author
  • Novice
  • April 16, 2026

Hi Aaron,

Deleting and recreating the VM is intended behaviour.
Commvault does collect and note your UUID during a backup (and restore), however Nutanix will always create a new UUID with a “new” VM.

https://portal.nutanix.com/page/documents/details?targetId=AHV-Admin-Guide-v10_0:ahv-vm-generation-id-bios-id-support-c.html

Hopefully this is of some assistance.

Hi ​@Jace Ross, thank you for your reply.

 

When you say Commvault note the UUID during backup and restore, does it note the new UUID anywhere after the restoration is complete that I can access programmatically?

 

With that said, VM Description, assigned categories and other metadata are also not restored(or re-set on the “new” vm). Is that expected as well?

 

If so, do you have the list of the vm-related items that are backed up and able to be restored, or the list of items that are not backed-up for Nutanix VMs available somewhere in your documentation?

 

Regards,

Aaron

A
Novice
Forum|alt.badge.img
  • Aaron YNovice
  • Author
  • Novice
  • April 16, 2026

Hi ​@Aaron Y ,

Good day!

Ideally in inplace restore we should retain the GUID

We  may need to look into the logs to see the reason for this 

can you attach vsbkkp.log or raise a case ?

Regards,
Sureshkumar S

 

Hello ​@Sureshkumar S . I have asked my colleague to create a case. Case number is 260416-873. Thanks!

J
Vaulter
Forum|alt.badge.img+9
  • Jace RossVaulter
  • Vaulter
  • April 16, 2026

Hi Aaron,

Deleting and recreating the VM is intended behaviour.
Commvault does collect and note your UUID during a backup (and restore), however Nutanix will always create a new UUID with a “new” VM.

https://portal.nutanix.com/page/documents/details?targetId=AHV-Admin-Guide-v10_0:ahv-vm-generation-id-bios-id-support-c.html

Hopefully this is of some assistance.

Hi ​@Jace Ross, thank you for your reply.

 

When you say Commvault note the UUID during backup and restore, does it note the new UUID anywhere after the restoration is complete that I can access programmatically?

 

With that said, VM Description, assigned categories and other metadata are also not restored(or re-set on the “new” vm). Is that expected as well?

 

If so, do you have the list of the vm-related items that are backed up and able to be restored, or the list of items that are not backed-up for Nutanix VMs available somewhere in your documentation?

 

Regards,

Aaron

Hi Aaron,

A good example of what I mean is this 

VSRstWorker::QueryRestoreObjects() - \ffd6867c-a417-48ae-92ad-3d82919919b2\ffd6867c-a417-48ae-92ad-3d82919919b2.json: File Name:ffd6867c-a417-48ae-92ad-3d82919919b2.json  Size:1178


The path Commvault references is the UUID, it’s how Commvault identifies the VM so Commvault is aware of the source UUID.

Towards the end of the job it does show a new UUID. This example is from an out-of-place restore so it may not say “new VM” on in-place but the line should still be there.

CNutanixInfo::RestoreVM_FullVM() - new VM [not-rocks] Guid = [b2bb8fd6-8443-4207-a6ac-b1ad55cbf65c]

I can also see when Commvault loads VM config these are the fields it populates:

VirtualServer_VMConfig
bParaVirtual="0"
guestHostName=""
hostName=""
nMemorySizeInMb="30720"
numOfCPU="6"
strArchitcteure=""
strBiosUUID=""
strDatacenterName=""
strDatastoreName=""
strFirmware=""
strGuestOSName=""
strInstanceType=""
strName="rocky-jr"
strNetworkId=""
strTemplateId=""
strUuid="ffd6867c-a417-48ae-92ad-3d82919919b2"

disks
bEncrypted="0"
isOSDisk="0"
nMaxSizeInBytes="344545280"
strControllerType="ide"
strDiskFullName="/default-container-56518487887421/.acropolis/vmdisk/7420bc49-066e-4308-aa23-de359ff45007"
strDiskGuid="7420bc49-066e-4308-aa23-de359ff45007"
strDiskIndexname="7420bc49-066e-4308-aa23-de359ff45007"
strEncyptKey=""
strVMFSPath=""

networkCards
isConnected="1"
label=""
macAddress="50:5b:8d:e8:13:ae"
networkName="vlan.1 [external]"
subnetId=""

 

None of these seem to outline the metadata you’re looking for so that is a perfect point to raise in your support incident to see if that is a limitation, bug or something we can add to the software.


Cheers,

Jace Ross, Senior Technical SME
Terms & ConditionsAccessibility statement