PROGRAM =pg_arman

PROGRAM =pg_probackup

OBJS = backup.o\

catalog.o\

data.o\

fetch.o\

init.o\

parray.o\

pg_arman.o\

pg_probackup.o\

restore.o\

show.o\

status.o\

REGRESS = init option show delete backup restore

all: checksrcdir datapagemap.h logging.h receivelog.h streamutil.hpg_arman

all: checksrcdir datapagemap.h logging.h receivelog.h streamutil.hpg_probackup

MAKE_GLOBAL="../../src/Makefile.global"

TEST_GLOBAL:=$(shell test -e ../../src/Makefile.global)

REGRESS =

subdir=contrib/pg_arman

subdir=contrib/pg_probackup

top_builddir=../..

include$(top_builddir)/src/Makefile.global

include$(top_srcdir)/contrib/contrib-global.mk

pg_arman forkfrom Postgres Professional

pg_probackup forkof pg_arman by Postgres Professional

This repository contains fork of pg_arman by Postgres Professional with

block level incremental backup support.

pg_arman is a backup and recovery manager for PostgreSQL servers able to do

pg_probackup is a backup and recovery manager for PostgreSQL servers able to do

differential and full backup as well as restore a cluster to a

state defined by a given recovery target. It is designed to perform

periodic backups of an existing PostgreSQL server, combined with WAL

The latest version of this software can be found on the project website at

https://github.com/postgrespro/pg_arman. Original fork ofpg_arman can be

https://github.com/postgrespro/pg_probackup. Original fork ofpg_probackup can be

found athttps://github.com/michaelpq/pg_arman.

Installation

Compilingpg_arman requires a PostgreSQL installation to be in place

Compilingpg_probackup requires a PostgreSQL installation to be in place

as well as a raw source tree. Pass the path to the PostgreSQL source tree

to make, in the top_srcdir variable:

In addition, you must have pg_config in $PATH.

The current version ofpg_arman is compatible with PostgreSQL 9.5 and

The current version ofpg_probackup is compatible with PostgreSQL 9.5 and

upper versions.

Platforms

pg_arman has been tested on Linux and Unix-based platforms.

pg_probackup has been tested on Linux and Unix-based platforms.

Documentation

All the documentation you can find[here](doc/pg_arman.md).

All the documentation you can find[here](doc/pg_probackup.md).

Regression tests

The test suite ofpg_arman is available in the code tree and can be

The test suite ofpg_probackup is available in the code tree and can be

launched in a way similar to common PostgreSQL extensions and modules:

some overhead to PostgreSQL performance. On our experiments it appears to be

less than 3%.

These two approaches were implemented in this fork ofpg_arman. The second

These two approaches were implemented in this fork ofpg_probackup. The second

approach requires[patch for PostgreSQL 9.5](https://gist.github.com/stalkerg/44703dbcbac1da08f448b7e6966646c0) or

[patch for PostgreSQL 10](https://gist.github.com/stalkerg/ab833d94e2f64df241f1835651e06e4b).

Example backup (assuming PostgreSQL is running):

pg_arman init -B /home/postgres/backup/pgarman

pg_probackup init -B /home/postgres/backup

pg_arman backup -B /home/postgres/backup/pgarman -D /home/postgres/pgdata/arman -b full -v -j 2

pg_probackup backup -B /home/postgres/backup -D /home/postgres/pgdata -b full -v -j 2

pg_arman show -B /home/postgres/backup/pgarman

pg_probackup show -B /home/postgres/backup

pg_arman backup -B /home/postgres/backup/pgarman -D /home/postgres/pgdata/arman -b page -v -j 2

pg_probackup backup -B /home/postgres/backup -D /home/postgres/pgdata -b page -v -j 2

pg_arman show -B /home/postgres/backup/pgarman

pg_probackup show -B /home/postgres/backup

For restore after remove your pgdata you can use:

Also, some WALs still need to be fetched in order to get consistent backup.pg_arman can fetch them trough the streaming replication protocol. Thus, you also need to[enable streaming replication connection](https://wiki.postgresql.org/wiki/Streaming_Replication).

Also, some WALs still need to be fetched in order to get consistent backup.pg_probackup can fetch them trough the streaming replication protocol. Thus, you also need to[enable streaming replication connection](https://wiki.postgresql.org/wiki/Streaming_Replication).

Example backup (assuming PostgreSQL is running):

pg_arman init -B /home/postgres/backup/pgarman

pg_probackup init -B /home/postgres/backup

pg_arman backup -B /home/postgres/backup/pgarman -D /home/postgres/pgdata/arman -b full -v -j 2 --stream

pg_probackup backup -B /home/postgres/backup -D /home/postgres/pgdata -b full -v -j 2 --stream

pg_arman show -B /home/postgres/backup/pgarman

pg_probackup show -B /home/postgres/backup

pg_arman backup -B /home/postgres/backup/pgarman -D /home/postgres/pgdata/arman -b ptrack -v -j 2 --stream

pg_probackup backup -B /home/postgres/backup -D /home/postgres/pgdata -b ptrack -v -j 2 --stream

pg_arman show -B /home/postgres/backup/pgarman

pg_probackup show -B /home/postgres/backup

For restore after remove your pgdata you can use:

License

pg_arman can be distributed under the PostgreSQL license. See COPYRIGHT

pg_probackup can be distributed under the PostgreSQL license. See COPYRIGHT

file for more information. pg_arman is a fork of the existing project

pg_rman, initially created and maintained by NTT and Itagaki Takahiro.

staticboolin_backup= false;/* TODO: more robust logic */

staticintstandby_message_timeout=10*1000;/* 10 sec = default */

staticXLogRecPtrstop_backup_lsn=InvalidXLogRecPtr;

constchar*progname="pg_arman";

constchar*progname="pg_probackup";

parray*backup_files_list;

time2iso(label,lengthof(label),current.start_time);

strncat(label," withpg_arman",lengthof(label));

strncat(label," withpg_probackup",lengthof(label));

pg_start_backup(label,smooth_checkpoint,&current);

elog(ERROR,"cannot lock backup catalog");

elseif (ret==1)

elog(ERROR,

"anotherpg_arman is running, skipping this backup");

"anotherpg_probackup is running, skipping this backup");

current.status=BACKUP_STATUS_RUNNING;

staticintlock_fd=-1;

elog(ERROR,"can't lock backup catalog.");

elseif (ret==1)

elog(ERROR,

"anotherpg_arman is running, stop delete.");

"anotherpg_probackup is running, stop delete.");

backup_list=catalog_get_backup_list(0);

elog(ERROR,"can't lock backup catalog.");

elseif (ret==1)

elog(ERROR,

"anotherpg_arman is running, stop delete.");

"anotherpg_probackup is running, stop delete.");

backup_list=catalog_get_backup_list(0);

for (i=0;i<parray_num(backup_list);i++)