Virtual machine disks don't replicate when configuring a new protection in Cloud Director Availability 4.x

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:

• While configuring a protection for a virtual machine, you see that the disk size is reported as 0.
• After creating the replication, the disk space for that replication shows as N/A.
• In the /opt/vmware/h4/replicator/log/replicator.log file on the source Replicator Appliance you see entries similar to:

2023-08-09 01:33:10.684 WARN - [UI-6fa94903-3550-48e9-8d24-921dbca1d775-r177-XV-3c-XA-MC] [https-jsse-nio-8043-exec-4] c.v.h.replicator.util.VirtualDiskHelper : Found disk with key 2001 in VM vm-20027 (VC null) with missing disk UUID. Skipping it!

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware Cloud Director Availability 4.x

Cause

This can issue occur when the source VM you're replicating does not contain a Disk Data Base UUID in the .vmdk disk file.

Resolution

To resolve this issue, fix the missing Disk Data Base UUID (ddb.uuid) for the .vmdk disk file on the source VM.

If you require assistance resolving this issue, contact VMware Support and note this Article ID (95197) in the problem description. For more information, see How to Submit a Support Request.