Upgrade to Veeam Backup & Replication 12.3 Fails During "Step 1 of 7: Installing PostgreSQL server 15.10-1..."
This article documents an issue where the Veeam Backup & Replication 12.3 upgrade fails while attempting to install PostgreSQL 15.10-1.
-
This issue will only occur for Veeam Backup & Replication deployments that are not utilizing a local PostgreSQL instance. For example, deployments of Veeam Backup & Replication that still utilize a local Microsoft SQL Server instance or connect to a remote PostgreSQL or Microsoft SQL Server instance.
-
With the introduction of Microsoft Entra ID backup in Veeam Backup & Replication 12.3, the installer will automatically deploy a local PostgreSQL instance if one does not already exist. This ensures that an initial default Microsoft Entra ID backup repository can be configured.
-
Deployments of Veeam Backup & Replication that are already utilizing a local PostgreSQL instance will not experience this issue, as the installer detects the existing local PostgreSQL instance connection details and configures the Microsoft Entra ID backup repository to use that same PostgreSQL instance.
Challenge
- Reviewing the latest VbrSuite installer log file found in C:\ProgramData\Veeam\Setup\Temp\, the following error is found:
[ERROR] Failed to install PostgreSQL server 15.10-1.
- Checking the System event logs with Event Viewer, the following information message is observed:
Event ID 1000Attempt to execute Windows Script Host while it is disabled.
Cause
In the scenario described, the upgrade fails to install PostgreSQL 15.10-1 because the Windows Script Host has been disabled.
The disabling of the Windows Script Host is recommended as part of the Security & Compliance Analyzer and is disabled when using the script to automate the implementation of Security & Compliance Analyzer Recommendations from KB4525.
However, as documented in the Security & Compliance Analyzer documentation:
Before disabling Windows Script Host, make sure that this service is not used by the backup infrastructure components you plan to install on the backup server. If there are any (for example, PostgreSQL database), install these components first, then disable the service. To update these components, you need to enable the service temporarily.
Solution
If the upgrade fails as described, do not attempt to upgrade Veeam Backup & Replication a second time without first completing the resolution steps in this article.
However, if you have already run the upgrade a second time, please review the More Information section of this article.
Post-Upgrade Failure Remediation
If the Veeam Backup & Replication upgrade has failed while attempting to install PostgreSQL, and you have not attempted to run the upgrade a second time, follow the steps below to complete the upgrade:
- If the Installation Failed screen is still open, click Finish to close it.
- Enable the Windows Script Host by removing the Enabled registry value.
This can be done manually or by using the provided PowerShell command:- Delete the Registry Value named 'Enabled' within the following registry keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script Host\Settings\
HKEY_CURRENT_USER\Software\Microsoft\Windows Script Host\Settings\ - PowerShell script to delete the registry value from the two possible registry keys:
- Delete the Registry Value named 'Enabled' within the following registry keys:
- Uninstall the partial PostgreSQL 15 installation. (appwiz.cpl)
Note: During the uninstall, the error "Error deleting service postgresql-x64-15" will appear multiple times. Click OK on each error and allow the uninstall to complete.
- With Windows Script Host enabled and the partial PostgreSQL 15 install removed, perform the Veeam Backup & Replication 12.3 upgrade again. The upgrade should now successfully deploy PostgreSQL 15.10-1 and complete the upgrade.
Note: After the upgrade completes, you are welcome to disable Windows Script Host once more.
More Information
Note for customers who ran the upgrade a second time, and it succeeded:
- If the Veeam Backup & Replication upgrade was attempted a second time and succeeded, the upgrade to 12.3 can be considered complete. However, because the initial upgrade attempt failed and left behind a partial PostgreSQL deployment, during the second upgrade attempt, the installer will have detected that PostgreSQL deployment and skipped installing PostgreSQL. This failure to install PostgreSQL leads to the issue described in KB4653, wherein the Microsoft Entra ID backup repository is left unconfigured.
- We recommend that you uninstall the partial PostgreSQL 15 deployment.
You can verify it's a partial deployment of PostgreSQL 15 because the service postgresql-x64-15 will not be present. - If you plan to use Microsoft Entra ID backup, you'll need to create a PostgreSQL 15 instance and configure the Microsoft Entra ID backup repository yourself. Keep in mind that you'll need to enable Windows Script Host to install PostgreSQL. Also, you can use the PostgreSQL installer included on the Veeam Backup & Replication ISO (D:\Redistr\x64\PostgreSQL\15.10-1).
After you deploy a PostgreSQL 15 instance to act as the Microsoft Entra ID backup repository, remember to review the Adjusting PostgreSQL Instance Configuration for advice on ensuring the PostgreSQL instance is configured for optimal performance to handle the backup load.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.