Showing with 5 additions and 1 deletion.
  1. +4 −0 README.md
  2. +1 −1 metadata.json
4 changes: 4 additions & 0 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,10 @@ You can modify the default backup schedule by provide an array of hashes that de

NOTE: If you change the default schedule you'll likely stop managing a crontab entry and there's not a clean way to remove unmanaged crontab entries. So you may want to simply delete the pe-postgres crontab entry and let puppet repopulate it. `crontab -r -u pe-postgres`

### Backup Retention policy

By default the script will only hold two backups for each database. When the script runs it will remove the older of the two backups before starting the backup process. You can configure the retention by setting `pe_databases::backup::retention_policy: <#number of backups to store>`.

### Disable the maintenance cron job

If you run into your maintenance cron job having DEADLOCK errors as described in the [reindexing section](#reindexing) you may want to disable it. You can do so by setting `pe_databases::maintenance::disable_maintenace: true` in your hieradata.
Expand Down
2 changes: 1 addition & 1 deletion metadata.json
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "npwalker/pe_databases",
"version": "0.8.0",
"version": "0.8.1",
"author": "npwalker",
"summary": "A Puppet Module for Backing Up / Maintaining / Tuning Your Puppet Enterprise Databases",
"license": "Apache-2.0",
Expand Down