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.
Read more: Veeam Help Center
In the Ultra Transcenders books
Each book explains failback in context, with comparison tables and the common traps.
Terms in this definition
- Virtual machines
Infrastructure-as-a-service compute giving complete control of the operating system, making it a fit for lift-and-shift moves and for software relying on OS-level pieces like COM.
- MATCH
Used in WHERE when querying SQL Graph, it describes how to walk from node to node through edge tables, with patterns written like p1-(f1)->p2.
- State
A parameter in OAuth that carries custom data through the authorisation flow and back, as with the "Support state parameter" option in APIM.
- failover
Switching workloads from production VMs over to replicas at the recovery site; replica, CDP replica and storage plans do this. The plan is left in FAILOVER until it is undone, made permanent or followed by failback.
Related terms
- backup file preference
A setting on a recovery location that chooses the source backups for a restore: Automatic (the latest restore point), Primary, Backup Copy or SOBR Capacity Tier. Failback ignores it.
- Check Networks
A plan step that keeps pinging a recovered machine and its network adapters until replies are steady or time runs out. It is used during failover, failback and DataLab testing.
- quick rollback
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.
- vSphere datastore
Where VM files live in vSphere, whether on VMFS, NFS, vSAN or vVols. Veeam's restore, replication, failback and Quick Migration wizards ask you to pick one as the destination.