From: Peter Palfrader Date: Sat, 28 Sep 2019 17:11:00 +0000 (+0200) Subject: remove things no longer relevant X-Git-Url: https://git.adam-barratt.org.uk/?p=mirror%2Fdsa-wiki.git;a=commitdiff_plain;h=79c78d626f7b2a91fc4d864457b555987b66d106 remove things no longer relevant --- diff --git a/input/howto/postgres-backup.creole b/input/howto/postgres-backup.creole index 4f497ca..1e45bdc 100644 --- a/input/howto/postgres-backup.creole +++ b/input/howto/postgres-backup.creole @@ -34,9 +34,9 @@ If there is potentially more than one cluster, we cannot use the puppet {{{postgresql::server}}} class. We also use this for clusters that were initially set up without puppet. -* Add the server to the postgresql_server role in puppet's - hieradata/common.yaml. This will cause some scripts to be installed on the - host, as well as an ssh key to be created for the postgres user. +* Add the server to the roles::postgresql::server class role in hiera. + This will cause some scripts to be installed on the host, as well as an ssh + key to be created for the postgres user. * Add these to {{{/etc/postgresql/9.6/main/postgresql.conf}}} or equivalent {{{ @@ -45,29 +45,20 @@ initially set up without puppet. wal_level = archive max_wal_senders = 3 archive_timeout = 1h - archive_command = '/usr/local/bin/pg-backup-file main WAL %p' + archive_command = '/usr/local/bin/pg-backup-file mXXXXXX-CLUSTERNAMEHERE-XXXXain WAL %p' }}} * Run puppet on the postgresql server, ==== ssh authkeys ==== + * If you need extra options in the {{{debbackup-ssh-wrap}}} call on the backup server (for instance of the host should be allowed to fetch files), manually copy {{{~postgres/.ssh/id_rsa.pub}}} to {{{puppet:modules/postgres/templates/backup_server/sshkeys-manual.erb}}}. -* Otherwise, add the host to the postgres::backup_server::register_backup_clienthost line - in {{{puppet:modules/postgres/manifests/backup_source.pp}}}. ==== base backup config ==== -* Register each cluster in puppet's - {{{puppet:modules/postgres/manifests/backup_source.pp}}}. - This takes care of adding the replication user to pgpass on the backup servers, - and the firewall rule and adds the cluster to {{{make-base-backups}}}. - (The module can also create the postgres role and modify the hba file, but we - do not do this when we don't configure the entire cluster via puppet.) -* Historically, we also have clusters hardcoded in - {{{puppet:modules/postgres/templates/backup_server/postgres-make-base-backups.erb}}}. * Run puppet on the backup hosts (storace and backuphost as of 2018). * On the db server, create a role. Find the password to use on the backup host in {{{~debbackup/.pgpass}}}:\\