pg_probackup3 supports the remote mode that allows you to perform backup operations remotely via SSH. In this mode, the backup catalog is stored on a local system, while Postgres Pro instance to be backed up is located on a remote system. You must have pg_probackup3 installed on both systems.
Note
pg_probackup3 relies on passwordless SSH connection for communication between the hosts.
Note
In addition to SSH connection, pg_probackup3 uses a regular connection to the database to manage the remote operation. See the section Configuring the Database Cluster for details on how to set up a database connection.
The typical workflow is as follows:
On your backup host, configure pg_probackup3 as explained in the section Backup and Recovery Setup. For the add-instance and set-config commands, make sure to specify remote mode options that point to the database host with the Postgres Pro instance.
If you would like to rely on ARCHIVE WAL delivery mode, configure continuous WAL archiving from the database host to the backup host as explained in the section Setting up continuous WAL archiving. For the archive-push and archive-get commands, you must specify the remote mode options that point to the backup host with the backup catalog.
Run the backup command with remote mode options on the backup host. pg_probackup3 connects to the remote system via SSH and creates a backup locally.
For example, to create an archive full backup of a Postgres Pro cluster located on a remote system with the host address 192.168.0.2 on behalf of the postgres user via the SSH connection through the port 2302, run:
pg_probackup3 backup -Bbackup_dir--instance=instance_name-b FULL --remote-user=postgres --remote-host=192.168.0.2 --remote-port=2302