Methods and apparatus for virus detection using journal data

BACKGROUND

p-0002Computer 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.

p-0003Conventional 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.

p-0004Another 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.

p-0005Current 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.

p-0006Conventional data protection systems can include antivirus mechanisms that are typically run directly from the server. This consumes production server resources and production storage bandwidth. In addition, in the event of a virus detection there is the potential for lost data.

SUMMARY

p-0007The present invention provides methods and apparatus for a continuous data protection system with journaling that includes anti-virus functionality. With this arrangement, anti-virus scanning can be offloaded from a production server, for example, to a replication side, for example. Searching can be performed efficiently by using the journal data to mount a point in time copy and searching only files or other data suspected for infection. The journal can be used to find the most recent clean, i.e., uninfected, image.

p-0008In one aspect of the invention, a method includes storing journal data including a do stream and an undo stream in a continuous data protection system, receiving a virus signature update containing a first new virus signature, scanning data for the first new virus signature, using the journal data for point in time images, and identifying a first one of the point in time images that is latest in time prior to infection by the first virus.

p-0009The method can include one or more of the following features: scanning the journal data, scanning point in time image data, scanning the data until identifying data of initial infection by the first virus, identifying an I/O operation for the data of initial infection, identifying a root cause of the first virus, identifying a user associated with the infection by the first virus, cleaning a file infected with the first virus, and cleaning the file to provide clean point in time images at times after the time of infection by the first virus, scanning the undo stream before the do stream.

p-0010In another aspect of the invention, a continuous data protection system, comprises a system to store journal data including a do stream and an undo stream, and an antivirus module to receive a virus signature update containing a first new virus signature for scanning data for the first new virus signature and use the journal data for point in time images for identifying a first one of the point in time images that is latest in time prior to infection by the first virus.

p-0011In another aspect of the invention, an article comprises a computer readable medium storing instructions to enable execution of: storing journal data including a do stream and an undo stream in a continuous data protection system, receiving a virus signature update containing a first new virus signature, scanning data for the first new virus signature, and using the journal data for point in time images, identifying a first one of the point in time images that is latest in time prior to infection by the first virus.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be more fully understood and appreciated from the following detailed description, taken in conjunction with the drawings in which:

<figref idrefs="DRAWINGS">FIG. 1</figref> is a simplified block diagram of a data protection system, in accordance with an embodiment of the present invention;

<figref idrefs="DRAWINGS">FIG. 2</figref> is a simplified illustration of a journal history of write transactions for a storage system, in accordance with an embodiment of the present invention;

<figref idrefs="DRAWINGS">FIG. 3A</figref> is a simplified illustration of a first stage of a journal and four data streams stored therein, after recording three write transactions, in accordance with an embodiment of the present invention;

<figref idrefs="DRAWINGS">FIG. 3B</figref> is a simplified illustration of a second stage of a journal and four data streams stored therein, after applying a first write transactions to a storage system, in accordance with an embodiment of the present invention;

<figref idrefs="DRAWINGS">FIG. 3C</figref> is a simplified illustration of a third stage of a journal history and four data streams stored therein, after applying a second write transactions to a storage system, in accordance with an embodiment of the present invention;

<figref idrefs="DRAWINGS">FIG. 3D</figref> is a simplified illustration of a fourth stage of a journal history and four data streams stored therein, after rolling back a write transaction, in accordance with an embodiment of the present invention;

<figref idrefs="DRAWINGS">FIG. 4</figref> is a simplified flowchart of a data protection method during a normal production mode, in accordance with an embodiment of the present invention;

<figref idrefs="DRAWINGS">FIG. 5</figref> is a simplified flowchart of a data protection method during a data recovery mode, prior to completion of rollback, in accordance with an embodiment of the present invention;

<figref idrefs="DRAWINGS">FIG. 6</figref> is a simplified flowchart of a data protection method during a data recovery mode, after completion of rollback, in accordance with an embodiment of the present invention;

<figref idrefs="DRAWINGS">FIG. 7</figref> is a simplified illustration of a time-line for tracking new processing of old data, in accordance with an embodiment of the present invention;

<figref idrefs="DRAWINGS">FIG. 8</figref> is a simplified illustration of a five-stage journaling process for continuous data replication, in accordance with an embodiment of the present invention;

<figref idrefs="DRAWINGS">FIG. 9</figref> is a simplified illustration of a four-stage journaling process for continuous data replication, for use when an I/O data rate is low, in accordance with an embodiment of the present invention;

<figref idrefs="DRAWINGS">FIG. 10</figref> is a simplified illustration of a three-stage journaling process for continuous data replication, for use when an I/O data rate is high, in accordance with an embodiment of the present invention;

<figref idrefs="DRAWINGS">FIG. 11</figref> is a simplified state diagram of transitions between 5-stage, 4-stage and 3-stage journal processing, in accordance with an embodiment of the present invention; and

<figref idrefs="DRAWINGS">FIG. 12</figref> is a simplified illustration of a variant of the three-stage journaling process shown in <figref idrefs="DRAWINGS">FIG. 10</figref>, which may be used in an alternative embodiment of the present invention.

<figref idrefs="DRAWINGS">FIG. 13</figref> is a block diagram of a data protection system having virus protection in accordance with an embodiment of the present invention;

<figref idrefs="DRAWINGS">FIG. 14</figref> is a timeline showing virus infection and detection;

<figref idrefs="DRAWINGS">FIGS. 15A-C</figref> show exemplary journal search embodiments; and

<figref idrefs="DRAWINGS">FIG. 16</figref> is a flow diagram showing an exemplary sequence of steps to provide virus protection in accordance with exemplary embodiments of the invention.

<figref idrefs="DRAWINGS">FIG. 17</figref> is a flow diagram showing exemplary antivirus functionality in a continuous data protection system; and

<figref idrefs="DRAWINGS">FIG. 18</figref> is a pictorial representation of identifying an I/O operation of first infection.

DETAILED DESCRIPTION

p-0034The following definitions are employed throughout the specification and claims.

p-0035BACKUP 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;

p-0036DPA—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;

p-0037HOST—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;

p-0038HOST DEVICE—an internal interface in a host, to a logical storage unit;

p-0039IMAGE—a copy of a logical storage unit at a specific point in time;

p-0040INITIATOR—a node in a SAN that issues I/O requests;

