Method and system of operating a continuous data protection backup data storage system

The method optimizes CDP backup data storage by selectively transferring metadata and data to a CDP journal, addressing inefficiencies and redundancy in existing systems, thereby enhancing resource utilization and storage efficiency.

WO2024235423A1PCT designated stage expired Publication Date: 2024-11-21HUAWEI TECH CO LTD +1
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2023/062776
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-12
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

Existing Continuous Data Protection (CDP) backup data storage systems face inefficiencies due to redundancy and resource wastage, particularly in log-structured storage systems, where frequent overwrites increase write amplification and reduce system lifetime, and the need for frequent snapshots to meet recovery objectives.

Method used

A method and system that determine whether data buffers overwrite previous versions, transferring only necessary metadata and data to a CDP journal, using a clean-up routine or index to identify and store only frequently overwritten data, thereby reducing redundancy and optimizing storage utilization.

Benefits of technology

This approach conserves resources, reduces storage requirements, and enhances CDP efficiency by eliminating duplicates and maintaining only relevant data, while minimizing write latency and extending data retention without excessive storage consumption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2023062776_21112024_PF_FP_ABST
    Figure EP2023062776_21112024_PF_FP_ABST
Patent Text Reader

Abstract

Provided is a method of operating a Continuous Data Protection, CDP backup data storage system (116) for backing up data being stored to a primary data storage system (102). The method includes receiving a buffer of data (106A) associated with a persistent data operation on the primary data storage system at the CDP backup data storage system. The method includes storing the received buffer of data into a storage subsystem data journal component (104). The method includes determining if the stored buffer of data is over-writing a previous version of the data stored on the primary data storage system. The method includes where it is determined that the stored buffer of data is over-writing a previous version of the data stored on the primary data storage system, transfer a buffer of data (106B) from the storage subsystem data journal component to a CDP data journal storage component (112).
Need to check novelty before this filing date? Find Prior Art

Description

[0001] METHOD AND SYSTEM OF OPERATING A CONTINUOUS DATA PROTECTION

[0002] BACKUP DATA STORAGE SYSTEM

[0003] TECHNICAL FIELD

[0004] The disclosure relates generally to a backup data storage system and more particularly, the disclosure relates to a method of operating a Continuous Data Protection (CDP) backup data storage system for backing up data being stored to a primary data storage system. The disclosure also relates to a system adapted for carrying out the method.

[0005] BACKGROUND

[0006] In computer systems, a snapshot represents a state of a computer system at a particular Point in Time (PIT). The state of the computer system may include fdes, configuration, and the like. The snapshot appears as an exact image of a snapped file system at the time when the snapshot is created. A function of the snapshot allows a backup or mirror program to run concurrently with user updates and obtain a consistent copy of a protected object as of the time during which the snapshot was created. The snapshot provides an online backup capability that allows recovery from common problems such as accidental deletion of files. CDP provides a granular backup capability and allows a user to recover a snapped file at any PIT. Continuous data protection (CDP) is a method for creating a copy of data with an ability to restore the data to any previous point in time.

[0007] An existing method and protocol create the snapshot and backup the snapshots incrementally for each user and vendor. The existing method includes CDP-based protection and snapshotbased protection. The user may select a period of time in which the CDP-based protection is applied to the computer system and select another period in which the snapshot-based protection is applied to the computer system. However, the CDP-based protection and the snapshot-based protection are not mutually exclusive and are defined per the user’s Recovery Point Object (RPO), and Recovery Time Objective (RTO) needs. The RPO defines a maximum length of time from the last data restoration point. The RTO is a target period for downtime in an event of a crash. Moreover, the CDP requires a baseline to recover the snapshot at any PIT and a written buffer is replayed on top of the baseline. However, the baseline function implies the written buffers are restored over an existing volume of a storage system. The RTO duration increases as the volume become more distant from a targeted recovery point. Additionally, the snapshots need to be taken frequently to meet the RTO according to the user’s requirements. When the user chooses the PIT for the recovery, a closest snapshot is chosen as the baseline, and the written buffers are replayed or re-written on top of the baseline to obtain the PIT for the recovery.

[0008] The snapshot is an exact copy of the backup of the protected object which is maintained (e g., a backup vmdk) and the written buffers are mirrored to the backup and the snapshots are taken periodically. However, the written buffers are mirrored again to an external CDP journal to support the CDP for PIT recovery

