Method and system for file-level continuous data protection
View Patent ↗Continuous data protection is performed as two parallel processes: creating an initial backup by copying a data as a file/directory from the storage device into the backup storage, and copying the data to be written to the data storage as a part of a file/directory into the incremental backup. Alternatively, it can be performed as one process: copying the data to be written to the data storage as a part of a file/directory on the storage. A write command to a file system driver is intercepted and redirected to the backup, and the data is written to the incremental backup. If the write command is also directed to a not yet backed up data (a file/directory), the identified data is copied from the storage device to intermediate storage. The write command is executed on the file/directory from the storage device, and the file/directory is copied from the intermediate storage.
1. A computer system operable to provide online continuous data protection, the system comprising:
a processor;
a memory coupled to the processor and storing instructions to work with a file system;
the file system that stores files on a storage media and addresses the storage media using clusters as a minimal addressable unit;
a file system driver that services the file system;
a list of protected objects, the protected objects being files or directories,
with each protected object residing below a protected folder including a first timestamp indicating when protection was enabled for that object and a second timestamp indicating when the object became unprotected;
a storage media for storing the file system data, the storage media connected to the file system driver;
a filter that monitors changes in the file system and having a set of files that are being monitored;
wherein the filter redirects, to backup storage, only portions of files that are being modified prior to the modification, and overwrites those portions with new data;
wherein, after a write file request is received, data is written to the file, file changes are copied to dirty pages, and the file changes are written to incremental backup,
wherein each file cluster is written to the backup storage only once for every opening of the file, and
wherein a new version of each file cluster is written to the backup storage for each time the file is opened;
upon user action, the filter providing a rollback to a prior state with the data prior to the modification coming from the backup storage, and unmodified portions of the file coming from the storage media.
2. The system of claim 1 , wherein a backup copy of the entire file is first created on the backup storage, by using a background backup process.
3. The system of claim 1 , wherein a backup copy of modified clusters is created every time the file is opened.
4. The system of claim 1 , wherein the backup copy of modified clusters is created periodically on the backup storage.
5. The system of claim 1 , wherein a backup copy of a current version of the file is created periodically on the backup storage.
6. The system of claim 1 , wherein the backup copy of modified clusters is created every time the file is saved.
7. The system of claim 1 , wherein, while the file is opened, the new data is used to overwrite a corresponding cluster in the backup storage.
8. The system of claim 1 , wherein the new data is also written to the backup storage.
9. The system of claim 1 , wherein the set of files is defined based on being located in a designated folder.
10. The system of claim 1 , wherein the file system driver backs up the entire file data onto the storage media.
11. The system of claim 1 , wherein the file system driver backs up the data required to be written by a write request prior to writing it into the file to the storage media.
12. The system of claim 11 , wherein the file system driver backs up only the file data to be written over by the write request.
13. The computer system of claim 11 , wherein the file system driver backs up the entire file data to the storage media and the data required to be written into the file by the write request.
14. The computer system of claim 11 , wherein the file system driver backs up to the storage media the data required to be written into the file by the write request.
15. The computer system of claim 11 , wherein the file system driver translates the write request into one or more block write operations.
16. The computer system of claim 11 , further comprising a storage device driver operable to read from a volume of the storage media and write to a volume of the storage media in block mode in response to the write request.
17. The system of claim 1 , wherein the file system driver maintains the list.
18. The system of claim 1 , wherein a size of the clusters depends on file size.
19. A method of providing online continuous data protection, the method comprising:
using a file system, storing files on a storage media and addressing the storage media using clusters as a minimal addressable unit,
servicing the file system using a file system driver;
maintaining a list of protected objects, the protected objects being files or directories,
with each protected object residing below a protected folder including a first timestamp indicating when protection was enabled for that object and a second timestamp indicating when the object became unprotected;
storing the file system data on the storage media, wherein the storage media is connected to the file system driver;
using a filter, monitoring changes in the file system, the filter a set of files that are being monitored;
using the filter, redirecting, to backup storage, only portions of files that are being modified prior to the modification, and overwriting those portions with new data;
wherein each file cluster is written to the backup storage only once for every opening of the file,
wherein, after a write file request is received, data is written to the file, file changes are copied to dirty pages, and the file changes are written to incremental backup, and
wherein a new version of each file cluster is written to the backup storage for each time the file is opened;
upon user action, providing, using the filter, a rollback to a prior state with the data prior to the modification coming from the backup storage, and unmodified portions of the file coming from the storage media.