Let’s take the backup using the pgbackrest command: For the sake of simplicity, we are considering backup for one DB Server only. is the name of the stanza for which backup is taken. Here, the backup will be stored on the local backup host at the /var/lib/pgbackrest_repo1 path that is already created with the proper user (in this case, Postgres) and permissions. Even though there is a single repository, the parameter’s name starts from “repo1” to accommodate as many repositories as possible. This configuration file contains details about the global section having common parameters like repo details, log details, etc. Scenario – 1: Behavior of pgBackRest with single repoīy default, pgBackRest takes backups in a single repository or location, which can reside locally on the same server, remote server, or cloud.īelow is the configuration file, which is normally configured for taking backups with single repo: Backup Host: >pgBackRest is installed and configured on a dedicated backup and database host.
>PostgreSQL installed and configured on the database host. Take backup locally and in multiple clouds Taking backup locally and remotely on the cloudĢ.4. Taking backup locally with multiple reposĢ.3. Configuring archives redundantly (async=y)Ģ.2. Behavior of pgBackRest with multiple reposĢ.1. Behavior of pgBackRest with single repoĢ. Let’s discuss a few scenarios one by one.ġ. This attribute helps take the redundant copies of the databases at multiple locations remotely on different servers or locally on the same server. In this blog, we will specifically discuss one of the important features of the pgBackRest called Multiple Repository (or, in short, Multi Repo). Repository means the location/path on the server or the cloud where the actual copy of the backup will reside. To briefly explain pgBackRest, it is an open source backup tool that takes FULL Backup, Incremental Backup, and Differential Backup for PostgreSQL databases. Our previous blogs discussed configuring and setting up backups using the pgBackRest solution.
0 kommentar(er)
