Host-based backup of VMware vSphere VMs.
Post Reply
jnett98
Lurker
Posts: 2
Liked: never
Joined: Oct 08, 2013 6:58 pm
Full Name: JN
Contact:

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

Post by 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
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Resized Disks on Source VM's cause Replication jobs to f

Post by 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.
VP, Product Management
Posts: 27055
Liked: 2710 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Resized Disks on Source VM's cause Replication jobs to f

Post by 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
Chief Product Officer
Posts: 31459
Liked: 6648 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Resized Disks on Source VM's cause Replication jobs to f

Post by Gostev »

You will just lose them automatically with Patch #2 :)
hannisch
Enthusiast
Posts: 34
Liked: 5 times
Joined: Dec 15, 2011 8:14 pm
Full Name: Sven Hannisch
Contact:

[MERGED] v7 replica job fails after resizing disk

Post by 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
Enthusiast
Posts: 34
Liked: 5 times
Joined: Dec 15, 2011 8:14 pm
Full Name: Sven Hannisch
Contact:

Re: v7 replica job fails after resizing disk

Post by 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.
VP, Product Management
Posts: 27055
Liked: 2710 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: v7 replica job fails after resizing disk

Post by Vitaliy S. » 1 person likes this post

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
Enthusiast
Posts: 34
Liked: 5 times
Joined: Dec 15, 2011 8:14 pm
Full Name: Sven Hannisch
Contact:

Re: v7 replica job fails after resizing disk

Post by hannisch »

Thanks for the info. This workaround is much better than deleting the replica.
Fbarahona
Lurker
Posts: 1
Liked: never
Joined: Oct 16, 2013 3:51 pm
Full Name: Franco Barahona

Re: Resized Disks on Source VM's cause Replication jobs to f

Post by Fbarahona »

Just for clarification. Does this mean deleting the snapshots off the datastore, or consolidating them though vSphere?
Vitaliy S.
VP, Product Management
Posts: 27055
Liked: 2710 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Resized Disks on Source VM's cause Replication jobs to f

Post by Vitaliy S. »

Do not delete these files manually, use Snapshot Manager to consolidate all the data. Thanks!
Bunce
Veteran
Posts: 259
Liked: 8 times
Joined: Sep 18, 2009 9:56 am
Full Name: Andrew
Location: Adelaide, Australia
Contact:

Re: Resized Disks on Source VM's cause Replication jobs to f

Post by 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.
Post Reply

Who is online

Users browsing this forum: Baidu [Spider] and 88 guests