You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please provide the following information when submitting an issue (feature requests or general comments can skip this):
pgBackRest version: 2.39
PostgreSQL version: 12.15
Operating system/version - if you have more than one server (for example, a database server, a repository host server, one or more standbys), please specify each:
Ubuntu 20
Did you install pgBackRest from source or from a package?
Source Code
are the above steps are good to go for the change ?
If you don't want to copy/move the old repo content to the new one, yes, those steps seems enough to me. stranza-create can safely be used to init a new repo. And changing the repo1-host IP will make pgBackRest send the WAL archives there.
update repo1-host IP to new backup server, then initialize a new stanza with the same name as old repo. Ensure old repo is decommissioned to prevent WAL archives from being sent there.
Please provide the following information when submitting an issue (feature requests or general comments can skip this):
pgBackRest version: 2.39
PostgreSQL version: 12.15
Operating system/version - if you have more than one server (for example, a database server, a repository host server, one or more standbys), please specify each:
Ubuntu 20
Did you install pgBackRest from source or from a package?
Source Code
Please attach the following as applicable:
pgbackrest.conf
file(s)postgresql.conf
settings applicable to pgBackRest (archive_command
,archive_mode
,listen_addresses
,max_wal_senders
,wal_level
,port
)/var/log/pgbackrest
for the commands run (e.g./var/log/pgbackrest/mystanza_backup.log
)Archive Command:
archive_command: pgbackrest --stanza=prod archive-push %p
DB Server Configuration
[global]
repo1-host=xx.xxx.xxx.xx
repo1-host-user=pgbackrest
spool-path=/var/spool/pgbackrest
compress-level=6
compress-type=gz
[global:restore]
process-max=8
[global:archive-get]
process-max=4
[prod]
pg1-path=/postgresql/main
========================================================
New Backup Server Configuration:
[global]
repo1-path=/backup/pgbackrest
repo1-retention-archive=4
repo1-retention-full=4
repo1-retention-diff=4
start-fast=y
backup-standby=y
spool-path=/var/spool/pgbackrest
log-level-file=detail
log-level-console=detail
compress-type=gz
compress-level=6
[global:backup]
process-max=8
[global:restore]
process-max=16
[global:archive-get]
process-max=16
[global:archive-push]
process-max=2
[prod]
pg1-host=xx.xxx.x.xx
pg1-path=/postgresql/main
pg2-host=xx.xx.x.xx
pg2-path=/postgresql/main
pg3-host=xx.xxx.x.xx
pg3-path=/postgresql/main
We need to change Current Backup Server to New Backup Server, as per Infra Team suggestions.
For the above requirement i am following below steps
we dont want to change the archive_command and stanza name.
Old backup Server DB Backups will not be move or copy to new backup server, so it will be a fresh New Backup Server.
are the above steps are good to go for the change ?
The text was updated successfully, but these errors were encountered: