Skip to main content
  • EN

As part of the Veeam Backup & Replication server v12.3.0.310 upgrade, the built-in PostgreSQL is installed like below:

The installation successful without any error.

However, there was no prompt or notification of what is the credential that can be used for accessing this default instance of PostgreSQL:

Via the command line: 

"C:\Program Files\PostgreSQL\15\scripts\runpsql.bat"

 

Or using the DB Configuration settings UI:

 

I have also tried to manually install PGAdmin interface, but not sure what is the default credential I can use to login to this default instance installed by Veeam Backup:

 

Any help would be greatly appreciated.

Hi ​@vAdmin while installing VBR software Postgre sql Database was installed as a built-in but why do we need to reset the password did you try to reset the password? Postgre SQL Database is installed as a built-in but why do we need to reset the password did you try to reset the password.

Hi ​@waqasali the password is required for the Entra ID backup since it uses the PostgreSQL as the repository.

You will get this error:

 

Job has been stopped with failures. Error: Failed to add Microsoft Entra ID backup repository: No password has been provided but the backend requires one (in MD5)

 

Hi ​@waqasali the password is required for the Entra ID backup since it uses the PostgreSQL as the repository.

You will get this error:

 

Job has been stopped with failures. Error: Failed to add Microsoft Entra ID backup repository: No password has been provided but the backend requires one (in MD5)

 

 

Hi ​@vAdmin so what is the best practice?  

Hi ​@vAdmin, you could try to add a specific account like mentioned in KB4542: "SSPI authentication failed for user". Maybe this would help you in this case.
 

Hi ​@vAdmin, you could try to add a specific account like mentioned in KB4542: "SSPI authentication failed for user". Maybe this would help you in this case.
 

let me check this ​@Dynamic 

Hi ​@vAdmin, you could try to add a specific account like mentioned in KB4542: "SSPI authentication failed for user". Maybe this would help you in this case.
 

This works for the config file mentioned.  Done it lots of times without issue.  Easiest way to get around the password issue.

Hi ​@vAdmin, perhaps you should take a look at this link for some vital information: https://www.atlassian.com/data/admin/how-to-set-the-default-user-password-in-postgresql 

FYI, the built-in Postgre SQL v15 that comes with Veeam Backup & Replication 12.3.0.310 only have this directory: 

C:\Program Files\PostgreSQL\15

Hence the steps described in KB4542: "SSPI authentication failed for user" may not work.

 

This is the evident from the C:\Program Files\PostgreSQL\15\installation_summary.log file.


Installation Directory: C:\Program Files\PostgreSQL\15

Server Installation Directory: C:\Program Files\PostgreSQL\15

Data Directory: C:\Program Files\PostgreSQL\15\data

Database Port: 5433

Database Superuser: postgres

Operating System Account: NT AUTHORITY\NetworkService

Database Service: postgresql-x64-15

Command Line Tools Installation Directory: C:\Program Files\PostgreSQL\15

Installation Log: ***unknown variable installationlogfile***

===== Installation completed at: 2024-12-05(YYYY-MM-DD) - 16:52:55(HH:MM:SS) =====

                            

​@Iams3le , ​@Chris.Childerhose & ​@Dynamic ,

I will use and download a separate Postgre SQL v15 from PostgreSQL: Windows installers page and let you know the progress.

FYI: The upgrade process has failed:

 

I would contact support in this case.

OK, it turns out to be there is already an existing Postgre SQL running in the Backup server as the default instance.

OK, it turns out to be there is already an existing Postgre SQL running in the Backup server as the default instance.

That would be why then. 😉

​@Chris.Childerhose , ​@Iams3le , ​@Dynamic and ​@waqasali ,

Turns out the issue is caused by the hardening process that was done years before using this https://www.veeam.com/kb4525

 

The solution is by following this official KB article: https://www.veeam.com/kb4698 fixed this issue.

 

Since the PostgreSQL is a 3rd party product, hence the installation or upgrade script, should incorporate:

  1. Enable WSH lWindows Script Host]
  2. Install or Upgrade the PostgreSQL
  3. Disable WSH Windows Script Host]  

 

Hope this helps everyone.

Glad you figured it out.

​@Chris.Childerhose , ​@Iams3le , ​@Dynamic and ​@waqasali ,

Turns out the issue is caused by the hardening process that was done years before using this https://www.veeam.com/kb4525

 

The solution is by following this official KB article: https://www.veeam.com/kb4698 fixed this issue.

 

Since the PostgreSQL is a 3rd party product, hence the installation or upgrade script, should incorporate:

  1. Enable WSH lWindows Script Host]
  2. Install or Upgrade the PostgreSQL
  3. Disable WSH Windows Script Host]  

 

Hope this helps everyone.


Since your initial question was on a specific use-case, it would have been difficult to figure out here. I am glad you could figure this out by digging deep into the log and for sharing the resolution with the community.

Comment


Terms & Conditions