ANS1715E
A filespace already exists for virtual machine (VM_name), but with a different virtual machine UUID (VM_UUID) than the current virtual machine UUID (VM_UUID).

Explanation

A virtual machine with this name was backed up, and it has a different virtual machine UUID than the virtual machine that is backed up now. This can occur if there are two virtual machines with the same name that are backed up to the same TSM data center node name. In this case, the backup can not continue because the backup-archive client uses the virtual machine name to uniquely reference the virtual machine on the TSM server.

This can also occur if the virtual machine UUID changed after a previous backup operation. This is the case after the following events:
  1. Virtual machine VM_1 backed up.
  2. Virtual machine VM_1 is restored with a new name: VM_2. A new UUID is assigned to VM_2.
  3. Virtual machine VM_1 is deleted.
  4. Virtual machine VM_2 is renamed to VM_1.

System action

The backup of this virtual machine fails. The backup process can continue with other virtual machines.

User response

If there are two or more virtual machines with the same name in the data center inventory, you can complete either of the following actions:
  • Rename the virtual machines so that all names in the data center inventory are unique.
  • Backup up virtual machines with the same name to different TSM servers.

If the VM's UUID changed, run a BACKUP VM command with VMBACKUPUPDATEGUID option. The VMBACKUPUPDATEGUID option updates the UUID on the TSM server.