p-0041JOURNAL—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;

p-0042LOGICAL UNIT—a logical entity provided by a storage system for accessing data from the storage system;

p-0043LUN—a logical unit number for identifying a logical unit;

p-0044PHYSICAL 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;

p-0045PRODUCTION 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;

p-0046SAN—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;

p-0047SOURCE 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;

p-0048STORAGE SYSTEM—a SAN entity that provides multiple logical units for access by multiple SAN initiators

p-0049TARGET—a node in a SAN that replies to I/O requests;

p-0050TARGET 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;

p-0051WAN—a wide area network that connects local networks and enables them to communicate with one another, such as the Internet.

p-0052Reference is now made to <figref idrefs="DRAWINGS">FIG. 1</figref>, which is a simplified illustration of a data protection system <b>100</b>, in accordance with an embodiment of the present invention. Shown in <figref idrefs="DRAWINGS">FIG. 1</figref> are two sites; Site I, which is a production site, on the right, and Site II, which is a backup site, on the left. Under normal operation the production site is the source side of system <b>100</b>, and the backup site is the target side of the system. The backup site is responsible for replicating production site data. Additionally, the backup site enables rollback of Site I data to an earlier pointing time, which may be used in the event of data corruption of a disaster, or alternatively in order to view or to access data from an earlier point in time.

p-0053During 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.

p-0054The 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.

p-0055The source and target sides communicate via a wide area network (WAN) <b>128</b>, although other types of networks are also adaptable for use with the present invention.

p-0056In accordance with an embodiment of the present invention, each side of system <b>100</b> 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 <figref idrefs="DRAWINGS">FIG. 1</figref>, the source side SAN includes a source host computer <b>104</b>, a source storage system <b>108</b>, and a source DPA <b>112</b>. Similarly, the target side SAN includes a target host computer <b>116</b>, a target storage system <b>120</b>, and a target DPA <b>124</b>.

p-0057Generally, 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.

p-0058In an embodiment of the present invention, the host communicates with its corresponding storage system using small computer system interface (SCSI) commands.

p-0059System <b>100</b> includes source storage system <b>108</b> and target storage system <b>120</b>. Each storage system includes physical storage units for storing data, such as disks or arrays of disks. Typically, storage systems <b>108</b> and <b>120</b> are target nodes. In order to enable initiators to send requests to storage system <b>108</b>, storage system <b>108</b> exposes one or more logical units (LU) to which commands are issued. Thus, storage systems <b>108</b> and <b>120</b> are SAN entities that provide multiple logical units for access by multiple SAN initiators.

p-0060Logical 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 <b>108</b> exposes a logical unit <b>136</b>, designated as LU A, and storage system <b>120</b> exposes a logical unit <b>156</b>, designated as LU B.

p-0061In 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 <b>120</b> serves as a backup for source side storage system <b>108</b>. Alternatively, as mentioned hereinabove, some logical units of storage system <b>120</b> may be used to back up logical units of storage system <b>108</b>, and other logical units of storage system <b>120</b> 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 <b>108</b> are used for replicating logical units of storage system <b>120</b>, and other logical units of storage system <b>120</b> are used for replicating other logical units of storage system <b>108</b>.

p-0062System <b>100</b> includes a source side host computer <b>104</b> and a target side host computer <b>116</b>. 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.

p-0063Generally, 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 <b>104</b> identifies LU A and generates a corresponding host device <b>140</b>, designated as Device A, through which it can access LU A. Similarly, host computer <b>116</b> identifies LU B and generates a corresponding device <b>160</b>, designated as Device B.

p-0064In an embodiment of the present invention, in the course of continuous operation, host computer <b>104</b> is a SAN initiator that issues I/O requests (write/read operations) through host device <b>140</b> 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 <b>104</b> 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.

p-0065System <b>100</b> includes two data protection appliances, a source side DPA <b>112</b> and a target side DPA <b>124</b>. 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 <b>112</b> and <b>124</b> is a computer that includes inter alia one or more conventional CPUs and internal memory.

p-0066For 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 perforin other tasks that require coordination between the computers, such as load balancing.

p-0067In the architecture illustrated in <figref idrefs="DRAWINGS">FIG. 1</figref>, DPA <b>112</b> and DPA <b>124</b> are standalone devices integrated within a SAN. Alternatively, each of DPA <b>112</b> and DPA <b>124</b> may be integrated into storage system <b>108</b> and storage system <b>120</b>, respectively, or integrated into host computer <b>104</b> and host computer <b>116</b>, respectively. Both DPAs communicate with their respective host computers through communication lines such as fiber channels using, for example, SCSI commands.

p-0068In accordance with an embodiment of the present invention, DPAs <b>112</b> and <b>124</b> 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 <b>112</b> and DPA <b>124</b> 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 <b>104</b> and <b>116</b>. Being target nodes, DPA <b>112</b> and DPA <b>124</b> may dynamically expose or remove one or more logical units.

p-0069As 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 <b>112</b> and DPA <b>124</b> may each behave as a source DPA for some logical units, and as a target DPA for other logical units, at the same time.

p-0070In accordance with an embodiment of the present invention, host computer <b>104</b> and host computer <b>116</b> include protection agents <b>144</b> and <b>164</b>, respectively. Protection agents <b>144</b> and <b>164</b> 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:

p-0071Send the SCSI commands to its intended logical unit.

p-0072Redirect the SCSI command to another logical unit.

p-0073Split 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.

p-0074Fail a SCSI command by returning an error return code.

p-0075Delay a SCSI command by not returning an acknowledgement to the respective host computer.

p-0076A 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.

p-0077Specifically, 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.

p-0078Communication 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.

p-0079In an embodiment of the present invention, protection agents <b>144</b> and <b>164</b> are drivers located in their respective host computers <b>104</b> and <b>116</b>. 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.

p-0080What follows is a detailed description of system behavior under normal production mode, and under recovery mode.

p-0081In accordance with an embodiment of the present invention, in production mode DPA <b>112</b> acts as a source site DPA for LU A. Thus, protection agent <b>144</b> is configured to act as a source side protection agent; i.e., as a splitter for host device A. Specifically, protection agent <b>144</b> replicates SCSI I/O requests. A replicated SCSI I/O request is sent to DPA <b>112</b>. After receiving an acknowledgement from DPA <b>124</b>, protection agent <b>144</b> then sends the SCSI I/O request to LU A. Only after receiving a second acknowledgement from storage system <b>108</b> will host computer <b>104</b> initiate another I/O request.

