Postgresql Backups fail with "Database found, but failed to backup Database '[database name]'" (4047046)

A PostgreSQL backup can fail with the following errors:

Launching backup command : '[pg_dump command]'
Database found, but failed to backup Database '[database name]' .
No data/items are saved in the media.

There are 3 common scenarios where this problem can occur.

1. The password configuration for the PostgreSQL plugin is incorrect.
2. Tar Archive format backup is not possible on the particular database
3. On Windows, database or table names use incompatible character encoding

For the above causes:

1. Ensure that the password provided in the Add Database Cluster/Configure Database Cluster window of the APM is correct. If the cluster is configured to use TRUST authentication for HOST connection while PASSWORD authentication for LOCAL connection, the backups will fail if the password is incorrect (blank).
   Note that you will be able to browse the tree and submit a job with a blank or incorrect password. However, the actual job will fail.
   The following is recommended in this scenario:
   - In the Configure Database Cluster window provide correct password, and run the job again.
   - To avoid this problem either use TRUST authentication for both HOST and LOCAL connection (in which case no password will be required) or use PASSWORD authentication for both in the pg_hba.conf (and provide the correct password in the Configure Database Cluster window).
    
2. Run and check the pg_dump command logged in the NetVault Backup log error with the TAR Archive format from the command prompt/terminal session. If the following error message appears:
   “pg_dump: [tar archiver] actual file length <xxxx> does not match expected <xxxx>”
   then you cannot use the TAR Archive backup format on the current installation. Use the Custom Archive format instead.
    
3. Run and check the pg_dump command logged in the NetVault Backup log error from the command prompt. If the following error message appears:
   “pg_dump: Cannot access “??-UTF8-C” [database to be dumped]: FATAL: database “??- UTF8-C” does not exist pg_dump: *** Stopped by error”
   then the problem lies in the character set encoding configured for the database cluster.
   The backups of databases or tables named with non-ASCII characters is not supported if the encoding is set to UTF-8 at initdb.
   Appropriate encoding must be set for the database cluster (e.g. EUC_JP for Japanese or EUC_KR for Korean) to successfully backup the databases/tables.

If the above 3 scenarios do not help to resolve the problem, then please contact PostgreSQL support with the errors reported by the pg_dump command from the prompt/terminal session.