In one aspect, a method to recover data includes annotating metadata entries in a journal to indicate changes by an application to an object stored in a continuous data protection environment. Each entry of the metadata corresponds to one of a unique group of DO stream data blocks or a unique group of undo stream data blocks. The method also includes determining a version of the object that meets criteria by searching the annotated entries and obtaining the version of the object that meets the criteria.
In another aspect, a method to recover data includes receiving criteria to recover an object, determining a version of the object that meets the criteria by searching point-in-time images using a DO stream and an undo stream and obtaining the version of the object that meets the criteria.
|
18. A method to recover data, comprising:
using a journal to record changes in date, the journal comprising:
a DO stream comprising new data for a write transaction in a logical unit;
a DO metadata stream comprising metadata for the write transaction, the metadata comprising a pointer to the offset in the DO stream data blocks where the new data is located;
an undo stream comprising old data overwritten in the logical unit; and
an undo metadata comprising a pointer to the offset in the undo stream data blocks where the old data is located;
receiving criteria to recover an object;
determining a version of the object that meets the criteria by searching point-in-time images using the DO stream and the undo stream; and
obtaining the version of the object that meets the criteria.
1. A method to recover data, comprising:
determining appropriate annotations to be recorded in metadata entries in a journal comprising:
a DO stream comprising new data for a write transaction in a logical unit;
a DO metadata stream comprising metadata for the write transaction, the metadata comprising a pointer to the offset in the DO stream data blocks where the new data is located;
an undo stream comprising old data overwritten in the logical unit; and
an undo metadata comprising a pointer to the offset in the undo stream data blocks where the old data is located;
annotating the metadata entries in the journal to indicate changes by an application to an object stored in a continuous data protection environment, each entry of the metadata corresponding to one of a unique group of data blocks in the DO stream or a unique group of data blocks in the undo stream;
determining a version of the object that meets criteria by searching the annotated entries; and
obtaining the version of the object that meets the criteria.
13. An apparatus to recover data, comprising:
circuitry to:
annotate metadata entries in a journal to indicate changes by an application to an object stored in a continuous data protection environment, the journal comprising a DO stream data blocks comprising new data for a write transaction in a logical unit, a DO metadata stream comprising metadata for the write transaction, the metadata comprising a pointer to the offset in the DO stream data blocks where the new data is located, an undo stream data blocks comprising old data overwritten in the logical unit and an undo metadata comprising a pointer to the offset in the undo stream data blocks where the old data is located, each entry of the metadata corresponding to one of a unique group of data blocks in the DO stream or a unique group of data blocks in the undo stream;
determine a version of the object that meets criteria by searching the annotated entries; and
obtain the version of the object that meets the criteria,
wherein the circuitry further comprises at least one of a processor, a memory, programmable logic and logic gates.
2. The method of
wherein determining a version of the object comprises using a search engine associated with the application to search the DO metadata stream and the undo metadata stream for changes in the object.
3. The method of
wherein determining a version of the object comprises searching a table associated with one of the DO metadata stream or the undo metadata stream.
4. The method of
5. The method of
determining a group of candidate objects; and
testing the group of candidate objects until the version of the object meeting the criteria is determined.
6. The method of
7. The method of
8. The method of
9. The method of
10. The method of
11. The method of
12. The method of
14. The apparatus of
wherein circuitry to determine a version of the object comprises circuitry to use a search engine associated with the application to search the DO metadata stream and the undo metadata stream for changes in the object.
15. The apparatus of
wherein circuitry to determine a version of the object comprises circuitry to search a table associated with one of the DO metadata stream or the undo metadata stream.
16. The apparatus of
17. The apparatus of
determine a group of candidate objects; and
test the group of candidate objects until the version of the object meeting the criteria is determined.
19. The method of
20. The method of
determining a group of candidate objects; and
testing the group of candidate objects until the version of the object meeting the criteria is determined.
|
|||||||||||||||||||||||||
Computer data is vital to today's organizations, and a significant part of protection against disasters is focused on data protection. As solid-state memory has advanced to the point where cost of memory has become a relatively insignificant factor, organizations can afford to operate with systems that store and process terabytes of data.
Conventional data protection systems include tape backup drives, for storing organizational production site data on a periodic basis. Such systems suffer from several drawbacks. First, they require a system shutdown during backup, since the data being backed up cannot be used during the backup operation. Second, they limit the points in time to which the production site can recover. For example, if data is backed up on a daily basis, there may be several hours of lost data in the event of a disaster. Third, the data recovery process itself takes a long time.
Another conventional data protection system uses data replication, by creating a copy of the organization's production site data on a secondary backup storage system, and updating the backup with changes. The backup storage system may be situated in the same physical location as the production storage system, or in a physically remote location. Data replication systems generally operate either at the application level, at the file system level, or at the data block level.
Current data protection systems try to provide continuous data protection, which enable the organization to roll back to any specified point in time within a recent history. Continuous data protection systems aim to satisfy two conflicting objectives, as best as possible; namely, (i) minimize the down time, in which the organization production site data is unavailable, during a recovery, and (ii) enable recovery as close as possible to any specified point in time within a recent history.
Continuous data protection typically uses a technology referred to as “journaling,” whereby a log is kept of changes made to the backup storage. During a recovery, the journal entries serve as successive “undo” information, enabling rollback of the backup storage to previous points in time. Journaling was first implemented in database systems, and was later extended to broader data protection.
One challenge to continuous data protection is the ability of a backup site to keep pace with the data transactions of a production site, without slowing down the production site. The overhead of journaling inherently requires several data transactions at the backup site for each data transaction at the production site. As such, when data transactions occur at a high rate at the production site, the backup site may not be able to finish backing up one data transaction before the next production site data transaction occurs. If the production site is not forced to slow down, then necessarily a backlog of un-logged data transactions may build up at the backup site. Without being able to satisfactorily adapt dynamically to changing data transaction rates, a continuous data protection system chokes and eventually forces the production site to shut down.
In one aspect, a method to recover data includes annotating metadata entries in a journal to indicate changes by an application to an object stored in a continuous data protection environment. Each entry of the metadata corresponds to one of a unique group of DO stream data blocks or a unique group of UNDO stream data blocks. The method also includes determining a version of the object that meets criteria by searching the annotated entries and obtaining the version of the object that meets the criteria.
In another aspect, an apparatus to recover data includes circuitry to annotate metadata entries in a journal to indicate changes by an application to an object stored in a continuous data protection environment. Each entry of the metadata corresponds to one of a unique group of DO stream data blocks or a unique group of UNDO stream data blocks. The apparatus also includes circuitry to determine a version of the object that meets criteria by searching the annotated entries and to obtain the version of the object that meets the criteria.
In a further aspect, a method to recover data includes receiving criteria to recover an object, determining a version of the object that meets the criteria by searching point-in-time images using a DO stream and an UNDO stream and obtaining the version of the object that meets the criteria.
The present invention will be more fully understood and appreciated from the following detailed description, taken in conjunction with the drawings.
The following definitions are employed throughout the specification and claims.
BACKUP SITE—a facility where replicated production site data is stored; the backup site may be located in a remote site or at the same location as the production site;
DPA—a computer or a cluster of computers that serve as a data protection appliance, responsible for data protection services including inter alia data replication of a storage system, and journaling of I/O requests issued by a host computer to the storage system;
HOST—at least one computer or networks of computers that runs at least one data processing application that issues I/O requests to one or more storage systems; a host is an initiator with a SAN;
HOST DEVICE—an internal interface in a host, to a logical storage unit;
IMAGE—a copy of a logical storage unit at a specific point in time;
INITIATOR—a node in a SAN that issues I/O requests;
JOURNAL—a record of write transactions issued to a storage system; used to maintain a duplicate storage system, and to rollback the duplicate storage system to a previous point in time;
LOGICAL UNIT—a logical entity provided by a storage system for accessing data from the storage system;
LUN—a logical unit number for identifying a logical unit;
PHYSICAL STORAGE UNIT—a physical entity, such as a disk or an array of disks, for storing data in storage locations that can be accessed by address;
PRODUCTION SITE—a facility where one or more host computers run data processing applications that write data to a storage system and read data from the storage system;
SAN—a storage area network of nodes that send and receive I/O and other requests, each node in the network being an initiator or a target, or both an initiator and a target;
SOURCE SIDE—a transmitter of data within a data replication workflow, during normal operation a production site is the source side; and during data recovery a backup site is the source side;
STORAGE SYSTEM—a SAN entity that provides multiple logical units for access by multiple SAN initiators
TARGET—a node in a SAN that replies to I/O requests;
TARGET SIDE—a receiver of data within a data replication workflow; during normal operation a back site is the target side, and during data recovery a production site is the target side;
WAN—a wide area network that connects local networks and enables them to communicate with one another, such as the Internet.
Reference is now made to
During normal operations, the direction of replicate data flow goes from source side to target side. It is possible, however, for a user to reverse the direction of replicate data flow, in which case Site I starts to behave as a target backup site, and Site II starts to behave as a source production site. Such change of replication direction is referred to as a “failover”. A failover may be performed in the event of a disaster at the production site, or for other reasons. In some data architectures, Site I or Site II behaves as a production site for a portion of stored data, and behaves simultaneously as a backup site for another portion of stored data. In some data architectures, a portion of stored data is replicated to a backup site, and another portion is not.
The production site and the backup site may be remote from one another, or they may both be situated at a common site, local to one another. Local data protection has the advantage of minimizing data lag between target and source, and remote data protection has the advantage is being robust in the event that a disaster occurs at the source side.
The source and target sides communicate via a wide area network (WAN) 128, although other types of networks are also adaptable for use with the present invention.
In accordance with an embodiment of the present invention, each side of system 100 includes three major components coupled via a storage area network (SAN); namely, (i) a storage system, (ii) a host computer, and (iii) a data protection appliance (DPA). Specifically with reference to
Generally, a SAN includes one or more devices, referred to as “nodes”. A node in a SAN may be an “initiator” or a “target”, or both. An initiator node is a device that is able to initiate requests to one or more other devices; and a target node is a device that is able to reply to requests, such as SCSI commands, sent by an initiator node. A SAN may also include network switches, such as fiber channel switches. The communication links between each host computer and its corresponding storage system may be any appropriate medium suitable for data transfer, such as fiber communication channel links.
In an embodiment of the present invention, the host communicates with its corresponding storage system using small computer system interface (SCSI) commands.
System 100 includes source storage system 108 and target storage system 120. Each storage system includes physical storage units for storing data, such as disks or arrays of disks. Typically, storage systems 108 and 120 are target nodes. In order to enable initiators to send requests to storage system 108, storage system 108 exposes one or more logical units (LU) to which commands are issued. Thus, storage systems 108 and 120 are SAN entities that provide multiple logical units for access by multiple SAN initiators.
Logical units are a logical entity provided by a storage system, for accessing data stored in the storage system. A logical unit is identified by a unique logical unit number (LUN). In an embodiment of the present invention, storage system 108 exposes a logical unit 136, designated as LU A, and storage system 120 exposes a logical unit 156, designated as LU B.
In an embodiment of the present invention, LU B is used for replicating LU A. As such, LU B is generated as a copy of LU A. In one embodiment, LU B is configured so that its size is identical to the size of LU A. Thus for LU A, storage system 120 serves as a backup for source side storage system 108. Alternatively, as mentioned hereinabove, some logical units of storage system 120 may be used to back up logical units of storage system 108, and other logical units of storage system 120 may be used for other purposes. Moreover, in certain embodiments of the present invention, there is symmetric replication whereby some logical units of storage system 108 are used for replicating logical units of storage system 120, and other logical units of storage system 120 are used for replicating other logical units of storage system 108.
System 100 includes a source side host computer 104 and a target side host computer 116. A host computer may be one computer, or a plurality of computers, or a network of distributed computers, each computer may include inter alia a conventional CPU, volatile and non-volatile memory, a data bus, an I/O interface, a display interface and a network interface. Generally a host computer runs at least one data processing application, such as a database application and an e-mail server.
Generally, an operating system of a host computer creates a host device for each logical unit exposed by a storage system in the host computer SAN. A host device is a logical entity in a host computer, through which a host computer may access a logical unit. In an embodiment of the present invention, host device 104 identifies LU A and generates a corresponding host device 140, designated as Device A, through which it can access LU A. Similarly, host computer 116 identifies LU B and generates a corresponding device 160, designated as Device B.
In an embodiment of the present invention, in the course of continuous operation, host computer 104 is a SAN initiator that issues I/O requests (write/read operations) through host device 140 to LU A using, for example, SCSI commands. Such requests are generally transmitted to LU A with an address that includes a specific device identifier, an offset within the device, and a data size. Offsets are generally aligned to 512 byte blocks. The average size of a write operation issued by host computer 104 may be, for example, 10 kilobytes (KB); i.e., 20 blocks. For an I/O rate of 50 megabytes (MB) per second, this corresponds to approximately 5,000 write transactions per second.
System 100 includes two data protection appliances, a source side DPA 112 and a target side DPA 124. A DPA performs various data protection services, such as data replication of a storage system, and journaling of I/O requests issued by a host computer to source side storage system data. As explained in detail hereinbelow, when acting as a target side DPA, a DPA may also enable rollback of data to an earlier point in time, and processing of rolled back data at the target site. Each DPA 112 and 124 is a computer that includes inter alia one or more conventional CPUs and internal memory.
For additional safety precaution, each DPA is a cluster of such computers. Use of a cluster ensures that if a DPA computer is down, then the DPA functionality switches over to another computer. The DPA computers within a DPA cluster communicate with one another using at least one communication link suitable for data transfer via fiber channel or IP based protocols, or such other transfer protocol. One computer from the DPA cluster serves as the DPA leader. The DPA cluster leader coordinates between the computers in the cluster, and may also perform other tasks that require coordination between the computers, such as load balancing.
In the architecture illustrated in
In accordance with an embodiment of the present invention, DPAs 112 and 124 are configured to act as initiators in the SAN; i.e., they can issue I/O requests using, for example, SCSI commands, to access logical units on their respective storage systems. DPA 112 and DPA 124 are also configured with the necessary functionality to act as targets; i.e., to reply to I/O requests, such as SCSI commands, issued by other initiators in the SAN, including inter alia their respective host computers 104 and 116. Being target nodes, DPA 112 and DPA 124 may dynamically expose or remove one or more logical units.
As described hereinabove, Site I and Site II may each behave simultaneously as a production site and a backup site for different logical units. As such, DPA 112 and DPA 124 may each behave as a source DPA for some logical units, and as a target DPA for other logical units, at the same time.
In accordance with an embodiment of the present invention, host computer 104 and host computer 116 include protection agents 144 and 164, respectively. Protection agents 144 and 164 intercept SCSI commands issued by their respective host computers, via host devices to logical units that are accessible to the host computers. In accordance with an embodiment of the present invention, a data protection agent may act on an intercepted SCSI commands issued to a logical unit, in one of the following ways:
Send the SCSI commands to its intended logical unit.
Redirect the SCSI command to another logical unit.
Split the SCSI command by sending it first to the respective DPA. After the DPA returns an acknowledgement, send the SCSI command to its intended logical unit.
Fail a SCSI command by returning an error return code.
Delay a SCSI command by not returning an acknowledgement to the respective host computer.
A protection agent may handle different SCSI commands, differently, according to the type of the command. For example, a SCSI command inquiring about the size of a certain logical unit may be sent directly to that logical unit, while a SCSI write command may be split and sent first to a DPA associated with the agent. A protection agent may also change its behavior for handling SCSI commands, for example as a result of an instruction received from the DPA.
Specifically, the behavior of a protection agent for a certain host device generally corresponds to the behavior of its associated DPA with respect to the logical unit of the host device. When a DPA behaves as a source site DPA for a certain logical unit, then during normal course of operation, the associated protection agent splits I/O requests issued by a host computer to the host device corresponding to that logical unit. Similarly, when a DPA behaves as a target device for a certain logical unit, then during normal course of operation, the associated protection agent fails I/O requests issued by host computer to the host device corresponding to that logical unit.
Communication between protection agents and their respective DPAs may use any protocol suitable for data transfer within a SAN, such as fiber channel, or SCSI over fiber channel. The communication may be direct, or via a logical unit exposed by the DPA. In an embodiment of the present invention, protection agents communicate with their respective DPAs by sending SCSI commands over fiber channel.
In an embodiment of the present invention, protection agents 144 and 164 are drivers located in their respective host computers 104 and 116. Alternatively, a protection agent may also be located in a fiber channel switch, or in any other device situated in a data path between a host computer and a storage system.
What follows is a detailed description of system behavior under normal production mode, and under recovery mode.
In accordance with an embodiment of the present invention, in production mode DPA 112 acts as a source site DPA for LU A. Thus, protection agent 144 is configured to act as a source side protection agent; i.e., as a splitter for host device A. Specifically, protection agent 144 replicates SCSI I/O requests. A replicated SCSI I/O request is sent to DPA 112. After receiving an acknowledgement from DPA 124, protection agent 144 then sends the SCSI I/O request to LU A. Only after receiving a second acknowledgement from storage system 108 will host computer 104 initiate another I/O request.
When DPA 112 receives a replicated SCSI write request from data protection agent 144, DPA 112 transmits certain I/O information characterizing the write request, packaged as a “write transaction”, over WAN 128 to DPA 124 on the target side, for journaling and for incorporation within target storage system 120.
DPA 112 may send its write transactions to DPA 124 using a variety of modes of transmission, including inter alia (i) a synchronous mode, (ii) an asynchronous mode, and (iii) a snapshot mode. In synchronous mode, DPA 112 sends each write transaction to DPA 124, receives back an acknowledgement from DPA 124, and in turns sends an acknowledgement back to protection agent 144. Protection agent 144 waits until receipt of such acknowledgement before sending the SCSI write request to LU A.
In asynchronous mode, DPA 112 sends an acknowledgement to protection agent 144 upon receipt of each I/O request, before receiving an acknowledgement back from DPA 124.
In snapshot mode, DPA 112 receives several I/O requests and combines them into an aggregate “snapshot” of all write activity performed in the multiple I/O requests, and sends the snapshot to DPA 124, for journaling and for incorporation in target storage system 120. In snapshot mode DPA 112 also sends an acknowledgement to protection agent 144 upon receipt of each I/O request, before receiving an acknowledgement back from DPA 124.
For the sake of clarity, the ensuing discussion assumes that information is transmitted at write-by-write granularity.
While in production mode, DPA 124 receives replicated data of LU A from DPA 112, and performs journaling and writing to storage system 120. When applying write operations to storage system 120, DPA 124 acts as an initiator, and sends SCSI commands to LU B.
During a recovery mode, DPA 124 undoes the write transactions in the journal, so as to restore storage system 120 to the state it was at, at an earlier time.
As described hereinabove, in accordance with an embodiment of the present invention, LU B is used as a backup of LU A. As such, during normal production mode, while data written to LU A by host computer 104 is replicated from LU A to LU B, host computer 116 should not be sending I/O requests to LU B. To prevent such I/O requests from being sent, protection agent 164 acts as a target site protection agent for host Device B and fails I/O requests sent from host computer 116 to LU B through host Device B.
In accordance with an embodiment of the present invention, target storage system 120 exposes a logical unit 176, referred to as a “journal LU”, for maintaining a history of write transactions made to LU B, referred to as a “journal”. Alternatively, journal LU 176 may be striped over several logical units, or may reside within all of or a portion of another logical unit. DPA 124 includes a journal processor 180 for managing the journal.
Journal processor 180 functions generally to manage the journal entries of LU B. Specifically, journal processor 180 (i) enters write transactions received by DPA 124 from DPA 112 into the journal, by writing them into the journal LU, (ii) applies the journal transactions to LU B, and (iii) updates the journal entries in the journal LU with undo information and removes already-applied transactions from the journal. As described below, with reference to FIGS. 2 and 3A-3D, journal entries include four streams, two of which are written when write transaction are entered into the journal, and two of which are written when write transaction are applied and removed from the journal.
Reference is now made to
Write transaction 200 generally includes the following fields:
one or more identifiers;
a time stamp, which is the date & time at which the transaction was received by source side DPA 112;
a write size, which is the size of the data block;
a location in journal LU 176 where the data is entered;
a location in LU B where the data is to be written; and
the data itself.
Write transaction 200 is transmitted from source side DPA 112 to target side DPA 124. As shown in
In practice each of the four streams holds a plurality of write transaction data. As write transactions are received dynamically by target DPA 124, they are recorded at the end of the DO stream and the end of the DO METADATA stream, prior to committing the transaction. During transaction application, when the various write transactions are applied to LU B, prior to writing the new DO data into addresses within the storage system, the older data currently located in such addresses is recorded into the UNDO stream.
By recording old data, a journal entry can be used to “undo” a write transaction. To undo a transaction, old data is read from the UNDO stream in a reverse order, from the most recent data to the oldest data, for writing into addresses within LU B. Prior to writing the UNDO data into these addresses, the newer data residing in such addresses is recorded in the DO stream.
The journal LU is partitioned into segments with a pre-defined size, such as 1 MB segments, with each segment identified by a counter. The collection of such segments forms a segment pool for the four journaling streams described hereinabove. Each such stream is structured as an ordered list of segments, into which the stream data is written, and includes two pointers—a beginning pointer that points to the first segment in the list and an end pointer that points to the last segment in the list.
According to a write direction for each stream, write transaction data is appended to the stream either at the end, for a forward direction, or at the beginning, for a backward direction. As each write transaction is received by DPA 124, its size is checked to determine if it can fit within available segments. If not, then one or more segments are chosen from the segment pool and appended to the stream's ordered list of segments.
Thereafter the DO data is written into the DO stream, and the pointer to the appropriate first or last segment is updated. Freeing of segments in the ordered list is performed by simply changing the beginning or the end pointer. Freed segments are returned to the segment pool for re-use.
When a write transaction is received, journaling is thus advanced as indicated in TABLE I below.
TABLE I
Entering a write transaction in the journal
Step 1
The new data is written at the end of the DO stream, assuming a
forward write direction, and corresponding metadata is written at
the end of the DO METADATA stream.
Step 2
Data is read from the beginning of the DO stream, and
corresponding metadata is read from the beginning of the DO
METADATA stream.
Step 3
Old data to be overwritten is read from LU B. The location and
size of such old data is determined from the DO METADATA
stream.
Step 4
The old data is written at the end of the UNDO stream, and
corresponding metadata is written at the end of the UNDO
METADATA stream.
Step 5
The new data read at Step 2 is written into LU B, and the
beginning and end pointers of the DO and DO METADATA
streams are moved appropriately.
Conversely, during a rollback to undo a write transaction, the above operations are reversed, as indicated in TABLE II below.
TABLE II
Undoing a write transaction in the journal
Step 1
Read the data and metadata from the end of the UNDO and UNDO
METADATA streams.
Step 2
Read from LU B the data that is to be overwritten. The location
and size of such data is determined from the UNDO METADATA
stream.
Step 3
Write the data from Step 2 at the beginning of the DO stream, and
update the DO METADATA stream accordingly.
Step 4
Write the data from Step 1 to LU B, and update the beginning and
end pointers of the UNDO and UNDO metadata streams
appropriately.
The following example, in conjunction with
Three write transactions are received, as indicated in TABLE III.
TABLE III
Example Write Transactions
Write
LU B
ID
Time
location
Length
Journal LU location
1
Dec. 3, 2005
LU B
15 blocks
Segment 1,
10:00:00.00
offset 57 blocks
offset 0
2
Dec. 3, 2005
LU B
20 blocks
Segment 1,
10:00:00.05
offset 87 blocks
offset 15
3
Dec. 3, 2005
LU B
20 blocks
Segment 3,
10:00:00.18
offset 12 blocks
Offset 15
The following discussion describes four stages of journaling and data storage; namely,
Stage #1: Enter the three write transactions as journal entries in the journal LU.
Stage #2: Apply the first write transaction to LU B.
Stage #3: Apply the second write transaction to LU B.
Stage #4: Rollback the second write transaction, to recover data from an earlier point in time.
The write transaction with ID=1 is written to the first 15 blocks of Segment #1. The metadata corresponding to this transaction is written to the first block of Segment #2. The second write transaction with ID=2 is written to the last 5 blocks of Segment #1 and the first 15 blocks of Segment #3. The metadata corresponding to this transaction is written to the second block of Segment #2. The third write transaction with ID=3 is written to the last 5 blocks of Segment #3 and the first 15 blocks of Segment #4. The metadata corresponding to this transaction is written to the third block of Segment #2.
Thus at stage #1, the DO stream in memory includes a list of segments 1, 3, 4; and a beginning pointer to offset=0 in Segment #1 and an end pointer to offset=10 in Segment #4. The DO METADATA stream in memory includes a list of one segment, namely Segment #2; and a beginning pointer to offset=0 in Segment #2 and an end pointer to offset=3 in Segment #2. The UNDO stream and the UNDO METADATA stream are empty. The journal and the four streams at the end of stage #1 are illustrated in
At stage #2 the write transaction with ID=1 is applied to LU B. New data to be written is read from the journal LU at the offset and length indicated in the DO METADATA; namely, 15 blocks of data located in blocks 0-14 of journal volume Segment #1. Correspondingly, old data is read from LU B at the offset and length indicated in the UNDO METADATA; namely, 15 blocks of data located in blocks 57-71 of LU B. The old data is then written into the UNDO stream in the journal LU, and the associated metadata is written into the UNDO METADATA stream in the journal LU. Specifically, for this example, the UNDO data is written into the first 15 blocks of Segment #5, and the UNDO METADATA is written into the first block of Segment #6. The beginning pointer of the UNDO data stream is set to offset=0 in Segment #5, and the end pointer is set to offset=15 in Segment #5. Similarly, the beginning pointer of the UNDO METADATA stream is set to offset=0 on Segment #6, and the end pointer is set to offset=1 in Segment #6.
At this point, the new data that was read from blocks 0-14 of journal LU Segment #1 is written to blocks 57-71 of LU B. The beginning pointer for the DO stream is moved forward to block 15 of journal LU Segment #1, and the beginning pointer for the DO METADATA stream is moved forward to block 1 of journal LU Segment #2. The journal and the four streams at the end of stage #2 are illustrated in
At stage #3 the write transaction with ID=2 is applied to the storage system. As above, 20 blocks of new data are read from blocks 15-19 of journal LU Segment #1 and from blocks 0-14 of journal LU Segment #3. Similarly, 20 blocks of old data are read from blocks 87-106 of LU B. The old data is written to the UNDO stream in the last 5 blocks of journal LU Segment #5 and the first 15 blocks of journal LU Segment #7. The associated metadata is written to the UNDO METADATA stream in the second block of Segment #6. The list of segments in the UNDO stream includes Segment #5 and Segment #7. The end pointer of the UNDO stream is moved to block 15 of Segment #7, and the end pointed of the UNDO METADATA stream is moved to block 2 of Segment #6.
Finally, the new data from blocks 15-19 of journal LU Segment #1 and blocks 0-14 of journal LU Segment #3 is written into blocks 87-106 of LU B. The beginning pointer for the DO stream is moved forward to block 15 of journal volume Segment #3, and the beginning pointer for the DO METADATA stream is moved forward to block 2 of journal LU Segment #2. Segment #1 is freed from the DO stream, for recycling within the segment pool, and the list of segments for the DO stream is changed to Segment #3 and Segment #4. The journal and the four streams at the end of stage #3 are illustrated in
At stage #4 a rollback to time 10:00:00.00 is performed. Since the write transaction with ID=3 was not applied yet, the only write transaction to be undone is the write transaction with ID=2. The last entry is read from the UNDO METADATA stream, the location of the end of the UNDO METADATA stream being determined by its end pointer, i.e., the metadata before block 2 of journal LU Segment #6 is read, indicating two areas each of 20 blocks; namely, (a) the last 5 blocks of journal LU Segment #5 and the first 15 blocks of journal LU Segment #7, and (b) blocks 87-106 of LU B. Area (a) is part of the UNDO stream.
The 20 blocks of data from area (b) are read from LU B and written to the beginning of the DO stream. As the beginning pointer of the DO stream is set to offset=15 of journal LU Segment #3, 5 blocks are written at the end of Segment #3, and the remaining 15 blocks are written to Segment #8. The end pointer for the DO stream is set to block 15 of Segment #8. The list of segments for the DO stream is changed to Segment #3, Segment #4 and Segment #8. The metadata associated with the 20 blocks from area (b) is written to block 3 of Segment #2, and the end pointer of the DO METADATA stream is advanced to block 4 of Segment #2.
The 20 blocks of data in area (a) of the journal LU are then written to area (b) of the LU B. Finally, Segment #7 is freed for recycling in the segment pool, the UNDO stream ending pointer is moved back to Segment #5 of the journal LU, block 15, and the UNDO METADATA stream ending pointed is moved back to Segment #6 of the journal LU, block 1. The journal and the four streams at the end of stage #4 are illustrated in
Thus it may be appreciated that the journal is thus used to rollback LU B to the state that it was in at a previous point in time. The journal is also used to selectively access data from LU B at such previous point in time, without necessarily performing a rollback. Selective access is useful for correcting one or more files that are currently corrupt, or for simply accessing old data.
TABLE IV below summarizes the behavior of the special protection components of system 100 during production mode. Reference is also made to
TABLE IV
Normal Production Mode Functionality
System
Component
Behavior
Source Side
Intercept SCSI commands issued to LU A by
Agent 144
source side host via Device A (step 404). Replicate write
commands, and route write commands to DPA (steps 408
and 412). Wait for first acknowledgement, from DPA
(step 416), and then route replicate I/O command to LU A
(step 420). Wait for second acknowledgement, from
storage system (step 424), and then process next
intercepted SCSI command (step 404).
Source Side
Receive write command from agent (step 428).
DPA 112
Format write command as write transaction, and send to
target DPA (step 428). In synchronous mode, wait for
acknowledgement from target DPA (step 432), and then
send acknowledgement to agent (step 436). In
asynchronous mode and in snapshot mode, send
acknowledgement to agent without waiting for
acknowledgement from target DPA (step 436).
Target Side
Receive write transaction from source DPA (step
DPA 124
444). Enter write transaction in journal DO and DO
METADATA streams (step 444), and send back
acknowledgement to source DPA (step 448). Process
journal entries by applying them to LU B, and enter undo
information in UNDO and UNDO METADATA streams
(step 440).
Target Side
Fail SCSI commands issued to LU B (step 452).
Agent 164
Only steps with arrows connecting them in
It is also noted in
Recovery mode is generally triggered as a result of a disaster at the source side. The source side data may become corrupt, or may not exist at all. In such case, after recovery is completed at the backup site, a user may perform a failover operation by switching the roles of the production site and backup site. The original backup site becomes a current production site, and the original production site becomes a current backup site. Alternatively, recovery mode can be triggered without a failover, in order to access data from a previous point in time.
While in recovery mode, target site DPA 124 continues to receive new write transactions from DPA 112 and enter them at the ends of the DO and DO METADATA streams. However, unlike production mode behavior, DPA 124 stops applying journal entries received from DPA 112 to LU B. Instead, DPA 124 uses the UNDO stream of the journal to rollback LU B, as described hereinabove.
During recovery, after or possibly before rollback of LU B is complete, a user may wish to access data from the target site. To this end, protection agent 164 stops failing I/O requests issued by host computer 160 and begins redirecting them to DPA 124. The processing of data by host computer 160 during recovery mode is referred to as “target side processing (TSP)”.
To manage TSP write commands that are received by target side DPA 124, journal processor 180 uses two additional data streams, referred to as TSP DO and TSP METADATA streams. When a TSP write command is received by DPA 124, it is entered at the end of the TSP DO stream and the end of the TSP DO METADATA stream. Since TSP writes relate to the state of LU B after the rollback is complete, the TSP DO stream writes are only applied to LU B after rollback is complete. Journal processor 180 applies TSP writes to LU B in a way similar to the way it applies write transactions deceiver from DPA 112; namely, journal processor 180 maintains the undo information for each write applied to LU B, in TSP UNDO and TSP UNDO METADATA streams.
When TSP read commands are received by target site DPA 124, DPA 124 returns the data to be read by identifying locations of the read command, and finding the most recent TSP write command or commands that were applied at these locations. The data is searched for (i) first in the TSP DO stream, and (ii) then in the journal UNDO data that was not yet applied to LU B and (iii) finally, if the data was not found in (i) and (ii), then the data is taken from LU B itself. In order to perform such a search efficiently, DPA 124 generates and stores in its memory a virtual image of the UNDO METADATA storage locations by using an efficient data structure, such as a binary search tree.
After rollback is completed, the TSP writes that were performed during the rollback are applied to LU B, and DPA 124 begins applying TSP writes synchronously; i.e., TSP writes are applied to LU B when they are received by DPA 124, without keeping them in the TSP DO stream. As such, when a read command is received after rollback is complete, it is sent directly to LU B instead of being redirected through DPA 124.
TABLES V and VI below summarize the behavior of the special protection components of system 100 during recovery mode, before and after the rollback is complete, in accordance with an embodiment of the present invention. Reference is also made to
TABLE V
Recovery Functionality prior to Completion of Rollback
System
Component
Behavior
Target Side
Intercept SCSI commands issued to LU B (step
Agent 164
576). Redirect commands to DPA (step 580).
Target Side
Use UNDO stream of journal to roll back target
DPA 124
storage system (step 540). Continue receiving write
transactions from DPA 112 and enter these transactions
into DO and DO METADATA streams without applying
them to LU B (step 548). Enter TSP write transactions to
TSP DO and TSP DO METADATA streams (step 564).
Create a virtual image, to reply to read commands issued
during the recovery process (step 572).
Source Side
As in production mode.
DPA 112
Source Side
As in production mode.
Agent 144
TABLE VI
Recovery Functionality after Completion of Rollback
System
Component
Behavior
Target Side
Intercept SCSI commands issued to LU B (step
Agent 164
664). Redirect write transactions to DPA (step 672), and
route read commands directly to LU B (step 680).
Target Side
Apply TSP write transactions to LU B, in the same
DPA 124
manner that write transactions received from DPA 112 are
applied in production mode; i.e., by entering data into TSP
UNDO and TSP UNDO METADATA streams (step 640).
Enter DO information and write transactions received
from DPA 112 into DO and DO METADATA streams,
without applying them to LU B (step 644). Apply TSP
write transactions to LU B as they are received (step 656).
Source Side
As in production mode.
DPA 112
Source Side
As in production mode.
Agent 144
It is also noted in
Reference is now made to
The data at time (1) is a common image for LU A and LU B at the same point in time, TCURRENT. Similarly, the data at time (2) is a common image for LU A and LU B at time TOLD. Rolled back data at time (2) may be processed by TSP writes, while at the same time current data at time (1) is being processed by source side writes. As such, the data evolves along the path from time (2) to time (3) as it is processed by the target side, and along the path from time (2) to time (4) as it is processed by the source side. The data images at the source and target sides at time TNEW are thus different.
When the recovery process is completed, the user may (i) return to a normal production mode, or (ii) perform a failover by switching the replication direction. In case (i), LU B is rolled back to its state at time (2), and the write transactions along the path from (2) to (4) are applied to LU B, so as to bring LU B to the same image as LU A. Conversely, in case (ii), LU B is maintained at its state at time (3), and its data is copied from the target side to the source side so as to bring LU A to the same image as LU B.
It may be appreciated that after rolling back the UNDO data stream to LU B, the state of the target side storage is substantially identical to the state that LU A was in at an earlier point in time. However, after applying TSP writes, the state of LU B is then in a new state that is different from the earlier state of LU A. As such, in order to return to a normal production mode, and ensure that LU B is a copy of LU A, DPA 124 undoes the TSP writes that were written to LU B using the TSP undo stream, and then returns to its normal production mode and begins applying the data that was written into the DO stream. The DO stream includes all write transactions that were undone while LU B was rolled back. Additionally, the DO stream includes new journal entries that were received from DPA 112 while DPA was in recovery mode. Similarly, protection agent 164 returns to its production mode by beginning to fail I/O requests issued by host 116.
Alternatively, the user want to perform a failover; i.e., to make LU B in its current state a production LU and ensure that LU A is a copy of LU B. In this case the write transactions in the DO stream that correspond to a point in time subsequent to the recovered point in time are ignored. Additionally, the TSP writes that were applied to LU B during the recovery process are applied to LU A. Thereafter, the replication direction changes. Specifically, DPA 124 and protection agent 164 begin behaving in accordance with source site behavior, and DPA 112 and protection agent 144 begin behaving in accordance with target site behavior.
It may be appreciated that in order to provide failover capability, in which the roles of the production site and the backup site are switched, it is desirable that the source side has the necessary system components to function as a target side, and vice versa. Thus, in an embodiment of the present invention, the source side includes its own journal LU 184 and journal processor 188, as indicated with dotted lines in
Referring back to TABLE I, it may be appreciated that during normal data replication, for each write transaction received from a production site, there are five I/O operations performed at a backup site. Reference is now made to
In accordance with an embodiment of the present invention, the meta-data for each transaction is of a fixed size, typically 30 bytes. The raw data varies in size, typically averaging around 10 KB per transaction.
As write transactions performed at a production site vary in frequency, and as each write transaction at the production site normally requires five I/O transactions at the backup site, it may be appreciated that the size of the DO stream grows and shrinks accordingly. When the I/O rate is low, the beginning of the DO stream is close to the end of the DO stream. In such case, it is possible to keep all write transactions between the beginning and the end of the DO stream in memory, and there is no need to read the beginning of the DO stream for every new transaction received in the backup site. As such, step 2 may be skipped.
Reference is now made to
However, during the steps 3-5 distribution of the write transaction that was just received, it is possible that a new transaction arrives at the backup site. In order to keep pace with the arriving transaction, as each write transaction is entered into the ends of the DO and DO METADATA streams, the write transaction is written into the end of a queue in memory. In accordance with an embodiment of the present invention, the queue in memory is handled similar to the way the DO stream is handled; namely, each received write is appended to the end of the queue, and when a write transaction is distributed according to steps 3-5, a subsequent write transaction is taken from the beginning of the queue. Effectively, the queue corresponds to a cached DO stream.
The 4-stage journaling process is used until the queue in memory is full, at which point the normal 5-stage journal processing is resumed. Also in the event of a disaster, the normal 5-stage journal processing is resumed. In order to resume the 5-stage journal processing, it is important to identify the last write in the DO stream that was written. As such, even during the 4-stage journal processing, the pointers to the first and last write transactions in the DO stream are updated.
Conversely, when the I/O rate is high, in order to control the size of the DO stream and ensure that it does not overflow its disk allotment, the present invention switches from the normal 5-stage mode to a faster 3-stage mode whenever the DO stream reaches a large percentage of its maximum capacity, typically 80%. The present invention afterwards switches back from the faster 3-stage mode to the normal 5-stage mode whenever the DO stream is reduced to a smaller percentage of its maximum capacity, typically 75%.
The 3-stage mode eliminates steps 3 and 4 from the normal mode; namely, the steps that record the UNDO information. As such, rollback of the backup storage unit to its state at the times of those transactions processed with the 3-stage mode is not possible.
Reference is now made to
TABLE VII summarizes the relative pros and cons of each of the journaling processes described hereinabove.
TABLE VII
Pros and Cons of Journaling Processes
Journaling
Process
Pros
Cons
3-Stage
Fastest replication time
Long time to recover to
Journaling
current time
4-Stage
Moderate replication time;
Only able to be used as long
Journaling
Full data recovery capability
as the beginning and the end
of the DO stream are close
5-Stage
Full data recovery capability
Slowest replication time
Journaling
One data replication strategy is the set of automated rules for controlling when a data replication system transitions between 5-stage, 4-stage and 3-stage journal processing. As mentioned hereinabove, transitions from 5-stage to 3-stage journaling, and from 3-stage back to 5-stage journaling, may be controlled based on the current size of the DO stream. Transitions from 5-stage to 4-stage journaling may be automated to occur when the beginning and end of the DO stream are close; and transitions from 4-stage back to 5-stage journaling may be automated to occur when the memory queue reaches its capacity.
Reference is now made to
It will be appreciated by those skilled in the art that using 4-stage journaling enables a data replication system to keep pace with higher I/O rates than can be handled when using 5-stage journaling. If the system is currently using 5-stage journaling and the I/O rate is higher than can be handled, a lag increases until the system necessarily transitions to the 3-stage journaling process. However, if the system can catch up with the lag, empty the DO stream and transition to a 4-stage journaling process, then the system can accommodate higher I/O rates before transitioning back to the 5-stage journaling process.
In this regard, it is noted that in general, if the system cannot keep pace with I/O rates using a 4-stage journaling process, then it most probably cannot keep pace using a 5-stage journaling process, and in either case the system would have to transition to a 3-stage journaling process. However, since the I/O rate changes continuously, a transition from 4-stage journaling to 5-stage journaling does not necessarily push the system to 3-stage journaling.
Reference is now made to
In a continuous data protection (CDP) environment, in a rollback, data can be recovered by rolling back to a specific point in time as described above. There are other situations, for example, in which an object (e.g., a file, a database table, an electronic message, a file folder and so forth) or a portion of an object is corrupted or an object is deleted and thus a point of time in which to rollback to may not be easily determined. In these situations, searching for a deleted object or trying to locate a latest version of an object before a corruption occurred can be a time-consuming task if not an impossible task for images that are replicated every second over a course of days or weeks by searching through each and every saved image.
Described below is a process to recover earlier versions of an object quickly and efficiently by using a data recovery module 720 (
Another aspect of the invention is shown in
The application 702 communicates with the source side protection agent 744 each time a change occurs with an object as a result of executing the application 702. In one example, the source side protection agent 744 interprets the transactions of the application 702 to determine the appropriate annotations to be recorded in the metadata in the journal 188. In another example, a driver (not shown) receives the transactions from the application 702 to determine the appropriate annotations to be recorded in the metadata streams in the journal 188. Each change is sent to the DRM 720 by the source-side agent 744. The DRM 720 annotates metadata (e.g., DO metadata stream or UNDO metadata stream) of a corresponding group of data blocks (e.g., DO stream data blocks or UNDO stream data blocks) containing the object. When a need arises to search for previous versions of the object, the DRM 720 searches the metadata for candidates (e.g., DO metadata entries corresponding to unique groups of DO stream data blocks that were annotated to indicate changes to the object) that meet certain criteria, rolls back to point-in-time images corresponding to these metadata entries and determines which version of the object should be obtained from these point-in-time images that meets the criteria. In one example, a user uses the GUI 703 to indicate which object needs to be restored and the criteria (e.g., an object is now corrupted or deleted and the most recent version of the object that is not corrupted or deleted is needed). The application 702 provides the object and criteria information from the GUI 703 to the DRM 720 in order to conduct a search to recover the object. In other examples, the GUI 703 may provide instructions directly to the source-side protection agent 144 for receipt by the DRM 720.
In one example, the DRM 720 conducts a search to locate the desired object based on the criteria. For example, if a given file has been corrupted, the DRM 720 searches those groups of data blocks where the metadata was annotated indicating a change to the given file. Starting with the most recent change, for example, the DRM 720 rolls back to that point in time to generate an image and checks the file in the image to determine if it is corrupted. There are a number of techniques known to one of ordinary skill in the art that may be used to perform this check. For example, if the file is compressed, then a cyclic redundancy check (CRC) may be performed on the file. If the file is corrupted for this group of data blocks, the next group of data blocks in time (where the metadata was annotated to indicate a change in the file) is also checked and so forth until an uncorrupted file is found. In another example, if a file is deleted, the DRM 720 locates the most recent version of the file before deletion by locating in the metadata the group of data blocks where the file was deleted, rolling back to the corresponding point-in-time image containing the file.
Referring to
The first application field 816 and the second application field 818 are each associated with a corresponding application. For example, metadata entries 822a-822e, having corresponding data blocks including objects that are changed by executing the corresponding application, are annotated in the corresponding application field 816, 818. In one example, the first application field 816 corresponds to a database application. Each time a table is deleted or changed in the database application the corresponding metadata entry 822 in the application field 816 is annotated. In this particular example, if a table A is deleted, then, under the metadata entry 822a, the first application field 816 is annotated. In another example, the second application field 818 corresponds to a word processing application. In this particular example, each time a file X is amended the corresponding metadata entries 822a, 822d are annotated in the second application field 818. While two applications fields 816, 818 are shown for simplicity; any number of fields may be used. For example, one application may include more than one corresponding metadata field. In other examples, there may be one or more data fields, each corresponding to one or more applications.
By annotating those metadata entries 822a-822e corresponding to changes to an object, the DRM 720 can isolate its search to candidates where the object has changed. For example, instead of checking all of the groups of data blocks corresponding to the metadata entries 822a-822e, to recover Table A, the DRM 720 checks the group of data blocks corresponding to the metadata entry 822a. In another example, if File X becomes corrupted, the DRM 720 checks those versions when the File X changed, for example, those groups of data blocks corresponding to metadata entries 822a, 822d. By narrowing the search to groups of data blocks that include changes to an object, the DRM 720 saves a significant amount of processing time by reducing the number of images that need to be analyzed.
The DRM 720 receives notification to recover an object based on criteria (906). The criteria may include recovering a most recent version of an object that is uncorrupted or a most recent version of the object before it is subsequently deleted. In one example, a user uses the GUI 703 to indicate that an object is be retrieved. In another example, a detection application (not shown) such as a virus detection program or a corruption detection program may be used to detect whether a file is corrupted and provide instructions to recover the file. In one particular example, the detection application can identify corrupted files and make corrections to the data stored without notifying the user, for example, as described in patent application Ser. No. 11/964,138, filed on Dec. 26, 2007, entitled “METHODS AND APPARATUS FOR VIRUS DETECTION USING JOURNAL DATA” having an obligation of assignment to the same assignee as this patent application and is incorporated herein in its entirety.
The DRM 720 determines the most recent version of the object that meets the criteria based on a search of the journal (912). For example, the DRM 720 searches those metadata entries 822 that include changes to the object (i.e., candidates). For example, the DRM 720 initiates a rollback to a most recent point in time corresponding to when the group of data blocks were saved and performs a check (e.g., a corruption check) on that object for that point in time. In one example, if the criteria is to recover an undeleted file, the UNDO data blocks which undo the deletion of the file are used to rewrite the data blocks that deleted the file in the DO stream.
The DRM 720 restores the most recent version of an object that meets criteria (914). For example, the DRM 720 rolls back to retrieve the desired object using the techniques described previously.
The processes and systems described herein are not limited to the specific embodiments described herein. For example, process 900 is not limited to the specific processing order of
In other embodiments, the metadata may include a field (e.g., a source field) that indicates a source of data. For example, the source-side host 704 may receive files from an outside source. In particular, the application 702 may be used to instruct DRM 720 to annotate metadata entries for corresponding groups of DO stream data blocks that include files from the outside source. If it is later determined that the outside source is malicious, the DRM 720 can be used to quickly locate the files from the outside source to delete these files or to quarantine these files.
The processing blocks in
Referring to
While the invention is shown and described in conjunction with particular embodiments having an illustrative architecture having certain components in a given order, it is understood that other embodiments well within the scope of the invention are contemplated having more and fewer components, having different types of components, and being coupled in various arrangements. Such embodiments will be readily apparent to one of ordinary skill in the art. All documents cited herein are incorporated herein by reference.
Natanzon, Assaf, Ahal, Shlomo, Drukh, Evgeny
| Patent | Priority | Assignee | Title |
| 10019194, | Sep 23 2016 | EMC IP Holding Company, LLC | Eventually consistent synchronous data replication in a storage system |
| 10031703, | Dec 31 2013 | EMC Corporation | Extent-based tiering for virtual storage using full LUNs |
| 10042751, | Sep 30 2015 | EMC IP HOLDING COMPANY LLC | Method and system for multi-tier all-flash array |
| 10055148, | Dec 22 2015 | EMC IP HOLDING COMPANY LLC | Storing application data as an enhanced copy |
| 10061666, | Dec 30 2011 | EMC International Company | Method and apparatus for adding a director to storage with network-based replication without data resynchronization |
| 10067837, | Dec 28 2015 | EMC IP HOLDING COMPANY LLC | Continuous data protection with cloud resources |
| 10078459, | Sep 26 2016 | EMC IP HOLDING COMPANY LLC | Ransomware detection using I/O patterns |
| 10082980, | Jun 20 2014 | EMC IP HOLDING COMPANY LLC | Migration of snapshot in replication system using a log |
| 10101943, | Sep 25 2014 | EMC IP HOLDING COMPANY LLC | Realigning data in replication system |
| 10108356, | Mar 25 2016 | EMC IP HOLDING COMPANY LLC | Determining data to store in retention storage |
| 10114581, | Dec 27 2016 | EMC IP HOLDING COMPANY LLC | Creating a virtual access point in time on an object based journal replication |
| 10133874, | Dec 28 2015 | EMC IP HOLDING COMPANY LLC | Performing snapshot replication on a storage system not configured to support snapshot replication |
| 10140039, | Dec 15 2016 | EMC IP HOLDING COMPANY LLC | I/O alignment for continuous replication in a storage system |
| 10152267, | Mar 30 2016 | EMC Corporation | Replication data pull |
| 10191687, | Dec 15 2016 | EMC IP HOLDING COMPANY LLC | Adaptive snap-based replication in a storage system |
| 10210073, | Sep 23 2016 | EMC IP Holding Company, LLC | Real time debugging of production replicated data with data obfuscation in a storage system |
| 10223023, | Sep 26 2016 | EMC IP HOLDING COMPANY LLC | Bandwidth reduction for multi-level data replication |
| 10229006, | Dec 28 2015 | EMC IP HOLDING COMPANY LLC | Providing continuous data protection on a storage array configured to generate snapshots |
| 10235060, | Apr 14 2016 | EMC IP Holding Company, LLC | Multilevel snapshot replication for hot and cold regions of a storage system |
| 10235061, | Sep 26 2016 | EMC IP HOLDING COMPANY LLC | Granular virtual machine snapshots |
| 10235064, | Dec 27 2016 | EMC IP HOLDING COMPANY LLC | Optimized data replication using special NVME protocol and running in a friendly zone of storage array |
| 10235087, | Mar 30 2016 | EMC IP HOLDING COMPANY LLC | Distributing journal data over multiple journals |
| 10235088, | Mar 30 2016 | EMC IP HOLDING COMPANY LLC | Global replication policy for multi-copy replication |
| 10235090, | Sep 23 2016 | EMC IP Holding Company, LLC | Validating replication copy consistency using a hash function in a storage system |
| 10235091, | Sep 23 2016 | EMC IP HOLDING COMPANY LLC | Full sweep disk synchronization in a storage system |
| 10235092, | Dec 15 2016 | EMC IP HOLDING COMPANY LLC | Independent parallel on demand recovery of data replicas in a storage system |
| 10235145, | Sep 13 2012 | EMC International Company | Distributed scale-out replication |
| 10235196, | Dec 28 2015 | EMC IP HOLDING COMPANY LLC | Virtual machine joining or separating |
| 10235247, | Sep 26 2016 | EMC IP HOLDING COMPANY LLC | Compressing memory snapshots |
| 10296419, | Mar 27 2015 | EMC IP HOLDING COMPANY LLC | Accessing a virtual device using a kernel |
| 10324637, | Dec 13 2016 | EMC IP HOLDING COMPANY LLC | Dual-splitter for high performance replication |
| 10324798, | Sep 25 2014 | EMC IP HOLDING COMPANY LLC | Restoring active areas of a logical unit |
| 10353603, | Dec 27 2016 | EMC IP HOLDING COMPANY LLC | Storage container based replication services |
| 10366011, | May 03 2018 | EMC IP HOLDING COMPANY LLC | Content-based deduplicated storage having multilevel data cache |
| 10409629, | Sep 26 2016 | EMC IP HOLDING COMPANY LLC | Automated host data protection configuration |
| 10409787, | Dec 22 2015 | EMC IP HOLDING COMPANY LLC | Database migration |
| 10409986, | Sep 26 2016 | EMC IP HOLDING COMPANY LLC | Ransomware detection in a continuous data protection environment |
| 10423634, | Dec 27 2016 | EMC IP HOLDING COMPANY LLC | Temporal queries on secondary storage |
| 10437783, | Sep 25 2014 | EMC IP HOLDING COMPANY LLC | Recover storage array using remote deduplication device |
| 10467102, | Dec 15 2016 | EMC IP HOLDING COMPANY LLC | I/O score-based hybrid replication in a storage system |
| 10489321, | Jul 31 2018 | EMC IP HOLDING COMPANY LLC | Performance improvement for an active-active distributed non-ALUA system with address ownerships |
| 10579282, | Mar 30 2016 | EMC IP HOLDING COMPANY LLC | Distributed copy in multi-copy replication where offset and size of I/O requests to replication site is half offset and size of I/O request to production volume |
| 10592166, | Aug 01 2018 | EMC IP HOLDING COMPANY LLC | Fast input/output in a content-addressable storage architecture with paged metadata |
| 10628268, | Dec 15 2016 | EMC IP HOLDING COMPANY LLC | Proof of data replication consistency using blockchain |
| 10691879, | Jan 04 2015 | EMC IP HOLDING COMPANY LLC | Smart multimedia processing |
| 10713221, | Jul 30 2018 | EMC IP HOLDING COMPANY LLC | Dual layer deduplication for a file system running over a deduplicated block storage |
| 10747606, | Dec 21 2016 | EMC IP HOLDING COMPANY LLC | Risk based analysis of adverse event impact on system availability |
| 10747667, | Nov 02 2018 | EMC IP HOLDING COMPANY LLC | Memory management of multi-level metadata cache for content-based deduplicated storage |
| 10776211, | Dec 27 2016 | EMC IP HOLDING COMPANY LLC | Methods, systems, and apparatuses to update point in time journal using map reduce to create a highly parallel update |
| 10838630, | Apr 18 2016 | NetApp, Inc.; NetApp, Inc | Write-ahead log maintenance and recovery |
| 10853181, | Jun 29 2015 | EMC IP HOLDING COMPANY LLC | Backing up volumes using fragment files |
| 10853286, | Jul 31 2018 | EMC IP HOLDING COMPANY LLC | Performance improvement for an active-active distributed non-ALUA system with address ownerships |
| 11016677, | Dec 13 2016 | EMC IP HOLDING COMPANY LLC | Dual-splitter for high performance replication |
| 11093158, | Jan 29 2019 | EMC IP HOLDING COMPANY LLC | Sub-lun non-deduplicated tier in a CAS storage to reduce mapping information and improve memory efficiency |
| 11120132, | Nov 09 2015 | WILMINGTON SAVINGS FUND SOCIETY, FSB | Restricted replication for protection of replicated databases |
| 11144247, | Aug 01 2018 | EMC IP HOLDING COMPANY LLC | Fast input/output in a content-addressable storage architecture with paged metadata |
| 11169707, | Jan 22 2016 | NetApp, Inc. | Garbage collection pacing in a storage system |
| 11449239, | Apr 18 2016 | NetApp, Inc. | Write-ahead log maintenance and recovery |
| 11561696, | Jan 22 2016 | NetApp, Inc. | Garbage collection pacing in a storage system |
| 11611595, | May 06 2011 | COLLABORATION TECHNOLOGIES, LLC | Systems and methodologies providing collaboration among a plurality of computing appliances, utilizing a plurality of areas of memory to store user input as associated with an associated computing appliance providing the input |
| 8224789, | Mar 12 2009 | Veritas Technologies LLC | Methods and systems for safely restoring files in a computing system |
| 8271447, | Jun 18 2010 | EMC International Company | Mirroring metadata in a continuous data protection environment |
| 8438135, | Jun 18 2010 | EMC International Company | Mirroring metadata in a continuous data protection environment |
| 8478955, | Sep 27 2010 | EMC International Company | Virtualized consistency group using more than one data protection appliance |
| 8612706, | Dec 21 2011 | Western Digital Technologies, INC | Metadata recovery in a disk drive |
| 8687306, | Mar 22 2010 | Western Digital Technologies, Inc. | Systems and methods for improving sequential data rate performance using sorted data zones |
| 8693133, | Mar 22 2010 | Western Digital Technologies, INC; Western Digital Technologies, Inc. | Systems and methods for improving sequential data rate performance using sorted data zones for butterfly format |
| 8699185, | Dec 10 2012 | Western Digital Technologies, Inc.; Western Digital Technologies, INC | Disk drive defining guard bands to support zone sequentiality when butterfly writing shingled data tracks |
| 8756361, | Oct 01 2010 | Western Digital Technologies, Inc. | Disk drive modifying metadata cached in a circular buffer when a write operation is aborted |
| 8756382, | Jun 30 2011 | Western Digital Technologies, Inc.; Western Digital Technologies, INC | Method for file based shingled data storage utilizing multiple media types |
| 8832399, | Sep 27 2010 | EMC International Company | Virtualized consistency group using an enhanced splitter |
| 8856438, | Dec 09 2011 | Western Digital Technologies, Inc. | Disk drive with reduced-size translation table |
| 8902527, | Mar 22 2010 | Western Digital Technologies, Inc. | Systems and methods for improving sequential data rate performance using sorted data zones |
| 8930914, | Feb 07 2013 | International Business Machines Corporation | System and method for documenting application executions |
| 8954664, | Oct 01 2010 | Western Digital Technologies, INC | Writing metadata files on a disk |
| 8996460, | Mar 14 2013 | EMC IP HOLDING COMPANY LLC | Accessing an image in a continuous data protection using deduplication-based storage |
| 9026696, | Sep 29 2010 | EMC IP HOLDING COMPANY LLC | Using I/O track information for continuous push with splitter for storage device |
| 9043758, | Mar 15 2013 | International Business Machines Corporation | System for generating readable and meaningful descriptions of stream processing source code |
| 9069709, | Jun 24 2013 | EMC International Company | Dynamic granularity in data replication |
| 9081842, | Mar 15 2013 | EMC IP HOLDING COMPANY LLC | Synchronous and asymmetric asynchronous active-active-active data access |
| 9087008, | Jun 24 2013 | EMC International Company | Replicating a volume using snapshots |
| 9087112, | Jun 24 2013 | EMC International Company | Consistency across snapshot shipping and continuous replication |
| 9110914, | Mar 14 2013 | EMC IP HOLDING COMPANY LLC | Continuous data protection using deduplication-based storage |
| 9146878, | Jun 25 2013 | EMC IP HOLDING COMPANY LLC | Storage recovery from total cache loss using journal-based replication |
| 9152339, | Mar 15 2013 | EMC IP HOLDING COMPANY LLC | Synchronization of asymmetric active-active, asynchronously-protected storage |
| 9152814, | Mar 15 2010 | EMC International Company | Writing and reading encrypted data using time-based encryption keys |
| 9158630, | Dec 19 2013 | EMC IP HOLDING COMPANY LLC | Testing integrity of replicated storage |
| 9189339, | Mar 28 2014 | EMC IP HOLDING COMPANY LLC | Replication of a virtual distributed volume with virtual machine granualarity |
| 9213493, | Dec 16 2011 | Western Digital Technologies, INC | Sorted serpentine mapping for storage drives |
| 9223659, | Jun 28 2012 | EMC International Company | Generating and accessing a virtual volume snapshot in a continuous data protection system |
| 9244997, | Mar 15 2013 | EMC IP HOLDING COMPANY LLC | Asymmetric active-active access of asynchronously-protected data storage |
| 9256605, | Aug 03 2011 | EMC International Company | Reading and writing to an unexposed device |
| 9274718, | Jun 20 2014 | EMC IP HOLDING COMPANY LLC | Migration in replication system |
| 9286052, | Sep 15 2011 | EMC International Company | Upgrading software on a pair of nodes in a clustered environment |
| 9323750, | Sep 29 2010 | EMC IP HOLDING COMPANY LLC | Storage array snapshots for logged access replication in a continuous data protection system |
| 9330715, | May 14 2013 | Western Digital Technologies, Inc.; Western Digital Technologies, INC | Mapping of shingled magnetic recording media |
| 9336094, | Sep 13 2012 | EMC International Company | Scaleout replication of an application |
| 9367260, | Dec 13 2013 | EMC IP HOLDING COMPANY LLC | Dynamic replication system |
| 9383937, | Mar 14 2013 | EMC IP HOLDING COMPANY LLC | Journal tiering in a continuous data protection system using deduplication-based storage |
| 9405481, | Dec 17 2014 | EMC IP HOLDING COMPANY LLC | Replicating using volume multiplexing with consistency group file |
| 9405765, | Dec 17 2013 | EMC IP HOLDING COMPANY LLC | Replication of virtual machines |
| 9411535, | Mar 27 2015 | EMC IP HOLDING COMPANY LLC | Accessing multiple virtual devices |
| 9501542, | Mar 11 2008 | EMC Corporation | Methods and apparatus for volume synchronization |
| 9529885, | Sep 29 2014 | EMC IP HOLDING COMPANY LLC | Maintaining consistent point-in-time in asynchronous replication during virtual machine relocation |
| 9557921, | Mar 26 2015 | EMC IP HOLDING COMPANY LLC | Virtual volume converter |
| 9600377, | Dec 03 2014 | EMC IP HOLDING COMPANY LLC | Providing data protection using point-in-time images from multiple types of storage devices |
| 9619543, | Jun 23 2014 | EMC IP HOLDING COMPANY LLC; EMC Corporation | Replicating in virtual desktop infrastructure |
| 9632881, | Mar 24 2015 | EMC IP HOLDING COMPANY LLC | Replication of a virtual distributed volume |
| 9665305, | Jun 26 2015 | EMC IP HOLDING COMPANY LLC | Tiering data between two deduplication devices |
| 9665307, | Dec 19 2013 | EMC IP HOLDING COMPANY LLC | Incremental continuous data protection |
| 9678680, | Mar 30 2015 | EMC IP HOLDING COMPANY LLC | Forming a protection domain in a storage architecture |
| 9684576, | Dec 21 2015 | EMC IP HOLDING COMPANY LLC | Replication using a virtual distributed volume |
| 9696939, | Mar 14 2013 | EMC IP HOLDING COMPANY LLC | Replicating data using deduplication-based arrays using network-based replication |
| 9792340, | Aug 31 2011 | METASWITCH NETWORKS LTD | Identifying data items |
| 9892002, | Dec 19 2013 | EMC IP HOLDING COMPANY LLC | Incremental continuous data protection |
| 9910621, | Sep 29 2014 | EMC IP HOLDING COMPANY LLC | Backlogging I/O metadata utilizing counters to monitor write acknowledgements and no acknowledgements |
| 9910659, | Nov 07 2012 | Qualcomm Incorporated | Methods for providing anti-rollback protection of a firmware version in a device which has no internal non-volatile memory |
| 9910735, | Mar 30 2016 | EMC IP HOLDING COMPANY LLC | Generating an application-consistent snapshot |
| Patent | Priority | Assignee | Title |
| 5170480, | Sep 25 1989 | International Business Machines Corporation | Concurrently applying redo records to backup database in a log sequence using single queue server per queue at a time |
| 5388254, | Mar 27 1992 | International Business Machines Corporation | Method and means for limiting duration of input/output (I/O) requests |
| 5499367, | Nov 15 1991 | Oracle International Corporation | System for database integrity with multiple logs assigned to client subsets |
| 5864837, | Jun 12 1996 | Unisys Corporation | Methods and apparatus for efficient caching in a distributed environment |
| 5879459, | Aug 29 1997 | EUGENUS, INC | Vertically-stacked process reactor and cluster tool system for atomic layer deposition |
| 5990899, | Oct 27 1995 | Microsoft Technology Licensing, LLC | Method for compressing journal streams |
| 6042652, | May 01 1999 | NATIONAL RESEARCH FOUNDATION OF KOREA NRF | Atomic layer deposition apparatus for depositing atomic layer on multiple substrates |
| 6065018, | Mar 04 1998 | GLOBALFOUNDRIES Inc | Synchronizing recovery log having time stamp to a remote site for disaster recovery of a primary database having related hierarchial and relational databases |
| 6143659, | Nov 18 1997 | Samsung Electronics, Co., Ltd. | Method for manufacturing aluminum metal interconnection layer by atomic layer deposition method |
| 6148340, | Apr 30 1998 | IBM Corporation | Method and system for differencing container files |
| 6174377, | Mar 03 1997 | AIXTRON, INC | Processing chamber for atomic layer deposition processes |
| 6174809, | Dec 31 1997 | Samsung Electronics, Co., Ltd. | Method for forming metal layer using atomic layer deposition |
| 6203613, | Oct 19 1999 | International Business Machines Corporation | Atomic layer deposition with nitrate containing precursors |
| 6260125, | Dec 09 1998 | TERADATA US, INC | Asynchronous write queues, reconstruction and check-pointing in disk-mirroring applications |
| 6270572, | Aug 07 1998 | SAMSUNG ELECTRONICS CO , LTD | Method for manufacturing thin film using atomic layer deposition |
| 6272534, | Mar 04 1998 | Storage Technology Corporation | Method and system for efficiently storing web pages for quick downloading at a remote device |
| 6287965, | Jul 28 1997 | SAMSUNG ELECTRONICS, CO , LTD | Method of forming metal layer using atomic layer deposition and semiconductor device having the metal layer as barrier metal layer or upper or lower electrode of capacitor |
| 6467023, | Mar 23 1999 | AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LIMITED | Method for logical unit creation with immediate availability in a raid storage environment |
| 6574657, | May 03 1999 | CLOUDING CORP | Methods and apparatuses for file synchronization and updating using a signature list |
| 6621493, | Oct 27 1995 | Microsoft Technology Licensing, LLC | Metafile compression |
| 6804676, | Aug 31 1999 | International Business Machines Corporation | System and method in a data processing system for generating compressed affinity records from data records |
| 6947981, | Mar 26 2002 | Hewlett Packard Enterprise Development LP | Flexible data replication mechanism |
| 7043610, | Aug 19 2002 | ADAPTEC INC | System and method for maintaining cache coherency without external controller intervention |
| 7076620, | Feb 27 2003 | Hitachi, LTD | Data processing system including storage systems |
| 7111197, | Sep 21 2001 | VALTRUS INNOVATIONS LIMITED | System and method for journal recovery for multinode environments |
| 7117327, | Apr 28 2004 | Hitachi, Ltd. | Data processing system |
| 7120768, | Mar 22 2002 | Hitachi, Ltd. | Snapshot acquisition method, storage system and disk apparatus |
| 7130975, | Sep 09 2003 | Hitachi, Ltd. | Data processing system |
| 7139927, | Mar 21 2002 | Wisconsin Alumni Research Foundation | Journaling and recovery method of shared disk file system |
| 7159088, | Aug 04 2004 | Hitachi, Ltd. | Storage system and data processing system |
| 7167963, | Apr 28 2004 | Hitachi, Ltd. | Storage system with multiple remote site copying capability |
| 7222136, | May 23 2002 | Oracle International Corporation | Communicating data dictionary information of database objects through a redo stream |
| 7296008, | Aug 24 2004 | Veritas Technologies LLC | Generation and use of a time map for accessing a prior image of a storage device |
| 7328373, | Jan 30 2004 | GOOGLE LLC | Data processing system |
| 7360113, | Aug 30 2004 | Veritas Technologies LLC | Protocol for communicating data block copies in an error recovery environment |
| 7426618, | Sep 06 2005 | Dot Hill Systems Corp. | Snapshot restore method and apparatus |
| 7516287, | Sep 28 2006 | EMC Corporation | Methods and apparatus for optimal journaling for continuous data replication |
| 7519625, | Sep 27 2005 | Hitachi, Ltd. | Snapshot management apparatus and method, and storage system |
| 7519628, | Jun 01 2004 | NetApp, Inc | Technique for accelerating log replay with partial cache flush |
| 7546485, | Aug 15 2006 | Hewlett Packard Enterprise Development LP | Method and system for efficient journal-based resynchronization |
| 7577867, | Feb 17 2006 | EMC Corporation | Cross tagging to data for consistent recovery |
| 7606940, | Jun 23 2003 | Hitachi, Ltd. | Remote copy system |
| 7627612, | Sep 28 2006 | EMC IP HOLDING COMPANY LLC; EMC Corporation | Methods and apparatus for optimal journaling for continuous data replication |
| 7627687, | Sep 28 2006 | EMC IP HOLDING COMPANY LLC; EMC Corporation | Methods and apparatus for managing data flow in a continuous data replication system having journaling |
| 7757057, | Nov 27 2006 | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | Optimized rollback of copy-on-write snapshot volumes |
| 20020129168, | |||
| 20030061537, | |||
| 20030110278, | |||
| 20030196147, | |||
| 20040205092, | |||
| 20040250032, | |||
| 20040254964, | |||
| 20050015663, | |||
| 20050028022, | |||
| 20050049924, | |||
| 20050172092, | |||
| 20050273655, | |||
| 20060031647, | |||
| 20060047996, | |||
| 20060064416, | |||
| 20060107007, | |||
| 20060117211, | |||
| 20060161810, | |||
| 20060195670, | |||
| 20060212462, | |||
| 20070055833, | |||
| 20070162513, | |||
| 20070180304, | |||
| 20070198602, | |||
| 20070198791, | |||
| 20070220311, | |||
| 20070266053, | |||
| 20080082591, | |||
| 20080082592, | |||
| 20080082770, | |||
| EP1154356, | |||
| WO45581, |
| Date | Maintenance Fee Events |
| Jun 21 2011 | ASPN: Payor Number Assigned. |
| Jun 30 2014 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
| May 22 2018 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
| May 19 2022 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
| Date | Maintenance Schedule |
| Dec 28 2013 | 4 years fee payment window open |
| Jun 28 2014 | 6 months grace period start (w surcharge) |
| Dec 28 2014 | patent expiry (for year 4) |
| Dec 28 2016 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Dec 28 2017 | 8 years fee payment window open |
| Jun 28 2018 | 6 months grace period start (w surcharge) |
| Dec 28 2018 | patent expiry (for year 8) |
| Dec 28 2020 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Dec 28 2021 | 12 years fee payment window open |
| Jun 28 2022 | 6 months grace period start (w surcharge) |
| Dec 28 2022 | patent expiry (for year 12) |
| Dec 28 2024 | 2 years to revive unintentionally abandoned end. (for year 12) |