db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2025-11-06 08:49:29 +02:00
Code Issues Releases Activity

Documentation for issue #93: Prevent misconfigured retention-archive setting

Browse Source 
Not an actual fix - just some documentation to (hopefully) keep users from getting bitten until then.
This commit is contained in:
David Steele
2015-06-10 15:44:13 -04:00
parent af98f164cd
commit aca4511350
2 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -701,7 +701,9 @@ example: retention-archive-type=diff
##### `retention-archive` key
Number of backups worth of archive log to keep.
Number of backups worth of archive log to keep. If this is set less than your backup retention then be sure you set `archive-copy=y` or you won't be able to restore some older backups.
For example, if `retention-archive=2` and `retention-full=4`, then any backups older than the most recent two full backups will not have WAL segments in the archive to make them consistent. To solve this, set `archive-copy=y` and use `type=none` when restoring. This issue will be addressed in a future release but for now be careful with this setting.
```
required: n
example: retention-archive=2

4
doc/doc.xml
View File

@@ -650,7 +650,9 @@ Run a <id>full</id> backup on the <id>db</id> stanza. <param>--type</param> can
<!-- CONFIG - RETENTION SECTION - ARCHIVE-RETENTION KEY -->
<config-key id="retention-archive">
<text>Number of backups worth of archive log to keep.</text>
<text>Number of backups worth of archive log to keep. If this is set less than your backup retention then be sure you set <setting>archive-copy=y</setting> or you won't be able to restore some older backups.
For example, if <setting>retention-archive=2</setting> and <setting>retention-full=4</setting>, then any backups older than the most recent two full backups will not have WAL segments in the archive to make them consistent. To solve this, set <setting>archive-copy=y</setting> and use <setting>type=none</setting> when restoring. This issue will be addressed in a future release, but for now be careful with this setting.</text>
<example>2</example>
</config-key>