PostgreSQL WAL Files Backup

To protect VMs with PostgreSQL instances, you can instruct the backup job to create image-level VM backups and periodically back up write ahead log (WAL) files of PostgreSQL instances. Thus, you will create transactionally consistent backups of PostgreSQL instances that will contain backups of WAL files. If a PostgreSQL instance fails, you can use Veeam Explorer for PostgreSQL to apply WAL files and recover PostgreSQL instances to the necessary state.

Requirements and Limitations

Before you back up WAL files for PostgreSQL instances, consider the following requirements and limitations:

Veeam Backup & Replication supports log backup and restore for PostgreSQL version 12, 13, 14, 15, 16 (PostgreSQL version 12, 13, 14, 15 - for version 12).
Veeam Backup & Replication supports only backup of PostgreSQL instances configured on Linux-based VMs.
Veeam Backup & Replication does not support backup of PostgreSQL clusters.
Veeam Backup & Replication does not support backup of individual PostgreSQL databases.
Veeam Backup & Replication does not support high availability cluster configurations and replication setups of PostgreSQL servers.

Set the archive_mode parameter to the on mode in PostgreSQL instances.
The archive_command parameter must not contain any values in PostgreSQL instances.

Set the wal_level parameter to replica or logical in PostgreSQL instances.
The temporary folder that keeps logs must have enough space and be accessible from Linux guest OS.

To perform guest processing for PostgreSQL instances on Linux servers, make sure that the /tmp directory is mounted with the exec option. Otherwise, you will get an error with the permission denial.