From e9561a9802ff728c8a4f08535656a3818a82d35b Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Fri, 22 Nov 2024 13:41:59 -0700 Subject: [PATCH] Update Workflows/Veeam Backup & Replication/Core Concepts.md --- Workflows/Veeam Backup & Replication/Core Concepts.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/Workflows/Veeam Backup & Replication/Core Concepts.md b/Workflows/Veeam Backup & Replication/Core Concepts.md index 6110ee6..df8eb74 100644 --- a/Workflows/Veeam Backup & Replication/Core Concepts.md +++ b/Workflows/Veeam Backup & Replication/Core Concepts.md @@ -20,6 +20,8 @@ Backup jobs take many forms, but the most common are explained in more detail be - **Linked Jobs**: These are the "Backup Jobs" you want to verify in in the virtual lab mentioned above. If you have a large backup job with a bunch of machines you don't want verified, you can configure "Exclusions" in the SureBackup job settings to exclude those objects/devices from verification. ## 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. - - **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. - !!! warning "Orchestrate Replication 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. \ No newline at end of file + +!!! warning "Orchestrate Replication 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.