An incremental restore back to the original place, where changed block tracking tells Veeam which blocks to copy so only those are reverted, also usable for failback. It is meant for problems inside the guest rather than failed hardware, storage or power.
Read more: Veeam Help Center
In the Ultra Transcenders books
Each book explains quick rollback in context, with comparison tables and the common traps.
Terms in this definition
- Deployment modes
The two ways ARM can deploy: Incremental, the default, creates or updates what the template lists and ignores everything else; Complete also removes resource group contents absent from the template.
- RESTORE
Puts a Delta table back to how it was at an older point, picked by
TO VERSION AS OForTO TIMESTAMP AS OF. You needMODIFY, and onceVACUUMhas cleared the old files it can't succeed. - WHERE
Limits a SELECT, UPDATE or DELETE to just the rows meeting a condition. Omit it, and the statement hits every row.
- Changed Block Tracking
Lets incremental backups and replication read only what has changed since last time instead of whole disks. With vSphere, Veeam gets this information from VMware CBT via VADP.
- failback
Moving workloads home from replicas, either onto the original VMs (updated to match the replicas' latest state) or onto VMs somewhere new. Being provisional, it ends with a commit or a roll-back to FAILOVER.
- General-purpose v1
The older storage account kind (
Storage), which lacks access tiers, Archive and premium file shares and retires on 13 October 2026. Converting to ZRS requires first upgrading to GPv2, a one-way change.
Related terms
- Entire VM restore
Puts a complete VM back on production storage from a backup, optionally starting it on a chosen host, so performance is normal straight away. Compare Instant Recovery, which runs from the backup, and quick rollback, which writes only changed blocks.