RPO Violation error message appears after VM virtual disk is resized, stating "New capacity is not greater than original capacity"
<VMNAME> [Error (RPO Violation]: "A replication error occurred at the vSphere Replication Server for replication '############'. Details: 'Error for (datastoreUUID: "vsan:#############################"), (pathname: "########-####-####-####-#############/hbrdisk.RDID-###########-=####-####-####-##########################-extend.vmdk"): New capacity (2566914048) is not greater than original capacity (10737418240); Extending disks'."
VMware vSphere ESXi 8.0.3x
vSphere Replication 9.0.x
This issue can occur when the disk of the source virtual machine has been resized to a value that is not a multiple of 1 kilobyte. The Host-Based Replication service requires a virtual machine's disk to be rounded up to a 1 kilobyte sector size boundary in order to be replicated.
From the /var/run/log/vmkernel.log
####-##-##T02:33:47.060Z Wa(180) vmkwarning: cpu102:30489805)WARNING: Hbr: 5362: Failed to establish connection to [###.#.#.#]:32032 (groupID=GID-d63032a0-7d72-4982-b81c-d81a46628746): The set of disks on the replication server doesn't match
To resolve this issue, resize the source virtual machine's disk while ensuring that the new size is a multiple of the required 1 kilobyte sector size.
Using the error and disk size numbers above as an example:
Source disk New capacity (2566914048) bytes
This is not a multiple of 1024:
2566914048 รท 1024 = 2506638.328125
That fractional result confirms misalignment.
Recommended Aligned Size:
To fix this, round up to the next whole multiple of 1024:
AlignedSize = (2566914048 / 1024) * 1024
= 2506639 * 1024
= 2566914560 bytes
So the corrected disk size of the virtual disk should be: 2566914560 bytes (2.39 GB)