[0009] A typical CDP application with a sequence of writes involves much redundancy in terms of capacity as the buffers and snapshots are stored and maintained in both the backup and the CDP journal. The mirroring buffer is CPU-intensive and Input / Output-intensive due to the arrival of the mirroring buffer as compressed buffers, and write amplification that reduces the lifetime of the computer system. Decompression of the buffers before updating the backup of the projected object is required to maintain an exact copy of the protected object. When the data or offset is frequently overwritten, the write amplification may be increased since the data has to be read from the storage for the data to be rewritten again to the CDP journal.

[0010] In a log- structured storage system, all data is logged and never overwritten in place, which means that overwritten data can still be accessed for a certain period of time depending on the storage's clean-up routine policy i.e. garbage collection routine policy, and implementation. As the logs in the log- structured storage system are designed to withhold a vast amount of data, relying solely on the log- structured storage system for the CDP might be inefficient, especially when protecting a smaller subset of the data.

[0011] Therefore, there arises a need to address the aforementioned technical problem / drawbacks to a backup data storage system of operating a CDP backup data storage system for backing up data being stored to a primary data storage system.

[0012] SUMMARY

[0013] It is an object of the disclosure to provide a method of operating a CDP backup data storage system for backing up data being stored to a primary data storage system, and a system adapted for carrying out the method, while avoiding one or more disadvantages of the prior art approaches. This object is achieved by the features of the independent claims. Further, implementation specifics are apparent from the dependent claims, the description, and the figures.

[0014] According to a first aspect, there is provided a method of operating a CDP backup data storage system for backing up data being stored to a primary data storage system. The method includes receiving a buffer of data associated with a persistent data operation on the primary data storage system at the CDP backup data storage system. The buffer includes data being stored by the persistent data operation, and first metadata related to the primary data storage system. The method includes storing the received buffer of data into a storage subsystem data journal component of the CDP backup data storage system. The method includes determining if the stored buffer of data is over-writing a previous version of the data stored on the primary data storage system, the previous version being a previous state of the data prior to the persistent data operation. The method includes determining that the stored buffer of data is over-writing a previous version of the data stored on the primary data storage system, transfer a buffer of data associated with the previous version of the data from the storage subsystem data journal component to a CDP data journal storage component of the CDP backup data storage system. The buffer of data associated with the previous version of the data contains the previous version of the data and the second metadata related to the CDP backup data storage system. The method includes where it is determined that the stored received buffer of data is not over-writing a previous version of the data stored on the primary data storage system, transfer, to the CDP data journal storage component, the second metadata related to the CDP backup data storage system without transferring the previous version of the data.

[0015] In one example implementation, the step of determining if the stored buffer of data is overwriting a previous version of the data stored on the primary data storage system includes using a CDP Journal clean up routine of the storage subsystem data journal component that writes overwritten buffers to an external CDP journal.

[0016] In another example implementation the step of determining if the stored buffer of data is overwriting a previous version of the data stored on the primary data storage system involves maintaining an index of a CDP journal by loading data from a backup object and writing the data to the CDP journal when an overwrite occurs, thereby enhancing the efficiency of the CDP and reducing the overhead of the CDP. This method enables redirecting of resources such as CPU, disk bandwidth, and conserved capacity for other use cases. This method eliminates redundancy and wasted resources and maintains metadata at the CDP journal. This method determines which type of data to include in the CDP journal while maintaining a consistent backup copy, thus conserving more resources. This method significantly conserves resources while maintaining the minimum necessary data for the CDP by identifying hotspots, i.e. offsets or the data that have been frequently overwritten since the last snapshot is taken.

[0017] This method eliminates duplicates and stores only the most relevant data in the CDP journal for optimizing storage utilization and reducing the overall storage requirement. In one example implementation, the storage subsystem data journal component persists incoming write buffers and maintains an index for serving future read requests. This method eliminates the written buffers later using the CDP Journal to reduce write latency. This method is less intrusive and can be deployed on systems from different proprietary storage vendors. This method enhances CDP applications. This method separates CDP data from backup data that can be captured through snapshots to retain the data in the CDP journal for a longer period, without consuming much storage space.

