Which Veeam technology meets a recovery point and recovery time objective, and what each keeps.
From Ultra Transcenders VBR-13 by Tony Rough (coming January 2027)
The three technologies answer different questions: how much data can be lost (RPO), how fast service must return (RTO) and how far back recovery must reach. Figure 9.1 places the three technologies by RPO and RTO and shows what each keeps.
| Characteristic | Backup job | Replication job | CDP policy |
|---|---|---|---|
| Capture method | Snapshot, written to backup files | Snapshot, written to a VM copy | I/O filter, no snapshots |
| RPO guidance | Interval between scheduled job runs | Hours | 2 seconds to 60 minutes |
| Storage format | Compressed, deduplicated backup files | Decompressed native VM | Native VM plus transaction logs and delta disks |
| Recovery | Restore, or Instant Recovery from the backup | Failover in seconds | Failover to a short-term or long-term point |
| Depth of history | Retention, GFS and copies | 28 points (vSphere) or 47 (Hyper-V) | Short-term up to 7 days; 95 long-term points per disk |
| Platforms | All supported workloads | vSphere, Hyper-V; Proxmox VE VM replication added in 13.1 | vSphere VMs; Universal CDP for Windows and Linux machines |
| Automated verification | SureBackup | SureReplica (vSphere) | SureReplica (vSphere) |
Decision rules:
Common trap: Using a replica as the long-term history of a VM - a vSphere replica keeps at most 28 restore points and a CDP replica at most 95 long-term points per disk, while backups with GFS retention can reach back years.
This note is one section of Ultra Transcenders VBR-13: Veeam Backup & Replication 13, an independent study guide that explains every topic the course covers by technology, with comparison tables, diagrams and the common traps, plus a glossary linked to the Veeam Help Center.
Due on Amazon in January 2027, in Kindle and paperback editions.
About the book · VBR-13 terms in the glossary · All VBR-13 study notes
How a backup proxy reads VM data, the order Veeam tries the modes in, and when it falls back to Network mode.
Where the full backup sits in each chain, what each method costs in storage and I/O, and why reverse incremental is deprecated in v13.
Immutability, single-use and certificate-based credentials, and what a hardened repository will not let you do.
How each backup copy mode picks restore points, when it runs and how GFS fulls are created.