Veeam Backup & Replication • Re: Synthetic full backups and file versioning

Hey Kurt, will add my 2 cents on the topic.

>I'm finding it difficult to see the added value in synthetic full backups

Value is simple:

1. Workload for creating a full backup is shifted from production to the repository
2. With Fast Clone, you get fast & "space-less" full backups
3. Full backups are usually a requirement

I think part of where you're getting thrown a bit here is that you need to differentiate between image level backups (backups of the entire machine) vs the granularity of file version backups that you've been asking about.

Image level backups capture the state of the machine at time of backup, as was mentioned before in the thread by others. If you're needing more granular control over file versioning, a file-level approach with Unstructured Data Backups is best, as that gives you the fine file level version control with minimal storage foot print.

You can have that kind of file version control with image level backups, it just means you will be having many incremental restore points to reflect that level of granularity -- if that works for you, then it works for you; Enterprise Manager allows you to browse through the guest file index to look for files from image level backups of a machine and helps a lot if you do go with this approach.

So from your original post, you ask about how it handles all the different file versions in a Synthetic Full, and the answer is simply that it doesn't really care, the goal of an image level backup is to capture the state of a machine at a specific point in time.

If you need more granular file level versioning than you get with the frequency of image level backups, use a file level backup approach like Unstructured Data Backup (this can be done in addition to normal image level backups, and it's pretty common option when both are required)

Statistics: Posted by david.domask — Oct 24, 2025 10:14 am

---