I am misunderstanding or overlooking something on my Veeam backups, but either way, could use some help. Here is the situation. I have a Server 2012 VM that is our main file server. It has 3 local volumes on 3 vmdk files. C: is the OS, J: and K: are 2 data drives that have 2012 data deduplication enabled on them. Here are the numbers from the OS:
DriveSize/Used Space /Dedup Savings
C:50 GB /15 GB /N/A
J:500 GB /167 GB /42 GB
K:750 GB /497 GB /119 GB
Totals1.3 TB /679 GB /161 GB
I ran a Veeam full backup of the server with in-line data deduplication enabled. The Job details show the VM size: 1.3 TB (1.0 TB used). I'm not sure where it is getting the 1.0 TB used value?
The main issue is, the backup file (.vbk) is 987 GB. Here are the numbers from the job:
Hard Disk 1 (50.0 GB) 17.1 GB read
Hard Disk 2 (500.0 GB) 323.1 GB read
Hard Disk 3 (750.0 GB) 723.1 GB read
Processed: 1.0 TB (100%)
Read: 1.0 TB
Transferred: 986.7 GB
Even if the backup re-hydrated the files before backing up (I don't think it is designed that way) that is only 840 GB of uncompressed raw data. How can the backup file be 147 GB larger than the raw data. I know there are vmx files etc. backed up, but those take up minimal space. How is the data read from each hard disk greater (by far) than the amount of data on the disk (whether you factor in deduplication or not)?
I would expect the vbk file to be close to 679 GB, or perhaps even a bit smaller with in-line dedup/compression enabled for the job.
Can someone help shed some light on what's happening here?