[Feature Request] - Config Backup to object storage

[DE&C]

Life could be much easier if the config backup could be done directly to object storage.

Goal

• To be independent of any repository that is used from Veeam,

• geo redundancy

• ransomware-protection

• Use of multiple vendors/provider at the same time (3-2-1)

• One single configuration, no "copy" etc. needed

Idea

• Add to config backup the possibility to add multiple buckets from different vendors

With this, we could add 2 or 3 providers and with just one job sent the backup to cloud. This would make my live as a system-integrator much easier to design solutions and for the customer to re-use in case the VBR server is down.

This should be one of the simplest use case to integrate, compared to all the high-level work Veeam is doing with SOBR + capacity tier

Why this would make my live much easier?

Case 1 - SMB customer

• Has a dedicated VM for VBR

• Can now use S3 with object lock to have a 1:1 copy of his backups. 3-2-1 and ransomware proof

• The only pain is now: how to get the config backup at the same level as his "normal backup"?

Instead of now the need of copy the backup somewhere or use a file copy job it would be much easier just to use a dedicated bucket. In a worst-case szenario the steps are very easy

• Setup VBR "naked" without any data

• Add one bucket with the config backup and load it for a restore

• Wait and grab a coffee

[veremin]

Hi, William,

The request to add:

- ability to run configuration backup to object storage repository
- ability to chose object storage repository during configuration restore

sounds quite reasonable, so, consider your voice heard.

Thanks!

[HannesK]

Hello,
I just saw that post when searching for something else... so I'm updating it now... configuration backup can be stored in object storage in V12.

Best regards,
Hannes

[ChristophWeber]

@HannesK
Hi Hannes. Thanks for the update regarding the configuration backup. I tested in the LAB. I was able to write the configuration backup to an MS Azure Repo with Immutability. My question now would be if "immutability" for the configuration backup is officially supported in such a scenario.
Many thanks for your update.

Best regards, Christoph

[veremin]

Currently, the configuration backups will be non-immutable, but we are planning to address this limitation in one of the next product versions (minor one, most likely). Thanks!

[jstiver]

How do you complete the configuration restore from S3 object storage? I connected it as a backup repository and imported the backups but I don't see anything in my inventory and I don't have the S3 repository as a selection in the restore wizard drop-down box.

[HannesK]

Hello,
and welcome to the forums.

don't have the S3 repository as a selection in the restore wizard drop-down box

that sounds like a bug, because I can see it. Can you please post the number for your observations?



Best regards,
Hannes

[jstiver]

I figured out the issue. It will not show in the list if you run "import backups" after adding the S3 repository.

[Mildur]

For a configuration restore, you can also just download the BCO file from your object storage and restore it on a new backup server. Use the web UI from your object storage provider/appliance or a S3 explorer such as "S3 browser" or "Cyberduck" to download the BCO file.
May come in handy when you don't want to connect to a bucket first.



Best,
Fabian