p-0082When DPA <b>112</b> receives a replicated SCSI write request from data protection agent <b>144</b>, DPA <b>112</b> transmits certain I/O information characterizing the write request, packaged as a “write transaction”, over WAN <b>128</b> to DPA <b>124</b> on the target side, for journaling and for incorporation within target storage system <b>120</b>.

p-0083DPA <b>112</b> may send its write transactions to DPA <b>124</b> 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 <b>112</b> sends each write transaction to DPA <b>124</b>, receives back an acknowledgement from DPA <b>124</b>, and in turns sends an acknowledgement back to protection agent <b>144</b>. Protection agent <b>144</b> waits until receipt of such acknowledgement before sending the SCSI write request to LU A.

p-0084In asynchronous mode, DPA <b>112</b> sends an acknowledgement to protection agent <b>144</b> upon receipt of each I/O request, before receiving an acknowledgement back from DPA <b>124</b>.

p-0085In snapshot mode, DPA <b>112</b> 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 <b>124</b>, for journaling and for incorporation in target storage system <b>120</b>. In snapshot mode DPA <b>112</b> also sends an acknowledgement to protection agent <b>144</b> upon receipt of each I/O request, before receiving an acknowledgement back from DPA <b>124</b>.

p-0086For the sake of clarity, the ensuing discussion assumes that information is transmitted at write-by-write granularity.

p-0087While in production mode, DPA <b>124</b> receives replicated data of LU A from DPA <b>112</b>, and performs journaling and writing to storage system <b>120</b>. When applying write operations to storage system <b>120</b>, DPA <b>124</b> acts as an initiator, and sends SCSI commands to LU B.

p-0088During a recovery mode, DPA <b>124</b> undoes the write transactions in the journal, so as to restore storage system <b>120</b> to the state it was at, at an earlier time.

p-0089As 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 <b>104</b> is replicated from LU A to LU B, host computer <b>116</b> should not be sending I/O requests to LU B. To prevent such I/O requests from being sent, protection agent <b>164</b> acts as a target site protection agent for host Device B and fails I/O requests sent from host computer <b>116</b> to LU B through host Device B.

p-0090In accordance with an embodiment of the present invention, target storage system <b>120</b> exposes a logical unit <b>176</b>, 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 <b>176</b> may be striped over several logical units, or may reside within all of or a portion of another logical unit. DPA <b>124</b> includes a journal processor <b>180</b> for managing the journal.

p-0091Journal processor <b>180</b> functions generally to manage the journal entries of LU B. Specifically, journal processor <b>180</b> (i) enters write transactions received by DPA <b>124</b> from DPA <b>112</b> 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. <b>2</b> and <b>3</b>A-<b>3</b>D, 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.

p-0092Reference is now made to <figref idrefs="DRAWINGS">FIG. 2</figref>, which is a simplified illustration of a write transaction <b>200</b> for a journal, in accordance with an embodiment of the present invention.

p-0093The journal may be used to provide an adaptor for access to storage <b>120</b> at the state it was in at any specified point in time. Since the journal contains the “undo” information necessary to rollback storage system <b>120</b>, data that was stored in specific memory locations at the specified point in time may be obtained by undoing write transactions that occurred subsequent to such point in time.

p-0094Write transaction <b>200</b> generally includes the following fields:

p-0095one or more identifiers;

p-0096a time stamp, which is the date &amp; time at which the transaction was received by source side DPA <b>112</b>;

p-0097a write size, which is the size of the data block;

p-0098a location in journal LU <b>176</b> where the data is entered;

p-0099a location in LU B where the data is to be written; and

p-0100the data itself.

p-0101Write transaction <b>200</b> is transmitted from source side DPA <b>112</b> to target side DPA <b>124</b>. As shown in <figref idrefs="DRAWINGS">FIG. 2</figref>, DPA <b>124</b> records the write transaction <b>200</b> in four streams. A first stream, referred to as a DO stream, includes new data for writing in LU B. A second stream, referred to as an DO METADATA stream, includes metadata for the write transaction, such as an identifier, a date &amp; time, a write size, a beginning address in LU B for writing the new data in, and a pointer to the offset in the do stream where the corresponding data is located. Similarly, a third stream, referred to as an UNDO stream, includes old data that was overwritten in LU B; and a fourth stream, referred to as an UNDO METADATA, include an identifier, a date &amp; time, a write size, a beginning address in LU B where data was to be overwritten, and a pointer to the offset in the undo stream where the corresponding old data is located.

p-0102In practice each of the four streams holds a plurality of write transaction data. As write transactions are received dynamically by target DPA <b>124</b>, 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.

p-0103By 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.

p-0104The 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.

p-0105According 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 <b>124</b>, 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.

p-0106Thereafter 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.

p-0107When a write transaction is received, journaling is thus advanced as indicated in TABLE I below.

p-0108<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217pt" align="center" /><thead><row><entry namest="1" nameend="1" rowsep="1">TABLE I</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Entering a write transaction in the journal</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="35pt" align="center" /><colspec colname="2" colwidth="182pt" align="left" /><tbody valign="top"><row><entry>Step 1</entry><entry>The new data is written at the end of the DO stream, </entry></row><row><entry /><entry>assuming a forward write direction, and corresponding </entry></row><row><entry /><entry>metadata is written at the end of the DO METADATA stream.</entry></row><row><entry>Step 2</entry><entry>Data is read from the beginning of the DO stream, </entry></row><row><entry /><entry>and corresponding metadata is read from the</entry></row><row><entry /><entry>beginning of the DO METADATA stream.</entry></row><row><entry>Step 3</entry><entry>Old data to be overwritten is read from LU B. </entry></row><row><entry /><entry>The location and size of such old data is determined</entry></row><row><entry /><entry>from the DO METADATA stream.</entry></row><row><entry>Step 4</entry><entry>The old data is written at the end of the UNDO stream, </entry></row><row><entry /><entry>and corresponding metadata is written at</entry></row><row><entry /><entry>the end of the UNDO METADATA stream.</entry></row><row><entry>Step 5</entry><entry>The new data read at Step 2 is written into LU B, </entry></row><row><entry /><entry>and the beginning and end pointers of the DO and</entry></row><row><entry /><entry>DO METADATA streams are moved appropriately.</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0109Conversely, during a rollback to undo a write transaction, the above operations are reversed, as indicated in TABLE II below.

