You've already forked pgbackrest
mirror of
https://github.com/pgbackrest/pgbackrest.git
synced 2025-07-05 00:28:52 +02:00
Multiple repository support.
Up to four repositories may be configured. A potential benefit is the ability to have a local repository for fast restores and a remote repository for redundancy. Some commands, e.g. stanza-create/stanza-update, will automatically work with all configured repositories while others, e.g. stanza-delete, will require a repository to be specified using the repo option. See the command reference for details on which commands require the repository to be specified. Note that the repo option is not required when only repo1 is configured in order to maintain backward compatibility. However, the repo option is required when a single repo is configured as, e.g. repo2. This is to prevent command breakage if a new repository is added later. The archive-push command will always push WAL to the archive in all configured repositories but backups will need to be scheduled individually for each repository. In many cases this is desirable since backup types and retention will vary by repository. Likewise, restores must specify a repository. It is generally better to specify a repository for restores that has low latency/cost even if that means more recovery time. Only restore testing can determine which repository will be most efficient. For single repository configurations there should be no change in behavior.
This commit is contained in:
@ -123,8 +123,19 @@ testRun(void)
|
||||
"\n"
|
||||
"Restore a database cluster.\n"
|
||||
"\n"
|
||||
"This command is generally run manually, but there are instances where it might\n"
|
||||
"be automated.\n"
|
||||
"The restore command automatically defaults to selecting the latest backup from\n"
|
||||
"the first repository where backups exist. The order in which the repositories\n"
|
||||
"are checked is dictated by the pgbackrest.conf (e.g. repo1 will be checked\n"
|
||||
"before repo2). To select from a specific repository, the --repo option can be\n"
|
||||
"passed (e.g. --repo=1). The --set option can be passed if a backup other than\n"
|
||||
"the latest is desired.\n"
|
||||
"\n"
|
||||
"For PITR, --type=time must be provided and the target time specified with the\n"
|
||||
"--target option. If a backup is not specified via the --set option, then the\n"
|
||||
"configured repositories will be checked, in order, for a backup that contains\n"
|
||||
"the requested time. If no backup can be found, the latest backup from the first\n"
|
||||
"repository containing backups will be used. See Point-in-Time Recovery for more\n"
|
||||
"details and examples.\n"
|
||||
"\n"
|
||||
"Command Options:\n"
|
||||
"\n"
|
||||
@ -188,6 +199,7 @@ testRun(void)
|
||||
"\n",
|
||||
"Repository Options:\n"
|
||||
"\n"
|
||||
" --repo set repository\n"
|
||||
" --repo-azure-account azure repository account\n"
|
||||
" --repo-azure-container azure repository container\n"
|
||||
" --repo-azure-endpoint azure repository endpoint\n"
|
||||
|
Reference in New Issue
Block a user