|
On 6/5/19 9:48 AM, Pavan Kumar wrote:
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. |
