3-2-1 with VB4A

[pirx]

Hi,

I'm sure I'm missing something obvious, but there seems to be no build in feature for copy jobs in VB4A. We currently backup to a S3 bucket wich has 3 copies in different availability zones, but as we all know, this is just like one copy. I found this https://helpcenter.veeam.com/docs/backu ... ml?ver=110 but it looks like this is only for copy to local repository. What do I need to do to create a second copy of my EC2 instances in a different zone or even at a different provider (Azure/Wasabi whatever)?

[nielsengelen]

Within VBA, you can tier to either Glacier storage or you can integrate with VBR and use backup copy job from there to anywhere you want (local, other clouds,…).

[pirx]

Ok, I tried it in VBR but could not chose any S3 bucket. I guess because they are all part of a SORB already.

[nielsengelen]

You can find more information about backup copy jobs via the integration in the user guide and the specific backup copy job section.

You should be able to use a SOBR that has an S3 bucket as a target.

[pirx]

We already use copy jobs a lot. I can't use a SOBR as I don't want a local copy, I need a copy at a different cloud provider. I'll create a test bucket and see how this works.

[nielsengelen]

In this case, if you (for example) use Azure Blob in the SOBR repository, it should work but currently requires a local copy to tier it off (copy/move). Enhancements for this are being looked into for a future version.

Have you considered making the daily backups in the current region/az and use another bucket for weekly/monthly/yearly backups within the policy schedule as another option?

[pirx]

Separating daily/weekly does not help, our policy requires a copy of each backup. If I understand right, it's not yet possible from within VB4A appliance or VBR to directly create a copy to a different S3 bucket/vendor?

[nielsengelen]

Correct, at the moment this is not possible within VB for AWS. In VBR, it requires a local copy to SOBR (which could be seen as offsite copy) and then tiering to another vendor.

We will look into improvements for this in the future based on your feedback/request.