> CommCell Console > Backup and Restore Agents > Snapshot Management > Supported Agents > PostgreSQL

Troubleshooting

Troubleshooting - PGSQL0001: An IntelliSnap Backup Copy Fails When You Have ext3, or ext4, or XFS LVM Volume for the Hardware Array

An IntelliSnap backup copy fails on the following agents when you have ext3, or ext4, or XFS LVM volume for the hardware engine:

  • MySQL

  • PostgreSQL

  • SAP HANA

  • SAP on Oracle

Resolution

If you use a Linux proxy for the backup copy, disable automatic activation of volumes. Automatic activation of volumes interferes with HotAdd operations during backup and recovery. For more information, see Best Practices - IntelliSnap for UNIX File System.

PGSQL0002: "Failed to start server": A full instance restore operation for FSBasedBackupSet completes with errors

Symptom

Data and archived logs are restored successfully, but the PostgreSQL server fails to start automatically.

Failed to start server

You can see the following error in the PostGresRestoreLog.log file:

cat wal_dir_path/postgresLogport
postgres cannot access the server configuration file "postgresql.conf path": No such file or directory

Cause 1

This error might occur during a backup operation, because configuration files were outside the data directory in a different mount point.

During a restore operation, the configuration files are restored inside the data directory.

Resolution 1

Copy the PostgreSQL configuration files from data directory to the actual path that is mentioned in postgresql.conf file. Start the PostgreSQL server manually.

If you are using PostgreSQL 12, follow the steps mentioned in Consideration for Restoring FSBased Backup Set on PostgreSQL 12.

Cause 2

This error might occur if there is a broken symlink to:

  • the pg_xlog directory for PostgreSQL version 9.x.

  • the pg_wal directory for PostgreSQL version 10.x.

These directories are located outside the data directory during a backup operation.

Resolution 2

List the files and folders in the data directory, and then find the symlink to the pg_xlog or pg_wal directory. Create a pg_xlog or pg_wal folder in the symlink path, and start the PostgreSQL server manually.

If you are using PostgreSQL 12, follow the steps mentioned in Consideration for Restoring FSBased Backup Set on PostgreSQL 12.

×

Loading...