How to Migrate Veeam Backup Enterprise Manager's Database from Microsoft SQL to PostgreSQL

^{Note: The account used to execute the Veeam.EM.DB.Migration.exe command must have the appropriate SQL-level permissions (db_owner or db_datareader + db_datawriter) to access and interact with the Enterprise Manager database.}

In the command above, replace the following placeholders with valid data.

• <path>
  
• <password>
• <password_hint>

Example:

Veeam.EM.DB.Migration.exe /file:"C:\tmp\BEMConf.emco" /backupemdatabase /encryptionpassword:1l0v3KB5 /encryptionhint:bestpassever

Part 3: Update Credentials for Veeam Backup & Replication Server(s)

• After migrating Enterprise Manager's Configuration Database, the credentials for each Veeam Backup & Replication Server added to Enterprise Manager must be updated to re-establish communication.
  1. Within the Enterprise Manager's Configuration section, select the Backup Servers section.
  2. For each Veeam Backup & Replication server listed:
     1. Select the entry.
     2. Click Edit...
     3. Enter Username and Password.
     4. Click OK.
  3. Once credentials for each Veeam Backup & Replication server have been updated, switch to the Sessions section.
  4. In the Sessions section, click Start Collecting and confirm that all new Database Replication tasks are completed Successfully.

• [Note: Starting in Veeam Backup & Replication 13, this limitation was removed, allowing Veeam Backup Enterprise Manager and the Veeam Backup & Replication deployments it manages to operate different database engines.]
  For all builds of Veeam Backup & Replication 12.x only, the Database Replication task will fail for any Veeam Backup & Replication Server whose Configuration Database is still using Microsoft SQL, for more information on migrating the Veeam Backup & Replication Configuration Database to PostgreSQL, refer to Migrating Configuration Database to PostgreSQL Server in the Veeam Backup & Replication User Guide.