Alternate Cloud Storage Options (Wasabi)

[donkeymagic]

Hi All,

This feature would not be limited just to Azure backups but also AWS and Google as well. While I appreciate that each respective appliance gets tied into the API's available by each respective platform so therefore uses the storage associated AWS goes to S3, Azure goes to Azure blob the only option to export this anywhere else is to have a copy job back to a Veeam Backup and Replication server which is great to give some flexibility and export the data 1. off the platform and 2. give alternate options for long term storage.

What I was wondering is with Veeam getting more and more integrated with Wasabi whether or not it would be feasible to allow the cloud compute appliances the ability to export to other storage such as Wasabi. While I appreciate there will be export costs from each cloud platform the significantly cheaper storage offered by Wasabi would potentially be worth it. We are finding more and more that protected AWS/Azure resources using Veeam is very costly especially when factoring in long term retention and trying to follow the 321 rule not to mention 32100 or however many zeros we are up to now. I can't imagine there are too many technical reasons why Wasabi could not be used for cloud repos (especially with the AWS appliance as its already classed as S3 compatible) its just whether it would be cost effective or not, to me it potentially would be but curious as to what others think.

Oliver

[nielsengelen]

Hi Oliver,

If you integrate VBR with our cloud products, you can use VBR to make copies to Wasabi. Have you considered this option?

There are currently no plans for direct integration with others from within the product.

[donkeymagic]

Hi,

I've already had a support case for this issue as at present but I was just told the same as what you have stated with there are no plans for future integration and I should raise it on here to get some feedback. At present I am aware that you can copy the data out of Azure/AWS Appliance backups back to a local Repo using VBR but at that point you cannot create an additional copy job to send it to Wasabi or another third party unless you send the entire repository which then has its own limitations/issues or I would have to use a SOBR with Wasabi as the capacity tier. It just seems like a lot of steps when the Azure/AWS appliance could be built to support different types of object based storage and have it built in, assuming that there is a call/need for it and it would be cost effective.

My reasoning for wanting to do this is Azure/AWS object based storage is quite expensive when compared to Wasabi especially for long term storage and as I originally stated trying to follow the 32100 rule everything is held within the same platform that you are protecting so is a bit of an oversight. It would be good to have some alternative options.

[nielsengelen]

With v12, you should be able to actually copy from object storage to object storage. Not only local repository. It will also offer you more restore capabilities (out of any cloud to anywhere).

We’ll note down your request for sure but as we already have these capabilities via VBR, we’ve noticed most customers benefit from the additional advantages of the platform.

[donkeymagic]

So if it is possible why have I been told via a support ticket to raise a post on here?!

I am currently running V12 and the latest version of Azure Appliance and it won't allow me to do this with an error. I raised this as a support ticket and was told its not possible?!

[nielsengelen]

Can you share the support case ID to better understand your setup?

[donkeymagic]

Hi Niels,

The case was 05985012 (To say I was frustrated with the initial responses from the case is an understatement and will be reflected in my feedback) but I've advised for it to be closed now as with your comments of what I wanted to do being supported and possible, I have resolved the issue that I was having and now have some VM's being copied from AWS S3 storage via VBR to Wasabi object based storage. How efficient this will be from an egress, processing and cost basis is yet to be determined over the course of a few weeks and some testing but good to know that it is possible.

I would like to keep the suggestion however of the feature that allows the direct use from Azure and AWS appliances to use other storage rather than just the native platforms. Surely this would be more efficient in the long run rather than having to use VBR as a go between.

[Markusd]

Watching this with interest. We have 500TB or so of long term, AWS backups of EC2 instances in S3, that is costing a motza. Would like an opportunity to move to cheaper storage like Wasabi..

[nielsengelen]

Hi Markus, understood. No updates for now as to the only workaround is an additional copy using VBR.