1.2. New Features of pg_probackup3 #

As compared to pg_probackup, pg_probackup3 comprises the following new features and optimizations:

  • Version independence: The same pg_probackup3 version can now be used with different versions of Postgres Pro or PostgreSQL, ensuring compatibility and flexibility.

  • API integration: pg_probackup3 provides programming interfaces for integration, which enables external backup management systems to utilize pg_probackup3 functionality for creating Postgres Pro backups and ensuring centralized backup management.

  • Work without SSH: pg_probackup3 can work without an SSH connection, simplifying data transfer.

  • FUSE: pg_probackup3 introduces the new fuse command, which enables running a database instance directly from a backup without requiring a full restore, using the FUSE (Filesystem in User Space) mechanism.

  • Operation by unprivileged users: pg_probackup3 can be started by users who do not have access rights to PGDATA. This helps to increase security and reduce the risk of potential errors.

  • New backup format: Each backup is now stored as a single file that contains both data and metadata, reducing disk usage and simplifying backup management.

  • pg_probackup3 supports various methods of accessing the server data via the following modes:

    • BASE: Leverages pg_basebackup replication protocol.

    • PRO: Uses the pg_probackup3's proprietary replication protocol, ensuring secure, high-speed data transfer from the Postgres Pro server.

    • DIRECT: Bypasses replication protocols entirely, accessing data files directly for backup operations.

    For more details on server access modes, see Section 3.1.

  • Merging incremental backup chains: It is now possible to merge chains of incremental backups while keeping full backups intact, thus saving storage space and enabling more flexible backup policies.

  • Completely reengineered core

  • Redesigned architecture

  • Improved performance

FAQ