Protect Configuration Database

There is a feature request open for a long time to get a secondary location ootion for the configuration backup. But it is not realized up to now.

At the moment we copy the configuration backups with an script to a secondary location.

Hello @Dale Johnson, Kindly see the following link: https://forums.veeam.com/veeam-backup-replication-f2/configuration-backup-copy-job-t34390.html 

Yes, I think this is the thread I was talking about. Thank you for finding it so fast @Iams3le  😎

You are welcome

Not the answer to the question you asked but something to think about:

Consider moving your Veeam B&R server to your DR site and then replicate it to production, will improve your RTO as you won’t be trying to recover your Veeam server before recovering workloads in a DR event, and if you have a problem with your DR site you can restore your Veeam server in your production site, much easier to focus on restoring the Veeam server when there’s not a Severity 1 down going on around you!

I always recommend my customers: treat your configurator backup according to the 3-2-1(-1-0) rule. A very easy and simple - and not dirty - solution is to copy the configuration backup to a location that is backup by VBR anyway. This way you treat it like your production backup. Copy can be done by file-copy job within Veeam or a scheduled robocopy task for example.

All our Off-site backup repositories are in a SOBR. We have to add the repo a second time with another path to be able to backup to this repo.
 

I get that; however, that is like a 2 minute task so I would strongly recommend to just do it.

yes we do :)

I have always practiced storing the configuration backup on encrypted offsite/cloud storage.  Then make sure you have two copies of your encryption key, one in secure electronic password database and 1 paper copy.   That key should rarely change, so a paper copy should last the life of the install. This is from a service provider perspective where you have multiple Veeam deployments being managed.  Follow 3-2-1 rule for your configuration backup as well….waiting on that feature to be added.