Resized Disks on Source VM's cause Replication jobs to fail

[jnett98]

I have a handful of VM's that grow continuously by nature of the apps/files they hold. Expanding the drives on these servers is a fairly regular occurance. I recently did this, and now replication my DR site is failing with the error of: Client error: An existing connection was forcibly closed by the remote host Exception from server: Declared and actual sizes of the disk.

I had this happen with a smaller VM, and removing the snapshots of the replica, resizing the disks there resolved the issue.

Is there a way around this without losing all of my current restore points?

Thanks.

[foggy]

Are you running v7? There is a known issue in this version regarding that, it will be addressed in patch 2. Thanks.

[Vitaliy S.]

But even with patch 2 you will lose all current restore points, as it is not possible to resize virtual disk that has existing snapshots (restore points) due to VMware limitation.

[Gostev]

You will just lose them automatically with Patch #2

[hannisch]

Hello,

In v6.5 I only got a warning, and all snapshots were deleted. In v7. replicas fails:
Exception from server: Declared and actual sizes of the disk [vddk://<vddkConnSpec><viConn name.........
What is to do to prevent this error?

b/r

Sven

[hannisch]

Searching the forum I found this post: http://forums.veeam.com/viewtopic.php?p=91924 So this is a known bug and will be fixed in patch2.
Is there a acceptable workaround? The only thing worked for me was deleting the replica.

[Vitaliy S.]

The current workaround is to remove all snapshots manually, resize your target disk to match production VM virtual disk size and start the replication job, should help!

[hannisch]

Thanks for the info. This workaround is much better than deleting the replica.

[Fbarahona]

Just for clarification. Does this mean deleting the snapshots off the datastore, or consolidating them though vSphere?

[Vitaliy S.]

Do not delete these files manually, use Snapshot Manager to consolidate all the data. Thanks!

[Bunce]

Don't consolidate all if you have a Veeam working snapshot as you'll likely end up with the CID mismatch error:
http://kb.vmware.com/selfservice/micros ... Id=1007969

Delete the Veeam Working snapshot first, at a minimum.