[0018] The persistent operation could be a write operation, a file creation operation or a file rename operation. The persistent operation could be any change made to a file system, including file copy, file deletion, attributes modification, etc.

[0019] The second metadata may include a flag having a first value specifying that the previous version of the data is stored at the storage subsystem data journal component of the CDP backup data storage system and having a second value specifying that the previous version of the data is stored at the CDP data journal storage component of the CDP backup data storage system.

[0020] The second metadata may include offset data specifying where data can be found in the storage subsystem data journal component of the CDP backup data storage system.

[0021] Optionally, the step of determining if the stored buffer of data is over-writing a previous version of the data stored on the primary data storage system is performed by a clean-up routine which identifies buffers of data in the storage subsystem data journal that have been over-written. Optionally, the step of determining if the stored buffer of data is over-writing a previous version of the data stored on the primary data storage system is performed by maintaining an index of the CDP backup data storage system.

[0022] Optionally, the index stores information regarding data which has been over-written.

[0023] Optionally, a determination is made as to whether the index stores data which has been overwritten, and when it has been determined that the index stores data which has been over- written, the data is transferred to the CDP backup data storage system.

[0024] Optionally, the method further includes a step of determining whether over-written data is defined by the system as being CDP-protected data and only transferring the buffer of data where the over- written data is determined to be CDP-protected data.

[0025] Optionally, during a point in time recovery flow, each entry in the CDP backup data storage component is accessed in time order and the second metadata is used to determine whether data associated with a respective entry is stored in the storage subsystem data journal component or whether data associated with the respective entry is stored in the CDP backup data storage system.

[0026] Optionally, the CDP backup data storage component stores over-written data.

[0027] Optionally, the storage subsystem data journal component stores data which has not been overwritten.

[0028] According to a second aspect, there is provided a system including means adapted for carrying out all the steps of the method.

[0029] According to a third aspect, a computer program includes instructions for carrying out all the steps of the method, when the computer program is executed on a computer system.

[0030] These and other aspects of the disclosure will be apparent from the implementation(s) described below.

[0031] BRIEF DESCRIPTION OF DRAWINGS

[0032] Implementations of the disclosure will now be described, by way of example only, with reference to the accompanying drawings, in which: FIG. 1 is a system view of operating a CDP backup data storage system for backing up data being stored to a primary data storage system in accordance with an implementation of the disclosure;

[0033] FIG. 2 is an exemplary flow diagram of storing overwritten buffers of data to a CDP journal in accordance with an implementation of the disclosure;

[0034] FIG. 3 is an exemplary flow diagram of a storing metadata to a CDP journal, when it is determined at Fig. 2 that a buffer is not overwritten, in accordance with an implementation of the disclosure;

[0035] FIG. 4 is an exemplary flow diagram of a clean-up routine of a Continuous Data Protection, CDP journal in accordance with an implementation of the disclosure;

[0036] FIG. 5 is an exemplary flow diagram of a PIT recovery operation in accordance with an implementation of the disclosure;

[0037] FIGS. 6A and 6B are flow diagrams that illustrate a method of operating a CDP backup data storage system for backing up data being stored to a primary data storage system in accordance with an implementation of the disclosure; and

[0038] FIG. 7 is an illustration of a computer system (e.g., a CDP backup data storage system) in which the various architectures and functionalities of the various previous implementations may be implemented.

[0039] DETAILED DESCRIPTION OF THE DRAWINGS

[0040] Implementations of the disclosure provide a method of operating a continuous data protection (CDP) backup data storage system for backing up data being stored to a primary data storage system, and a system adapted for carrying out the method.

[0041] To make solutions of the disclosure more comprehensible for a person skilled in the art, the following implementations of the disclosure are described with reference to the accompanying drawings.

[0042] Terms such as "a first", "a second", "a third", and "a fourth" (if any) in the summary, claims, and foregoing accompanying drawings of the disclosure are used to distinguish between similar objects and are not necessarily used to describe a specific sequence or order. It should be understood that the terms so used are interchangeable under appropriate circumstances, so that the implementations of the disclosure described herein are, for example, capable of being implemented in sequences other than the sequences illustrated or described herein. Furthermore, the terms "include" and "have" and any variations thereof, are intended to cover a non-ex elusive inclusion. For example, a process, a method, a system, a product, or a device that includes a series of steps or units, is not necessarily limited to expressly listed steps or units but may include other steps or units that are not expressly listed or that are inherent to such process, method, product, or device.

