Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hYXXQ-00080R-F6 for pgsql-general@arkaria.postgresql.org; Wed, 05 Jun 2019 15:09:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hYXXP-0006D6-6R for pgsql-general@arkaria.postgresql.org; Wed, 05 Jun 2019 15:09:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hYXXO-0006Cz-Jk for pgsql-general@lists.postgresql.org; Wed, 05 Jun 2019 15:09:14 +0000 Received: from mail-oi1-x244.google.com ([2607:f8b0:4864:20::244]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hYXXM-00007Y-33 for pgsql-general@lists.postgresql.org; Wed, 05 Jun 2019 15:09:13 +0000 Received: by mail-oi1-x244.google.com with SMTP id u64so18446268oib.1 for ; Wed, 05 Jun 2019 08:09:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=ZXgqna+IxBoDVoYRf2SG6f+HBlcC5axOnuLoPRjwwOg=; b=pillcDKgQMDmw5vHfZHYYpiR6RErHVy0lwFzhAL1HJ3/fdnr+ewev6YcMny3W+t2dj de2J28eJY/pj10zf5OyUJYBzhMy1/co9BhhUYOWULWXWamkQcJbQhi1ni99OZomFsSCX 7BZ+jdLG/kMxb43ZOgYQ5ACt4p1FNL+6b+nO6QIV/BcMvg2C9O/5SsVpSwJE2GwqCVqa dq4l7tHJ2GEL3e+lBGnXxnlo5DWu6zyBZ3dqn5ZA1CvxUnIc1NZiQA+RS1Q7WPX0YbbQ MhRia6uHCVNfAh8FM8DAHZiPve+nJCeMSPdKzsfC+FNI2tIuTc/H1pseouk7OqyMSr7p f41Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=ZXgqna+IxBoDVoYRf2SG6f+HBlcC5axOnuLoPRjwwOg=; b=nxzUPQ2heiPwZqOU8v9EY+cejJHfn76sLVqHe4CUdrhV7256QbhEHRjXM+LCF+hHPH blN64O4/nUZ2xwunXbbJ3E/KJa8D6KDVC6VIQQ8OK5RqwnOU8iydj9i0EPlifNWn9jEz PhV5uXIMaNnPaA3arnqfZGMnkgzGnDjlzJDcHPfF0fj7xJ5hnEcYQ7ix4H4aUELwtxDb u3l4pfTqbxzoSJj+zuNicyWBFIWOavEABSJrAYpIHnESumQVL4PT+a1mOpEBjaLdEN5C bqdQo7hVLDAM0s9MrsFqaDGJiyytOBB3ITA30m9cbfM0M8CGjcmTqcic1zpa4n3dfmkg Wrdw== X-Gm-Message-State: APjAAAUQcTbFwcBv7Ved014CPhkXJvggWfnsOlTMMegGv64frnN9pIkl 3g127iqlo303Cb1uFPLzXnrb3c6QHiBquQ== X-Google-Smtp-Source: APXvYqzM9UZBh37s+HvxvXx1FthttOnef05ujaWSob0ZtOy9U/OmSNr0FFcQhCf0qF8RP0dHcBneRg== X-Received: by 2002:aca:3e54:: with SMTP id l81mr6465412oia.150.1559747350784; Wed, 05 Jun 2019 08:09:10 -0700 (PDT) Received: from [192.168.1.10] (ip70-171-116-89.no.no.cox.net. [70.171.116.89]) by smtp.googlemail.com with ESMTPSA id c204sm10250866oih.19.2019.06.05.08.09.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Jun 2019 08:09:09 -0700 (PDT) Subject: Re: configure multiple repository path in pgbackrest To: pgsql-general@lists.postgresql.org References: From: Ron Message-ID: Date: Wed, 5 Jun 2019 10:09:08 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------BA874980ABBF91FB005D870C" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------BA874980ABBF91FB005D870C Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 6/5/19 9:48 AM, Pavan Kumar wrote: > Hello Experts, > > Is it possible to configure multiple backup repositories in pgbackrest > tool in one server? > I am getting few issues with that. https://pgbackrest.org/command.html#command-backup 3.4.9 Repository Path Option (--repo-path) Path where backups and archive are stored. The repository is wherepgBackReststores backups and archives WAL segments. It may be difficult to estimate in advance how much space you'll need. The best thing to do is take some backups then record the size of different types of backups (full/incr/diff) and measure the amount of WAL generated per day. This will give you a general idea of how much space you'll need, though of course requirements will likely change over time as your database evolves. default: /var/lib/pgbackrest example: --repo1-path=/backup/db/backrest Since there's a --repo*1*-path, then presumably there can also be a --repo2-path. You'd presumably associate a database with repo2 by using --pg2-path https://pgbackrest.org/command.html#command-archive-get 2.5 Stanza Options 2.5.1 PostgreSQL Path Option (--pg-path) PostgreSQLdata directory. This should be the same as thedata_directorysetting inpostgresql.conf. Even though this value can be read frompostgresql.conforPostgreSQLit is prudent to set it in case those resources are not available during a restore or offline backup scenario. Thepg-pathoption is tested against the value reported byPostgreSQLon every online backup so it should always be current. example: --pg1-path=/data/db Deprecated Name: db-path Of course, this might not work, so you'll have to try it yourself. -- Angular momentum makes the world go 'round. --------------BA874980ABBF91FB005D870C Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

On 6/5/19 9:48 AM, Pavan Kumar wrote:
Hello Experts,

Is it possible to configure multiple backup repositories in pgbackrest tool in one server?
I am getting few issues with that. 

https://pgbackrest.org/command.html#command-backup

3.4.9
Repository Path Option (--repo-path)
Path where backups and archive are stored.
The repository is where pgBackRest stores backups and archives WAL segments.

It may be difficult to estimate in advance how much space you'll need. The best thing to do is take some backups then record the size of different types of backups (full/incr/diff) and measure the amount of WAL generated per day. This will give you a general idea of how much space you'll need, though of course requirements will likely change over time as your database evolves.
default: /var/lib/pgbackrest
example: --repo1-path=/backup/db/backrest

Since there's a --repo1-path, then presumably there can also be a --repo2-path.

You'd presumably associate a database with repo2 by using --pg2-path

https://pgbackrest.org/command.html#command-archive-get

2.5
Stanza Options
2.5.1
PostgreSQL Path Option (--pg-path)
PostgreSQL data directory.
This should be the same as the data_directory setting in postgresql.conf. Even though this value can be read from postgresql.conf or PostgreSQL it is prudent to set it in case those resources are not available during a restore or offline backup scenario.

The pg-path option is tested against the value reported by PostgreSQL on every online backup so it should always be current.
example: --pg1-path=/data/db
Deprecated Name: db-path

Of course, this might not work, so you'll have to try it yourself.

--
Angular momentum makes the world go 'round.
--------------BA874980ABBF91FB005D870C--