mirror of
https://github.com/pgbackrest/pgbackrest.git
synced 2024-12-12 10:04:14 +02:00
34c63276cd
There are a number of cases where a checksum delta is more appropriate than the default time-based delta: * Timeline has switched since the prior backup * File timestamp is older than recorded in the prior backup * File size changed but timestamp did not * File timestamp is in the future compared to the start of the backup * Online option has changed since the prior backup A practical example is that checksum delta will be enabled after a failover to standby due to the timeline switch. In this case, timestamps can't be trusted and our recommendation has been to run a full backup, which can impact the retention schedule and requires manual intervention. Now, a checksum delta will be performed if the backup type is incr/diff. This means more CPU will be used during the backup but the backup size will be smaller and the retention schedule will not be impacted. Contributed by Cynthia Shang. |
||
|---|---|---|
| .. | ||
| Archive | ||
| Backup | ||
| Check | ||
| Common | ||
| Config | ||
| Protocol | ||
| Storage | ||
| Db.pm | ||
| DbVersion.pm | ||
| Expire.pm | ||
| Info.pm | ||
| InfoCommon.pm | ||
| LibC.pm | ||
| LibCAuto.pm | ||
| Main.pm | ||
| Manifest.pm | ||
| Restore.pm | ||
| RestoreFile.pm | ||
| Stanza.pm | ||
| Version.pm | ||