p-0110<tables id="TABLE-US-00002" num="00002"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217pt" align="center" /><thead><row><entry namest="1" nameend="1" rowsep="1">TABLE II</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Undoing a write transaction in the journal</entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="56pt" align="center" /><colspec colname="2" colwidth="161pt" align="left" /><tbody valign="top"><row><entry>Step 1 </entry><entry>Read the data and metadata from the end </entry></row><row><entry /><entry>of the UNDO and UNDO METADATA streams</entry></row><row><entry>Step 2</entry><entry>Read from LU B the data that is to be overwritten. </entry></row><row><entry /><entry>The location and size of such data is determined</entry></row><row><entry /><entry>from the UNDO METADATA stream.</entry></row><row><entry>Step 3</entry><entry>Write the data from Step 2 at the beginning </entry></row><row><entry /><entry>of the DO stream, and update the DO METADATA</entry></row><row><entry /><entry>stream accordingly.</entry></row><row><entry>Step 4</entry><entry>Write the data from Step 1 to LU B, and update </entry></row><row><entry /><entry>the beginning and end pointers of the UNDO and</entry></row><row><entry /><entry>UNDO metadata streams appropriately.</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0111The following example, in conjunction with <figref idrefs="DRAWINGS">FIGS. 3A-3D</figref>, describes specific details of the journaling process, in accordance with an embodiment of the present invention. A journal volume includes a plurality of segments from a segment pool, each segment including 20 data blocks.

p-0112Three write transactions are received, as indicated in TABLE III.

p-0113<tables id="TABLE-US-00003" num="00003"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217pt" align="center" /><thead><row><entry namest="1" nameend="1" rowsep="1">TABLE III</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Example Write Transactions</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="5"><colspec colname="1" colwidth="28pt" align="center" /><colspec colname="2" colwidth="42pt" align="left" /><colspec colname="3" colwidth="49pt" align="center" /><colspec colname="4" colwidth="35pt" align="center" /><colspec colname="5" colwidth="63pt" align="left" /><tbody valign="top"><row><entry>Write</entry><entry /><entry>LU B</entry><entry /><entry /></row><row><entry>ID</entry><entry>Time</entry><entry>location</entry><entry>Length</entry><entry>Journal LU location</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row><row><entry>1</entry><entry>Dec. 3, 2005</entry><entry>LU B</entry><entry>15 blocks</entry><entry>Segment 1,</entry></row><row><entry /><entry>10:00:00.00 </entry><entry>offset 57 blocks</entry><entry /><entry>offset 0</entry></row><row><entry>2</entry><entry>Dec. 3, 2005</entry><entry>LU B</entry><entry>20 blocks</entry><entry>Segment 1,</entry></row><row><entry /><entry>10:00:00.05</entry><entry>offset 87 blocks</entry><entry /><entry>offset 15</entry></row><row><entry>3</entry><entry>Dec. 3, 2005</entry><entry>LU B</entry><entry>20 blocks</entry><entry>Segment 3,</entry></row><row><entry /><entry>10:00:00.18</entry><entry>offset 12 blocks</entry><entry /><entry>Offset 15</entry></row><row><entry namest="1" nameend="5" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0114The following discussion describes four stages of journaling and data storage; namely,

p-0115Stage #1: Enter the three write transactions as journal entries in the journal LU.

p-0116Stage #2: Apply the first write transaction to LU B.

p-0117Stage #3: Apply the second write transaction to LU B.

p-0118Stage #4: Rollback the second write transaction, to recover data from an earlier point in time.

p-0119The 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.

p-0120Thus 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 <figref idrefs="DRAWINGS">FIG. 3A</figref>.

p-0121At 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.

p-0122At 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 <figref idrefs="DRAWINGS">FIG. 3B</figref>.

p-0123At 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.

p-0124Finally, 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 <figref idrefs="DRAWINGS">FIG. 3C</figref>.

p-0125At 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.

p-0126The 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.

p-0127The 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 <figref idrefs="DRAWINGS">FIG. 3D</figref>.

p-0128Thus 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.

p-0129TABLE IV below summarizes the behavior of the special protection components of system <b>100</b> during production mode. Reference is also made to <figref idrefs="DRAWINGS">FIG. 4</figref>, which is a simplified flowchart of a data protection method corresponding to TABLE IV. <figref idrefs="DRAWINGS">FIG. 4</figref> is divided into four columns. The leftmost column indicates steps performed by source side protection agent <b>112</b>, the middle left column indicates steps performed by source side DPA <b>144</b>, the middle right column indicates steps performed by target side DPA <b>124</b>, and the rightmost column indicates steps performed by target side protection agent <b>164</b>.

p-0130<tables id="TABLE-US-00004" num="00004"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217pt" align="center" /><thead><row><entry namest="1" nameend="1" rowsep="1">TABLE IV</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Normal Production Mode Functionality</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="49pt" align="left" /><colspec colname="2" colwidth="168pt" align="left" /><tbody valign="top"><row><entry>System </entry><entry /></row><row><entry>Component</entry><entry>Behavior</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>Source Side </entry><entry>Intercept SCSI commands issued to LU A by</entry></row><row><entry>Agent 144</entry><entry>source side host via Device A (step 404). Replicate write</entry></row><row><entry /><entry>commands, and route write commands to DPA (steps 408</entry></row><row><entry /><entry>and 412). Wait for first acknowledgement, from DPA</entry></row><row><entry /><entry>(step 416), and then route replicate I/O command to LU A</entry></row><row><entry /><entry>(step 420). Wait for second acknowledgement, from</entry></row><row><entry /><entry>storage system (step 424), and then process next</entry></row><row><entry /><entry>intercepted SCSI command (step 404).</entry></row><row><entry>Source Side </entry><entry>Receive write command from agent (step 428).</entry></row><row><entry>DPA 112</entry><entry>Format write command as write transaction, and send to</entry></row><row><entry /><entry>target DPA (step 428). In synchronous mode, wait for</entry></row><row><entry /><entry>acknowledgement from target DPA (step 432), and then</entry></row><row><entry /><entry>send acknowledgement to agent (step 436). In</entry></row><row><entry /><entry>asynchronous mode and in snapshot mode, send</entry></row><row><entry /><entry>acknowledgement to agent without waiting for</entry></row><row><entry /><entry>acknowledgement from target DPA (step 436).</entry></row><row><entry>Target Side</entry><entry>Receive write transaction from source DPA (step</entry></row><row><entry>DPA 124</entry><entry>444). Enter write transaction in journal DO and DO</entry></row><row><entry /><entry>METADATA streams (step 444), and send back</entry></row><row><entry /><entry>acknowledgement to source DPA (step 448). Process</entry></row><row><entry /><entry>journal entries by applying them to LU B, and enter undo</entry></row><row><entry /><entry>information in UNDO and UNDO METADATA streams</entry></row><row><entry /><entry>(step 440).</entry></row><row><entry>Target Side </entry><entry>Fail SCSI commands issued to LU B (step 452).</entry></row><row><entry>Agent 164</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0131Only steps with arrows connecting them in <figref idrefs="DRAWINGS">FIG. 4</figref> are necessarily sequential. Thus steps <b>432</b> and <b>436</b>, which do not have arrows connecting them, are not necessarily sequential. In synchronous mode these steps are sequential, but in asynchronous mode and in snapshot mode they are not sequential. In particular, DPA <b>112</b> may send an acknowledgement to protection agent <b>144</b> before receiving an acknowledgement back from DPA <b>124</b>.

