Backup configuration to SOBR

[FrancWest]

Hi,

we want to store the configuration backup our Veeam server off-site. Our service provider uses a SOBR for our backups. Configuration backup doesn't allow to select a SOBR as the destination for a config backup. I've also tried a file backup job to the remote repository, but that also doesn't work since it's a cloud repository.

Is there any other way to store the config offsite, except from storing it in a VM who's backup will be stored offsite using a copy job and extracting the file from the backup (be it either using Veeam itself if that's still operational in case of an emergency or using Veeam Extract)?

Franc.

[Gostev]

Hi, Franc. I'm not aware of other methods, but this is something we've been wanting to address for a long time. @Egor Yakovlev please take a look at this as well, seems like another weird limitation just to save on testing in the original release, let's see if we can unlock this capability in the next release? Thanks!

[Egor Yakovlev]

Noted and will do research on it.
/Thanks!

[FrancWest]

Hi Egor,

Any update on this?

Franc

[Egor Yakovlev]

Hi Franc.

There are no real technical showstoppers from implementing it.
Will try to make it happen, but no ETA, as usual

/Cheers!

[FrancWest]

ok, thanks!

[TitaniumCoder477]

Scenario:
1. Local repo is SOBR
2. Offsite repo is cloud repo backed by SOBR

As a result, we cannot do what we typically be the best practice: Send the configuration backup to the offsite location in case we completely lose the VM. Additionally, we cannot configure the backup to the local repo since it's also SOBR (doesn't even show in the list of targets for the config backup). So that leaves pointing it to the default C:\Backups location which I'd rather decommission altogether. As a workaround, I could add one of the protected servers into Veeam and then add one of the disks as a repo and then point the configuration backup to that, which will end up getting scooped up by the local backup job and offsite copy job. But that's pretty "jenky". At least I can mitigate the security issue by encrypting the backup file at rest. But still...

So a few questions:

• What is the technical challenge preventing config backups from going to SOBR?

• Is it reasonable to accept this challenge as unavoidable?

• Should I post a feature request, or is there one already?

Thanks!

[Mildur]

You find an official answer about this topic here, from march 2021

post405978.html#p405978

Another FR Topic about conf backup to SOBR:
veeam-backup-replication-f2/config-back ... 57942.html