When installing Veeam Backup & Replication, selecting an existing configuration database fails due to the following error message:
Unable to use database VeeamBackup, because it was created with a later version of Veeam Backup and Replication.
The Configuration Database Connection Settings utility is unable to select a database due to the following error message:
Unable to use database VeeamBackup, because it was not created with current version of Veeam Backup and Replication.
In older versions of the software, or if the configuration database location is changed via the registry, no error message appears, but the Veeam Backup Service fails to start.
When Veeam Backup & Replication is updated, the configuration database is upgraded and its version number is changed. The updated database is not compatible with the Generally Available version of the software.
For example, Veeam Backup & Replication v9 GA (188.8.131.522) is upgraded to v9 Update 1 (184.108.40.2061), and then uninstalled. In this scenario, attempting to reinstall from the v9 ISO using the existing configuration database will fail. This is because the database version is greater than the latest version supported by the software.
If Veeam Backup & Replication is already installed, apply the latest update.
If it is not installed:
- Choose a new database name during installation. An empty database will be created with this name.
- Once installation has completed, apply the latest update.
- Switch from the empty database to the original configuration database using the Configuration Database Connection Settings utility.
To delete the empty database after installation, use SQL Server Management Studio.
- In Object Explorer, connect to the instance containing the empty database (such as localhost\VEEAMSQL2012).
- Expand Databases, right-click the empty database, and then click Delete.
- Confirm the correct database is selected, and then click OK.
The version number of the configuration database can be reverted with the following query:
UPDATE [Version] SET current_version = <see table below>
Once the version number is reverted, it is possible to install using the existing database. However, the software cannot be used in this configuration: it must immediately be updated to the same or later version that was previously installed. Otherwise, data corruption or unexpected behavior may occur.
Certain updates alter the database schema in a way that requires an additional change to the Version table before the update can be installed:
|v7 Patch 4 (220.127.116.111)||1200|
|v8 Update 3 (18.104.22.1684)||2022|
|v9.5 update 3 (22.214.171.1246)||4051|
|v9.5 update 3a (126.96.36.1992)||4087|
Do not attempt to revert to a previous release of the software (such as to v8 from v9).
If there may be other problems with the configuration database, try restoring from configuration backup. It is recommended to create a configuration backup prior to updating the software.
ISOs containing updated versions of the software (maintenance releases) are not available. For more information on this topic, consult the Community Forum.
Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.