pgbackrest | Reliable PostgreSQL Backup & Restore | Continuous Backup library

by pgbackrest C Version: release/2.46 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(5)Vulnerabilities Install Support

kandi X-RAY | pgbackrest Summary

pgbackrest is a C library typically used in Backup Recovery, Continuous Backup, Amazon S3 applications. pgbackrest has no bugs, it has no vulnerabilities and it has medium support. However pgbackrest has a Non-SPDX License. You can download it from GitHub, GitLab.

pgBackRest aims to be a reliable, easy-to-use backup and restore solution that can seamlessly scale up to the largest databases and workloads by utilizing algorithms that are optimized for database-specific requirements. pgBackRest v2.37 is the current stable release. Release notes are on the Releases page.

Support

Quality

Security

License

Reuse

Support

pgbackrest has a medium active ecosystem.

It has 1714 star(s) with 172 fork(s). There are 63 watchers for this library.

There were 1 major release(s) in the last 12 months.

There are 49 open issues and 1479 have been closed. On average issues are closed in 14 days. There are 11 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of pgbackrest is release/2.46

Quality

pgbackrest has no bugs reported.

Security

pgbackrest has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

pgbackrest has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

pgbackrest releases are available to install and integrate.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of pgbackrest

Get all kandi verified functions for this library.

pgbackrest Key Features

No Key Features are available at this moment for pgbackrest.

pgbackrest Examples and Code Snippets

No Code Snippets are available at this moment for pgbackrest.

Community Discussions

Trending Discussions on pgbackrest

Boot backup image of server when postgres replication configured

PostgreSQL: even read access changes data files disk leading to large incremental backups using pgbackrest

How to exclude a particular table in postgres backup using pgbackrest?

Solve a permission problem found when running pgbackrest as a cron job

Configuring Different repo path for pgbackrest wal archive

QUESTION

Boot backup image of server when postgres replication configured

Asked 2021-Mar-04 at 09:21

I am running a server in Linode.

I am backing up to a s3 type server using pgbackrest. Streaming backup.

Linode takes a complete image of my server.

I am spinning up a server using a backup image to test a linux upgrade.

My concern is that Postgres is configured to start on boot-up. I fear that it will connect to the pgbackrest store with the same configuration as the primary server, with possibly bad results.

Has anyone got any advice before I boot the server?

Thanks

...

ANSWER

Answered 2021-Mar-04 at 09:21

It turned out straight forward.

Linode created the copy of the server but did not start it.

I was able to start the new server in "rescue" mode. I connected via the web interface (LISH).

I mounted the hard drive, /dev/sdb, I think.

I edit /etc/pgbackrest/pgbackrest.conf and commented out the information.

I edited /var/spool/cron/crontabs/* and commented out everything.

I then booted the server.

I modified /etc/hosts on my local PC to direct to the backup server, and verified it.

I was able to test my Linux upgrade before touching my production server.

Source https://stackoverflow.com/questions/66390832

QUESTION

PostgreSQL: even read access changes data files disk leading to large incremental backups using pgbackrest

Asked 2021-Feb-16 at 16:34

We are using pgbackrest to backup our database to Amazon S3. We do full backups once a week and an incremental backup every other day. Size of our database is around 1TB, a full backup is around 600GB and an incremental backup is also around 400GB!

We found out that even read access (pure select statements) on the database has the effect that the underlying data files (in /usr/local/pgsql/data/base/xxxxxx) change. This results in large incremental backups and also in very large storage (costs) on Amazon S3.

Usually the files with low index names (e.g. 391089.1) change on read access.

On an update, we see changes in one or more files - the index could correlate to the age of the row in the table.

Some more facts:

Postgres version 13.1
Database is running in docker container (docker version 20.10.0)
OS is CentOS 7

We see the phenomenon on multiple servers.

Can someone explain, why postgresql changes data files on pure read access? We tested on a pure database without any other resources accessing the database.

...

ANSWER

Answered 2021-Feb-16 at 16:34

This is normal. Some cases I can think of right away are:

a SELECT or other SQL statement setting a hint bit

This is a shortcut for subsequent statements that access the data, so they don't have t consult the commit log any more.
a SELECT ... FOR UPDATE writing a row lock
autovacuum removing dead row versions

These are leftovers from DELETE or UPDATE.
autovacuum freezing old visible row versions

This is necessary to prevent data corruption if the transaction ID counter wraps around.

The only way to fairly reliably prevent PostgreSQL from modifying a table in the future is:

never perform an INSERT, UPDATE or DELETE on it
run VACUUM (FREEZE) on the table and make sure that there are no concurrent transactions

Source https://stackoverflow.com/questions/66227766

QUESTION

How to exclude a particular table in postgres backup using pgbackrest?

Asked 2020-Mar-04 at 18:12

Trying to exclude a particular table alone during postgres backup. Is there something similar in pgbackrest like pg_dump

pg_dump --exclude-table-data=ex_table demodb

...

ANSWER

Answered 2020-Mar-04 at 18:12

I have not found such option in pbBackRest and that is expected because it's a physical backup tool and not a logical backup tool like pg_dump.

Source https://stackoverflow.com/questions/60532079

QUESTION

Solve a permission problem found when running pgbackrest as a cron job

Asked 2019-Sep-24 at 17:36

I have a permissions error on a ubuntu host from the cron job setup to make a database backup using pgbackrest.

ERROR [041]: : unable to open /var/lib/postgresql/10/main/global/pg_control

The cron job is setup to run under my administrator account. The only option I see to fix this is to change the directory permissions to /var/lib/postgresql/10/main to allow my admin account in, and I don't want to do that.

Clearly only the postgres user has access to this directory and I found that its not possible to setup a cron job using that user. i.e.

...

ANSWER

Answered 2019-Sep-24 at 17:18

Only the PostgreSQL OS user (postgres) and its group are allowed to access the PostgreSQL data directory. See this code from the source:

Source https://stackoverflow.com/questions/58084901

QUESTION

Configuring Different repo path for pgbackrest wal archive

Asked 2019-Jun-10 at 08:46

I have installed and started using pgbackrest for postgresql incremental backups. Everything is working fine but i have a requirement to have separate repository for archived wals from the base backups. In pgbackrest documentation i can find only one setting for both.

repo1-path=/var/lib/pgbackrest

...

ANSWER

Answered 2019-Jun-10 at 08:46

I've ended up by setting a symbolic link for the archive directory after creating the stanza and working perfectly.

Source https://stackoverflow.com/questions/56107576

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install pgbackrest

pgBackRest strives to be easy to configure and operate:. Documentation for v1 can be found here. No further releases are planned for v1 because v2 is backward-compatible with v1 options and repositories.
User guides for various operating systems and PostgreSQL versions.
Command reference for command-line operations.
Configuration reference for creating pgBackRest configurations.

Support

Tablespaces are fully supported and on restore tablespaces can be remapped to any location. It is also possible to remap all tablespaces to one location with a single command which is useful for development restores. File and directory links are supported for any file or directory in the PostgreSQL cluster. When restoring it is possible to restore all links to their original locations, remap some or all links, or restore some or all links as normal files or directories within the cluster directory.

Find more information at: