Error: The capacity of the seed disk does not match during replication reconfiguration

Products

• VMware Live Recovery

Issue/Introduction

 When reconfiguring vSphere Replication with seed disks, the process fails with a disk capacity mismatch error. This typically occurs after expanding source disks or removing the VM from replication.

Symptoms:

• Error: "The capacity of the seed disk does not match the capacity of the replication source disk."
• Multiple VMDKs share the same filename across different datastores.
• Target datastore contains multiple orphaned replica folders (e.g., VMNAME#1).

Environment

VMware Live Recovery 9.0.5

Cause

Removing a VM from replication purges the Replication Disk ID (RDID) mapping at the source. If the VM has many disks with identical filenames, the system cannot correlate source disks to the correct seed copies on the destination datastore.

Resolution

1. Remove the VM from any existing replication configuration.
2. Clean up orphaned replica folders and disks on the destination datastore to prevent naming collisions.
3. Configure the replication from scratch without selecting seed disks.
4. Allow a full initial synchronization to establish new RDID mappings.

Additional Information

 For assistance with manual RDID mapping, see Contact Support.