pg_probackup3 currently has the following limitations:
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 14 or higher.
For Postgres Pro and PostgreSQL 14: If a new database is created in the instance between a FULL and DELTA backup, incremental backups will fail until a new FULL backup is taken.
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,
and validate.
The default path for WAL files during backup and restore is set to
PGDATA/pg_wal.
The --dry-run option only works for the
delete command.
Validation is only available for the whole backup.