Editing Backup (section)

====Near-CDP{{anchor|Continuous_data_protection}}====
[[Continuous Data Protection]] (CDP) refers to a backup that instantly saves a copy of every change made to the data. This allows restoration of data to any point in time and is the most comprehensive and advanced data protection.<ref name=InformationWeekWhyCDPGettingMorePractical>{{cite web
   |author=Behzad Behtash
   |url=https://www.informationweek.com/why-continuous-data-protections-getting-more-practical/d/d-id/1088883
   |title=Why Continuous Data Protection's Getting More Practical
   |work=Disaster recovery/business continuity
   |publisher=InformationWeek |date=6 May 2010 |access-date=12 November 2011 |quote=A true CDP approach should capture all data writes, thus continuously backing up data and eliminating backup windows.... CDP is the gold standard—the most comprehensive and advanced data protection. But "near CDP" technologies can deliver enough protection for many companies with less complexity and cost. For example, snapshots can provide a reasonable near-CDP-level of protection for file shares, letting users directly access data on the file share at regular intervals--say, every half-hour or 15 minutes. That's certainly a higher level of protection than tape-based or disk-based nightly backups and may be all you need.}}</ref> Near-CDP backup applications—often [[List of backup software#Proprietary|marketed]] as "CDP"—automatically take incremental backups at a specific interval, for example every 15 minutes, one hour, or 24 hours. They can therefore only allow restores to an interval boundary.<ref name=InformationWeekWhyCDPGettingMorePractical /> Near-CDP backup applications use [[Journaling file system|journaling]] and are typically based on periodic "snapshots",<ref name="ComputerWeeklyCDPExplained">{{cite web |title=Continuous data protection (CDP) explained: True CDP vs near-CDP |url=https://www.computerweekly.com/Continuous-data-protection-CDP-explained-True-CDP-vs-near-CDP |website=ComputerWeekly.com |publisher=TechTarget |access-date=22 June 2019 |date=July 2010 |quote=... copies data from a source to a target. True CDP does this every time a change is made, while so-called near-CDP does this at pre-set time intervals. Near-CDP is effectively the same as snapshotting....True CDP systems record every write and copy them to the target where all changes are stored in a log. [new paragraph] By contrast, near-CDP/snapshot systems copy files in a straightforward manner but require applications to be quiesced and made ready for backup, either via the application's backup mode or using, for example, Microsoft's Volume Shadow Copy Services (VSS).}}</ref> [[file system permissions|read-only]] copies of the data frozen at a particular [[point in time]].

Near-CDP (except for [[Apple Time Machine]])<ref name="PondiniHowTMWorksItsMagic">{{cite web |last1=Pond |first1=James |title=How Time Machine Works its Magic |url=https://www.baligu.com/pondini/TM/Works.html |website=Apple OSX and Time Machine Tips |publisher=Baligu.com (as mirrored after James Pond died in 2013) |access-date=10 July 2019 |date=31 August 2013 |quote=The File System Event Store is a hidden log that OSX keeps on each HFS+ formatted disk/partition of changes made to the data on it. It doesn’t list every file that’s changed, but each directory (folder) that’s had anything changed inside it.}}</ref> [[Intent log|intent-logs]] every change on the host system,<ref name="deGuiseEnterprise09#A.3.3">{{cite book |url=https://books.google.com/books?id=2OtqvySBTu4C&pg=PA287|title=Enterprise Systems Backup and Recovery: A Corporate Insurance Policy |author=de Guise, P. |publisher=CRC Press |pages=285–287 |year=2009 |isbn=978-1-4200-7639-4}}</ref> often by saving byte or block-level differences rather than file-level differences. This backup method differs from simple [[disk mirroring]] in that it enables a roll-back of the log and thus a restoration of old images of data. Intent-logging allows precautions for the consistency of live data, protecting ''self-consistent'' files but requiring ''applications'' "be quiesced and made ready for backup."

Near-CDP is more practicable for ordinary personal backup applications, as opposed to ''true'' CDP, which must be run in conjunction with a virtual machine<ref name="VictorWuEMCRecoverPointVM">{{cite web |last1=Wu |first1=Victor |title=EMC RecoverPoint for Virtual Machine Overview |url=https://wuchikin.wordpress.com/2017/03/04/emc-recoverpoint-for-virtual-machine-overview/ |website=Victor Virtual |publisher=WuChiKin |access-date=22 June 2019 |date=4 March 2017 |quote=The splitter splits out the Write IOs to the VMDK/RDM of a VM and sends a copy to the production VMDK and also to the RecoverPoint for VMs cluster.}}</ref><ref name="RES-QServicesZertoOrVeeam">{{cite web |title=Zerto or Veeam? |url=https://resqdr.com/zerto-or-veeam/ |website=RES-Q Services |access-date=7 July 2019 |date=March 2017 |quote=Zerto doesn’t use snapshot technology like Veeam. Instead, Zerto deploys small virtual machines on its physical hosts. These Zerto VMs capture the data as it is written to the host and then send a copy of that data to the replication site.....However, Veeam has the advantage of being able to more efficiently capture and store data for long-term retention needs. There is also a significant pricing difference, with Veeam being cheaper than Zerto.}}</ref> or equivalent<ref name="CloudEndureAgentRelated">{{cite web |title=Agent Related |url=https://docs.cloudendure.com/Content/FAQ/FAQ/Agent_Related.htm |website=CloudEndure.com |access-date=3 July 2019 |at=What does the CloudEndure Agent do? |date=2019 |quote=The CloudEndure Agent performs an initial block-level read of the content of any volume attached to the server and replicates it to the Replication Server. The Agent then acts as an OS-level read filter to capture writes and synchronizes any block level modifications to the CloudEndure Replication Server, ensuring near-zero RPO.}}</ref> and is therefore generally used in enterprise client-server backups.

Software may create copies of individual files such as written documents, multimedia projects, or user preferences, to prevent failed write events caused by power outages, operating system crashes, or exhausted disk space, from causing data loss. A common implementation is an appended [[Bak file|".bak" extension]] to the [[file name]].