liveBook · Manning

Continuous backup

Continuous backup is the ongoing capture or archival of data changes so a system can be restored to a recent point after disruption.

How 2 Manning books explain it

MongoDB 8.0 in Action, Third Edition

Continuous cloud backup continuously captures database changes and write history to support restoration to a selected point within a retention window.

How it is used
Protects Atlas clusters against accidental deletion and corruption by retaining changes for recovery within a configured window.
How deep it goes
Explains snapshot-based oplog replay and shows a restore command, but defers continuous-backup setup details to documentation.
Examples
Shows an Atlas CLI point-in-time restore specifying a UNIX timestamp, source cluster, target cluster, and target project.
What you can do after
Apply it via the Atlas CLI to request and monitor a restore to a selected time within the retention window.

Read how MongoDB 8.0 in Action, Third Edition explains continuous backup →

PostgreSQL Mistakes and How to Avoid Them

Continuous archiving is the ongoing preservation of database transaction-log segments so changes can be replayed during recovery.

How it is used
Enables point-in-time recovery beyond the state captured by the latest full backup.
How deep it goes
Explains configuration, backup-time WAL retention, recovery_target_time restoration, and restore testing without detailing archive-command implementations.
Examples
Uses recovery immediately before damage and a cascaded replication topology for redundancy and backup.
What you can do after
Operate/configure WAL archiving, base backups, timed recovery, redundant backup storage, and full-restore verification.

Read how PostgreSQL Mistakes and How to Avoid Them explains continuous backup →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.