From 33b4cfc68f3dd66693b322336f501a33c614d38d Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Fri, 22 Nov 2024 13:49:52 -0700 Subject: [PATCH] Update Workflows/Veeam Backup & Replication/Core Concepts.md --- Workflows/Veeam Backup & Replication/Core Concepts.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/Workflows/Veeam Backup & Replication/Core Concepts.md b/Workflows/Veeam Backup & Replication/Core Concepts.md index df8eb74..f784d3b 100644 --- a/Workflows/Veeam Backup & Replication/Core Concepts.md +++ b/Workflows/Veeam Backup & Replication/Core Concepts.md @@ -21,7 +21,10 @@ Backup jobs take many forms, but the most common are explained in more detail be ## Replication As the name states, Veeam Backup & Replication can also handle replicating Servers/VMs from either their original locations or from a recent backup and push them into a hypervisor for rapid failover/failback functionality. Very useful for workloads that need to be spun up nearly immediately due to strict RTO requirements. There are some additional notes regarding replication seen below. -!!! warning "Orchestrate Replication via Veeam, not the Hypervisor" +!!! warning "Orchestrate Replication & Failover via Veeam, not the Hypervisor" You want to coordinate anything replication-wise directly in Veeam Backup & Replication, not directly on the hypervisor itself. While you can do this, it is not only slower, but does not give you the option to failback replicas back into production if you spin up a replica directly on its hypervisor. - **Replication Restore Points**: Similar to backups, replicas can have multiple restore points associated with them, so you have more than one option when spinning up a replica in a hypervisor. +- **Planned Failover**: A planned failover is when you are scheduling the hypervisor to be offline and simply don't have enough resources to live-migrate it to another cluster host, or you might not even have a virtualization cluster to work with in the first place. In cases like this, a "Planned Failover" tells Veeam to make a fresh replica right now, then shuts down the production VM on its hypervisor, and spins up the replica on the replica server. (If you installed Hyper-V on the Veeam server, it would spin up the replica on the backup server itself). + - A "Planned Failover" allows you to perform a "**Failback to Production**" when the failover event has concluded. This means that while the production VM was offline and the replica took over the production load, any changes made such as new files added, applications installed, etc will be replicated back to the production VM when the replica is "Failed back to Production". This is the ideal choice in most circumstances. +- **Failover Now**: Failover now means that the production hypervisor is likely completely dead, and may need to be re-built, or you simply dont need to replicate changes back to production hypervisor after the failover event has concluded, such as on a low-priority print server. Any changes made while the replica is operational will be completely lost when the production VM is turned back on again or a restore is pushed back onto a new hypervisor.