Search Current Space

compared with
Current by Nadja Pollard
on Apr 24, 2013 10:40.

(show comment)
Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (3)

View Page History
{page-title}
There is a big debate between the advantages of "True" CDP v.s. near-Continuous.  R1Soft's Continuous Data Protection products are technically near-continuous.  A good definition is available at [http://en.wikipedia.org/wiki/Near_Continuous_Backup]\\

True CDP is a variation of replication technology and to be a True Continuous Backup, an application must provide at least one -second granularity between recovery points.   This is why this True CDP Technology is only available to Storage Area Networks and also has limited application particularly to streaming type applications.

The reason True CDP is not useful for most servers is that most servers tend to be transaction or file oriented.  For example a user edits a file or sends an email.  Or a person purchases something online which involves one or more database transactions.   All of these end up as File System I/O.
If you have dealt with performance tuning on a server you probably have experienced that frequently flushing the Disk cache can seriously degrade performance.  So a flush done every second on the order of so called "True CDP" is completely impractical.

Near-Continuous backup applications like R1Soft in contrast to True CDP have user scheduled synchronizations.  Realistically these can only be performed as frequently as every 15 minutes as that is about as often as frequent as you can safely flush the disk cache without loosing any performance.
|| || True CDP \\ || near-Continuous (R1Soft) \\ ||
| {color:#000000}{*}Recovery Point Granularity{*}{color} \\ | {color:#000000}{*}1 Second or less playback{*}{color} \\ | {color:#000000}{*}User scheduled e.g. every 15 minutes{*}{color} \\ |