[0043] FIG. 1 is a system view 100 of operating a CDP backup data storage system 116 for backing up data being stored to a primary data storage system 102 in accordance with an implementation of the disclosure. The system view 100 includes the primary data storage system 102 and the CDP backup data storage system 116. The CDP backup data storage system 116 includes a storage subsystem data journal component 104, and a CDP data journal storage component 112. The CDP backup data storage system 116 receives a buffer of data 106A associated with a persistent data operation on the primary data storage system 102. The buffer of data 106A includes data 108A being stored by the persistent data operation, and first metadata 110 related to the primary data storage system 102. The CDP backup data storage system 116 stores the received buffer of data 106A into the storage subsystem data journal component 104. The CDP backup data storage system 116 determines if the stored buffer of data 106A is over- writing a previous version of the data stored on the primary data storage system 102. The previous version of the data being a previous state of the data 108B prior to the persistent data operation. When the CDP backup data storage system 116 determines that the stored buffer of data 106A is overwriting a previous version of the data stored on the primary data storage system 102, the CDP backup data storage system 116 transfers a buffer of data 106B associated with the previous version of the data from the storage subsystem data journal component 104 to the CDP data journal storage component 112. The buffer of data 106B associated with the previous version of the data contains the previous version of the data 108B and second metadata 114 related to the CDP backup data storage system 116. When the CDP backup data storage system 116 determines that the stored buffer of data 106A is not over-writing a previous version of the data stored on the primary data storage system 102, the CDP backup data storage system 116 transfers the second metadata 114 related to the CDP backup data storage system 116 to the CDP data journal storage component 112 without transferring the previous version of the data. Operating the CDP backup data storage system 116 includes a system including means adapted for carrying out all the above-mentioned steps.

[0044] To determine whether the stored buffer of data 106 A is overwriting a previous version of the data, in a first example embodiment, the system utilises an existing CDP Journal clean up routine of the storage subsystem data journal component 104 that, during a scheduled clean-up operation, determines which buffers of data have been overwritten.

[0045] This first embodiment is leveraging the storage subsystem’s Data Journal for the purpose of CDP. This journal persists the incoming write buffers and maintains an index for the purpose of serving future read requests.

[0046] The Data Journal flushes the written buffers at a later time, thus achieving low write latency.

[0047] Flushing of the written buffers would involve a later Journal clean-up routine.

[0048] In this first embodiment, during the clean-up routine, the overwritten buffers are copied to the external CDP journal, which might be another volume in the storage subsystem, or on a different, longer-term, storage.

[0049] Typically, in a log-structured storage system all data is logged and never written in-place. Overwritten data should still be accessible for a varying period of time, depending on the storage’s clean-up (garbage collection) routine policy and implementation.

[0050] However, logs of such systems are large and designed to withhold vast amount of data. Relying solely on this log for the purpose of CDP might be inefficient since usually it is desired to protect a smaller subset of the user’s data.

[0051] It may not be necessary to copy all the overwritten data, but only the data relevant for CDP. For example, in CDP where a filesystem is the protected object, it would typically be preferable to have a PIT recovery for specific directories set by the user or docx (or other) files.

[0052] Buffers that were not overwritten are already indexed by the CDP journal. Only the metadata

[0053] - offset and next snapshot id is written to the CDP journal. • next_snapshot_id - would be the id / name given to the next snapshot that would later be taken on the backup object. This is used to know where to read the nonoverwritten data from.

[0054] In a second example implementation, the system determines whether the stored buffer of data is overwriting a previous version of the data in a different way from the first example implementation, at the application level, as opposed to at the storage subsystem level, by maintaining an index data structure of a CDP journal by loading data from a backup object. When a write buffer is received, before sending the write buffer to the subsystem data journal component, the system writes the metadata (the offset and the snapshot identifier of where the buffer will be written on the storage subsystem data journal component) to the index data structure. The index can then be used to check whether a newly received buffer is an overwrite by checking the index data structure. If it is determined to be an overwrite, then instead of writing the new data to the storage subsystem data journal, the system reads the older version of the data and then rewrites it to the CDP data journal component. The new data is then written.

