Loading howto/postgresql.md +3 −5 Original line number Diff line number Diff line Loading @@ -626,19 +626,17 @@ it isn't available in Debian. ### BASE-IS-OLD WARNING: this procedure was taken from the [DSA wiki](https://dsa.debian.org/howto/postgres-backup/) and is untested. Our nagios check warns us when a backup server has not successfully fetched a base backup recently. The causes often are that either the postgres server or the backup host went down or was down during the time of the weekly cronjob. time of the weekly cronjob. The TLS certificate could have also been renewed without the postgres daemon having been restarted. To re-run a base backup for a specific cluster, log into the backup server(s) (currently `bungei`), then find the port for the affected cluster: cat /etc/dsa/postgresql-backup/base-backup-clusters tail /usr/local/bin/postgres-make-base-backups Then run this backup in a screen: Loading Loading
howto/postgresql.md +3 −5 Original line number Diff line number Diff line Loading @@ -626,19 +626,17 @@ it isn't available in Debian. ### BASE-IS-OLD WARNING: this procedure was taken from the [DSA wiki](https://dsa.debian.org/howto/postgres-backup/) and is untested. Our nagios check warns us when a backup server has not successfully fetched a base backup recently. The causes often are that either the postgres server or the backup host went down or was down during the time of the weekly cronjob. time of the weekly cronjob. The TLS certificate could have also been renewed without the postgres daemon having been restarted. To re-run a base backup for a specific cluster, log into the backup server(s) (currently `bungei`), then find the port for the affected cluster: cat /etc/dsa/postgresql-backup/base-backup-clusters tail /usr/local/bin/postgres-make-base-backups Then run this backup in a screen: Loading