Upgrading the PostgreSQL Database Engine Software Used by Veeam Backup for Microsoft 365
This article is provided as a courtesy to give customers a high-level explanation of how to upgrade the underlying PostgreSQL database engine used to host the Veeam Backup for Microsoft 365 configuration database.
Per the Veeam Customer Support Policy, section 10: Support for Veeam Configuration Databases:
Veeam Support does not assist with upgrades or patching the SQL Instance or Operating System hosting the Veeam Configuration Database.
"SQL Instance" in this statement broadly refers to both Microsoft SQL Server and PostgreSQL.
Purpose
This article documents the procedure for upgrading the underlying PostgreSQL database engine software that Veeam Backup for Microsoft 365 uses for its configuration database and cache databases.
Unless indicated elsewhere by Veeam or under the advisement of Veeam Support, upgrading the PostgreSQL database engine in use by Veeam Backup for Microsoft 365 should be considered optional. Before upgrading, ensure that the version of PostgreSQL software being upgraded to is supported by Veeam Backup for Microsoft 365.
Solution
Identify the Configuration Database Location
Review the Veeam Backup for Microsoft 365 configuration to identify the current database connection information.
- On the machine where Veeam Backup for Microsoft 365 is installed open the following file in a text editor:
C:\ProgramData\Veeam\Backup365\Config.xml - Look for the node named ControllerPostgres. On that line will be the current database connection information.
- Example 1: Using VB365 Installer-deployed PostgreSQL Instance
<ControllerPostgres ControllerConnectionString="host=vb365srv;port=5432;database=VeeamBackup365;username=postgres;maxpoolsize=100;connectionidlelifetime=10" />
In this example, we can see that the PostgreSQL server is named vb365srv, the configuration database is named VeeamBackup365, and we can tell that SSPI authentication is being used because there is no password= parameter. - Example 2: Using Remote Dedicated PostgreSQL Instance
<ControllerPostgres ControllerConnectionString="host=pgsqlsrv;port=5432;database=VeeamBackup365;username=veeam365svc;password=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAAnyPJ1ttvw06By6Ldd2NKOkEHjdXl7buhzxlW4MjXMBBqLZQGWWjXHgyM%3D;maxpoolsize=100;connectionidlelifetime=10;PasswordEncrypted=True" />
In this example, we can see that the PostgreSQL server is named pgsqlsrv, the configuration database is named VeeamBackup365, the user is named veeam365svc, and native password-based authentication is in use because there is a passsword= parameter configured.
- Example 1: Using VB365 Installer-deployed PostgreSQL Instance
Determine if Upgrade is Available
Before proceeding, it is critical to identify if an upgrade to PostgreSQL is available for your Veeam Backup for Microsoft 365 deployment.
Use the following command to check the current PostgreSQL version:
System Requirements
Ensure that the version being upgraded to is compatible with Veeam Backup for Microsoft 365:
Veeam Backup for Microsoft 365 System Requirements > Configuration and Cache Database
Before You Begin
It is highly advisable to create a Backup of the configuration database so that if anything goes wrong, you can restore or roll back the Veeam Backup for Microsoft 365 configuration.
- Ensure that there are no jobs or restore tasks occurring.
- On the primary Veeam Backup for Microsoft 365 server and all associated Proxies, stop the Veeam Backup for Microsoft 365 services:
- Veeam Backup for Microsoft 365 Server
Veeam Backup for Microsoft 365 Proxy ServiceGet-Service Veeam.Archiver.Proxy | Stop-Service
Veeam Backup for Microsoft 365 ServiceGet-Service Veeam.Archiver.Service | Stop-Service
- Veeam Backup for Microsoft 365 Windows Proxy
Veeam Backup for Microsoft 365 Proxy ServiceGet-Service Veeam.Archiver.Proxy | Stop-Service
- Veeam Backup for Microsoft 365 Linux Proxy
Veeam.Archiver.Proxysystemctl stop Veeam.Archiver.Proxy
- Veeam Backup for Microsoft 365 Server
- Using the database location information from the previous section, create a backup of the database.
PostgreSQL Database Engine Upgrade Procedure
These instructions assume you are upgrading the PostgreSQL install that came prepackaged with Veeam Backup for Microsoft 365. If the deployment of Veeam Backup for Microsoft 365 you are working with is using a different PostgreSQL server, you may need to adapt some of these steps.
- Download the PostgreSQL 15.13 Windows Installer.
- Either run the installer directly or use the unattended option below.
- If running the installer directly:
- It will offer to install pgAdmin and Stack Builder.
- pgAdmin is not required, but may be helpful if future direct interaction with the database is needed. If not selected, it can always be installed separately at a later time.
- Stack Builder is not required and should be unselected.
- The installer will detect the existing installation and the existing data directory. Click Next on each page of the wizard to continue.
- If you have opted to install/upgrade pgAdmin, just before the upgrade begins, a pop-up will appear stating:
Please ensure the pgAdmin server is shutdown before proceeding with the upgrade.
- Open Task Manager and ensure no processes named pgAdmin.exe are running, then click OK to proceed with the upgrade.
- It will offer to install pgAdmin and Stack Builder.
- For unattended mode, run the installer from a command line with the following options:
- If running the installer directly:
- After the upgrade completes, restart the Veeam Backup for Microsoft 365 Server and all proxies.
- Remember to enable the Jobs you stopped in Step 1.
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.