Archiving Backup with Microsoft Azure Blob


Userlevel 7
Badge +6

Hello everybody!

Today I’m coming to talk about archive backup with blob Azure.

Archiving is good option to save money with your full (GFS) backups. It means that you can save your backups as archive instead of traditional hot/cool blob of Microsoft Azure.

To do that you need configure a Scale Out Backup Repository with the Archive Tier enable.

After that you can move your full backups older than X day to this kind of archive, as this example:

 

But first you need to configure your blob repository as an archive option. To do this go go to Backup Repositories inside Backup Infrastructure menu. Right click on the pane and chose Add backup repository

 

On this screen chose Object Storage:

 

On the next step choose Microsoft Azure Blob Storage option:

 

After that click on Azure Blob Storage Archive Tier:

 

Type Name and Description of your archive blob:

 

Enter with your Credentials for this blob and chose what Gateway Server will be used for this function:

 

On the next screen you just need to set what Container and Folder will be used to save your backups:

 

Now you just need to input your Subscription credentials on the Microsoft Azure:

 

On the Customize button you can chose the size and the network options of your Proxy Appliance:

After that just click on Ok and Apply.

 

On the last screen just click Finish:

 

So, with all these steps you configured the blob, the proxy appliance and the SOBR.

After that your backups are going to be move of the capacity tier to the archive tier in 4 hours period.

 

At the final of movement, you can see your task on Storage Management inside the History menu:

 

 

And now you can see your archive backups in Backups/Archive on Home menu:

 


14 comments

Userlevel 7
Badge +8

Great post @wolff.mateus.  Nice to see the other storage options for archiving and how people are using them.  I use Wasabi at home but at work we have Cloudian, ECS and HCPCS (HCP Cloud Scale).

Userlevel 7
Badge +5

Great guide as always

Userlevel 7
Badge +5

Nice work @wolff.mateus 

Userlevel 7
Badge +5

Nice post @wolff.mateus , thx for sharing

Userlevel 7
Badge +7

Cool stuff @wolff.mateus ! Thanks for sharing in this great post!

Userlevel 7
Badge +6

Thanks for posting this guide @wolff.mateus!

Userlevel 7
Badge +8

Great article, very clean and precise (aka easy to follow!).

 

Good work 🙂

Userlevel 3

Hi

Could someone who has done this deployment confirm that the container we add for archive tier is a regular Standard V2 Storage account with an additional cool tier .

The same is converted to archive using veeam..

Please confirm as there is no option to create an archive tier storage container

Userlevel 7
Badge +8

Hi

Could someone who has done this deployment confirm that the container we add for archive tier is a regular Standard V2 Storage account with an additional cool tier .

The same is converted to archive using veeam..

Please confirm as there is no option to create an archive tier storage container

Yes when it comes to Azure you need the regular tier and cool for it to work with Veeam. Very similar to AWS as well from what I have tested.

Userlevel 3

Thanks for the reply Chris.

So we have a customer who needs to maintain a 30 day retention onpremise ,12 Monthly and 10 yearly which will be a GFS backup methodology to be followed.

So in terms of cost estimation we would need to factor in both Cool tier , archive tier costs and the cost for the proxy appliance Standard_D2 /Standard_F4 (will run during the archiving period from cool to archive tier for a day or 2 and get deleted considering total data size is 1.5TB. 

Correct me if im wrong.

Userlevel 7
Badge +8

Thanks for the reply Chris.

So we have a customer who needs to maintain a 30 day retention onpremise ,12 Monthly and 10 yearly which will be a GFS backup methodology to be followed.

So in terms of cost estimation we would need to factor in both Cool tier , archive tier costs and the cost for the proxy appliance Standard_D2 /Standard_F4 (will run during the archiving period from cool to archive tier for a day or 2 and get deleted considering total data size is 1.5TB. 

Correct me if im wrong.

Yeah that sounds about right.

Userlevel 6
Badge +1

Nice post! There is no object lock yet in Azure right ?

Userlevel 7
Badge +8

Nice post! There is no object lock yet in Azure right ?

I believe not as yet.

Userlevel 7
Badge +6

Nice post! There is no object lock yet in Azure right ?

There's immutability available for Azure Blob since last year; I think it's even out of preview status new. But from Veeam side it's not supported, though we could see some changes with v12.

https://forums.veeam.com/post423304.html#p423304

Comment