Any FULL or DELTA backup taken with pg_probackup3 must use one of these WAL delivery modes: ARCHIVE or STREAM.

The remote mode is not supported on Windows systems.

The Postgres Pro server from which the backup was taken and the restored server must be compatible by the block_size and wal_block_size parameters and have the same major release number. Depending on cluster configuration, Postgres Pro itself may apply additional restrictions, such as CPU architecture or libc/icu versions.

pg_probackup3 only supports Postgres Pro and PostgreSQL 15 or higher.

Creating backups using different backup data source modes (--backup-source) within one backup chain is disabled.

The ability to run pg_probackup3 on parallel threads (using the -j option) is currently implemented only for the following commands: backup, restore, merge, catchup, and validate.

The recovery target options are not yet fully implemented. Point-in-time recovery functionality is under development.

Cross-version recovery is not supported — a backup cannot be restored to a Postgres Pro version different from the one on which it was created. Backups are not suitable for upgrading Postgres Pro versions.

The default path for WAL files during backup and restore is set to PGDATA/pg_wal.

WAL validation works only for Postgres Pro Standard and Postgres Pro Enterprise from version 15 to 18. For other versions/editions, TDE, and the s390 architecture, validation is skipped.

Validation is only available for the whole backup.

The --dry-run option only works for the delete command.

Incremental backups are not supported during TDE status transitions (enabling or disabling). Following any TDE status change, a full backup must be performed.

merge operations are prohibited if incremental backup chains contain a backup capturing a TDE status change. In such cases, a complete cluster-level full backup is required.

Clusters with TDE enabled do not support catchup or fuse operations.