p-0132It is also noted in <figref idrefs="DRAWINGS">FIG. 4</figref> that the steps performed by target side DPA <b>124</b> include two non-sequential groups; namely, (i) step <b>440</b>, and (ii) steps <b>444</b> and <b>448</b>.

p-0133Recovery 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.

p-0134While in recovery mode, target site DPA <b>124</b> continues to receive new write transactions from DPA <b>112</b> and enter them at the ends of the DO and DO METADATA streams. However, unlike production mode behavior, DPA <b>124</b> stops applying journal entries received from DPA <b>112</b> to LU B. Instead, DPA <b>124</b> uses the UNDO stream of the journal to rollback LU B, as described hereinabove.

p-0135During 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 <b>164</b> stops failing I/O requests issued by host computer <b>160</b> and begins redirecting them to DPA <b>124</b>. The processing of data by host computer <b>160</b> during recovery mode is referred to as “target side processing (TSP)”.

p-0136To manage TSP write commands that are received by target side DPA <b>124</b>, journal processor <b>180</b> uses two additional data streams, referred to as TSP DO and TSP METADATA streams. When a TSP write command is received by DPA <b>124</b>, 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 <b>180</b> applies TSP writes to LU B in a way similar to the way it applies write transactions deceiver from DPA <b>112</b>; namely, journal processor <b>180</b> maintains the undo information for each write applied to LU B, in TSP UNDO and TSP UNDO METADATA streams.

p-0137When TSP read commands are received by target site DPA <b>124</b>, DPA <b>124</b> 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 <b>124</b> 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.

p-0138After rollback is completed, the TSP writes that were performed during the rollback are applied to LU B, and DPA <b>124</b> begins applying TSP writes synchronously; i.e., TSP writes are applied to LU B when they are received by DPA <b>124</b>, 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 <b>124</b>.

p-0139TABLES V and VI below summarize the behavior of the special protection components of system <b>100</b> during recovery mode, before and after the rollback is complete, in accordance with an embodiment of the present invention. Reference is also made to <figref idrefs="DRAWINGS">FIGS. 5 and 6</figref>, which are simplified flowcharts of data protection methods corresponding to TABLES V and VI, respectively. <figref idrefs="DRAWINGS">FIGS. 5 and 6</figref> are divided into four columns. The leftmost column indicates steps performed by target side protection agent <b>164</b>, the middle left column indicates steps performed by target side DPA <b>124</b>, the middle right column indicates steps performed by source side DPA <b>112</b>, and the rightmost column indicates steps performed by source side protection agent <b>144</b>.

p-0140<tables id="TABLE-US-00005" num="00005"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217pt" align="center" /><thead><row><entry namest="1" nameend="1" rowsep="1">TABLE V</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Recovery Functionality prior to Completion of Rollback</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="49pt" align="left" /><colspec colname="2" colwidth="168pt" align="left" /><tbody valign="top"><row><entry>System </entry><entry /></row><row><entry>Component</entry><entry>Behavior</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>Target Side </entry><entry>Intercept SCSI commands issued to LU B (step</entry></row><row><entry>Agent 164</entry><entry>576). Redirect commands to DPA (step 580).</entry></row><row><entry>Target Side </entry><entry>Use UNDO stream of journal to roll back target</entry></row><row><entry>DPA 124</entry><entry>storage system (step 540). Continue receiving write</entry></row><row><entry /><entry>transactions from DPA 112 and enter these transactions</entry></row><row><entry /><entry>into DO and DO METADATA streams without applying</entry></row><row><entry /><entry>them to LU B (step 548). Enter TSP write transactions to</entry></row><row><entry /><entry>TSP DO and TSP DO METADATA streams (step 564).</entry></row><row><entry /><entry>Create a virtual image, to reply to read commands issued</entry></row><row><entry /><entry>during the recovery process (step 572).</entry></row><row><entry>Source Side </entry><entry>As in production mode.</entry></row><row><entry>DPA 112</entry><entry /></row><row><entry>Source Side </entry><entry>As in production mode.</entry></row><row><entry>Agent 144</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0141<tables id="TABLE-US-00006" num="00006"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217pt" align="center" /><thead><row><entry namest="1" nameend="1" rowsep="1">TABLE VI</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Recovery Functionality after Completion of Rollback</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="49pt" align="left" /><colspec colname="2" colwidth="168pt" align="left" /><tbody valign="top"><row><entry>System </entry><entry /></row><row><entry>Component </entry><entry>Behavior</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>Target Side </entry><entry>Intercept SCSI commands issued to LU B (step</entry></row><row><entry>Agent 164</entry><entry>664). Redirect write transactions to DPA (step 672), and</entry></row><row><entry /><entry>route read commands directly to LU B (step 680).</entry></row><row><entry>Target Side </entry><entry>Apply TSP write transactions to LU B, in the same</entry></row><row><entry>DPA 124</entry><entry>manner that write transactions received from DPA 112 are</entry></row><row><entry /><entry>applied in production mode; i.e., by entering data into TSP</entry></row><row><entry /><entry>UNDO and TSP UNDO METADATA streams (step 640).</entry></row><row><entry /><entry>Enter DO information and write transactions received</entry></row><row><entry /><entry>from DPA 112 into DO and DO METADATA streams,</entry></row><row><entry /><entry>without applying them to LU B (step 644). Apply TSP</entry></row><row><entry /><entry>write transactions to LU B as they are received (step 656).</entry></row><row><entry>Source Side</entry><entry>As in production mode.</entry></row><row><entry>DPA 112</entry><entry /></row><row><entry>Source Side</entry><entry>As in production mode.</entry></row><row><entry>Agent 144</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0142It is also noted in <figref idrefs="DRAWINGS">FIG. 5</figref> that the steps performed by target side DPA <b>124</b> include three non-sequential groups; namely, (i) step <b>540</b>, (i) steps <b>548</b> and <b>552</b>, and (iii) steps <b>556</b>, <b>560</b>, <b>564</b>, <b>568</b> and <b>572</b>. Similarly in <figref idrefs="DRAWINGS">FIG. 6</figref> target side DPA performs three non-sequential groups of steps; namely, (i) step <b>640</b>, (ii) steps <b>644</b> and <b>648</b>, and (iii) steps <b>652</b>, <b>656</b> and <b>660</b>.

