Replications enter an RPO violation state after resizing the source virtual machine in Cloud Director Availability
search cancel

Replications enter an RPO violation state after resizing the source virtual machine in Cloud Director Availability

book

Article ID: 315006

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

Symptoms:
  • After resizing a virtual machine that is being replicated via Cloud Director Availability, the replication enters an RPO violation state.
  • In the /var/run/log/hostd.log file on the destination host for the replication, you see entries similar to:
2023-02-16T15:13:33.255Z warning hostd[2100602] [Originator@6876 sub=Vdisksvc opID=hsl-39bd5be8-3d66 user=vpxuser] New capacity (3972844748) is not greater than original capacity (3972844748).
-->
2023-02-16T15:13:33.278Z warning hostd[2100602] [Originator@6876 sub=Vdisksvc opID=hsl-39bd5be8-3d66 user=vpxuser] Got Methodfault exception: Fault cause: vmodl.fault.InvalidArgument
-->

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 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.

Resolution

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.