TSM Backup Error: ANS1715E A filespace already exists for virtual machine (vmname), but with a different virtual machine UUID

Problem: You've restored a virtual server using TSM and notice your backup is failing with error 4379. Examining the dsmerror. log you find this error; ANS1715E A filespace already exists for virtual machine (vmname), but with a different virtual machine UUID.

IBM info.

VMWare info.

Solution: Modify the UUID of the virtual server to match the previous UUID, thus reconnecting the new VM to the TSM Filenode that already exists.

Specifying a UUID for a Virtual Machine
Note: VMware Tools may need to be removed from the virtual machine prior changing the UUID to prevent the UUID from reverting.
In some circumstances you may want to assign a specific UUID to the virtual machine. To do this, you need to override the automatically generated UUID value. Power off the virtual machine and edit its configuration (.vmx) file to set the value of the UUID parameter. Use a text editor to edit the configuration file. The format for the line is:
uuid.bios = ""

The UUID value must be surrounded by quotation marks. A sample configuration line looks like:

uuid.bios = "00 11 22 33 44 55 66 77-88 99 aa bb cc dd ee ff"

After you add this line to the configuration file, power on the virtual machine. The new UUID is used when the virtual machine boots.