[0055] The advantages of this second embodiment versus the first embodiment are that it is less intrusive and can be deployed on different proprietary storage vendors.

[0056] The disadvantages of this second embodiment versus the embodiment are that it may be less performant.

[0057] The CDP Journal is indexed - a small in-memory table, could be a Bloomfilter, containing information per offset, specifically, whether it been written or not.

[0058] 1. When the CDP application receives a write request, the system writes merely the metadata (offset and next snapshot id) of the request to the CPD Journal.

[0059] 2. The system then checks the index of the CDP Journal for overwrites. If there were any, the system reads the data from the backup object and writes it back to the CDP Journal.

[0060] Using a Bloomfilter reduces the memory footprint for the CDP Journal index at the price of a potential false-positive (which means an extra read). Specifically, the system scans the CDP journal to determine if a previous write occurred on that same offset to determine whether this is an overwrite that triggers a corresponding data load. 3. The offset is then added to the index.

[0061] 4. The data is then written normally to the backup object.

[0062] When a snapshot is taken on the backup object, the in-memory index can be reset.

[0063] By employing such techniques, the system helps to guarantee that the CDP Journal contains all overwritten data, while the backup object contains the newest data.

[0064] By carrying out these steps, the system thereby results in enhancing an efficiency of the CDP and reducing the overhead of the CDP. The system enables redirecting of resources such as CPU, disk bandwidth, and conserved capacity for other use cases. The system eliminates redundancy and wasted resources and maintains metadata at the CDP journal. The system determines which type of data to include in the CDP journal while maintaining a consistent backup copy, thus conserving more resources. The system significantly conserves resources while maintaining the minimum necessary data for the CDP by identifying hotspots i.e. offsets or the data that have been frequently overwritten since a last snapshot is taken.

[0065] The system eliminates duplicates and stores only the most relevant data in the CDP journal for optimizing a storage utilization and reducing an overall storage requirement. The storage subsystem data journal component 104 persists incoming write buffers and, maintains an index for serving future read requests. The system eliminates the written buffers later using the CDP Journal to reduce write latency. The system is less intrusive and can be deployed on different proprietary storage vendors. The system enhances CDP applications. The system separates CDP data from backup data that can be captured through snapshots to retain the data in the CDP journal for a longer period without consuming much storage space.

[0066] FIG. 2 is an exemplary flow diagram of storing an overwritten buffer of data to the CDP journal in accordance with an implementation of the disclosure. At a step 202, a write buffer of data request is received. The write buffer of data request may be received on a CDP backup data storage system, when the data is backing up in a primary data storage system. At a step 204, metadata of the buffer, offset, and next snapshot ID of the buffer are stored in a storage subsystem data journal component. The next snapshot ID may be an identifier to the snapshot that has been taken from the backup obj ect that is utilized for determining a location from which the buffer of data may be read. At a step 206, whether the buffer of data is over-writing a previous version of the data stored on the primary data storage system is determined. If the buffer of data is over-writing the previous version of the data stored on the primary data storage system, determine whether the overwritten buffer of data is in the CDP protection, at a step 208. If the overwritten buffer of data is in the CDP protection, the overwritten buffer of data is written to the continuous data protection, CDP journal at a step 210.

[0067] Optionally, if the buffer of data is over-writing the previous version of the data stored on the primary data storage system, the CDP Journal utilizes an indexed structure that includes a compact in-memory table such as a Bloom filter that tracks a status of each offset or the buffer of data to determine whether each offset has been written or not. The Bloom filter may reduce the requirements of the memory for the CDP Journal. Optionally, the Bloom filter determine overwrites of the buffer of data by determining if the previous version of the data occurs on the same offset on the primary data storage system, which triggers a loading or writes of a corresponding data or the overwritten buffer of data to the CDP journal. Optionally, the offset can be added to an index of the buffer of data when the offset is determined for the buffer of data and writing the buffer of data to the backup obj ect using the determined offset.

[0068] Optionally, if the snapshot is taken on the backup object, the in-memory index can be reset, which enables the CDP Journal to retain all overwritten data, while the backup object contains most recent data.

