The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →To take an incremental backup in PostgreSQL 18, pass pg_basebackup --incremental the manifest from an earlier backup of the same server. The server must have WAL summarization enabled and retain summaries covering the interval between backups. An incremental backup is not a complete data directory: use pg_combinebackup to reconstruct it with its dependencies before recovery.
What PostgreSQL 18 incremental backups contain
pg_basebackup backs up an entire PostgreSQL cluster, not selected databases or individual objects. In incremental mode, it compares the current cluster with a prior backup identified by its manifest. PostgreSQL uses WAL summaries to find changed blocks. Some relation files can be stored as incremental files containing changed blocks and reconstruction metadata; non-relation files are included in full. See the PostgreSQL 18 pg_basebackup documentation.
As an Amazon Associate I earn from qualifying purchases.
The manifest is the reference that ties the new backup to its predecessor. It also records backup file information and may include file checksums. Keep manifests with their corresponding backups: later increments need the correct earlier manifest, and the backup chain is part of the recovery input.
Prerequisites before taking an incremental backup
Enable WAL summarization and retain summaries
Set summarize_wal to enable WAL summarization; it is off by default. Summaries are stored in pg_wal/summaries. For an incremental backup to succeed, the server must have summaries for the full WAL range between the referenced backup and the new one. If any required summaries are missing, the incremental backup fails.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
wal_summary_keep_time controls how long summaries are kept. Its documented default is 10 days, but that is not a universal recommendation: configure it to cover the longest interval between backups that might later be used as dependencies. Consult PostgreSQL’s WAL configuration documentation for the setting details.
Provide replication access
pg_basebackup connects through PostgreSQL’s replication protocol. The connecting role must have the REPLICATION attribute or be a superuser, the applicable pg_hba.conf rule must allow the replication connection, and max_wal_senders must allow the backup connection and any WAL streaming being used. See the connection and server requirements.
Use a compatible server and client
The PostgreSQL 18 pg_basebackup documentation supports incremental backups with server version 17 and later. Confirm which server the client connects to and that the referenced manifest came from that same server.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
How to take an incremental backup with pg_basebackup
First create a full base backup and retain its manifest. For each subsequent incremental backup, point --incremental to the manifest of the backup you want to use as its reference. The path below is illustrative; replace it with the actual manifest path on the machine running the command.
-
Create and retain a full backup, including its manifest. For example, a tar-format backup can be made with
pg_basebackup --format=tar --pgdata=/backups/base. Ensure the resulting backup includes its manifest; PostgreSQL’s default is to write a manifest unless manifest generation has been disabled. -
Take the incremental backup using that manifest:
pg_basebackup --format=tar --pgdata=/backups/incremental-1 --incremental=/backups/base/backup_manifest.Rank #3
Seagate Portable 1TB External Hard Drive HDD – USB 3.0 for PC, Mac, PlayStation, & Xbox, 1-Year Rescue Service (STGX1000400) , Black- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
-
For later increments, choose the manifest for the intended earlier backup in the same chain. For example:
pg_basebackup --format=tar --pgdata=/backups/incremental-2 --incremental=/backups/incremental-1/backup_manifest.DriversOutdated Drivers Are Slowing You DownPerformancePC Slower Than It Used to Be?DriversCrashes, No Sound, or Screen Glitches?Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Retain each backup and its manifest, and confirm the command completed successfully. If the required WAL summaries are unavailable, resolve the summary-retention gap or take a new full backup before trying to establish a usable incremental chain.
The command examples show the option relationships, not a complete production backup policy. Choose output format, destination, authentication, WAL streaming, and scheduling to suit the deployment. The documentation’s pg_basebackup options describe additional settings.
Rank #4
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
How to reconstruct and restore an incremental chain
An incremental backup cannot be used directly as a complete data directory. Before recovery, combine it with all earlier backups on which it depends using pg_combinebackup. For example, if a full backup is followed by two increments, provide the chain in order and write the reconstructed output to a separate destination:
pg_combinebackup /backups/base /backups/incremental-1 /backups/incremental-2 -o /restore/clusterUse the resulting reconstructed data directory as the base for the recovery procedure appropriate to your deployment. If you are using continuous archiving for point-in-time recovery, you also need the WAL segments required from the base backup onward; recovery time depends in part on how much WAL must be replayed. PostgreSQL’s guides explain combining incremental backups and continuous archiving and point-in-time recovery.
Verify backups and protect their integrity
Run pg_verifybackup against a backup to check its files against the backup manifest. The manifest can include checksums for files; PostgreSQL’s default file checksum is CRC32C, and SHA-family checksums are also supported. CRC32C is faster and useful for detecting accidental changes, but it is not designed to resist malicious modification. A cryptographic SHA digest can help detect changes, but a manifest stored beside the backup can itself be altered. Protect the manifest or establish its integrity separately if tampering is in scope. See the manifest format, manifest top-level object, and backup verification guidance.
Best Value
- [Upgraded Version] - This external hard drive features a mirrored logo stripe combined with a striped anti-slip design, and the rounded corners of the casing make it easier to grip. The stripes also have a heat dissipation function, ensuring stable and fast data transfer.
- 【Ultra-thin and quiet】 - The motherboard adopts JMicron 578 noise-free solution, giving you a quiet working environment. Lightweight and portable size designed to fit in your pocket for easy portability.
- 【Ultra-Fast Data Transfers】 - Pairing this external hard drive with JMicron 578 solution USB 3.0 and USB 2.0 interfaces enables blazing-fast data transfer. It boasts theoretical read speeds of up to 125MB/s and write speeds of up to 103MB/s.
- 【Plug and Play】 - With no software to install, just plug it in and the drive is ready to use.The hard disk chip is wrapped with an aluminum anti-interference layer to increase heat dissipation and protect data.
- 【What You Get】 - 1 x Portable Hard Drive, 1 x USB 3.0 Cable, 1 x User Manual, Gift-type shell packaging ,Three-year manufacturer's warranty and free technical support services.
Plan retention around recovery, not just backup age
PostgreSQL does not automatically determine which earlier backups remain necessary for later increments. Do not delete a parent backup or its manifest while a retained incremental depends on it. Define retention by the recovery points you intend to preserve, tracing each point back through its full dependency chain. If the recovery plan includes continuous archiving, retain the required WAL as well as the base backup and increments.
When incremental backups fit—and what they do not promise
Incremental backups can reduce the amount of relation-file data written when relatively few blocks have changed, but the documentation does not establish a universal speed, storage, or cost advantage. Results depend on workload and operations, including WAL-summary availability, the size of changed data, chain retention, reconstruction, and restore requirements.
| Approach | Recovery outcome and workflow | Operational consideration |
|---|---|---|
| SQL dump | Logical backup restored by replaying SQL; not the same workflow as restoring a physical cluster. | Choose when logical export and restore are appropriate; it does not provide the physical incremental-chain workflow described here. |
| File-system-level backup | Copies the cluster’s files; consistency and recovery depend on how the copy is taken and the accompanying WAL strategy. | Requires a suitable method for obtaining a consistent backup and managing associated recovery data. |
| Base backup with continuous archiving | Can support point-in-time recovery by restoring a base backup and replaying archived WAL. | Requires retaining the WAL needed from the base backup onward and planning for replay time. |
| Incremental base backup | Must be reconstructed with its dependent backups using pg_combinebackup before it can serve as a complete recovery input. |
Requires a prior manifest from the same server, a complete range of WAL summaries, and deliberate retention of the dependency chain. |
PostgreSQL describes these options and their different recovery workflows in its backup and restore documentation. Select based on the required recovery outcome and the process your team can reliably operate, rather than assuming one method is always faster or cheaper.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
