This article applies to:
OS: All supported OS
Product edition: Cloud
Problem description
VM backup fails with
vm-mor is not found for uuid
error.
Cause
VM back fails when the backup proxy is disconnected on the Management Console. The backup proxy is migrated to another vCenter and is no longer present in the vCenter deployed for backups resulting in the error.
Traceback
[ERROR] Error <type 'exceptions.Exception'>:vm-mor is not found for uuid: 422bfb6a-93df-67d3-29a5-53c1508c9481. Traceback -Traceback (most recent call last): File "roboSyncController.py", line 309, in run File "roboSyncController.py", line 295, in _run File "roboSyncController.py", line 131, in connect_sync_server File "roboVmUtil.py", line 291, in get_vm_detail File "roboVmUtil.py", line 147, in get_bkproxy_mor_by_uuid Exception: vm-mor is not found for uuid: 422bfb6a-93df-67d3-29a5-53c1508c9481
Resolution
Reboot the proxy as this helps in freeing up the memory allocation of the proxy server.
📝 Note
This helps to clear any Zombie process.
Check if a VM backup proxy is present in the configured vCenter. If not, refer to the following articles to deploy a new backup proxy:
See also
Related keywords: Backups are failing with error INTERNAL65535, resolve backup failures INTERNAL65535, VMware vm INTERNAL65535