hesela.devSynthetic full backup
A synthetic full backup reconstructs a complete backup for a selected recovery point from retained full and incremental backup data without rereading the entire protected dataset from production.
Synthesis reuses existing backup data. Veeam's documented Hyper-V workflow first takes a new incremental backup, so the overall job still reads recent production changes. [2]
Relations
- related
- full-backup, incremental-backup, backup-manifest, backup-verification, restore-test
Advantages
- PostgreSQL can use a combined full backup in place of its source chain for a later combination. [1]
Limitations
- PostgreSQL pg_combinebackup checks chain relationships, not the integrity of every input. [1]
- With pg_combinebackup --link, hard-linked input and output files can affect each other when modified. [1]
- PostgreSQL --no-sync skips the final durability wait; checksum-state changes across inputs can leave invalid page checksums. [1]
- Linux reflinks isolate later writes through copy-on-write but still share underlying storage; they are not independent media copies. [4]