- Posts: 122
- Liked: 16 times
- Joined: Aug 28, 2013 9:46 am
- Full Name: Thomas Braun
- Location: Germany.Europe.Terra.Sol.Milkyway.Localgroup.Virgo
when looking at the backup jobs for my Exchange server, I typically see the following numbers:
Transferred: 6,6 GB
The numbers for read/transferred vary from job to job, but only a few GB more or less.
When I look at the actual size of the backup files on disk, there is a .vbk file with almost 156GB and several incrementals ranging from 5 to 10 GB
I'm actually wondering how this can be, especially for the full backup file, shouldn't there be a backup job with much higher "Transferred" amount?
Is this what "synthetic full" does? Is the .vbk file not actually backed up in realtime but the result of merging older incrementals into a new full backup?
- Veeam Software
- Posts: 17712
- Liked: 1481 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
Exactly. If you're running synthetic fulls (not active ones), VM data is not retrieved from the datastore to make the next full, but the full backup is rather synthetically built up from the data you already have in the backup repository. So the amount of transferred data is the size of the incremental changes, as an ordinary incremental job run is always performed prior to creating synthetic full. Please refer to the corresponding user guide section for more details. Thanks.TommyB wrote:Is this what "synthetic full" does? Is the .vbk file not actually backed up in realtime but the result of merging older incrementals into a new full backup?
Users browsing this forum: No registered users and 10 guests