What is continuous data protection (CDP)?

Continuous data protection (CDP) is a data protection method that captures every write to protected storage as it happens and records it in a time-stamped journal. Any moment the journal covers can be restored, which brings the recovery point objective close to zero, at the cost of a short history.

How does journal-based change tracking work?

A component at the hypervisor, operating system or storage layer intercepts each write, sends a copy to a replica, often at another site, and records it with a timestamp in a journal. To recover, an operator picks a timestamp and the replica is rebuilt as it stood at that moment, with journaled writes applied up to that point and later ones discarded.

The journal is what separates CDP from plain data replication. A replica on its own holds only the latest state, so when a table is dropped or a volume is encrypted, the replica follows within seconds and no earlier version remains.

What does CDP do to the recovery point?

A nightly backup can lose up to a day of work and an hourly one up to an hour. With CDP the recovery point objective falls to seconds, bounded by how far the replica lags the source. Because every write is time-stamped, recovery can also land on the second before a faulty deployment or a bulk delete, which is the fine-grained form of point-in-time recovery.

How is CDP different from frequent snapshots?

PropertyContinuous data protectionFrequent snapshots (near-CDP)
What is capturedEvery individual writeThe state at fixed intervals
Recovery pointsAny moment in the journalOnly the moments a snapshot was taken
Recovery point objectiveSecondsThe snapshot interval, usually minutes
Storage and bandwidthGrow with every writeGrow with changed data per interval

Snapshot schedules are simpler and work on more systems. CDP is used where minutes of lost transactions are not acceptable.

Why does the journal cover only hours or days?

Every write is kept, so the journal grows with the write rate of the protected systems and is sized in days of changes, not months. Attackers who stay inside longer than the journal reaches leave every available point already containing their work. CDP also records malicious writes as faithfully as legitimate ones, so mass encryption is journaled like any other activity.

Where long-term backup takes over

Long-term immutable backups cover everything older than the journal. They also cover the case where the CDP platform itself is attacked: whoever controls the platform can truncate the journal, so history meant to survive a stolen administrator account is kept in storage that enforces its own retention lock. The 3-2-1-1-0 backup rule describes the same layering.

Frequently asked questions

Does continuous data protection replace backup?

No. It gives very fine recovery points over a short window. Retention for months or years, and protection when the journal itself is compromised, still come from backup.

Is CDP the same as replication?

No. Replication keeps the latest copy at another site, while CDP adds a time-stamped journal so earlier states can also be recovered.

What does CDP cost in storage and bandwidth?

Both scale with the write rate of the protected systems. A busy database sends a continuous stream to the replica and fills the journal quickly, which is why journal length is limited.