- Posts: 2
- Liked: never
- Joined: Jul 08, 2021 6:47 pm
- Full Name: Jake Ryan
To implement a Scale-Out Backup Repository we want to deploy local dedupe placed before a Linux hardened device to keep our data immutable for 30 days. We would then move data to Azure.
We read "Product x is great but it breaks the concept of 3-2-1 Backup Rule with global dedupe. You want your second off-site copy to be 100% independent from your primary data centre."
If we dedupe locally are we at risk of impacting our ability to recover if our data centre burns?
Any help is appreciated.
- Veeam Legend
- Posts: 1682
- Liked: 675 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: St. Gallen, Switzerland
Your SOBR configuration
- Performance Tier: „deploy local dedupe placed before a Linux hardened device“ (What is that exactly? A Linux hardened Repo with xfs FastClone should be enough, no need to add a second local dedup whatever that would be in your case)
- Capacity Tier: „azure Blob Storage“
Your offloaded backups in Azure Blob Storage are 100% independent from the local backups.
If your datacenter burns down (or you loose your performance tier) and you loose your local backups on the performance Tier, you can install a new VBR Server and connect it to the Azure Blob Storage.
You can then restore all Data without having access to the old performance tier directly from the capacity tier.
At the moment, there is only immutable backups for the Linux Hardened Repo. Azure Blob Storage doesn‘t have immutable backups yet, but it should be possible in one of the next Veeam versions.
Working with Veeam since 2017 for a VCSP in Switzerland
Users browsing this forum: No registered users and 10 guests