I have been asked this often enough that I thought I would answer it here! This is what I do:
- I have a password protected backup config. With it being password protected it will protect passwords too. This is a complete copy of your config and with it and the basic and quick install you are done at recovering. This is very important and worth doing regardless if you are using a remote SQL db or not (I use the embedded SQL). I store this backup config on different media from where I do backups.
There are several other options that I know work good.
- You can replicate the backup server to another location. If you have the embedded SQL server then this is in fact ready to be turned on. You should replicate it at least daily.
- You can use the Veeam Agent for Windows (even the free one) to backup the Veeam backup server. Again, if you have the embedded SQL server you have a complete copy of your backup server and ready to recover.
- If you have a remote SQL database, the replica, or the Agent backup once turned on or recovered will need to be pointed at the existing DB. In SQL, you have many options on how you might protect the Veeam database.
No matter what you do, make sure you have at a minimum the backup config done.