Ok, VeeamON is done & over, so we’re back in full “question” swing this week. 
Here’s this week’s first question…
And of course, please remember to hide your comment!
Your Veeam Backup & Replication server OS is nearing end-of-life, so you decide to build a new Veeam server. What is the best way to retain all your Veeam and Job settings on the new server?
- It’s Veeam!...it just works after install!
- Open SQL Management Studio, right-click the Veeam Database, and select Backup. After installing Veeam on the new server, Import the backed up SQL Database
- Perform a Configuration Database Export operation
- Perform a Configuration Database Restore operation
- Perform a Configuration Database Migrate operation
- It's Veeam best practice to install Veeam in a greenfield manner and reconfigure all your Jobs and settings
Theoretically, b. can be done, but this is not a recommended backup/migration/restore process for the Veeam DB. If you know Veeam and, at the very least, skimmed through the User Guide on the Veeam DB backup/restore process, you know this isn’t a listed procedure. There is no such thing as a Config DB export process, so c. isn’t correct. F. is a possible soluton, but no...it isn’t a Veeam best practice, which leaves only d. and e. as possibilities. To differentiate a Restore vs Migrate operation, you simply need to glance at the User Guide to see when Veeam recommends to use 1 vs the other. For Config DB Restores, Veeam recommends this operation when you want to keep your VBR server, or SQL/PSQL if a separate server, in tact, but need to perform a Config DB recovery in case of corruption or perform a Config DB rollback of sorts. You perform a Config DB Migrate operation when you want to build a new Veeam Server, and/or new SQL/PSQL server, and keep all your configurations and settings. Review the 2 links below for further information.