Veeam backup files exceed provision size

[nestorius]

Hi; I have a problem. My virtual machine's backup vmdk files exceed original size. Why this problem occurs and how can I solve this. Thanks...

[Vitaliy S.]

Hi reha,

Do you mean that VBK file or incremental restore points exceed the size of the used space of your VM?

Thanks!

[nestorius]

All .vmdk files total size in my replica app. 420GB, but replica's disk provision size is 314GB.

[Vitaliy S.]

Are you using the same disk format? Do you compare total VM size (including snapshots) or just source VMDKs?

[nestorius]

Use same format. I compare only vmdk's original vm and replica vm.

[Vitaliy S.]

Can you please post two screenshots of the disk size you compare? It would help us to better understand the root cause if this difference.

[veremin]

By the way, I'm wondering whether deleted file blocks exclusion is enabled. Thanks.

[nestorius]

To Vitality:

I have shared my snapshots as you wish. Thanks...

https://www.flickr.com/photos/146839404 ... res/ex9R7V
https://www.flickr.com/photos/146839404 ... res/2Kg032


To Eremin :

I have using Veeam B&R 7. There is no Delete File Block Exclude option on my veeam. Thanks...

[foggy]

Not sure what confuses you here. I do not see anything unexpected on these screenshots, in terms of VMDK size.

[nestorius]

In first snapshot, left side of picture is my original vm, there is no problem here but right side is my replica, this vm's vmdk total size is exceed replica's provisioned disk size.

In second snaphot, there is no problem, this is my original vm.

Thanks.

[foggy]

...but right side is my replica, this vm's vmdk total size is exceed replica's provisioned disk size.

Do you mean the total size of all VMDK files, including restore points?

[nestorius]

True, I calculate restore points vmdk files too.

[foggy]

Each of them contains changes occurred inside original VM between corresponding job cycles, so it is expected they occupy the space.

[nestorius]

At that case. At recovery time, is a problem occur in recovery process because of this exceed.

[foggy]

Not sure what exceed you're talking about. You will be able to failover to any of the existing restore points - the replica VM will be reverted to the corresponding snapshot.

[nestorius]

In my snapshot; on my replica total vmdk disk size above 400GB but server's provisoned disk size just 314GB. This difference that I want to explain.

[jmmarton]

How many restore points do you have configured in the replication job?

Joe

[Vitaliy S.]

This is expected, as the sum of restore points plus base virtual disk should always be bigger than the size of the original VM.

[nestorius]

to jmmarton :

10 restore points in my replication job


to Vitality :

In that case, there is no problem and I will not encounter a trouble when I want to recover from this replica. Am I right ?

Thanks...

[Vitaliy S.]

Yes, that's correct. Every restore point (snapshot) has its size, so the size of the entire replica VM can easily be larger than the size of the original VM virtual disks.

[nestorius]

Thanks so much Vitaliy for your valuable informations, and thanks to other friends try to help me too.