Comprehensive data protection for all workloads
Post Reply
alainseys
Novice
Posts: 5
Liked: never
Joined: Dec 15, 2017 2:00 pm
Full Name: Alain Seys
Contact:

Veeam second copy to wasabi

Post by alainseys »

Hello,

Can someone assist me with this use case?

Currently we have 2 veeam servers running (v13), with Backup and Replication at both ends.
This backs up the local vms on dc1 , then with backup copy i send it to DC2.

When thats done i want on DC2 that the received backup is send to wasabi.
Note this has to run on DC2 so DC1 is offloaded so its free to perform the general backup.

DC1-VEEAM (main backups , copy job to dc2)
DC2-VEEAM (received jobs from dc1 to wasabi)

How can is confiure this ?
What i have done so far:

DC1:
Add: local repo
Add: remote repo (dc2)

DC2:
Add: wasabi repo
vnikiforov
Product Manager
Posts: 108
Liked: 34 times
Joined: Aug 17, 2022 5:03 am
Full Name: Vladimir Nikiforov
Location: Romania
Contact:

Re: Veeam second copy to wasabi

Post by vnikiforov » 1 person likes this post

Hello, Alain,

This isn't doable with two backup servers. In Veeam, repositories and remote components (gateways, proxies) are owned by a single backup server and can't be shared between two, so DC2's server can't take over and offload backups that DC1 created. An External Repository doesn't fit either: it's read-only and only imports cloud-native backups from Veeam Backup for AWS, Azure, and Google Cloud.

Run it all from one backup server (VBR-1 in DC1) that manages both sites:
  • DC1-repo: local repository at DC1, any type you like
  • DC2-repo: a repository physically located at DC2 (any type you like)
  • DC2-gateway: a server located at DC2 that will manage all offload traffic to Wasabi
  • Wasabi-DC2 an object storage repository on VBR-1 in DC1, with its gateway server set to DC2-gateway
  • A scale-out backup repository with DC2-repo as the performance tier and the Wasabi repo as the capacity tier
  • Source backup job: DC1 VMs to DC1-repo
  • Backup copy job: DC1-repo to the SOBR with subsequent tiering to Wasabi
Flow: the source job runs the primary backup locally at DC1. The copy job lands those backups on the SOBR, whose performance tier physically sits at DC2. The capacity-tier offload then reads from DC2-repo and uploads to Wasabi through DC2-gateway, so the cloud traffic originates at DC2. DC1 is busy only for the initial backup. Set the copy/move policy and retention to your liking; a support case can help tune the SOBR settings.

As for the VBR-2 in DC2 it could be used for disaster recovery and possible restores in case of disaster.
---
BR,
Vladimir
Veeam Software
Post Reply

Who is online

Users browsing this forum: Bing [Bot], Michael.A, Semrush [Bot] and 2166 guests