Synthetic Full Backups: Getting a Full Backup Without Running One

The Full Backup Burden

Full backups are valuable because they capture everything in one complete copy, making restores simple, but they are expensive to run: they take a long time, consume significant bandwidth and storage, and strain the systems being backed up. This burden is why organizations avoid running fulls frequently, relying on incrementals or differentials between them. The synthetic full backup offers a clever way to get the benefit of a full backup, a complete up-to-date copy, without paying the cost of running one, which addresses the central tension between the simplicity of full backups and the burden of creating them. Understanding how it works reveals why it has become a valuable technique.

What a Synthetic Full Is

A synthetic full backup is a complete backup assembled from existing backups rather than captured fresh from the source systems. Instead of reading all the data from production again, the backup system combines a previous full backup with the subsequent incrementals to construct a new, up-to-date full backup. The result is a genuine full backup, a complete copy as of the latest increment, but it was built from backups already on hand rather than by burdening the production systems with another full read. A well-implemented synthetic full backup delivers the complete copy a traditional full provides while sparing the source systems the load of producing it.

How It Is Built

Building a synthetic full works by merging. The backup system starts with the last full backup and applies each subsequent incremental in order, exactly as a restore would, but instead of restoring to production it writes the merged result as a new full backup. The merging happens within the backup infrastructure, using the backups already stored, so the source systems are not touched. The product is a new full backup reflecting the state as of the most recent incremental, assembled entirely from existing backup data. This construction is what lets the synthetic full exist without a fresh full read, turning stored backups into a new complete copy through merging rather than recapture.

Sparing the Source Systems

The central benefit of the synthetic full is that it spares the source systems the burden of a traditional full backup. Because the synthetic full is built within the backup infrastructure from existing backups, production systems are not subjected to the heavy read load, bandwidth consumption, and performance impact of another full backup. This matters especially for busy systems that can ill afford the strain of frequent fulls, or for environments where backup windows are too short to accommodate a traditional full. By moving the work of creating a full backup off the source systems and into the backup infrastructure, the synthetic full removes the main reason organizations hesitate to have current full backups available.

Faster, Simpler Restores

A synthetic full backup delivers the restore advantage of a traditional full: because it is a complete copy, restoring from it requires only that single full backup, not a full plus a long chain of incrementals. This gives the fast, simple restore of a full backup without the cost of running one. An organization using synthetic fulls can keep a recent complete backup available for quick recovery while still enjoying the efficiency of incremental backups from the source systems. The synthetic full thus combines the best of both: the efficient, low-impact incremental capture from production and the fast, simple restore of a full backup, assembled where the two meet in the backup infrastructure.

Reducing the Restore Chain

Beyond providing a fast restore point, synthetic fulls keep incremental chains short, which benefits any restore. Without synthetic fulls, incrementals accumulate between infrequent traditional fulls, lengthening the chain a restore must apply and slowing recovery. By regularly constructing synthetic fulls, an organization effectively resets the chain without burdening production, so restores never have to apply an excessively long series of incrementals. This keeps recovery times bounded even as the organization relies on efficient incremental backups day to day. The synthetic full thus solves the incremental approach's main drawback, the growing restore chain, without reintroducing the burden of frequent traditional fulls that the incremental approach was adopted to avoid.

Immutability for Synthetic Fulls

Like any backup, synthetic full backups must be immutable to defend against ransomware, which targets backups to prevent recovery. The synthetic full, being a complete and recent copy, is an especially valuable recovery point, which makes protecting it with immutability all the more important. Immutable synthetic fulls, unalterable during retention even by a compromised administrator, ensure that this convenient complete backup survives an attack and remains available for the fast recovery it was built to provide. Applying immutability to synthetic fulls is what ensures that the technique's benefit, a readily restorable complete copy, is not lost to an attacker who would otherwise target exactly such a valuable backup first.

The Best of Both Worlds

The synthetic full backup resolves the tension between the simplicity of full backups and the burden of creating them by assembling a complete, up-to-date full from existing backups rather than capturing one fresh from production. It spares the source systems, delivers the fast simple restore of a full, and keeps incremental chains short, all without the cost of running a traditional full. With immutability to protect this valuable recovery point against ransomware, the synthetic full gives an organization the best of both worlds: efficient, low-impact incremental capture and the quick recovery of a full backup, which is why it has become a technique worth understanding and using. For organizations that long accepted the weekly full backup as a necessary burden, straining their systems and tying up their backup windows, the synthetic full is something close to a free lunch: the same complete, restorable copy they always needed, produced without the cost that made full backups something to minimize rather than embrace, which is a rare case of a technique that improves both the efficiency of backups and the speed of recovery at the same time rather than trading one for the other. That rare combination is what has earned the synthetic full its place in modern backup design, and why an organization still running heavy traditional fulls out of habit owes it to itself to look at what the synthetic approach could save.