- directly buckets as a target for the config backup
- Configure multiple targets to have the config backup on multiple location
For the second point: When multiple target can be configured we could use a local disc on VBR where we can directly access it and on the same time have an offloading into the cloud.
A third option would be to use object lock (immutable) config backup. So even ransomware or an insider attack on the VBR would not be a problem to get the config back. Of course assuming that the rest of the data is protected to. But at the moment the single point of failure on the object storage scenario with object lock is the VBR config backup / file.
I don't see any problems here with the buckets, if the buckets are only used for the config backup. on a DR szenario you only setup VBR and put in the credentials of the bucket. From this point you gain access to your config (of course you need the encryption key if the backup is encrypted).
This Feature would help me on a lot of scenarios from small to medium business customers