Application aware PostgreSQL issue

[evandrosp]

Hi There,

Support - Case # 07630883

I am having some trouble backing up a PostgreSQL instance on a Linux VM. Our instances are located in different locations by default, so we use the "/etc/veeam/VeeamPostgreSQLAgent.xml" file to specify the location of our instances.

The backups run fine for almost all instances, but one specific instance fails. The database that fails is 8TB in size. If I remove this 8TB database from the "VeeamPostgreSQLAgent.xml" file, all backups run fine. However, when I include this database in the "VeeamPostgreSQLAgent.xml" file, all PostgreSQL backups fail. We have already validated access to the server, database, and user permissions, and everything is OK.

The VM backup runs fine; only the PostgreSQL backup fails.

Are there any limitations regarding the size of databases and instances for PostgreSQL?
Are there any logs where I can verify the error in more detail?
The error is as follows:

--- deleted by moderator ---

Maybe it's this line, but I'm not exactly sure what it is:

--- deleted by moderator ---


Thanks

[PetrM]

Hi Evandro,

As far as I can see, our engineer is already working on the issue. Let's wait to see what our support team can find out. I doubt that we can effectively troubleshoot the issue through forum posts. Also, let's avoid posting the debug log snippets, you may refer to this post for more information about forum rules.

Thanks!

[evandrosp]

Hi PetrM.

The backups are OK, and we found the problem.
We use custom names for the PostgreSQL configuration files, and the database was not using some parameters.

For instance, Veeam reads the default files:
postgresql.conf
pg_hba.conf

However, we use custom names for our configuration files. We applied the same parameters to both postgresql.conf and our custom file postgresql.custon.conf, then restarted the database to apply the configurations. Now, the backups run smoothly.

Thanks