Veeam Synthetic Full

I am trying to understand What Synthetic Full Backup backs up as data.
I thought it will create a full backup from storage and inject the incremental backup it has created the same day to the Full backup.

However looking at the Veeamone reporter, I see under Transferred (GB) column 48.13 GB,  it is less than the incremental one day before.

Any Veeam Expert to explain the report as shown in the screenshot below:

Thank you
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

The synthetic full backup is collection of last full backup + all incremental backups, it don't retrieve from data store but collects from previous backups

Only thing before creating synthetic backup, it 1st create one incremental backup and then create full backup, however after creating full synthetic backup, Veeam deletes last incremental backup

hence whatever you seen is incremental backup and not synthetic backup
jskfanAuthor Commented:
in the report above, why Synthetic Full is smaller in size than incremental
if you check again, data size remains same however the amount of compression can be plus / minus

further synthetic full is aggregate of last full and all incremental except last one (which is triggered before synthetic backup)

All you need to check if backup logs are appropriate
jskfanAuthor Commented:
on the Report, it shows that there are 8 VMs backed up, Total 8 VMs size is 480 GB (Source Size)

how can you explain the Transferred (GB) and Total Backup Size(GB), even though it is the Synthetic Full, but it shows almost as the smallest in size compared to other incremental Backups. you would think it should be the opposite,
what I am trying to tell is whatever you see is not synthetic full backup, it is incremental backup which triggered prior to synthetic backup
jskfanAuthor Commented:
Ah where is the Full Backup ?
jskfanAuthor Commented:
my Thought was When synthetic full runs, it  first creates incremental backup , but it also creates Full backup from the repository and inject all the incremental backups  to the new full backup. However I cannot see it on the report.
jskfanAuthor Commented:
I put a screenshot for several Synthetic full backups, probably it will give you a better picture to figure out how it works.

I have noticed on the 6th Incremental Backup , the Total Backup Size(GB) is smaller than the previous Total Backup Size(GB) of the 5th incremental backup.

I do not know where the numbers , I indicated with red mark, came up from ?

Thank you

Blue Street TechLast KnightCommented:
Hi jskfan,

What is the actual backup method you are using:
  • Forward incremental
  • Forward incremental, active full
  • Forward incremental, transform
  • Forward incremental, synthetic full
  • Reversed incremental
  • Synthetic full with transform to rollbacks

Based on your report it looks like Forward incremental, synthetic full but please confirm because it could be a few others listed above. Also, what is your Maintenance plan set to? What you are seeing in your report looks like you have configured Backup Chain Transform, which transforms the Active Full and the Synthetic Full so that all you have on your disc is a Synthetic Full. This transform option would reduce the amount of space required to store backups, which I suspect is why during your Synthetic your storage size shrinks. Check this by looking in your backup chain for VRB (reverse incremental backup) files or go into Job Settings > Advanced > Backup > Incremental > and see if Transform previous backup chains into rollbacks option enabled. Also, for the data small growths then reduction consider deleted content with dedup running.

If you have this configured I really think this is a risky practice...I like to see an Active Full always in the case the worst should take place and your original Full was partially corrupted and now your Synthetic has been created from a tarnished iteration.

Let me know how it goes!
Blue Street TechLast KnightCommented:
I updated my last post....please refresh and respond to see changes!
jskfanAuthor Commented:
Here is the Synthetic Configuration for Veeam Back up job
Blue Street TechLast KnightCommented:
Great thanks! And what about your Maintenance tab...can you screenshot that for me?
jskfanAuthor Commented:
Maintenance screenshot:

Blue Street TechLast KnightCommented:
Something is running that is reducing the size every Friday. You should definitely enable Storage Level Corruption Guard, which runs health checks to prevent corruption. An automatic health check can help you avoid a situation when a restore point gets corrupted, making all dependent restore points corrupted, too.

 If you are concerned that the data is not being backed up you can you run the health check immediately and then test restore.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jskfanAuthor Commented:
Thank you ... I am not using Veeam now
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.