PostgreSQL in 13.1

[cmaier]

Hello,

Were there any changes regarding PostgreSQL in version 13.1? Since this version, I’m getting warnings that the account I’m using cannot log in (which is actually the case). These warnings weren’t present in version 13.0.

Is there any way to exclude PostgreSQL from application-aware processing while keeping Microsoft and Oracle SQL enabled?

Thanks

[Mildur]

Hi Christian

We have now Application aware processing for Postgresql on windows since v13.1.
I assume thats the warning you have seen in the backup jobs. Please contact customer support if my assumption is wrong.

Disabling only PostgreSQL processing is not possible. Any reason why you don‘t want to have a application aware backup for PostgreSQL?

Best,
Fabian

[cmaier]

Hi Fabian,

No, right now I just want to get rid of the warning message.

So far, no one has ever requested a PostgreSQL restore, and there are also a few instances where I simply don't have the login credentials.

[Mildur]

Hi Christian,

Thank you for your answer.

One of our partners opened a support case today, from which I learned about an option to exclude specific PostgreSQL server from application aware processing. By setting this exclusion parameter, PostgreSQL configuration in this folder path will not be scanned, therefore we won't try to apply Application Aware Processing to this PostgreSQL instance.

Keep in mind that, by setting this exclusion, you will not be able to use our PostgreSQL Restore Explorer for excluded PostgreSQL instances. Database files are still protected with VSS, same as before with v13.0 or older versions.

I tested an instant recovery restore of a VM with an "excluded" PostgreSQL server, and the database was still working for my application.
______________________________________________

1.) Connect to the affected Windows guest VM.
2.) Go to, or create, the following folder: C:\ProgramData\Veeam\Backup\PostgreSqlConfig
3.) Create or edit <VeeamPostgreSQLAgent.xml> file with this line:

Code: Select all

<config ExcludeConfigDirs="C:\Program Files\PostgreSQL\" />

4.) Start a new backup session with AAIP enabled

Please note: The path used for ExcludeConfigDirs must be your PostgreSQL installation path.

______________________________________________




Best,
Fabian

[cmaier]

Hi Fabian,

Sounds good, but I don't get it to work.

Here is the process:



I've tried the following, without success:

Code: Select all

<config ExcludeConfigDirs="C:\Program Files\HP\RS\pgsql\" />

Code: Select all

<config ExcludeConfigDirs="C:\Program Files\HP\RS\pgsql\bin\" />

Code: Select all

<config ExcludeConfigDirs="C:/Program Files/HP/RS/pgsql/" />

Code: Select all

<config ExcludeConfigDirs="C:/Program Files/HP/RS/pgsql/bin/" />

Code: Select all

<config ExcludeConfigDirs="C:/ProgramData/HP/RS/DATA/database" />

Code: Select all

<config ExcludeConfigDirs="C:\ProgramData\HP\RS\DATA\DATABASE" />

Warning : Failed to explore PostgreSQL instance ********:7950 : PostgreSQL server on port 7950 has returned an error "connection to server at "localhost" (::1), port 7950 failed: FATAL: password authentication failed for user "************"". Failed to invoke rpc command

[Mildur]

Please open a case with our support team. Don‘t forget to provide me the case number.

Best,
Fabian

[cmaier]

Yeah, that would be the third case for version 13.1. I'm slowly running out of time for this. 13.1 is starting to get on my nerves.

I'm thinking about how to proceed with this. Another case is much more important right now.

[cmaier]

Ok, it's case #08189454

[DaStivi]

Why not use Application-Aware Processing for PostgreSQL?

There is one downside: it requires additional configuration and can be somewhat cumbersome due to PostgreSQL's user mapping and authentication model.

When using a gMSA for Application-Aware Processing, you cannot use an integrated SSPI connection to PostgreSQL. In that case, I would recommend using:

A gMSA for the Windows Application-Aware Processing connection
A dedicated PostgreSQL account for the PostgreSQL connection (using the username/password authentication method)

I would generally avoid using a regular Windows account for Application-Aware Processing unless there is a specific reason to do so.

For non-domain-joined VMs, a dedicated Windows account is required for Application-Aware Processing anyway. In this scenario, you can use SSPI for the PostgreSQL login with that account. You still need to select username/password authentication in the PostgreSQL settings, but you can simply create a PostgreSQL user (for example, postgres) without a password and map the Windows account to that PostgreSQL user.

[cmaier]

As I already said: I don't have login credentials for all PostgreSQL databases. A specific example is HPE Insight Remote Support. They install PostgreSQL, and I can't find a working password anywhere.

[cmaier]

Okay, I mounted the database in “trust” mode and created a new account for Veeam. That was way too easy.