understanding file sizes for backups and copy jobs

Availability for the Always-On Enterprise

understanding file sizes for backups and copy jobs

Veeam Logoby rntguy » Thu Jun 08, 2017 1:14 pm

So we have a single VM that we're backing up and copying that job offsite. I'm trying to understand how big the file really is and why.

VM1 - C Drive = 12GB in use out of 149GB; E drive 2.08TB in use out of 3.12TB. Was closer to 1.55TB in use a couple weeks ago.

VM1 - job says the VM is 2.1TB and the 'total size is 2.07 TB'. Weird but I'm guessing for the VM list to backup it's rounding to tenth place. And this is the 'used' space not the volume sizes.

I also assume based on the numbers below from 5/27 that this must have grown from 1.7 TB because of what you'll see below about the backup file size.

In Disk Properties for the job I can see this chain:
6/01 - VIB - Data Size: 1.65 GB; Backup Size: 725 MB
5/31 - VIB - Data Size: 3.49 GB; Backup Size: 1.76 GB
5/30 - VIB - Data Size: 3.33 GB; Backup Size: 1.98 GB
5/29 - VIB - Data Size: 1.06 GB; Backup Size: 409 MB
5/28 - VIB - Data Size: 1.03 GB; Backup Size: 390 MB
5/27 - FULL/VBK - Data Size 3.27 TB (volume size?) - Backup Size 1.7 TB

On 6/1 we started an Active Full seed copy job to the cloud. It just finished this morning, 6/8. It says it copied the restore point from 5/31, which I assume means it took the chain from 5/27 to 5/31 since 5/27 is where the FULL is that 5/31 feeds off of.

VM Size: 2.1 TB
DATA Processed: 2.1 TB
DATA Read: 2.1 TB
DATA Transferred 1.7 TB (1.2x)

However when I go to the Copy Job properties to see the chain and file sizes in the cloud I see:

Data Size: 3.27 TB
Backup Size 2.06 TB

I thought this would show the size of the file at the backup repository. But it appears the BACKUP SIZE is showing the raw used TB amount on the volume, not the size of the backup.

So some questions:

How could the size of the file be 2.06 TB when it only transferred 1.7 TB?
Where do I see the actual size of the VBK file in Veeam software (either the backup job file or the copy job file post-backup)?
Does the active full on 5/31 really merge all the data from the full on 5/27 and all VIBs up to 5/31?

We have another similar file server that's bigger and we're trying to estimate how much space it will need for both the Full and 14 days of changes as well as the copy job full (just weekly fulls, no changes).

Service Provider
Posts: 57
Liked: never
Joined: Fri Jan 29, 2016 8:31 pm
Full Name: Rnt Guy

Re: understanding file sizes for backups and copy jobs

Veeam Logoby dellock6 » Fri Jun 16, 2017 1:17 pm

there are a couple of concepts you need to acquire before doing these calculations:
1- Veeam does backups at the block level, not the file level, so the size of the files in a volume may not be completely equal to the size of the backup.
2- we do compression and deduplication over a backup file, so the source size and the target size may be different.

This said, did you used by any chance the WAN accelerator for the backup job to the remote location? Because "transferred" means exactly data transferred from repo to repo, but it doesn't mean that some blocks were reused at destination by the destination cache of the wan-x for example...

for sizing, have you ever used the Restore Point Simulator?:

It may help you in these calculations.

Luca Dell'Oca
EMEA Cloud Architect @ Veeam Software

vExpert 2011-2012-2013-2014-2015-2016
Veeam VMCE #1
Veeam Software
Posts: 4989
Liked: 1308 times
Joined: Sun Jul 26, 2009 3:39 pm
Location: Varese, Italy
Full Name: Luca Dell'Oca

Re: understanding file sizes for backups and copy jobs

Veeam Logoby rntguy » Fri Jun 16, 2017 1:33 pm


No wan accelerator was used.

I get that block size will be bigger than file size depending on the files and the block size. It must be that it was able to do some of it's own compression and deduplication before sending it over. The source and target should be pretty close but the amount transferred over the wire could (and hopefully will) be smaller.

It's too bad the job properties says Data Size 3.27TB, backup Size 1.7TB since 3.27 TB is not really the amount of raw data, but the total size of the volumes. The amount of data in use is actually only 2.06 TB. It would be useful more so to see the amount of actual data you're protecting and then the backup file size. If you wanted to see the size of the volume i suppose that could be helpful but it's a bit misleading saying 'data size' when in reality it's volume size allocation not actual data size.

similarly in the backup job when it calculates the VM size it doesn't say 'used GB' just 'volume size'. Figuring out what that means was not simple from the documentation but checking a few against actual VMs you can see it's disk space in use.
Service Provider
Posts: 57
Liked: never
Joined: Fri Jan 29, 2016 8:31 pm
Full Name: Rnt Guy

Return to Veeam Backup & Replication

Who is online

Users browsing this forum: Google [Bot] and 26 guests