Failed to create a restore point: PostgreSQL database operation failed multiple times with transient error.

KB ID: 4794
Product: Veeam Backup for Microsoft 365 | 8.2 | 8.3
Published: 2026-01-15
Last Modified: 2026-01-15
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

After upgrading to Veeam Backup for Microsoft 365 8.2 or 8.3, jobs fail with the erorr:

Failed to create a restore point: PostgreSQL database operation failed multiple times with transient error.

Cause

This issue occurs because various one-time PostgreSQL queries that the software attempted to run after upgrading to 8.2 or 8.3 failed to execute within the default 60-second PostgreSQL command timeout.

Solution

This solution requires that the Veeam Backup for Microsoft 365 deployment be running at least 8.3.0.2201.

To resolve this issue, temporarily increase the timeout to allow the queries to run, then revert the timeout change.

  1. Ensure at least Veeam Backup for Microsoft 365 8.3.0.2201 is installed.
  2. On the machine where Veeam Backup for Microsoft 365 is installed, stop the following services:
    • Veeam Backup for Microsoft 365 Service
    • Veeam Backup for Microsoft 365 Proxy Service
  3. On that machine, open the following configuration file:
    C:\ProgramData\Veeam\Backup365\Config.xml
  4. Within the Config.xml file, under the "Veeam/Archiver/RemoteProxyDeploymentSettings" node, identify the following settings and note their existing values. Each setting and value will be listed twice in that line. Once noted, so you can revert the value later, update the values as shown below:
    • command timeout=600
    • timeout=600
  5. Start the Veeam Backup for Microsoft 365 Service service.
  6. Open the Veeam Backup for Microsoft 365 Console, and use the Upgrade function on each proxy used by the job that was failing to push the updated timeout values.
  7. Run the job that failed, and once it succeeds, revert the timeout changes:
    1. Ensure all jobs are stopped.
    2. Stop the Veeam Backup for Microsoft 365 Service and Veeam Backup for Microsoft 365 Proxy Service services.
    3. Modify the Config.xml file and replace the updated timeout values with the original ones (default is 60).
    4. Start the Veeam Backup for Microsoft 365 Service service.
    5. Upgrade the Proxies again to push out the updated timeout values.

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!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.