How to Migrate the Configuration and Repository Cache Databases

Export from Source

Using pgAdmin, connect to the PostgreSQL server where the Veeam Backup for Microsoft 365 configuration database is located and export the following (the sections that follow explain in detail how to export these):

• SQL Script files to recreate:
  
  • Group Role: proxy_role_<config_db_name>
    Example Export Filename: proxyrole.sql
  • User: proxy_dbuser_<config_db_name>
    Example Export Filename: proxyuser.sql
• Database Backup Files
  • Configuration Database: VeeamBackup365
    Example Export Filename: VeeamBackup365.backup
  • Cache Database(s): cache_<guid>
    Example Export Filename: cache_<guid>.backup

Note: When connecting to the default included PostgreSQL instance, the default authentication method for the postgres user is SSPI, and you may see the error "SSPI authentication failed for user." If this occurs, review KB4542. If prompted to specify a password after connecting, click OK with the password field empty.

Import to Destination

Notes:

• The destination PostgreSQL instance can be hosted on either Windows or Linux.
• When migrating the Configuration Database to a remote PostgreSQL instance, the authentication method Veeam Backup for Microsoft 365 uses to connect to the PostgreSQL instance must be switched to native password-based authentication.
  
• Due to the variability of possible PostgreSQL configurations, this guide cannot account for all possible custom configurations that may occur when a PostgreSQL instance is already in use by other third-party software. This guide instead aims to document the configuration changes required to modify a default new deployment of PostgreSQL to allow it to host the Veeam Backup for Microsoft 365 Configuration and Cache databases.
• Ensure that the destination PostgreSQL instance is running a version supported by Veeam Backup for Microsoft 365.

Copy Generated Files to Destination

17. Copy the generated .sql and .backup files to the new PostgreSQL server.

Recreate and Restore Cache Databases

If any databases named cache_<guid> were backed up from the original PostgreSQL instance:

30. Create new cache_<guid> database(s) with their original names.
31. Use the .backup file from each cache_ database to restore the cache database(s).

35. Update the role name (vb365svc) and password (pa55word) values in the query and Execute it.
    
    Tip: Remember which role name and password you specified, as you'll need that when reconfiguring Veeam Backup for Microsoft 365.
    
    Note: The password must not contain the following characters:
    • @
    • <
    • >
    • '
    • "

38. Save the pg_hba.conf file.
39. Restart the PostgreSQL service.

Update Connection Settings on Veeam Backup for Microsoft 365 Machine

40. On the machine where Veeam Backup for Microsoft 365 is installed, navigate to:
    C:\ProgramData\Veeam\Backup365\
41. Make a copy of Config.xml and Proxy.xml, just in case changes need to be reverted or a misconfiguration occurs.

Update Config.xml

42. Open Config.xml in a text editor.
    
43. On the line starting with <ControllerPostgres, review and update each parameter as needed:
    1. host=  —  Hostname of the new PostgreSQL machine.
    2. port=  —  Port to connect to the PostgreSQL instance.
    3. database=  —  Configuration Database name. (This should not have changed if you followed the steps in this guide.)
    4. username=  —  Set the username= parameter to use the new user role you created in the previous section.
    5. password= — This value should be configured as follows:
       ^{For more information on updating the password used by Veeam Backup for Microsoft 365 to connect to PostgreSQL, review KB4669.}
       • If the password= parameter is not present:
         1. Add ;password=<password> with the password in plaintext after the username parameter.
            ^{Note: Once the service is started, the plaintext password in the file will be replaced with an encrypted value.}
            Example:

            <ControllerPostgres ControllerConnectionString="host=pgsql;port=5432;database=VeeamBackup365;username=veeam365svc;password=pa55word;maxpoolsize=100;connectionidlelifetime=10" />
            

       • If the ;password= parameter is present:
         1. Replace the encrypted password value with the new password in plaintext.
            ^{Note: Once the service is started, the plaintext password in the file will be replaced with an encrypted value.}
         2. Remove the ;PasswordEncrypted=True parameter from the end of the same line.
44. On the line starting with <RemoteProxyDeploymentSettings, review and update each parameter as needed.
    
    Note: Only the host and port values should need to be checked to make sure they are correct. Neither the username nor password should need to be updated since the proxy user role was exported and imported into the new PostgreSQL instance.
45. Save the updated Config.xml

Update Proxy.xml

46. Open Proxy.xml in a text editor.
    
47. On the line starting with <ProxyPostgres, review and update each parameter as needed.
    
    Note: Only the host and port values should need to be checked to make sure they are correct. Neither the username nor password should need to be updated since the proxy user role was exported and imported into the new PostgreSQL instance.
48. On any line(s) starting with <PersistentCachePostgres, review and update each parameter as needed.
    
    Note: Only the host and port values should need to be checked to make sure they are correct.
49. Save the updated Proxy.xml

Update Proxy.xml

52. Open Proxy.xml in a text editor.
    
53. On the line starting with <ProxyPostgres, review and update each parameter as needed.
    
    Note: Only the host and port values should need to be checked to make sure they are correct. Neither the username nor password should need to be updated since the proxy user role was exported and imported into the new PostgreSQL instance.
54. On any line(s) starting with <PersistentCachePostgres, review and update each parameter as needed.
    
    Note: Only the host and port values should need to be checked to make sure they are correct.
55. Save the updated Proxy.xml