Skip to main content
Solved

Is rollback to MS SQL supported after in-place migration of VBR v12 database to PostgreSQL?

  • Nov 11, 2026 4:41 AM UTC
  • 1 comment
  • 13 views

Hello,

We currently have Veeam Backup & Replication v12 installed on Windows Server, using Microsoft SQL Server for the VBR configuration database.

We are planning an in-place migration of the configuration database from Microsoft SQL Server to PostgreSQL on the same VBR server.

We do not plan to build a new Windows Server or a separate VBR server for the migration.

Before proceeding, we need to establish a supported rollback procedure.

If the PostgreSQL migration completes successfully but we later find an issue during validation, is it officially supported to revert the existing VBR server to the original Microsoft SQL configuration database?

Specifically, we would like to confirm:

  • Whether reconnecting VBR to the preserved pre-migration Microsoft SQL database is supported.
  • Whether a VBR configuration backup/restore is required or recommended for rollback.
  • Whether the original Microsoft SQL database can be used directly as long as it has remained unchanged since the migration.
  • Whether there are any database schema, VBR build/version, or configuration compatibility considerations when rolling back.
  • Whether there is an officially documented rollback procedure for this scenario.

Our goal is to define a safe and supported rollback plan before performing the MS SQL to PostgreSQL migration.

Thank you for your assistance.

Best answer by tm67

Hi, the “official” rollback would be to manually connect to the old database again. You can use the database connection utility for this: Using Veeam Configuration Database Connection Utility in Veeam Backup & Replication for Windows - Veeam Backup & Replication User Guide

another option would be a config backup restore: Restoring Configuration Database on Windows-Based Backup Server - Veeam Backup & Replication User Guide

So, if you have a config backup, you have a rollback scenario. The MSSQL database should be untouched in a migration scenario so you have this as well to reconnect. Just to be sure, you could do a quick manual backup of the MSSQL just to be on the safe side. 

If you need to do a rollback it would be wise to stay on the same VBR version

Hope this helps!

Timo 

View original

    1 comment

    tm67
    Forum|alt.badge.img+4
    • tm67
    • Veeam Legend
    • Answer
    • Nov 11, 2026 5:06 AM UTC

    Hi, the “official” rollback would be to manually connect to the old database again. You can use the database connection utility for this: Using Veeam Configuration Database Connection Utility in Veeam Backup & Replication for Windows - Veeam Backup & Replication User Guide

    another option would be a config backup restore: Restoring Configuration Database on Windows-Based Backup Server - Veeam Backup & Replication User Guide

    So, if you have a config backup, you have a rollback scenario. The MSSQL database should be untouched in a migration scenario so you have this as well to reconnect. Just to be sure, you could do a quick manual backup of the MSSQL just to be on the safe side. 

    If you need to do a rollback it would be wise to stay on the same VBR version

    Hope this helps!

    Timo 

      Terms & ConditionsAccessibility statement