What to expect when using .bco file when upgrading version of Veeam

[37rellimcm19]

We're planning on upgrading from Veeam 9.0 with MS SQL Lite currently as the back end database to Veeam 9.5.4 with MS SQL Standard for the back end. Only changing the version of Veeam and version of MS SQL version.

Currently we are backing up 7 days of the Veeam Backup and Replication Server .bco file.

If we upgrade versions and then import the .bco file from the Configuration Backup Settings Window and clicking restore and pointing it at the latest .bco file, it should not have an issue upgrading from version to version, correct?

Also, what other info and/or setttings does the .bco file import into Veeam?

thanks

[Gostev]

Configuration backups contains everything, so after restoring it will all be the same as on the original server/database.

However, 9.0 configuration backup is too old and cannot be imported into 9.5 Update 4. So you should upgrade your 9.0 install to 9.5 Update 4, create configuration backup, and then change the database and restore.

Thanks!

[foggy]

Hi Chris, please check your current Veeam B&R version. Unless it is earlier than Veeam B&R v9.0u2 (9.0.0.1715), you can import the configuration to v9.5u4 directly.

[37rellimcm19]

Hmmm...Checked the version, which is: 9.0.0.902

Looks like we won't be able to import the .bco when we do our upgrade, correct?

thanks

[Gostev]

Correct, since 902 is lower than 1715.

[37rellimcm19]

Still doing more research on this.

If we can't use the .bco file with our upgrade. Is there also any way to import out old previous backup jobs? Or will it be a manual process to recreate all of the backup jobs?

Currently have Windows 2008 Server, with MSSQL Express backend on a physical HP Server. This will be replaced with Windows 2016 Server, using a Golden Image on the same physical HP Server. Then install MS SQL Server 2017 Std with Veeam 9.5.4. Once this is done, we'll use the same old hostname and use the same old IP Address for the HP Server.

thanks

[foggy]

You can upgrade to Veeam B&R v9.0u2 (or any newer version) first, create configuration backup, then perform all the re-imaging and import configuration into Veeam B&R v9.5u4 - this will work fine and you will keep al the jobs and other stuff.