Using Azure with Veeam

[Archipelego1]

Hi all,

 

I thought I'd create a separate thread from my original Cloud question, as this is quite specific.

We currently have Veeam 9.5 U4 and are using it to back and replicate our VMWare VM's. Veeam runs backup jobs on a daily basis, then once per month carries out a copy job to a different repository. All onsite.What I'd like to do is configure Veeam to send backups to Azure, either once per week or once per month.I found the following website : https://www.carysun.com/step-by-step-to-use-veeam-archive-on-premises-data-to-azure-blob-veeam-azure-blob-mvphour/ that talks you through some of the steps. I'm up to step 28, at which point the guide references making sure the extents are not the same as the target backup repository. This is the bit I'm confused at, as the extent is part of the current backup infrastructure.Does anyone know of a guide as to how I can setup Veeam to do what I require? As I'm struggling a bit to find a definite answer to what I'm trying to achieve.

[Steve21]

The best way to do it would be to create a secondary storage area (or just a new repository etc within veeam), and then just use that for your scaling. If you do it on the old one it'll auto enable scaling for all jobs.

 

Though by the sounds of it what you're asking isn't really designed to do that, the way you're setting this up is for when the local storage is basically full up it'll offload the oldest to the storage blob. So like your monthly backup will physically move offsite to Azure, it's not like the copy job where it creates a secondary one.

 

If you're expecting to end up with an on-site monthly backup and off-site (same restore point etc) which it sounds like you were I'm not sure if this will do what you want compared to CloudConnect etc

 

Steve

[Archipelego1]

Thanks for the reply. I'm basically trying to get a VM level backup into Azure storage, probably on a weekly basis.

 

Thought a backup copy job would be the best way of doing this, but understanding how to get Veeam to see the Azure storage as a repository is where I'm coming a bit unstuck. Or would it be better to run another independent backup job that just uses Azure?