[0069] FIG. 3 is an exemplary flow diagram showing the steps that are taken when a NO branch is taken at step 206 of Fig. 2 in accordance with an implementation of the disclosure. At a step 302, a write buffer of the data request is received (this is also shown at 202 of Fig. 2). At a step 304, because step 206 has determined that the buffer of data is not overwriting previous data, metadata of the buffer, offset, and next snapshot ID of the buffer are written to the CDP journal, if the buffer of data is not over- writing a previous version of the data stored on a primary data storage system. The next snapshot ID may be an identifier to the snapshot that has been taken from the backup object that is utilized for determining a location from which the nonoverwritten buffer of data may be read. At a step 306, the non-overwritten buffer of data is written and stored in a backup object if the CDP journal is not overwriting the buffer of data. At a step 308, the non-overwritten buffer of data is written and stored in a storage subsystem data journal component.

[0070] FIG. 4 is an exemplary flow diagram of a clean-up routine of a Continuous Data Protection, CDP journal in accordance with an implementation of the disclosure. At a step 402, the CDP journal clean-up request is received. At a step 404, whether a buffer is overwriting a previous version of the data stored on a primary data storage system is determined. If the buffer is overwriting the previous version of the data, the overwritten buffer is copied to the CDP journal which may be located on another volume within a storage subsystem or on a separate, longterm storage, at a step 406. The CDP journal clean-up routine may be performed periodically to maintain a CDP journal's performance and ensure that the CDP journal is not taking up unnecessary storage space.

[0071] FIG. 5 is an exemplary flow diagram of a Point in Time, PIT recovery in accordance with an implementation of the disclosure. At a step 502, the point in time, PIT recovery request is received. At a step 504, metadata or next metadata of a buffer is read from a CDP journal. At a step 506, whether the metadata is contained in the CDP journal is determined If the metadata is contained in the CDP journal, the metadata from a database of the CDP journal is read, at a step 508. If the metadata is not contained in the CDP journal, the metadata from a storage subsystem data journal component is read using a snapshot and offset, at a step 510. Optionally, the CDP journal determines where to read the data either from the database of the CDP journal or from the storage subsystem data journal component. Only the relevant data for the CDP journal may be copied. For example, in the CDP journal with a file system is a protected object, the PIT recovery is done for specific directories which may be set by a user or specified files such as docx file.

[0072] FIGS. 6A and 6B are flow diagrams that illustrate a method of operating a CDP backup data storage system for backing up data being stored to a primary data storage system in accordance with an implementation of the disclosure. At a step 602, a buffer of data associated with a persistent data operation on the primary data storage system is received at the CDP backup data storage system. The buffer includes data being stored by the persistent data operation, and first metadata related to the primary data storage system. At a step 604, the received buffer of data is stored into a storage subsystem data journal component of the CDP backup data storage system. At a step 606, whether the stored buffer of data is over-writing a previous version of the data stored on the primary data storage system is determined. The previous version being a previous state of the data prior to the persistent data operation. At a step 608, the stored buffer of data is over-writing a previous version of the data stored on the primary data storage system is determined, a buffer of data associated with the previous version of the data is then transferred from the storage subsystem data journal component to a CDP data journal storage component of the CDP backup data storage system. The buffer of data associated with the previous version of the data contains the previous version of the data and the second metadata related to the CDP backup data storage system. At a step 610, the stored received buffer of data is not over-writing a previous version of the data stored on the primary data storage system is determined, the second metadata related to the CDP backup data storage system is transferred to the CDP data journal storage component, without transferring the previous version of the data.

[0073] This method eliminates duplicates and stores only a most relevant data in the CDP journal for optimizing a storage utilization and reducing an overall storage requirement. The storage subsystem data journal component persists incoming write buffers and maintains an index for serving future read requests. This method eliminates the written buffers later using the CDP Journal to reduce write latency. This method is less intrusive and can be deployed on different proprietary storage vendors. This method enhances CDP applications. This method separates CDP data from backup data that can be captured through snapshots to retain the data in the CDP journal for a longer period, without consuming much storage space.

[0074] Optionally, the persistent operation is a write operation, a file creation operation or a file rename operation. The persistent operation could be any change made to the file system, including file copy, file deletion or attribute modification, etc.

[0075] Optionally, the second metadata includes a flag having a first value specifying that the previous version of the data is stored at the storage subsystem data journal component of the CDP backup data storage system and having a second value specifying that the previous version of the data is stored at the CDP data journal storage component of the CDP backup data storage component.