p-0143Reference is now made to <figref idrefs="DRAWINGS">FIG. 7</figref>, which is a simplified illustration of a time-line for tracking new processing of old data, in accordance with an embodiment of the present invention. <figref idrefs="DRAWINGS">FIG. 7</figref> illustrates journal processor <b>180</b> bringing the timeline back to a previous time, TOLD, and journal processor <b>180</b> applying TSP writes to bring the timeline forward from time TCURRENT to time TNEW. As shown in <figref idrefs="DRAWINGS">FIG. 7</figref>, current data at time (<b>1</b>) is rolled back to old data at time (<b>2</b>). After rolling back the data to time (<b>2</b>), the rolled back data becomes the image upon which target side processing advances to new data at time (<b>3</b>); i.e., the target side processing is applied to data (<b>2</b>) and not to data (<b>1</b>).

p-0144The data at time (<b>1</b>) is a common image for LU A and LU B at the same point in time, TCURRENT. Similarly, the data at time (<b>2</b>) is a common image for LU A and LU B at time TOLD. Rolled back data at time (<b>2</b>) may be processed by TSP writes, while at the same time current data at time (<b>1</b>) is being processed by source side writes. As such, the data evolves along the path from time (<b>2</b>) to time (<b>3</b>) as it is processed by the target side, and along the path from time (<b>2</b>) to time (<b>4</b>) as it is processed by the source side. The data images at the source and target sides at time TNEW are thus different.

p-0145When 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 (<b>2</b>), and the write transactions along the path from (<b>2</b>) to (<b>4</b>) 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 (<b>3</b>), 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.

p-0146It 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 <b>124</b> 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 <b>112</b> while DPA was in recovery mode. Similarly, protection agent <b>164</b> returns to its production mode by beginning to fail I/O requests issued by host <b>116</b>.

p-0147Alternatively, 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 <b>124</b> and protection agent <b>164</b> begin behaving in accordance with source site behavior, and DPA <b>112</b> and protection agent <b>144</b> begin behaving in accordance with target site behavior.

p-0148It 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 <b>184</b> and journal processor <b>188</b>, as indicated with dotted lines in <figref idrefs="DRAWINGS">FIG. 1</figref>.

p-0149Referring 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 <figref idrefs="DRAWINGS">FIG. 8</figref>, which is a simplified illustration of a 5-stage journaling process for continuous data replication, in accordance with an embodiment of the present invention. The five steps shown in <figref idrefs="DRAWINGS">FIG. 8</figref> correspond respectively to the five steps listed in TABLE I. For the sake of clarity, <figref idrefs="DRAWINGS">FIG. 8</figref> only shows three meta-data elements; namely, a size, a journal address and a storage address. It may be appreciated that the meta-data in the DO METADATA and UNDO METADATA streams includes an ID, a time, and other attributes.

p-0150In 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.

p-0151As 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 <b>2</b> may be skipped.

p-0152Reference is now made to <figref idrefs="DRAWINGS">FIG. 9</figref>, which is a simplified illustration of a 4-stage journaling process for continuous data replication, for use when an I/O data rate is low, in accordance with an embodiment of the present invention. The first step in <figref idrefs="DRAWINGS">FIG. 9</figref> copies the write transaction to the end of the DO stream and the end of the DO METADATA stream, as in the 5-stage journaling process. Unlike, the 5-stage journaling process, though, instead of reading write transaction data from the beginning of the DO and DO METADATA streams, the 4-stage journaling process takes advantage of the fact that the write transaction that was just received at the backup site is still resident in memory. For this write transaction, steps <b>3</b>-<b>5</b> are performed, as indicated in <figref idrefs="DRAWINGS">FIG. 9</figref>.

p-0153However, during the steps <b>3</b>-<b>5</b> 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 <b>3</b>-<b>5</b>, a subsequent write transaction is taken from the beginning of the queue. Effectively, the queue corresponds to a cached DO stream.

p-0154The 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.

p-0155Conversely, 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%.

p-0156The 3-stage mode eliminates steps <b>3</b> and <b>4</b> 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.

p-0157Reference is now made to <figref idrefs="DRAWINGS">FIG. 10</figref>, which is a simplified illustration of a 3-stage journaling process for continuous data replication, for use when the DO stream is near its maximum capacity, in accordance with an embodiment of the present invention.

p-0158TABLE VII summarizes the relative pros and cons of each of the journaling processes described hereinabove.

