I thought we would be able to keep multiple backup sets with a synthetic full. This would allow a roll-up, then changes since that point in time. Sort of like a single diff instead of incrementals.

It sort of works that way, but does a roll-up, and creates a huge single file and starts a new volume backup based on that huge file. That immediately doubles our disk usage. So we're not saving any disk space at all, only consolidating smaller files into one large file. This is fine for offsite backup transfers to save bandwidth, but doesn't allow for longer retention times from what I see.

I don't see a reason to do a synthetic full on PCs. We trade a regular full backup for processing time on the consolidation and end up with a single file that has a higher chance of getting corrupted. Am I right or am I missing something?

Legacy Forum Name: Synthetic Full with Multiple Backup Sets, Huge Single File and No Savings on Disk Space,
Legacy Posted By Username: runnetworks