[0076] Optionally, the second metadata includes offset data specifying where data can be found in the storage subsystem data journal component of the CDP backup data storage component.

[0077] Optionally, the method is performed by a clean-up routine which identifies buffers of data in the storage subsystem data journal that have been over- written.

[0078] Optionally, the method is performed by maintaining an index of the CDP backup data storage component.

[0079] Optionally, the index stores information regarding data which has been over-written. Optionally, a determination is made as to whether the index stores data which has been overwritten, and when it has been determined that the index stores data which has been over- written, the data is transferred to the CDP backup data storage component.

[0080] Optionally, the method further includes a step of determining whether over-written data is defined by the system as being CDP-protected data and only proceeding to step (d) where the over-written data is determined to be CDP-protected data.

[0081] Optionally, during a point in time recovery flow, each entry in the CDP backup data storage component is accessed in time order and the second metadata is used to determine whether data associated with a respective entry is stored in the storage subsystem data journal component or whether data associated with the respective entry is stored in the CDP backup data storage component.

[0082] Optionally, the CDP backup data storage component stores over-written data.

[0083] Optionally, the storage subsystem data journal component stores data which has not been overwritten.

[0084] Optionally, a computer program including instructions for carrying out all the steps of the method, when the computer program is executed on a computer system.

[0085] FIG. 7 is an illustration of a computer system (e.g. a CDP backup data storage system) in which the various architectures and functionalities of the various previous implementations may be implemented. As shown, the computer system 700 includes at least one processor 704 that is connected to a bus 702, wherein the computer system 700 may be implemented using any suitable protocol, such as PCI (Peripheral Component Interconnect), PCI-Express, AGP (Accelerated Graphics Port), Hyper Transport, or any other bus or point-to-point communication protocol (s). The computer system 700 also includes a memory 706.

[0086] Control logic (software) and data are stored in the memory 706 which may take a form of random-access memory (RAM). In the disclosure, a single semiconductor platform may refer to a sole unitary semiconductor-based integrated circuit or chip. It should be noted that the term single semiconductor platform may also refer to multi-chip modules with increased connectivity which simulate on-chip modules with increased connectivity which simulate on- chip operation, and make substantial improvements over utilizing a conventional central processing unit (CPU) and bus implementation. Of course, the various modules may also be situated separately or in various combinations of semiconductor platforms per the desires of the user.

[0087] The computer system 700 may also include a secondary storage 710. The secondary storage 710 includes, for example, a hard disk drive and a removable storage drive, representing a floppy disk drive, a magnetic tape drive, a compact disk drive, digital versatile disk (DVD) drive, recording device, universal serial bus (USB) flash memory. The removable storage drive at least one of reads from and writes to a removable storage unit in a well-known manner.

[0088] Computer programs, or computer control logic algorithms, may be stored in at least one of the memory 706 and the secondary storage 710. Such computer programs, when executed, enable the computer system 700 to perform various functions as described in the foregoing. The memory 706, the secondary storage 710, and any other storage are possible examples of computer-readable media.

[0089] In an implementation, the architectures and functionalities depicted in the various previous figures may be implemented in the context of the processor 704, a graphics processor coupled to a communication interface 712, an integrated circuit (not shown) that is capable of at least a portion of the capabilities of both the processor 704 and a graphics processor, a chipset (namely, a group of integrated circuits designed to work and sold as a unit for performing related functions, and so forth).

[0090] Furthermore, the architectures and functionalities depicted in the various previous-described figures may be implemented in a context of a general computer system, a circuit board system, a game console system dedicated for entertainment purposes, an application-specific system. For example, the computer system 700 may take the form of a desktop computer, a laptop computer, a server, a workstation, a game console, an embedded system.

[0091] Furthermore, the computer system 700 may take the form of various other devices including, but not limited to a personal digital assistant (PDA) device, a mobile phone device, a smart phone, a television, and so forth. Additionally, although not shown, the computer system 700 may be coupled to a network (for example, a telecommunications network, a local area network (LAN), a wireless network, a wide area network (WAN) such as the Internet, a peer-to-peer network, a cable network, or the like) for communication purposes through an VO interface 708. It should be understood that the arrangement of components illustrated in the figures described are exemplary and that other arrangement may be possible. It should also be understood that the various system components (and means) defined by the claims, described below, and illustrated in the various block diagrams represent components in some systems configured according to the subject matter disclosed herein. For example, one or more of these system components (and means) may be realized, in whole or in part, by at least some of the components illustrated in the arrangements illustrated in the described figures.

