Option 2: Self-Service Resolution
Customers with an understanding of how to execute a SQL query and are comfortable with making modifications to their Veeam Backup & Replication Configuration Database directly are welcome to follow these steps to resolve the issue:
- Back up the Veeam Backup & Replication Configuration Database.
- Locate the Veeam Backup & Replication Configuration Database and execute the following query to update all conflicting OS version entries.
- For Microsoft SQL:
update dbo.[Backup.Model.EpHosts] set os_version='0.0' where os_version=''
- For PostgreSQL:
UPDATE "backup.model.ephosts" SET os_version='0.0' WHERE os_version='';
Note: Starting with Veeam Backup & Replication 12, the configuration database can be hosted using either MS SQL or PostgreSQL. As this issue only affects environments where Veeam Backup & Replication was upgraded, and an upgrade will always reuse the existing database engine, most customers facing this issue will still be using Microsoft SQL. If, however, after upgrading to Veeam Backup & Replication 12, the configuration database was migrated to PostgreSQL, use the appropriately formatted query for PostgreSQL.