Comprehensive data protection for all workloads
Post Reply
FictionalBeast
Novice
Posts: 7
Liked: 1 time
Joined: Jun 08, 2024 9:43 am
Contact:

Backup copy of a Cloud Connect repository

Post by FictionalBeast »

I inherited a Veeam CC server from an employee that has recently left as ee provide cloud connect repository for some of our customer base, so their only backup repository is our cloud connect instance. I want to have copies of these backups somewhere else for safety, I tried to create a backup copy job of the existing CC repository, but there is no way to do it. I raised a ticket with support about this, but it seems like there is no way around it and the only option give was a convoluted over the top crazy as follow:

The only thing that comes to my mind is to deploy Scale-Out Backup Repository with Capacity Tier extents on S3 Object Storage repositories. This option doesn't have advantages of the backup copy jobs but allows to copy tenants' backups to S3 as-is.

I don't want to send my backups to a hyper-scaler or anyone else, we self-host everything as provide as a service to our customers.

How do you guys work around this? I need to have a more resilient backup repository, I find crazy I cannot make a backup copy like anything else in Veeam and just store on a remote repository. This does not give me a ransomware protection for example, I want to use linux hardened as a secondary repository, but I cannot do it.
tyler.jurgens
Veeam Software
Posts: 442
Liked: 260 times
Joined: Apr 11, 2023 1:18 pm
Full Name: Tyler Jurgens
Contact:

Re: Backup copy of a Cloud Connect repository

Post by tyler.jurgens »

I handled that, when I worked with a service provider, with a Scale-Out Backup Repository. You don't need to use a hyper-scaler - any S3 will do for Capacity tier integration. For me, that meant running an S3 repository as well in house that we built (we used Minio, but there is plenty of choice out there).

You have options if you don't want to build your own S3. You could setup multiple backup/backup copy jobs from your tenant to multiple CC repositories you control. Not as smooth because the data has to travel twice (once to each CC repository), but it can work - I've done it, because I've been in your shoes.

Alternatively you could use tenant backup to tape. https://helpcenter.veeam.com/docs/backu ... ml?ver=120

If you do want to adjust your business model you could use Veeam Vault or any hyper-scaler of choice. It ultimately comes down to how much you want to invest in building your own solution verses using an existing solution already in the market. The cost of that decision is not just hardware, but also knowledge amongst your team. Partnering with a vendor of your choice can still leave you with the margins you need for your business, and the outcomes your customers require, even without building the solution it yourself. The benefit of partnering with a vendor of choice is you can turn around this product offering a lot faster than if you had to build your own solution.

Keep in mind you can always use a Veeam Hardened Repository for your Cloud Connect repositories directly for that immutable storage.
Tyler Jurgens
Blog: https://explosive.cloud
Twitter: @Tyler_Jurgens BlueSky: @explosive.cloud
Post Reply

Who is online

Users browsing this forum: AdsBot [Google], Baidu [Spider], Google [Bot], Semrush [Bot] and 28 guests