[0092] In addition, while at least one of these components are implemented at least partially as an electronic hardware component, and therefore constitutes a machine, the other components may be implemented in software that when included in an execution environment constitutes a machine, hardware, or a combination of software and hardware.

[0093] Although the disclosure and its advantages have been described in detail, it should be understood that various changes, substitutions, and alterations can be made herein without departing from the spirit and scope of the disclosure as defined by the appended claims.

Claims

CLAIMS1. A method of operating a Continuous Data Protection, CDP, backup data storage system (116) for backing up data being stored to a primary data storage system (102), comprising the steps of:(a) receiving, at the CDP backup data storage system (116), a buffer of data (106A) associated with a persistent data operation on the primary data storage system (102), the buffer of data (106A) containing data (108A) being stored by the persistent data operation, and first metadata (110) related to the primary data storage system (102);(b) storing the received buffer of data (106 A) into a storage subsystem data journal component (104) of the CDP backup data storage system (116);(c) determining if the stored buffer of data (106 A) is over- writing a previous version of the data stored on the primary data storage system (102), the previous version being a previous state of the data (108B) prior to the persistent data operation;(d) where it is determined that the stored buffer of data (106 A) is over- writing a previous version of the data stored on the primary data storage system (102), transfer the buffer of data (106B) associated with the previous version of the data from the storage subsystem data journal component (104) to a CDP data journal storage component (112) of the CDP backup data storage system (116), wherein the buffer of data (106B) associated with the previous version of the data contains the previous version of the data (108B) and second metadata (114) related to the CDP backup data storage system (116); and(e) where it is determined that the stored received buffer of data (106 A) is not overwriting a previous version of the data stored on the primary data storage system (102), transfer, to the CDP data journal storage component (112), the second metadata (114) related to the CDP backup data storage system (116) without transferring the previous version of the data.

2. The method of claim 1 wherein the persistent operation is a write operation, a fde creation operation or a file rename operation.

3. The method of claim 1 wherein the second metadata (114) includes a flag having a first value specifying that the previous version of the data is stored at the storage subsystemdata journal component (104) of the CDP backup data storage system (116) and having a second value specifying that the previous version of the data is stored at the CDP data journal storage component (112) of the CDP backup data storage system (116).

4. The method of claim 1 wherein the second metadata (114) includes offset data specifying where data can be found in the storage subsystem data journal component (104) of the CDP backup data storage system (116).

5. The method of claim 1 wherein the step (c) is performed by a clean-up routine which identifies buffer of data 106A in the storage subsystem data journal component (104) that have been over- written.

6. The method of claim 1 wherein the step (c) is performed by maintaining an index of the CDP backup data storage system (116).

7. The method of claim 6 wherein the index stores information regarding data which has been over-written.

8. The method of claim 7 wherein a determination is made as to whether the index stores data which has been over-written, and when it has been determined that the index stores data which has been over-written, the data is transferred to the CDP backup data storage system (116).

9. The method of claim 1 further including the step of determining whether over- written data is defined by the system as being CDP-protected data and only proceeding to step (d) where the over-written data is determined to be CDP-protected data.

10. The method of claim 1 wherein, during a point in time recovery flow, each entry in the CDP backup data storage system (116) is accessed in time order and the second metadata is used to determine whether data associated with a respective entry is stored in the storage subsystem data journal component (104) or whether data associated with the respective entry is stored in the CDP backup data storage system (116).

11. The method of claim 1 wherein the CDP backup data storage system (116) stores overwritten data.

12. The method of claim 1 wherein the storage subsystem data journal component (104) stores data which has not been over-written.

13. A system comprising means adapted for carrying out all the steps of the method according to any preceding method claim.

14. A computer program comprising instructions for carrying out all the steps of the method according to any preceding method claim, when said computer program is executed on a computer system.

Citation Information

Patent Citations

  • A method for implementing continuous data protection utilizing allocate-on-write snapshots

    EP2290544A1

  • Systems and methods for continuous data protection

    US20200349030A1

  • Updating snapshots

    US7587431B1

  • Snapshots in de-duplication

    US8712962B1