p-0159<tables id="TABLE-US-00007" num="00007"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217pt" align="center" /><thead><row><entry namest="1" nameend="1" rowsep="1">TABLE VII</entry></row></thead><tbody valign="top"><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>Pros and Cons of Journaling Processes</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="3"><colspec colname="1" colwidth="42pt" align="left" /><colspec colname="2" colwidth="84pt" align="left" /><colspec colname="3" colwidth="91pt" align="left" /><tbody valign="top"><row><entry>Journaling </entry><entry /><entry /></row><row><entry>Process</entry><entry>Pros</entry><entry>Cons</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row><row><entry>3-Stage </entry><entry>Fastest replication time</entry><entry>Long time to recover to</entry></row><row><entry>Journaling</entry><entry /><entry>current time</entry></row><row><entry>4-Stage </entry><entry>Moderate replication time;</entry><entry>Only able to be used as long</entry></row><row><entry>Journaling</entry><entry>Full data recovery capability</entry><entry>as the beginning and the end</entry></row><row><entry /><entry /><entry>of the DO stream are close</entry></row><row><entry>5-Stage </entry><entry>Full data recovery capability</entry><entry>Slowest replication time</entry></row><row><entry>Journaling</entry></row><row><entry namest="1" nameend="3" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

p-0160One 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.

p-0161Reference is now made to <figref idrefs="DRAWINGS">FIG. 11</figref>, which is a simplified state diagram of transitions between 5-stage, 4-stage and 3-stage journal processing, in accordance with an embodiment of the present invention. Shown in <figref idrefs="DRAWINGS">FIG. 11</figref> are three nodes, representing each of the journaling processes, and directed edges between the nodes corresponding to rules that govern transitions therebetween. As shown in <figref idrefs="DRAWINGS">FIG. 11</figref>, a 5-stage to 3-stage transition occurs when the size of the DO stream exceeds 80% of its allotted capacity, and a 3-stage to 5-stage transition occurs when the size of the DO stream falls under 75% of its allotted capacity. Similarly, a 5-stage to 4-stage transition occurs when the beginning and end of the DO stream are close; and a 4-stage to 5-stage transition occurs when the memory queue reaches its capacity.

p-0162It 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.

p-0163In 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.

p-0164Reference is now made to <figref idrefs="DRAWINGS">FIG. 12</figref>, which is a simplified illustration of a variant of the three-stage journaling process shown in <figref idrefs="DRAWINGS">FIG. 10</figref>, which may be used in an alternative embodiment of the present invention. The alternative 3-stage journaling proceeds according to the last three stages of the 4-stage journaling process. That is, the stage of writing to the DO stream is skipped within 4-stage journaling, for the alternative embodiment of 3-stage journaling. When performing 4-stage journaling, the backup site DPA (element <b>124</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>) can return an acknowledgement to the production site DPA (element <b>112</b> of <figref idrefs="DRAWINGS">FIG. 1</figref>) immediately after the first stage, when the write transaction is written to the DO stream. However, when performing the alternative 3-stage journaling, the backup site DPA must wait until the write transaction is written to storage, before it can return an acknowledgement to the production site DPA. Since the last three stages of 4-stage journaling can be performed in a separate thread than the thread that performs the first stage, the alternative 3-stage journaling may result in a longer time lag between the source and target sites.

p-0165In another aspect of the invention, a continuous data protection system with journaling includes anti-virus functionality. With this arrangement, anti-virus scanning can be offloaded from a production server, for example, to a replication side, for example. In one embodiment, journal data can be searched, such as after receiving a new virus update. In another embodiment, journal data can be used to mount a point in time image that enables searching at the file level. Searching can be performed efficiently by using the journal data to mount a point in time copy and searching only files or other data suspected for infection. The journal can be used to find the most recent clean, i.e., uninfected, image.

p-0166<figref idrefs="DRAWINGS">FIG. 13</figref> shows an exemplary continuous data protection system <b>1300</b> having an antivirus capability as part of the journaling functionality in accordance with exemplary embodiments of the invention. The CDP system <b>1300</b> has some commonality with the system <b>100</b> of <figref idrefs="DRAWINGS">FIG. 1</figref> with the addition of an antivirus module <b>1302</b> and an antivirus database <b>1304</b> to store virus signatures forming a part of the source (production) data protection appliance <b>112</b>. The target side data protection appliance <b>124</b> similarly includes an AV module <b>1350</b> and virus database <b>1352</b> to provide antivirus flexibility, such as synchronous and asynchronous mode antivirus detection and failover switches.

p-0167The methods and apparatus of exemplary embodiments of the invention may take the form, at least partially, of program code (i.e., instructions) embodied in tangible media, such as disks (element <b>5</b> in <figref idrefs="DRAWINGS">FIG. 13</figref>), CD-ROMs <b>6</b>, hard drives <b>7</b>, random access or read only-memory <b>8</b>, or any other machine-readable storage medium, including transmission medium. When the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention. The media can include portions in different system components, such as memory in a host, an application instance, and or, a management station. The methods and apparatus of the present invention may be embodied in the form of program code that may be implemented such that when the program code is received and loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention. When implemented on processor, the program code combines with the processor to provide a unique apparatus that operates analogously to specific logic circuits. The program code (software-based logic) for carrying out the method is embodied as part of the system described below. In addition, it is understood that functionality can be implemented in various hardware, software, and combinations of hardware and software to meet the needs of a particular application without departing from the invention.

p-0168In general, the AV module <b>1302</b> utilizes the journal data to enable offloading of virus detection processing from the production server of conventional systems. The journal data structures, e.g., the DO stream and UNDO stream, can be examined for the presence of virus signatures. Since journal entries are time-stamped, using point in time images the time of infection can be determined at the I/O level. That is, the I/O operation creating the virus infection can be identified and addressed. In one embodiment, each I/O operation is time stamped as part of the meta data in the meta data DO and UNDO stream. In another embodiment, the journal data is used to mount a point in time (PIT) image, which can be examined at the file level. Using the image, I/O operations can be replayed while checking for the presence of viruses.

p-0169<figref idrefs="DRAWINGS">FIG. 14</figref> shows an exemplary timeline in which a virus infection occurs at time t<b>0</b>. At time t<b>1</b>, an antivirus download updates the antivirus database and the remote user volumes mounted to point in time (PIT) t<b>1</b> are checked and found to have a virus. It is understood that the virus detection processing can also be performed on the source production site. When a virus is detected on the production site, the replicated site can be searched, such as by binary scan, for the PIT when the virus entered. Since journal data is time-stamped, the time of infection can be determined. A point-in-time image can be mounted using the journal, as described in detail above, to enable checking only data, e.g., files, that are suspected for infection. The system can automatically recover, repair, etc, the infected item, in a manner well known to one of ordinary skill in the art. Alternatively, the system can fail over, as described above.

