Continuous Data Protection
Protect against damage from ransomware, malware and other sources of data corruption
Rollback to restore a volume to an arbitrary point-in-time state in a defined time frame
Generate known-good restore points
Operates independant of operating system or applications
No need to quisce or interrupt applications
No host agents required
Easy to enable protection and create rollback volumes
How Continuous Data Protection Works
CDP records every write I/O (or change), with a corresponding timestamp, that occurs against a protected volume. With continuous data protection, a rollback volume can be created representing any point-in-time just before the undesired event occurred. The rollback volume is then mapped to the original application server or a different one.
As data is written to the protected production volume, a copy of each write I/O is copied to the designated continuous data protection journal. A rollback volume can be created based on the data that resides in the CDP journal at a specified time.
CDP Ensures Lower RPO Than Traditional Backup and Snapshots
Because traditional backup is done on a daily basis and snapshots are taken every few hours, the recovery point objective (RPO) with these operations is much higher than CDP. Since CDP can restore the data in the affected volume to just right before the event of disruption, RPO for CDP is close to zero. Recovery time objective (RTO) values are also lower for CDP when compared to storage backup and snapshots.
The figure above highlights the differences in RPO and RTO values between storage backup, snapshot, and CDP