Create the standby.signal file and start the standby PostgreSQL server and monitor the PostgreSQL log file.Restore_command = 'cp /home/postgres/wal_archive/%f %p'Īrchive_cleanup_command = 'pg_archivecleanup -d /home/postgres/wal_archive %r' Configure the standby parameters by editing its nf file.data]$ pg_basebackup -h pg13-master -p 5432 -U postgres -D /var/lib/pgsql/13/data -Fp -Xs -P data]$ ls -ltr.Take the base backup of the master server from the standby server by using the pg_basebackup utility.~]$ systemctl stop ~]$ cd data]$ rm -rf data]$ ls -ltr.Stop the standby server and remove all the contents of its data directory before taking the base backup of the master server.Reload the Postgres server for the changes to take effect. On the master server pg_hba.conf file make an entry for the standby server to take remote base backup of the master server from the standby server.
Postgres=# select ~]$ cd wal_archive]$ ls -ltr Verify the WAL archiving is working fine by manually switching the WAL on the master node and listing the standby WAL directory.Select name,setting,unit from pg_settings where name in ('wal_level','archive_command','archive_mode','archive_timeout') Restart the PostgreSQL server and validate the settings.~]# su - ~]$ ssh-keygen -t ~]$ ls -ltr ~]$ ssh-copy-id -i ~/.ssh/id_rsa.pub ~]$ ssh Configure master server parameters by editing the nf file for the continuous archiving of WAL to the standby location.Īrchive_command = 'test ! -f & rsync -a %p = on.
On the master, execute ssh-keygen with the empty passphrase to generate public and private keys and then transfer the public key to the standby node using the ssh-copy-id command.
Two VM hosts with PostgreSQL 13 preinstalled.
0 kommentar(er)
