Under normal circumstances, resizing a source disk should result in the following:

  1. The VPG enters “Updating” state, and a re-size of the associated target disk occurs.

  2. The VPG updates to reflect the target disk resize.

  3. The VPG re-enters the “Protecting” state.


An administrator may note that under certain circumstances, re-sizing a source disk may result in the associated VPG entering “Needs Configuration” state.  Some possible reasons include the following:

  • A disconnection between sites occurred when the re-size operation was ongoing.

  • The source volume is associated with an RDM as a target for replication - in this case, the RDM will need to be resized manually.

  • The target host for the relevant VM is installed with ESX/ESXi 4.0 (a VMware limitation).

  • The datastore on which the target disk is located does not have sufficient free space to accommodate the resize of the vmdk.



  1. Remove the VM whose disk was re-sized from the VPG, or if there is only one VM within the VPG, delete the VPG, and choose to preserve the target disks.  Then save the VPG changes.  

  2. Re-protect the VM whose disk was re-sized, and choose to preseed the target disks associated with those disks that were not re-sized as described in the Preseeding Volumes solution article.