Replication stays in "Not active" state and source vCenter Server has event "Disk size mismatch" when source disk size is not divisible by 1024

Products

• VMware Live Recovery
• VMware vSphere ESXi

Issue/Introduction

If you used P2V or manually created a source disk with a size that is not divisible by 1024, vSphere Replication creates a placeholder replica disk of a smaller size on the target datastore. vSphere Replication server fails to process the incoming data from the source host. The source vCenter Server posts the following event:

No connection to VR Server for virtual machine ... : Disk size mismatch

The replication status is Not Active.

Resolution

1. Stop the replication to clean up the replica files from the target datastore.

2. Increase the size of the source disk to the next multiple of 1024 by editing the settings of the source virtual machine. You can also temporarily detach the disk from the virtual machine and use vmkfstools to increase the disk size.

vmkfstools --extendvirtualdisk <size> <path to vmdk>

where size is the size of the disk rounded up to the next multiple of 1024.

3. Configure the replication again.