p-0170In addition, since the virus can be found in the I/O operation that contained the virus, some forensic information can be obtained. For example, the machine/user associated with originating the virus can be identified. In addition, information on spreading the virus over time can be accumulated for later analysis. Further, malicious file deletions and/or corruptions may be traced to a particular user.

p-0171It is understood that a variety of searching protocols can be used to meet the needs of a particular application. That is, the DO stream, or portions of the DO stream, may be searched before the UNDO stream, or portions of the UNDO stream, based upon certain factors, such as time of virus signature update, size of DO stream, etc. In addition, the system can search for signatures in the journal, mounted point in time images, and virtual images. This enables virus searching/detection only in files that became infected in some (later) point in time.

p-0172<figref idrefs="DRAWINGS">FIGS. 15A-15C</figref> show exemplary virus detection scenarios. In <figref idrefs="DRAWINGS">FIG. 15A</figref>, a virus is detected at a first time tVD. The virus was detected during examination of the DO stream, the production site, and/or a mounted PIT on the replicated site. From analysis of the time-stamp information for the DO stream entry, a time of infection tVI can be determined. <figref idrefs="DRAWINGS">FIG. 15B</figref> shows a time of virus detection tVD and infection tVI during examination of the UNDO stream. <figref idrefs="DRAWINGS">FIG. 15C</figref> shows a time of virus detection tVD and time of infection tVI in the UNDO stream. After virus detection in the journal data, it may be desirable to mount a PIT image.

p-0173It understood that virus updates that are received may be treated differently than existing virus signatures. For example, recent virus updates, such as priority updates due to recent virus outbreak, can be processed to immediately search DO and UNDO streams.

p-0174In an exemplary embodiment, a point in time image for the time of detection is mounted for the time at which the virus signature was first detected. The image can be scanned to identify infected data.

p-0175In one embodiment, a PIT image is mounted and full virus scan is performed to identify/list infected files. A binary search is performed from a selected time, such as one day ago, to test all the files that are suspected to be infected. If the files are found to be clean, then infection occurred less than one day ago. So for example, an image from about twelve hours ago can then be scanned to detect the virus. A series of PIT images incrementally decreasing the amount of time into the past can mounted and scanned until the virus is detected. Once detected, PIT images going less far back in time can be mounted and examined until the time of first infection at the I/O level is identified. In an exemplary embodiment, only the first scan of the PIT image examines the entire image data, later scans examine only suspected files.

p-0176Since going to another PIT is relatively immediate, the process will be efficient to determine when a file is not infected in one I/O operation and is infected in the next I/O operation, i.e., the time/of infection. A full scan can be performed to ensure that no other files are infected.

p-0177The latest ‘good’ version of a file can be found even if other files are still infected. Using a point in time image, one can find the last uninfected version of a file using the latest timestamp the file was not infected even if not working at the file level since the system provides single I/O operation granularity.

p-0178<figref idrefs="DRAWINGS">FIG. 16</figref> shows an exemplary sequence of steps for using journal data in a continuous data protection system to detect virus infection in accordance with exemplary embodiments of the invention. In step <b>1600</b>, a continuous data protection system receives data to be stored. In step <b>1602</b>, a virus infection occurs that is unknown to the system. Processing by the CDP system continues and in step <b>1604</b> a virus update is received containing additional virus signatures. In step <b>1606</b>, the system scans the journal data for the virus signatures. A virus is detected in step <b>1608</b> for a give time-stamped journal entry. In step <b>1610</b>, a point in time image is mounted for further examination of the journal. In an exemplary embodiment, the point in time image corresponds to the time at which the virus was first detected.

p-0179In step <b>1612</b>, data, e.g., files associated with the first detection are flagged as suspect for infection. The detection process continues in step <b>1614</b> until the time/data of initial infection is identified. In an exemplary embodiment, an optional cleaning operation can be initiated in step <b>1616</b>. Repair/clean/quarantine processes are well known to one of ordinary skill in the art. In one embodiment, the file is cleaned without using conventional virus cleaning. Rather, once the data of first infection is identified and removed, PIT images after the time of infection will be clean.

p-0180<figref idrefs="DRAWINGS">FIG. 17</figref> shows a further exemplary sequence of steps for providing antivirus functionality in a continuous data protection system. In step <b>1700</b>, a data transaction occurs and in step <b>1702</b> a virus infection occurs. In step <b>1704</b>, a virus update is received containing new virus signatures. A point in time (PIT) image is mounted in step <b>1706</b> using the journal data to roll back data to a selected time. In step <b>1708</b>, the image is scanned and in step <b>1710</b> it is determined whether any infected files were found. If not, in step <b>1712</b>, another PIT image is mounted for a time not as far back in time as the first image. The new image is mounted in step <b>1706</b> and scanned for viruses in step <b>1708</b>.

p-0181If infected files were found in step <b>1710</b>, then in step <b>1714</b> it is determined whether the I/O is the time of first infection. If so, in step <b>1716</b> the I/O information is output to the user. If not, in step <b>1718</b>, a time for another PIT image is selected that is further back in time than the previous one for mounting in step <b>1706</b>.

p-0182An exemplary scenario for identifying the I/O of first infection in <figref idrefs="DRAWINGS">FIG. 18</figref>. The first PIT image PIT<b>1</b> is examined but no virus is found since the image is prior to the time of first infection. A second image PIT<b>2</b>, which is not as far back in time as the first image PIT<b>1</b>, is then mounted and examined. Again, no virus is found since the time is before the time of infection. A third image PIT<b>3</b> is mounted and examined. A virus is found since the image is after the time of infection. A fourth image PIT<b>4</b> is then mounted and examined. The fourth image PIT <b>4</b> is further back in time, but before the time of infection so no virus is found. This process continues until the I/O containing the infection is identified. That is, a first I/O operation is uninfected and the next I/O operation is infected. Since the images are at the file level, only suspect files can be examined for efficient identification of the problem I/O operation.

p-0183The present inventive embodiments enable anti-virus functionality to be offloaded from production resources to replica resources so that production processing is not bogged down by virus scanning. By using remote copy of the data to detect the virus, the more recent clean image can be identified from time-stamped journal entries. Also, new virus signatures can be applied retroactively due to the nature of the journal data.

p-0184While the invention is shown and described in conjunction with a particular embodiment 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.