Migrating Configuration Database to PostgreSQL Server

If you need to migrate the Veeam Backup & Replication configuration database from Microsoft SQL Server to PostgreSQL, you need to create a new configuration backup and restore it on the PostgreSQL instance. As a result, you will be able to continue using the same Veeam Backup & Replication server but it will be connected to a configuration database on PostgreSQL instead of Microsoft SQL Server.

Limitations and Considerations

Before you migrate the configuration database of Veeam Backup & Replication to PostgreSQL, consider the following limitations and considerations:

This section gives instructions on how to migrate a configuration database to PostgreSQL. If you need to migrate the Veeam Backup & Replication application itself, see Migrating Veeam Backup & Replication to Another Backup Server.
If you want to migrate configuration database from PostgreSQL to another SQL server, see Migrating Configuration Database to Another SQL Server.
It is recommended that you use Veeam Backup & Replication tools to create configuration backups and migrate the configuration database.
If a backup server and a configuration database are located in different AD domains, the AD domain where the configuration database is located must have a trust relationship with the AD domain to which the backup server is added.
You can migrate the configuration database created only in Veeam Backup & Replication 12.
PostgreSQL standard system database named template1 must have UTF-8 encoding.

Migrating Configuration Database

If you want to migrate the configuration database of Veeam Backup & Replication to another PostgreSQL, perform the following steps:

Stop and disable jobs.
Back up the configuration database.
Restore the configuration database from the backup.
[Optional] Reactivate the Enterprise Manager Keyset.
Finish the configuration.

Step 1. Stop and Disable Jobs

Before you start the database migration, you must finish all jobs and restore sessions. If the job is scheduled, you must disable the job. For instructions on how to stop and disable jobs, see Managing Jobs.

Note

Do not start or enable any jobs until the migration of Veeam Backup & Replication is finished. If you start a job before migration is completed, Veeam Backup & Replication will produce a new restore point in the chain and update the chain metadata. The created configuration backup will not contain information about this new restore point. When you migrate data from the configuration backup to the database and start the job again, Veeam Backup & Replication will fail to synchronize the metadata of the backup chain with data in the database. As a result, the job will fail.

Step 2. Create Configuration Database Backup

To create a configuration database backup manually, perform the following steps:

From the main menu of the Veeam Backup & Replication console, select Configuration Backup.
Make sure that the Enable configuration backup to the following repository check box is selected.
From the list of repositories, select a backup repository in which the configuration backup must be stored.
Click Backup now.

Note

Loss protection disabled warning is safe to ignore if you do not have Veeam Backup Enterprise Manager installed, your backup server is not registered with Veeam Backup Enterprise Manager server, or your system administrator chose not to enable loss protection functionality.

Step 3. Restore Configuration Database from Backup

To restore the configuration database, perform the following:

From the main menu of the Veeam Backup & Replication console, select Configuration Backup.
In the Restore section, click Restore.

At the Restore Mode step of the Veeam Backup & Replication Configuration Restore wizard, select Migrate.

Complete the wizard as described in section Restoring Configuration Database. On the Target Database tab of the configuration restore wizard, select PostgreSQL as the database engine.

Important

After the restore process, make sure that PostgreSQL target instance is configured according to the recommended hardware resources values. You can modify settings of PostgreSQL target instance using the Set-VBRPSQLDatabaseServerLimits cmdlet. For more information, see Veeam PowerShell Reference.

Note

After you complete the restore process, Veeam Backup & Replication will connect to the database you specified as a target.

Step 4. [Optional] Reactivate Enterprise Manager Keyset

After you migrate the Veeam Backup & Replication configuration database to another server, Veeam Backup Enterprise Manager still sees the Veeam Backup & Replication server. However, you may need to reactivate encryption keys.

If you use the Data Encryption feature to encrypt backups and your Veeam Backup & Replication server is added to the Veeam Backup Enterprise Manager infrastructure, then you must reactivate the Enterprise Manager keyset.

To reactivate the Enterprise Manager key, perform the following steps:

In the Veeam Backup Enterprise Manager web console, open the Settings section of the Configuration view.
Open the Key Management tab.
In the Managed keys section, select the necessary keyset and click Activate.

For detailed instructions, see the Activating Enterprise Manager Keyset section in the Veeam Backup Enterprise Manager Guide.

Step 5. Finish Configuration

After restoring the configuration database from the backup, finalize the configuration:

Configure all necessary settings to ensure that you have a working configuration database backup. You can now perform a backup of your new configuration database in the Configuration Backup Settings window.

Reschedule your configuration database backup. Also, check if you can see the Loss protection enabled label.

If you have local repositories, after migration to another VM they may be displayed as empty. In this case, add them again and remap the jobs.

Enable your backup jobs and backup copy jobs. Take a closer look at your backup infrastructure to ensure that everything is working as expected.