Patent Grant
10983870
Current storage management systems employ a number of different methods to perform storage operations on electronic data. For example, data can be stored in primary storage as a primary copy that includes production data, or in secondary storage as various types of secondary copies including, as a backup copy, a snapshot copy, a hierarchical storage management copy (“HSM”), as an archive copy, and as other types of copies.
A primary copy of data is generally a production copy or other “live” version of the data that is used by a software application and is generally in the native format of that application. Primary copy data may be maintained in a local memory or other high-speed storage device that allows for relatively fast data access. Primary copy data is typically intended for short term retention (e.g., several hours or days) before some or all of the data is stored as one or more secondary copies, for example to prevent loss of data in the event a problem occurred with the data stored in primary storage.
Secondary copies include point-in-time data and are typically intended for long-term retention (e.g., weeks, months or years depending on retention criteria), before some or all of the data is moved to other storage or is discarded. Secondary copies may be indexed so users can later browse, search and restore the data. After primary copy data is backed up, a pointer or other location indicia such as a stub may be placed in the primary copy to indicate the current location of that data. Further details may be found in the assignee's U.S. Pat. No. 7,107,298, filed Sep. 30, 2002, entitled SYSTEM AND METHOD FOR ARCHIVING OBJECTS IN AN INFORMATION STORE.
One type of secondary copy is a backup copy. A backup copy is generally a point-in-time copy of the primary copy data stored in a backup format as opposed to in native application format. For example, a backup copy may be stored in a backup format that is optimized for compression and efficient long-term storage. Backup copies generally have relatively long retention periods and may be stored on media with slower retrieval times than other types of secondary copies and media (e.g., on magnetic tape), or be stored at on offsite location.
Another form of secondary copy is a snapshot copy. From an end-user viewpoint, a snapshot may be thought as a bitmap or instant image of the primary copy data at a given point in time. A snapshot may capture the directory structure of a primary copy volume at a particular moment in time, and may also preserve file attributes and contents. In some embodiments, a snapshot may exist as a virtual file system, parallel to the actual file system. Users may gain a read-only access to the record of files and directories of the snapshot. By electing to restore primary copy data from a snapshot taken at a given point in time (e.g., via a reversion process), users may also return the current file system to the prior state of the file system that existed when the snapshot was taken.
A snapshot may be created instantly, using a minimum of file space, but may still function as a conventional file system backup. A snapshot may not actually create another physical copy of all the data, but may simply create pointers that map files and directories to specific disk blocks and that indicate which blocks have changed. The snapshot may be a copy of a set of files and/or directories as they were at a particular point in the past. That is, the snapshot is an image, or representation, of a volume of data at a point in time. A snapshot may be as a secondary copy of a primary volume of data, such as data in a file system, an Exchange server, a SQL database, an Oracle database, and so on. The snapshot may be an image of files, folders, directories, and other data objects within a volume, or an image of the blocks of the volume.
Snapshots may be created using various techniques, such as copy-on-write, redirect-on-write, split mirror, copy-on-write with background copy, log structure file architecture techniques, continuous data protection techniques, and/or other techniques. Once a snapshot has been taken, subsequent changes to the file system typically do not overwrite the blocks in use at the time of a snapshot. Therefore, the initial snapshot may use only a small amount of disk space to record a mapping or other data structure representing or otherwise tracking the blocks that correspond to the current state of the file system. Additional disk space is usually only required when files and directories are actually modified later. Furthermore, when files are modified, typically only the pointers which map to blocks are copied when taking a new snapshot, not the blocks themselves. For example in the case of copy-on-write snapshots, when a block changes in primary storage, the block is copied to secondary storage before the block is overwritten in primary storage and the snapshot mapping of file system data is updated to reflect the changed block(s) at that particular point in time, e.g., the pointer in that snapshot now points to the old block now in secondary storage.
Data storage systems may utilize snapshots for a variety of reasons. One typical use of snapshots is to copy a volume of data without disabling access to the volume for a long period. After performing the snapshot, the data storage system can then copy the data set by leveraging the snapshot of the data set. As another example, a data storage system may use a snapshot and/or other point-in-time secondary copies (e.g., copies generated from a snapshot) to permit a user to revert data back to its state at a specific point in time during a reversion process.
An HSM copy is generally a copy of the primary copy data, but which typically includes only a subset of the primary copy data that meets a certain criteria and is usually stored in a format other than the native application format. For example, an HSM copy might include only that data from the primary copy that is larger than a given size threshold or older than a given age threshold and that is stored in a backup format. Often, HSM data is removed from the primary copy, and an address, pointer or stub is stored in the primary copy to indicate its new location. When a user requests access to the HSM data that has been removed or migrated, systems use the stub to locate the data and often make recovery of the data appear transparent even though the HSM data may be stored at a location different from the remaining primary copy data.
An archive copy is generally similar to an HSM copy, however the data satisfying criteria for removal from the primary copy is generally completely removed with no stub left in the primary copy to indicate the new location (i.e., where it has been moved to). Archive copies of data are generally stored in a backup format or other non-native application format. In addition, archive copies are generally retained for very long periods of time (e.g., years) and in some cases are never deleted. Such archive copies may be made and kept for extended periods in order to meet compliance regulations or for other permanent storage applications.
Application data over its lifetime typically moves from more expensive quick access storage to less expensive slower access storage. This process of moving data through these various tiers of storage is sometimes referred to as information lifecycle management (“ILM”). This is the process by which data is “aged” from more expensive forms of secondary storage with faster access/restore times down through less expensive secondary storage with slower access/restore times, for example, as the data becomes less important or mission critical.
In some embodiments, storage management systems may perform additional operations upon copies, including deduplication, content indexing, data classification, data mining or searching, electronic discovery (E-discovery) management, collaborative searching, encryption and compression.
One example of a system that performs storage operations on electronic data that produce such copies is the Simpana storage management system by CommVault Systems of Oceanport, N.J. The Simpana system leverages a modular storage management architecture that may include, among other things, storage manager components, client or data agent components, and media agent components as further described in U.S. Pat. No. 7,246,207, filed Apr. 5, 2004, entitled “SYSTEM AND METHOD FOR DYNAMICALLY PERFORMING STORAGE OPERATIONS IN A COMPUTER NETWORK.” The Simpana system also may be hierarchically configured into backup cells to store and retrieve backup copies of electronic data as further described in U.S. Pat. No. 7,395,282, filed Jul. 15, 1999, entitled “HIERARCHICAL BACKUP AND RETRIEVAL SYSTEM.”
The Simpana system and other storage systems may perform backup and Direct Access Recovery (“DAR”) storage operations under the Network Data Management Protocol (“NDMP”), an open standard protocol for backups of heterogeneous network-attached storage across an enterprise. Under the NDMP standard, during backup, an NDMP data server is responsible for creating backup data and sending it to an NDMP mover in a data stream format specified by the NDMP protocol. To the NDMP mover, the data stream may appear to be simply a raw stream of bytes or bits. The NDMP mover is then responsible for writing the data stream to backup or secondary storage media, such as tape. The NDMP mover may be on the same physical machine as the data server, or different machine. During a restore or recovery of a backed-up data object, the NDMP data server is responsible for requesting NDMP-formatted backup data from the mover and restoring the data object to a target location from that backup data, e.g., a target location in primary storage. To request a backup copy of a data object, the NDMP data server sends an offset and length that identify the location of the data object in the original NDMP data stream that was sent to the NDMP mover at backup. Using the offset and length information provided by the NDMP data server, the NDMP mover retrieves the desired data from the backup media and returns it to the NDMP data server in the form of an NDMP-formatted data stream.
Unfortunately, NDMP standards do not readily facilitate restore operations if the NDMP mover modified the NDMP data stream via encryption, compression, deduplication, etc., before writing the data to tape or other secondary storage media. These modification techniques may alter the data in an unpredictable way. For example, when an NDMP data stream is deduplicated and/or compressed, the total size of the modified data that must be stored is typically much smaller than the size of the original NDMP data stream. However, the modified data is not simply a linearly “scaled down” version of the original data stream. Instead, the original data stream is scaled down unevenly in a manner that depends on the contents of the original data stream and/or the types of modification techniques that are applied to the original data stream. Since these modification techniques alter the data in an unpredictable manner, at the time of restore, the NDMP mover can no longer use the offset and length provided by the NDMP data server to correctly retrieve and return requested data objects. For example, if a data object was originally represented in an original NDMP backup data stream at offset OF1 and length L1, the modified version of that object may instead be stored in modified form with an offset OF2 and length L2; furthermore, there may be no closed-form mathematical relationship to automatically derive OF2 and L2 from OF1 and L1. Thus, if the data mover receives a request from an NDMP data server to retrieve an object using offset and length values OF1 and L1, the data mover may be unable to fulfill the request.
The Simpana system and other storage systems may also permit users to perform a reversion operation in order to return client data to a previous state at a specified point in time by using a previously obtained point-in-time copy, such as a snapshot copy or other secondary copy. However, this reversion operation will effectively erase all changes to that data that were made after the specified point in time. Thus, such a reversion operation is irreversible, since a user cannot undo the reversion operation in order to return data to its state at the time the reversion operation was performed.
The need exists for systems and methods that overcome the above problems, as well as systems and methods that provide additional benefits. Overall, the examples herein of some prior or related systems and methods and their associated limitations are intended to be illustrative and not exclusive. Other limitations of existing or prior systems and methods will become apparent to those of skill in the art upon reading the following detailed description.
In the drawings, the same reference numbers and acronyms identify elements or acts with the same or similar functionality for ease of understanding and convenience.
The headings provided herein are for convenience only and do not necessarily affect the scope or meaning of the claimed invention.
Overview
The systems and methods described herein permit storage systems to correctly perform direct access recovery of NDMP backup data that was modified prior to its storage in secondary storage media, such as tape. For example, as described in greater detail herein, the systems and methods may permit NDMP backup data to be encrypted, compressed, deduplicated, and/or otherwise modified prior to storage. During a direct access recovery operation, the systems and methods described herein permit an NDMP data server to use index information (such as logical offsets and/or lengths) generated by the NDMP data server in order to request an unmodified version of NDMP data that was previously stored in modified form.
The systems and methods described herein also permit a user to perform a precautionary snapshot of the current state of data (e.g., primary data) prior to reverting data to a previous state using point-in-time data. In this way, a reversion process becomes reversible, instead of irreversible, because data that would otherwise be erased or overwritten by a reversion process is first captured via a snapshot operation.
Various examples of the invention will now be described. The following description provides specific details for a thorough understanding and enabling description of these examples. One skilled in the art will understand, however, that the system may be practiced without many of these details. Additionally, some well-known structures or functions may not be shown or described in detail, so as to avoid unnecessarily obscuring the relevant description of the various examples.
The terminology used in the description presented below is intended to be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a detailed description of certain specific examples of the system. Certain terms may even be emphasized below; however, any terminology intended to be interpreted in any restricted manner will be overtly and specifically defined as such in this Detailed Description.
Suitable Environments
The clients 130, as part of their functioning, utilize data, which includes files, directories, metadata (e.g., access control lists (ACLs), descriptive metadata, and any creation/edit dates associated with the data), and other data objects, which may be stored in an associated primary data store 160. (More details as to the storage operations involving ACLs may be found in the assignee's U.S. patent application Ser. No. 12/058,518, entitled “SYSTEM AND METHOD FOR STORAGE OPERATION ACCESS SECURITY”, the entirety of which is incorporated by reference herein.)) The data of a client 130, which is stored in a primary data store 160, is generally a primary copy (e.g., a production copy). Although described as a “client” of the secondary storage computing device 165, a client 130 may in fact be a production server, such as a file server or Exchange server, which provides live production data to multiple user workstations as part of its function. During a copy, backup, snapshot, archive or other storage operation, the clients 130 send a copy of data objects in a primary data store 160 to the secondary storage computing device 165.
Some clients 130, such as client 1 and client 2, may include an NDMP data server 106 configured to permit the client to perform NDMP backup and direct access recovery (DAR) (or “restore”) storage operations, as described in greater detail herein. Some clients, such as client 1 and client N, may include a snapshot component 108 configured to permit the client to perform snapshot operations, including taking snapshots and performing data reversions from a snapshot or other point-in-time data, as described in greater detail herein. As shown in
The secondary storage computing device 165 may include various components that perform various functions. These components include an NDMP mover 170, a control module 168, a media daemon 172, a snapshot module 174, and an interface module 176. The NDMP mover permits the secondary storage computing device to perform NDMP backup and direct access recovery (DAR) storage operations, as described in greater detail herein. The NDMP mover is configured to communicate with the NDMP data server 106 during NDMP backup and restore operations. The control module is configured to control NDMP backup and restore operations, and the media daemon is configured to store and retrieve a modified version of an NDMP data stream in the storage device 115. The NDMP mover and/or media daemon are also configured to modify data received from the NDMP data server via operations such as deduplication, encryption, modification, indexing, and/or the addition of metadata, before the data is stored in the storage device 115. The snapshot module 174 is configured to facilitate snapshot operations upon data (e.g., data stored in primary data stores 160), and to permit a client 130 to revert to earlier versions of data using snapshots or other point-in-time data. The interface module 176 is configured to present user interfaces that permit a user to initiate a reversion operation and select options associated with that reversion. The functionality of each of these components is described in greater detail herein.
Together, the NDMP data server 106 on a client 130 and the NDMP mover 170 on the secondary storage computing device 165 facilitate NDMP backup and restore operations of the primary data in the client's associated primary data store 160. Turning to an NDMP backup operation first, generally speaking, the control module 168 communicates with the NDMP data server in order to configure and initiate an NDMP copy operation or “backup job” of a set of primary data from the primary data store (such as a volume, sub-client, or file system). For example, the control module may instruct the NDMP data server to package the set of primary data into an NDMP backup data stream and to send the NDMP data stream to a specified data port on the secondary storage computing device. The configuration of the backup operation, including which set of data is backed up and other configuration parameters, may be specified by a storage policy and/or schedule policy, as described in greater detail herein. The control module may also cause the NDMP mover 170 to begin listening for the incoming NDMP backup data stream on the specified port. In accordance with the control module's instructions and NDMP protocols, the NDMP data server packages up the specified set of primary data from the primary data store into an NDMP-formatted backup data stream and begins sending the data stream to the NDMP mover, which receives the data stream, e.g., at the specified port. The precise format of the NDMP data stream may be dependent upon the type of NDMP data server that is sending the stream, so that effectively the NDMP mover cannot parse or discern a file-level or directory-level organization within the NDMP data stream. Instead, from the NDMP mover's perspective, the NDMP data stream may be seen simply as an ordered collection, or stream, of raw bytes or bits that needs to be stored. Any contiguous subset of data within the NDMP data stream may be described by a “logical offset” and “logical length” that together indicate the position of the subset within the larger stream (e.g., at an offset from the origin or head of the stream).
As the NDMP backup data stream is received, the NDMP mover 170 takes additional steps to modify the data stream and store the modified data in a manner that permits later retrieval and restoration of a portion of the original received NDMP backup data stream. The NDMP mover 170 may set up a data pipeline from the NDMP mover to the media daemon 172 to convey the received data stream (or a modified form thereof) to the media daemon. The NDMP mover and/or the media daemon may perform modifying operations upon the received NDMP data stream (e.g., encryption, deduplication, compression, indexing, adding metadata). The NDMP mover may perform modifying operations before sending the modified data to the media daemon and/or the media daemon may modify the data it receives from the NDMP mover. The media daemon writes the modified data to a storage device 115 in chunks. As described in greater detail herein, the media daemon also generates mapping information for each chunk. The mapping information associates each chunk of modified data stored with (1) a “physical offset” and a “physical length” that reflect where the chunk of modified data is physically stored within the storage device, and (2) a logical offset and a logical length that are associated with the contiguous subset of the unmodified NDMP backup data stream that was received by the NDMP mover and subsequently modified to create the chunk of modified data. In other words, the mapping information correlates the original NDMP offset and length parameters with new physical locations on the storage device.
While it is packaging data and sending the NDMP backup data stream during a backup job, the NDMP data server 106 may also locally generate and/or store index information or file history information; alternatively, or additionally, the NDMP data server may embed such information within the NDMP backup data stream (e.g., at the beginning or end of the data stream). The index information or file history information may associate each data object (e.g., file, directory, or sub-file data object) embodied within the data stream with a logical offset and logical length of the data object within the original data stream (these values indicate the object's position or location in the stream) and/or provide information about directory structures or other logical organizations that may also be defined by logical offset and logical length descriptors. The NDMP data server may also intermittently or periodically provide such index information to the NDMP mover 170; for example, it may send the index information for a batch of objects in the backup job. The media daemon 172 may store this index information, e.g., in the storage device 115. However, the NDMP data server typically provides its index information post-hoc, after the related portion of the data stream has already been received, modified, and/or stored by the NDMP mover and/or media daemon. Thus, typically, the media daemon cannot use the received index information to generate a mapping of data objects to physical offsets in real-time as the modified data is being written to the storage device 115.
Turning now to an NDMP direct access recovery or restore operation, at a later time, the NDMP data server 106 may restore data objects that were backed up during a backup operation to a target location (e.g., a target location in primary data store 160). As part of the restoration, the NDMP mover may retrieve and echo back stored information about the NDMP backup operation or job, such as indexing information or file history information that was generated and sent by the NDMP data server 106 at the time of the backup operation. Using this index information (or other index information, e.g., information stored locally by the NDMP data server), the NDMP data server may send one or more requests for a portion of a specified NDMP backup stream by providing a desired logical offset and a logical length that identify a desired contiguous subset of the original, unmodified NDMP backup data stream sent during the backup job. The NDMP mover 170 may then send the provided logical offset and logical length to the media daemon, which utilizes the mapping information to translate the provided logical offset and logical length into physical offsets and physical lengths that reflect where a modified version of the requested subset of the data stream has been physically stored in the storage device 115. Using those physical offsets and lengths, the media daemon may retrieve or read the modified data from the storage device 115, convert the retrieved modified data back into an NDMP-formatted data stream that contains the backup data associated with the logical offset and logical length, and send the desired portion of the NDMP-formatted data stream back to the NDMP data server, e.g., via the NDMP mover. More details about NDMP backup and restore operations, including mapping information, are provided herein with respect to
Normally, a reversion process that involves reverting data to a previous state using point-in-time data such as a snapshot is “irreversible” because the reversion process may erase and/or overwrite all or portions of a table that indicates the current state of data (e.g., an active block table or block map) at the moment just before the reversion process is initiated and/or may overwrite blocks of data. Thus, effectively, a reversion process irreversibly erases or overwrites current data, since that data is no longer accessible to a user. As described in greater detail herein, the secondary storage computing device 165, including its snapshot module 174 and/or interface module 176, and/or the snapshot component 108 on a client 130 may permit a user to perform a precautionary snapshot of the current state of data (e.g., in a primary data store 160) prior to reverting data to a previous state using point-in-time data. In this way, the reversion process becomes reversible instead of irreversible, because data that would otherwise be erased or overwritten by a reversion process is captured via a snapshot.
The snapshot component 108 on the client 130 creates snapshots of the client's data. The snapshot component 108 includes software components and may also include hardware and/or firmware components. The snapshot component 108 may be provided in its entirety by a single entity (for example, a single vendor), or the snapshot component 108 may include sub-components that are provided by different entities (such as multiple vendors). In some examples, the snapshot component includes a Microsoft Volume Shadow Copy Service (VSS) sub-component and a software-based VSS provider sub-component that is provided by the assignee of the present application, CommVault Systems, Inc. In these examples, a data agent (not shown) associated with the client interacts with the Microsoft VSS sub-component to create snapshots. In other examples, in addition to or as an alternative to the software-based VSS provider sub-component, the snapshot component 108 includes other software-based VSS provider sub-components, such as a Microsoft system software provider, a Microsoft Data Protection Manager provider sub-component or a NetApp SnapManager provider sub-component. In other examples, in addition to the Microsoft VSS sub-component, the snapshot component 108 includes one or more hardware-based VSS provider sub-components, such as those provided by vendors such as Hewlett-Packard, EMC, NetApp, IBM, and other vendors. Those of skill in the art will understand that the snapshot component 108 may include various software-based and/or hardware-based sub-components, and may interact with other components in various ways in order to create snapshots of a client's data.
The snapshot component 108 may create snapshots using various techniques, such as copy-on-write, redirect-on-write, split mirror, copy-on-write with background copy, log structure file architecture techniques, continuous data protection techniques, and/or other techniques. The snapshot component 108 may also perform operations relating to reversion operations. The snapshot component 108 may store the created snapshots on a particular volume of the client 130.
The snapshot module 174 may also copy snapshots from the client 130 to another storage device, such as the storage device 115, and/or maintain index information for snapshots. The snapshot module may also utilize snapshots from a client to create other point-in-time secondary copies of a client's data. The snapshot module may also be configured to perform functions similar to the snapshot component 108.
The secondary storage computing device 165 also includes the interface module 176. The interface module 176 provides access to the copied snapshot data. The interface module 176 can be used to access data objects created in other types of secondary copies, such as backup copies, archive copies, and other types of copies. The interface module 176 can also be used to display to a user available snapshots or point-in time-copies of the data that can be used for reversion, recovery, or other purposes.
Snapshot operations and reversions from snapshots and other secondary copies are described in greater detail in commonly assigned applications U.S. Provisional Application No. 61/291,805, filed Dec. 31, 2009, entitled “SYSTEMS AND METHODS FOR ANALYZING SNAPSHOTS”, U.S. Provisional Application No. 61/291,803, filed Dec. 31, 2009, entitled “SYSTEMS AND METHODS FOR PERFORMING DATA MANAGEMENT OPERATIONS USING SNAPSHOTS”, and U.S. application Ser. No. 12/558,947, filed Sep. 14, 2009, entitled “USING A SNAPSHOT AS A DATA SOURCE,” now U.S. Published Application No. US 20100070726, all of which are hereby incorporated herein in their entirety.
The above system may be incorporated within a data storage system and may be subjected to or receive a data stream during a data copy operation. Referring to
The storage device 115 receives the data from the secondary storage computing device 165 and stores the data as a secondary copy, such as a backup copy, archive copy, and/or snapshot copy. Secondary storage devices may be magnetic tapes, optical disks, USB and other solid-state memory media, disk, and tape drives, and so on.
NDMP Backup Operation
Before beginning the process 300, a component of the secondary storage computing device 165, such as the control module 168, may trigger or initiate the backup operation or job in accordance with applicable storage and/or schedule policies, and/or at the request of other system components (such as a storage manager, discussed herein). For example, the control module may instruct an NDMP data server 106 resident on a client 130 to initiate an NDMP backup operation upon a subset of the client's data storage (e.g., a volume, sub-client, and/or file system) in an associated primary data store 160 and to send an NDMP backup data stream to a specified port. As another example, the control module may start an NDMP mover 170 process for the backup job and direct the NDMP mover to listen for an NDMP backup data stream at a specified port and/or may start a media daemon 172 process for the job. The control module may also take other steps, such as further configuring the NDMP backup operation (e.g., identifying a storage device 115 to use during the operation).
As shown, the process 300 begins at block 305, when the NDMP mover 170 receives an unmodified NDMP backup data stream from an NDMP data server 106 resident on a client 130, such as in response to an instruction sent to the NDMP data server. For example, the NDMP mover 170 may receive the stream by listening at a specified port.
At block 310, the NDMP mover 170 and/or another component such as the media daemon 172 modifies the received NDMP backup data stream by various modification procedures, such as the modification procedures described below. The examples of data modification procedures provided below are intended to be illustrative, not exhaustive, and any suitable data modification techniques may be employed at block 310. Furthermore, at block 310, the NDMP mover 170 or other components may perform any combination of modification procedures, such as those described below, and may perform modification procedures in any order. For example, more details regarding how the secondary storage computing device 165 can simultaneously support encryption, compression, and/or deduplication may be found in the assignee's U.S. application Ser. No. 12/145,342, filed Jun. 24, 2008, entitled “APPLICATION-AWARE AND REMOTE SINGLE INSTANCE DATA MANAGEMENT,” now U.S. Published Application No. US 20090319585. The NDMP mover 170 may perform some or all of the modification procedures before sending the data to the media daemon 172. Alternatively, or additionally, the media daemon may receive the NDMP data stream (either unmodified or modified) from the NDMP mover and perform modification procedures upon the data stream it receives.
As one example, at block 310, the NDMP mover 170 or the media daemon 172 may encrypt the received data stream using well-known techniques. For example, the system may employ encryption techniques that satisfy Federal Information Processing Standards (FIPS). Further details about encryption and encrypting copies of data may be found in commonly assigned U.S. Patent Publication No. US2008-0320319A1, filed on Mar. 31, 2008, entitled SYSTEM AND METHOD FOR ENCRYPTING SECONDARY COPIES OF DATA. As another example, the NDMP mover may compress the received data stream using well-known techniques. For example, the system may employ many different well-known techniques or applications for compressing data, including Lempel-Ziv (LZ) techniques, DEFLATE techniques, and LZ-Renau (LZR) techniques. As yet another example, at block 310, the NDMP mover may add additional metadata to the data stream.
As yet another example, at block 310, the NDMP mover 170 or the media daemon 172 may perform deduplication upon the received data stream, either before or after encryption and/or compression. Generally speaking, deduplication refers to storing a single or reduced number of instances of a unique data object or unique data block (or other multiple-byte or multiple-bit unit of data) in secondary storage. For example, the system may store in secondary storage one or more instances, but fewer than the total number of instances, of each unique data object or unique data block.
Overall, at block 310, the NDMP mover 170 or the media daemon 172 may perform object-level, sub-object-level, block-level or multi-byte-/multi-bit-level deduplication procedures and/or encryption procedures and/or compression procedures via techniques that create “chunk folders” and similar deduplication data structures.
In examples described in more detail in the assignee's U.S. patent application Ser. No. 12/565,576, filed Sep. 23, 2009, entitled “SYSTEMS AND METHODS FOR MANAGING SINGLE INSTANCING DATA,” now U.S. Published Application No. US 20100082672, the NDMP mover 170 or the media daemon 172 stores the modified data in a data structure comprising a chunk folder when performing object- or sub-object-level deduplication. Contained within the chunk folder are three container files: 1) a metadata file; 2) an “N” file; and 3) an “S” file. The three files are each logical containers of data. The “S” file stores deduplicated data (e.g., deduplicated files). The “N” file stores data that is not deduplicated (e.g., metadata, such as descriptive metadata associated with deduplicated files). The metadata file stores references to the location(s) of the data objects in the “S” file and the “N” file. Note that although three container files are described (S, N, and metadata index), a chunk folder may comprise more than one “S” file (e.g., S1, S2 . . . Sy, where y is an integer) to store deduplicated data and/or more than one “N” file (e.g., N1, N2 . . . Nz, where z is an integer). While described as being stored on the storage device 115, the “N” and metadata files may alternatively or additionally be stored elsewhere, such as on the secondary storage computing device and/or with a storage manager, described herein. The chunk folder and the container files may be equivalent to a directory and files (or folder and files) on a file system. For example, the chunk folder may be a directory and the container files may be files located within the directory. As another example, the chunk folder may be a file and the container files may be portions of the file. As another example, the container files may be collections of blocks, bytes, or bits grouped together. Those of skill in the art will understand that the chunk folder and the container files may be comprised in various data structures and are not limited to a directory and files within the directory.
During deduplication, an index file may be created within a data structure that consists of one or more stream headers and stream data. The stream header describes a data object contained in an “N” file or an “S” file (e.g., its location, its size, an offset within the file, etc.). The stream data contains the pointer to the data object contained in the “N” file or the “S” file. For example, the pointer may give its location within the “N” file or the “S” file. The location of the data object may be given by offsets within the “N” file or the “S” file. For example, its location may be given by a starting offset, and its length or size. As another example, its location may be given by a starting offset and an ending offset. As previously mentioned, the data object may be in an “S” file in another chunk folder, and the stream data would point to this “S” file in the other chunk folder (e.g., give its location in the “S” file in the other chunk folder). Each time the NDMP mover 170 or media daemon 172 places a data object in the “S” file, it may add a stream header and corresponding stream data to the index file.
In examples where block-level deduplication is performed at block 310, the data structures used to store modified data may include one or more volume folders, one or more chunk folders within a volume folder, and multiple files within a chunk folder. Each chunk folder includes a metadata file, a metadata index file, one or more container files, and a container index file. The metadata file stores non-deduplicated data blocks as well as links to deduplicated data blocks stored in container files. The metadata index file stores an index to the data in the metadata file. The container files store deduplicated data blocks. The container index file stores an index to the container files. Among other things, the container index file stores an indication of whether a corresponding block in a container file is referred to by a link in a metadata file. Those of skill in the art will understand that the volume folder and its constituent folders and files may be comprised in various data structures and are not limited to a directory and files within the directory; instead, e.g., they may be collections of blocks, bytes, or bits grouped together.
In some examples, chunk folders, volume folders, and/or their constituent files are stored in an archive file format. The archive file may be stored on various storage devices 115, such as on disk drives or on magnetic tapes, and may contain chunk folders and/or volume folders. The archive file may include, for example, a “chunk folder 0” located at offset 0, a “chunk folder 1” located at offset 5, a “chunk folder 2” located at offset 10, a “chunk folder 3” located at offset 15, and so on until a “chunk folder n” located at offset 65. The offsets may be expressed in relation to the start of the archive file. More details regarding a suitable archive file format may be found in the assignee's U.S. application Ser. No. 11/950,376, filed Dec. 4, 2007, entitled “SYSTEMS AND METHODS FOR CREATING COPIES OF DATA, SUCH AS ARCHIVE COPIES,” now U.S. Published Application US 20080229037, the entirety of which is incorporated by reference herein. An archive file may be considered as a container of data objects.
At block 310, modification procedures may be performed separately upon different subsets of the NDMP backup data stream. For example the procedures may be performed separately upon different subsets of the NDMP backup data stream that are associated with different “chunks,” as described in greater detail herein. For example, the NDMP mover 170 may perform a modification procedure or procedures (e.g., compression or encryption) upon the first 3 GB of an NDMP data stream as a subset, and then perform the same modification procedure upon the next 3 GB of an NDMP data stream as a subset.
Generally speaking, the modification operations performed at block 310 will create an unknown and unpredictable change in the volume of data that is needed to store the modified form of the received NDMP backup data stream. For example, if the received unmodified NDMP data stream is 1 GB, the volume of data needed to store the modified version of the NDMP data stream may be 1 GB, 0.75 GB, 0.2 GB, or any other value. The degree of change will depend on the contents of the data stream, the configuration settings, and the types and/or order of the modification operations that are performed at block 310. For example, deduplication will change (e.g., reduce) the volume of data that is stored during a backup or other storage operation; however, the amount of change is a function of the amount of redundancy that is present in a primary data set. As an example, if a received data set of 1 GB has 50% redundancy (e.g., each unique block appears twice), block-level deduplication may reduce the amount of data that is stored by approximately 50%. As another example, the level of compression achieved by a compression procedure may depend on the particular compression technique utilized. As yet another example, the addition of metadata prior to storage may increase the volume of the data that is stored. Furthermore, the modification procedures may create uneven volume changes through the entire NDMP data stream. For example, a deduplication procedure might reduce the first half of an NDMP data stream by a factor of two, but might reduce the second half of the NDMP data stream by a factor of three. Since the modification procedures change the volume of data in an unpredictable and/or uneven fashion, the logical offsets associated with the received original NDMP data stream may have no closed-form or predictable relationship to the offsets of a post-modification NDMP data stream or image.
At block 315, the NDMP mover 170 or media daemon 172 writes the modified data in “chunks” to the storage device 115. For example, the media daemon may write chunks of modified data to tape media. Each chunk written is a modified version of a contiguous subset of the received NDMP backup data stream that is associated with a certain logical offset and logical length.
In some examples, each “chunk” written at block 315 is a separate “chunk folder” and/or “volume folder” such as those deduplication data structures described previously. Alternatively, a “chunk” may be a sub-division of one of these deduplication data structures (e.g., a logical sub-division, a constituent file or folder, or an arbitrary sub-division (e.g., each chunk folder may be divided into approximately 0.5 GB chunks), a modified version of one of these deduplication data structures (e.g., a compressed version of a chunk folder), or a group of multiple deduplication data structures. In other examples, a “chunk” may simply refer to a subset of the modified data which is addressable (i.e., readable) by a media location, a physical offset, and a physical length (or a physical starting offset and physical ending offset). The length of each such chunk may be configurable. For example, at approximately every 1 GB “checkpoint” along the modified data stream, the media daemon 172 may simply define a new chunk.
In some examples, for each chunk, the media daemon 172 writes approximately 2 GB of modified data to the storage device 115. However, any chunk size may be used, and chunk size may be configurable, e.g., to tune the performance of restore operations. A storage policy may specify chunk size. Furthermore, during a single backup operation, chunk size may vary from one chunk to the next. Chunk size is typically expressed in terms of the amount of modified data that is written per chunk; however, the size of a chunk may instead be specified by or based on the amount of unmodified data that is associated with a given chunk and/or other characteristics of the unmodified data that is used to create a chunk. For example, each chunk may be chosen to correspond to approximately 5 GB of unmodified data, resulting in unevenly sized chunks being written during an operation. When chunks are stored in physical media, the series of chunks may or may not be stored sequentially or contiguously. Chunks also may or may not be demarcated or separated by separators such as file marks or separate file marks.
As described previously, the modifying operations performed at block 310 may destroy any relationship between the logical offset used by the NDMP data server 106 to identify a subset of the original NDMP data stream and the offsets of a post-modification NDMP data stream or image. Accordingly, at block 320, the NDMP mover 170 or media daemon 172 associates each chunk written with (1) the logical offset and logical length of the contiguous subset of the received original NDMP data stream that is now represented in modified form by the stored chunk, and (2) the physical offset and physical length indicative of where the chunk is stored within the storage device 115 (and possibly a physical media identifier that indicates the physical media on which the chunk is stored, such as a particular tape cassette). For example, at block 320, the NDMP mover or media daemon 172 may populate a table, such as the one shown in
At a later time, the modified data that is written at block 315 may be moved from one physical location to a different physical location during a subsequent storage operation. For example, during a scheduled archive storage operation, some portion of the modified data written at block 315 may be copied or transferred to a new archive file on a new tape. Thus, at decision block 325, the NDMP mover or media daemon 172 determines whether one or more chunks of data that were written at block 315 are being moved to a changed physical location during a storage operation. If not, then the process 300 returns. Otherwise, if one or more chunks are being moved, then at block 330 the NDMP mover or media daemon updates the physical offsets, physical lengths, and/or physical media identifiers to indicate the new physical storage locations of those chunks. The process 300 then returns.
(1) a job identifier (ID) column 402 indicative of the NDMP backup operation or job during which the chunk was written,
(2) a chunk ID column 405 indicative of a unique chunk identifier within an NDMP backup job,
(3) a logical offset and length column 410 indicative of the portion of the unmodified NDMP backup data stream that was received during a backup job, and that is now represented in a modified form by the physical chunk;
(4) a physical media ID column 415 indicative of the media upon which the chunk is stored (e.g., a tape ID number), and
(5) a physical offset and length column 420 indicative of a portion of the indicated physical media (e.g., tape) on which the chunk is physically stored.
The logical offset and length in the table are typically the same as the logical offset and length that the NDMP data server 106 would associate with the same subset of the unmodified NDMP backup data stream. For example, row 425 conveys mapping information for the first modified data chunk that was written as part of NDMP backup job number “A5629.” This chunk corresponds to a modified version of the subset of the unmodified NDMP backup data stream for the job that is identified by the logical offset LO1 and the logical length LL1. As shown in row 430, the chunk of modified data was written to physical media in the storage device 115 (e.g., tape) identified as “Media A,” with a physical offset PO1 and physical length PL1. Of course, the secondary storage computing device 165 may store such mapping information in any other suitable format (e.g., a relational database), and/or some of the mapping information shown in Table 4 may be stored in other components within a storage system (e.g., such as in a storage manager described herein).
NDMP Restore Operation
The process begins at block 505, when the NDMP mover 170 receives a request (e.g., a read request) to send a subset of an unmodified NDMP backup data stream associated with a particular backup operation or job. In order to identify the specific subset needed, the request may specify for example, a backup job identifier and/or a logical offset and logical length. The logical offset requested (“LOR”) at block 505 may correspond to or fall at the beginning, end, or middle of a data chunk that was created and stored during the backup operation. Furthermore the logical offset may correspond to or fall within the first, last, or an intermediate data chunk created during the specified job. Similarly, the specified logical offset and the logical length requested (“LLR”) may span more than one data chunk from the specified job.
At block 510, the NDMP mover 170 or media daemon 172 looks up the first chunk that is needed to satisfy the read request using the logical offset and logical length and any job identifier. To do so, the NDMP mover may use a job identifier and the logical offset and logical length as a lookup into a chunk mapping table or database, such as the example table shown in
At block 515, the NDMP mover 170 or media daemon 172 uses the chunk identifier determined at block 510 to look up the physical media identifier, physical offset, and physical length necessary to access the first needed chunk. To do so, the NDMP mover may use the chunk identifier as a lookup into a chunk mapping table or database, such as the example table shown in
At block 520, the NDMP mover 170 or media daemon 172 uses the retrieved media identifier, physical offset, and physical length retrieved at block 515 in order to read the chunk of modified data. In the previous example, the NDMP mover or media daemon may access a tape B and begin reading at physical offset PO2 until it has read data corresponding to physical length PL2.
At block 525, the NDMP mover 170 and/or media daemon 172 converts the chunk of modified data that is read at block 520 back into an unmodified NDMP data stream format by undoing or reversing each of the modifying procedures that was performed upon the original NDMP data stream. For example, the NDMP mover or media daemon may decompress compressed data, decrypt encrypted data, “rehydrate” deduplicated data by restoring multiple instances of data objects to the data stream, and/or remove metadata that was added during the backup operation. Various methods for reversing these modifying procedures are well-known in the art and/or are described in the commonly-assigned applications related to modification techniques that are incorporated by reference herein.
At block 530, the NDMP mover 170 or media daemon 172 scans the converted version of the chunk until it arrives at the logical offset needed to satisfy the data request. In the previous example, if the received requested logical offset LOR is equal to LO2+217, the NDMP mover may scan the converted version of chunk 2 until it reaches position 217 within the converted chunk. The NDMP mover may discard the preceding portion of the converted version of the chunk or cache it for later use (e.g., in local memory in order to respond quickly to anticipated read requests).
At block 535, the NDMP mover 170 uses the converted chunk to return an unmodified NDMP data stream starting at the requested logical offset, e.g., by sending it to a requesting NDMP data server 106. In the previous example, if the received requested logical offset LOR is equal to LO2+217, the NDMP mover may send a copy of the converted chunk starting at position 217. The NDMP mover will continue to send the unmodified NDMP data stream until the read request has been satisfied (i.e., the logical length requested has been reached) and/or the end of the converted chunk is reached.
Of course, blocks 520-535 may be performed in parallel to the extent that the modified data can be read, converted, scanned, and sent in a parallel manner. For example, the NDMP mover 170 and/or media daemon 172 may be reading the end of a stored chunk at the same time that it is converting a middle portion of the same chunk and sending the converted version of the first part of the same chunk. Similarly, the data that is being read, converted, scanned, and/or returned, may be buffered in any manner at any of blocks 520-535.
At decision block 540, the NDMP mover 170 or media daemon 172 determines whether it is necessary to read, convert, scan, and return a portion of another data chunk. For example, the NDMP mover may determine that the requested logical offset and logical length implicates more than one data block, because the requested subset of the NDMP data stream spans more than one chunk. If the NDMP mover determines that it needs to read another data chunk to satisfy the read request, the process may be repeated beginning at block 510, this time using an adjusted logical offset and logical length that reflect how a portion of the last chunk was read, converted, and sent to partially satisfy the read request.
Of course, different iterations of blocks 520-535 may be performed in parallel. For example, the NDMP mover 170 and/or media daemon 172 may be reading the beginning of a third physical chunk at the same time that it is converting a middle portion of a second physical chunk and sending the converted version of a first physical chunk.
In some examples, the NDMP mover 170 anticipates future read requests by buffering unmodified NDMP backup data that is obtained by reading and converting stored chunks. For example, at block 535, once the entire subset of the requested NDMP backup data stream corresponding to the requested logical offset LOR and logical length LLR has been sent, the NDMP mover may continue to buffer the contents of the converted chunk until it reaches the end of the converted chunk (or another point in the converted chunk). As another example, even if the read request does not require that the NDMP mover repeat steps 510-535 for another chunk (e.g., because the read request has been fully satisfied), the NDMP mover, at the conclusion of block 535, may look up the chunk that corresponds to the next or otherwise adjacent section of the NDMP backup data stream for the same job and perform blocks 515-535. While doing so, it may buffer the NDMP data generated at block 535. By doing so, the NDMP mover may be able to satisfy subsequent read requests more quickly, since often a series of read requests related to a restore operation implicate several subsets of a backup data stream that are near to one another.
Although the description of NDMP operations herein have primarily referred to sets of data as being associated with or addressable by an offset (e.g., either a physical offset or logical offset) and length (e.g., either a physical length or logical length), one having skill in the art will appreciate that this is equivalent to associating or addressing a subset of data by a starting offset and an ending offset, since these two quantities together inherently indicate a length.
Reversion Operation
As shown, the process begins at block 605, when the secondary storage computing device 165 receives a request to revert data to its earlier state at a previous time using previously obtained point-in-time data, such as an earlier snapshot copy or backup copy. For example, a user may utilize a graphical user interface, (e.g., provided by the interface module 176) to browse previous snapshots of client data. Those snapshots and other secondary copies available to the user may be stored in a primary data store 160 and/or may be stored in snapshot format or another secondary format in a secondary storage device, such as storage device 115. The user may indicate that he wishes to revert to all of the data captured by a particular snapshot or secondary copy or only a particular subset of the data captured by a particular snapshot or secondary copy (e.g., a particular logical unit, disk volume, file server volume, file, email object, etc.).
At block 610, the secondary storage computing device 165 presents the user with the option to take a snapshot of the current state of data that will be partially or wholly overwritten or erased as a result of the requested reversion process, e.g., a snapshot of a logical unit of data that will be partially or wholly overwritten. For example, using the interface module 176, the secondary storage computing device may present the user with an interface such as the example interface 700 shown in
Referring again to
At block 625, the secondary storage computing device 165 reverts the requested data using the point-in-time data (e.g., the snapshot or other secondary copy) indicated at block 605 using procedures such as those described previously and/or other techniques known in the art. For example, the secondary storage computing device may instruct the snapshot module 174 on the secondary storage computing device 165 and/or the snapshot component 108 on a client 130 to initiate a reversion operation, e.g., of a logical unit that is being reverted. After the reversion, the requested data may be brought back online.
Although not shown in
Suitable System
The system 250 may generally include combinations of hardware and software components associated with performing storage operations on electronic data. Storage operations include copying, backing up, creating, storing, retrieving, and/or migrating primary storage data (e.g., data stores 260 and/or 262) and secondary storage data (which may include, for example, snapshot copies, backup copies, hierarchical storage management (HSM) copies, archive copies, and other types of copies of electronic data stored on storage devices 215). The system 250 may provide one or more integrated management consoles for users or system processes to interface with in order to perform certain storage operations on electronic data as further described herein. Such integrated management consoles may be displayed at a central control facility or several similar consoles distributed throughout multiple network locations to provide global or geographically specific network data storage information.
In one example, storage operations may be performed according to various storage preferences, for example, as expressed by a user preference, a storage policy, a schedule policy, and/or a retention policy. A “storage policy” is generally a data structure or other information source that includes a set of preferences and other storage criteria associated with performing a storage operation. The preferences and storage criteria may include, but are not limited to, a storage location, relationships between system components, network pathways to utilize in a storage operation, data characteristics, compression or encryption requirements, preferred system components to utilize in a storage operation, a single instancing or variable instancing (or deduplication) policy to apply to the data, and/or other criteria relating to a storage operation. For example, a storage policy may indicate that certain data is to be stored in the storage device 215, retained for a specified period of time before being aged to another tier of secondary storage, copied to the storage device 215 using a specified number of data streams, etc.
A “schedule policy” may specify a frequency with which to perform storage operations and a window of time within which to perform them. For example, a schedule policy may specify that a storage operation is to be performed every Saturday morning from 2:00 a.m. to 4:00 a.m. In some cases, the storage policy includes information generally specified by the schedule policy. (Put another way, the storage policy includes the schedule policy.) A “retention policy” may specify how long data is to be retained at specific tiers of storage or what criteria must be met before data may be pruned or moved from one tier of storage to another tier of storage. Storage policies, schedule policies and/or retention policies may be stored in a database of the storage manager 205, to archive media as metadata for use in restore operations or other storage operations, or to other locations or components of the system 250.
The system 250 may comprise a storage operation cell that is one of multiple storage operation cells arranged in a hierarchy or other organization. Storage operation cells may be related to backup cells and provide some or all of the functionality of backup cells as described in the assignee's U.S. patent application Ser. No. 09/354,058, now U.S. Pat. No. 7,395,282, which is incorporated herein by reference in its entirety. However, storage operation cells may also perform additional types of storage operations and other types of storage management functions that are not generally offered by backup cells.
Storage operation cells may contain not only physical devices, but also may represent logical concepts, organizations, and hierarchies. For example, a first storage operation cell may be configured to perform a first type of storage operations such as HSM operations, which may include backup or other types of data migration, and may include a variety of physical components including a storage manager 205 (or management agent 231), a secondary storage computing device 265, a client 230, and other components as described herein. A second storage operation cell may contain the same or similar physical components; however, it may be configured to perform a second type of storage operation, such as storage resource management (SRM) operations, and may include monitoring a primary data copy or performing other known SRM operations.
Thus, as can be seen from the above, although the first and second storage operation cells are logically distinct entities configured to perform different management functions (i.e., HSM and SRM, respectively), each storage operation cell may contain the same or similar physical devices. Alternatively, different storage operation cells may contain some of the same physical devices and not others. For example, a storage operation cell configured to perform SRM tasks may contain a secondary storage computing device 265, client 230, or other network device connected to a primary storage volume, while a storage operation cell configured to perform HSM tasks may instead include a secondary storage computing device 265, client 230, or other network device connected to a secondary storage volume and not contain the elements or components associated with and including the primary storage volume. (The term “connected” as used herein does not necessarily require a physical connection; rather, it could refer to two devices that are operably coupled to each other, communicably coupled to each other, in communication with each other, or more generally, refer to the capability of two devices to communicate with each other.) These two storage operation cells, however, may each include a different storage manager 205 that coordinates storage operations via the same secondary storage computing devices 265 and storage devices 215. This “overlapping” configuration allows storage resources to be accessed by more than one storage manager 205, such that multiple paths exist to each storage device 215 facilitating failover, load balancing, and promoting robust data access via alternative routes.
Alternatively or additionally, the same storage manager 205 may control two or more storage operation cells (whether or not each storage operation cell has its own dedicated storage manager 205). Moreover, in certain embodiments, the extent or type of overlap may be user-defined (through a control console) or may be automatically configured to optimize data storage and/or retrieval.
Data agent 295 may be a software module or part of a software module that is generally responsible for performing storage operations on the data of the client 230 stored in data store 260/262 or other memory location. Each client 230 may have at least one data agent 295 and the system 250 can support multiple clients 230. Data agent 295 may be distributed between client 230 and storage manager 205 (and any other intermediate components), or it may be deployed from a remote location or its functions approximated by a remote process that performs some or all of the functions of data agent 295.
The overall system 250 may employ multiple data agents 295, each of which may perform storage operations on data associated with a different application. For example, different individual data agents 295 may be designed to handle Microsoft Exchange data, Lotus Notes data, Microsoft Windows 2000 file system data, Microsoft Active Directory Objects data, and other types of data known in the art. Other embodiments may employ one or more generic data agents 295 that can handle and process multiple data types rather than using the specialized data agents described above.
If a client 230 has two or more types of data, one data agent 295 may be required for each data type to perform storage operations on the data of the client 230. For example, to back up, migrate, and restore all the data on a Microsoft Exchange 2000 server, the client 230 may use one Microsoft Exchange 2000 Mailbox data agent 295 to back up the Exchange 2000 mailboxes, one Microsoft Exchange 2000 Database data agent 295 to back up the Exchange 2000 databases, one Microsoft Exchange 2000 Public Folder data agent 295 to back up the Exchange 2000 Public Folders, and one Microsoft Windows 2000 File System data agent 295 to back up the file system of the client 230. These data agents 295 would be treated as four separate data agents 295 by the system even though they reside on the same client 230.
Alternatively, the overall system 250 may use one or more generic data agents 295, each of which may be capable of handling two or more data types. For example, one generic data agent 295 may be used to back up, migrate and restore Microsoft Exchange 2000 Mailbox data and Microsoft Exchange 2000 Database data while another generic data agent 295 may handle Microsoft Exchange 2000 Public Folder data and Microsoft Windows 2000 File System data, etc.
Data agents 295 may be responsible for arranging or packing data to be copied or migrated into a certain format such as an archive file. Nonetheless, it will be understood that this represents only one example, and any suitable packing or containerization technique or transfer methodology may be used if desired. Such an archive file may include metadata, a list of files or data objects copied, the file, and data objects themselves. Moreover, any data moved by the data agents may be tracked within the system by updating indexes associated with appropriate storage managers 205 or secondary storage computing devices 265. As used herein, a file or a data object refers to any collection or grouping of bytes of data that can be viewed as one or more logical units.
Generally speaking, storage manager 205 may be a software module or other application that coordinates and controls storage operations performed by the system 250. Storage manager 205 may communicate with some or all elements of the system 250, including clients 230, data agents 295, secondary storage computing devices 265, and storage devices 215, to initiate and manage storage operations (e.g., backups, migrations, data recovery operations, etc.).
Storage manager 205 may include a jobs agent 220 that monitors the status of some or all storage operations previously performed, currently being performed, or scheduled to be performed by the system 250. (One or more storage operations are alternatively referred to herein as a “job” or “jobs.”) Jobs agent 220 may be communicatively coupled to an interface agent 225 (e.g., a software module or application). Interface agent 225 may include information processing and display software, such as a graphical user interface (“GUI”), an application programming interface (“API”), or other interactive interface through which users and system processes can retrieve information about the status of storage operations. For example, in an arrangement of multiple storage operations cells, through interface agent 225, users may optionally issue instructions to various storage operation cells regarding performance of the storage operations as described and contemplated herein. For example, a user may modify a schedule concerning the number of pending snapshot copies or other types of copies scheduled as needed to suit particular needs or requirements. As another example, a user may employ the GUI to view the status of pending storage operations in some or all of the storage operation cells in a given network or to monitor the status of certain components in a particular storage operation cell (e.g., the amount of storage capacity left in a particular storage device 215).
Storage manager 205 may also include a management agent 231 that is typically implemented as a software module or application program. In general, management agent 231 provides an interface that allows various management agents 231 in other storage operation cells to communicate with one another. For example, assume a certain network configuration includes multiple storage operation cells hierarchically arranged or otherwise logically related in a WAN or LAN configuration. With this arrangement, each storage operation cell may be connected to the other through each respective interface agent 225. This allows each storage operation cell to send and receive certain pertinent information from other storage operation cells, including status information, routing information, information regarding capacity and utilization, etc. These communications paths may also be used to convey information and instructions regarding storage operations.
For example, a management agent 231 in a first storage operation cell may communicate with a management agent 231 in a second storage operation cell regarding the status of storage operations in the second storage operation cell. Another illustrative example includes the case where a management agent 231 in a first storage operation cell communicates with a management agent 231 in a second storage operation cell to control storage manager 205 (and other components) of the second storage operation cell via management agent 231 contained in storage manager 205.
Another illustrative example is the case where management agent 231 in a first storage operation cell communicates directly with and controls the components in a second storage operation cell and bypasses the storage manager 205 in the second storage operation cell. If desired, storage operation cells can also be organized hierarchically such that hierarchically superior cells control or pass information to hierarchically subordinate cells or vice versa.
Storage manager 205 may also maintain an index, a database, or other data structure 211. The data stored in database 211 may be used to indicate logical associations between components of the system, user preferences, management tasks, media containerization and data storage information or other useful data. For example, the storage manager 205 may use data from database 211 to track logical associations between secondary storage computing device 265 and storage devices 215 (or movement of data as containerized from primary to secondary storage).
Generally speaking, the secondary storage computing device 265, which may also be referred to as a media agent, may be implemented as a software module that conveys data, as directed by storage manager 205, between a client 230 and one or more storage devices 215 such as a tape library, a magnetic media storage device, an optical media storage device, or any other suitable storage device. In one embodiment, secondary storage computing device 265 may be communicatively coupled to and control a storage device 215. A secondary storage computing device 265 may be considered to be associated with a particular storage device 215 if that secondary storage computing device 265 is capable of routing and storing data to that particular storage device 215.
In operation, a secondary storage computing device 265 associated with a particular storage device 215 may instruct the storage device to use a robotic arm or other retrieval means to load or eject a certain storage media, and to subsequently archive, migrate, or restore data to or from that media. Secondary storage computing device 265 may communicate with a storage device 215 via a suitable communications path such as a SCSI or Fibre Channel communications link. In some embodiments, the storage device 215 may be communicatively coupled to the storage manager 205 via a SAN.
Each secondary storage computing device 265 may maintain an index, a database, or other data structure 261 that may store index data generated during storage operations for secondary storage (SS) as described herein, including creating a metabase (MB). For example, performing storage operations on Microsoft Exchange data may generate index data. Such index data provides a secondary storage computing device 265 or other external device with a fast and efficient mechanism for locating data stored or backed up. Thus, a secondary storage computing device index 261, or a database 211 of a storage manager 205, may store data associating a client 230 with a particular secondary storage computing device 265 or storage device 215, for example, as specified in a storage policy, while a database or other data structure in secondary storage computing device 265 may indicate where specifically the data of the client 230 is stored in storage device 215, what specific files were stored, and other information associated with storage of the data of the client 230. In some embodiments, such index data may be stored along with the data backed up in a storage device 215, with an additional copy of the index data written to index cache in a secondary storage device. Thus the data is readily available for use in storage operations and other activities without having to be first retrieved from the storage device 215.
Generally speaking, information stored in cache is typically recent information that reflects certain particulars about operations that have recently occurred. After a certain period of time, this information is sent to secondary storage and tracked. This information may need to be retrieved and uploaded back into a cache or other memory in a secondary computing device before data can be retrieved from storage device 215. In some embodiments, the cached information may include information regarding format or containerization of archives or other files stored on storage device 215.
One or more of the secondary storage computing devices 265 may also maintain one or more single instance databases 223. Single instancing, a method of deduplication, generally refers to storing in secondary storage only a single instance of each data object (or data block) in a set of data (e.g., primary data). More details as to single instancing may be found in one or more of the following commonly-assigned U.S. patent applications: 1) U.S. application Ser. No. 11/269,512, filed Nov. 7, 2004, entitled “SYSTEM AND METHOD TO SUPPORT SINGLE INSTANCE STORAGE OPERATIONS,” now U.S. Published Application No. US 20060224846; 2) U.S. application Ser. No. 12/145,347, filed Jun. 24, 2007, entitled “APPLICATION-AWARE AND REMOTE SINGLE INSTANCE DATA MANAGEMENT,” now U.S. Published Application No. US 20090319534; 3) U.S. application Ser. No. 12/145,342, filed Jun. 24, 2008, entitled “APPLICATION-AWARE AND REMOTE SINGLE INSTANCE DATA MANAGEMENT,” now U.S. Published Application No. US 20090319585, 4) U.S. application Ser. No. 11/963,623, filed Dec. 21, 2007, entitled “SYSTEM AND METHOD FOR STORING REDUNDANT INFORMATION,” now U.S. Published Application No. US 20080243879; and 5) U.S. application Ser. No. 11/950,376, filed Dec. 4, 2007, entitled “SYSTEMS AND METHODS FOR CREATING COPIES OF DATA SUCH AS ARCHIVE COPIES,” now U.S. Published Application No. US 20080229037, each of which is incorporated by reference herein in its entirety.
In some examples, the secondary storage computing devices 265 maintain one or more variable instance databases. Variable instancing, a method of deduplication, generally refers to storing in secondary storage one or more instances, but fewer than the total number of instances, of each data block (or data object) in a set of data (e.g., primary data). More details as to variable instancing may be found in the commonly-assigned U.S. Provisional Application No. 61/164,803, filed Mar. 30, 2009, entitled “STORING A VARIABLE NUMBER OF INSTANCES OF DATA OBJECTS”.
In some embodiments, certain components may reside and execute on the same computer. For example, in some embodiments, a client 230 such as a data agent 295, or a storage manager 205, coordinates and directs local archiving, migration, and retrieval application functions as further described in the previously-referenced U.S. patent application Ser. No. 09/610,738. This client 230 can function independently or together with other similar clients 230.
As shown in
Moreover, in operation, a storage manager 205 or other management module may keep track of certain information that allows the storage manager 205 to select, designate, or otherwise identify metabases to be searched in response to certain queries as further described herein. Movement of data between primary and secondary storage may also involve movement of associated metadata and other tracking information as further described herein.
In some examples, primary data may be organized into one or more sub-clients. A sub-client is a portion of the data of one or more clients 230, and can contain either all of the data of the clients 230 or a designated subset thereof. As depicted in
Systems and modules described herein may comprise software, firmware, hardware, or any combination(s) of software, firmware, or hardware suitable for the purposes described herein. Software and other modules may reside on servers, workstations, personal computers, computerized tablets, PDAs, and other devices suitable for the purposes described herein. Modules described herein may be executed by a general-purpose computer, e.g., a server computer, wireless device, or personal computer. Those skilled in the relevant art will appreciate that aspects of the invention can be practiced with other communications, data processing, or computer system configurations, including: Internet appliances, hand-held devices (including personal digital assistants (PDAs)), wearable computers, all manner of cellular or mobile phones, multi-processor systems, microprocessor-based or programmable consumer electronics, set-top boxes, network PCs, mini-computers, mainframe computers, and the like. Indeed, the terms “computer,” “server,” “host,” “host system,” and the like, are generally used interchangeably herein and refer to any of the above devices and systems, as well as any data processor. Furthermore, aspects of the invention can be embodied in a special purpose computer or data processor that is specifically programmed, configured, or constructed to perform one or more of the computer-executable instructions explained in detail herein.
Software and other modules may be accessible via local memory, a network, a browser, or other application in an ASP context, or via another means suitable for the purposes described herein. Examples of the technology can also be practiced in distributed computing environments where tasks or modules are performed by remote processing devices, which are linked through a communications network, such as a Local Area Network (LAN), Wide Area Network (WAN), or the Internet. In a distributed computing environment, program modules may be located in both local and remote memory storage devices. Data structures described herein may comprise computer files, variables, programming arrays, programming structures, or any electronic information storage schemes or methods, or any combinations thereof, suitable for the purposes described herein. User interface elements described herein may comprise elements from graphical user interfaces, command line interfaces, and other interfaces suitable for the purposes described herein.
Examples of the technology may be stored or distributed on computer-readable media, including magnetically or optically readable computer disks, hard-wired or preprogrammed chips (e.g., EEPROM semiconductor chips), nanotechnology memory, biological memory, or other data storage media. Indeed, computer-implemented instructions, data structures, screen displays, and other data under aspects of the invention may be distributed over the Internet or over other networks (including wireless networks), on a propagated signal on a propagation medium (e.g., an electromagnetic wave(s), a sound wave, etc.) over a period of time, or they may be provided on any analog or digital network (packet switched, circuit switched, or other scheme).
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling or connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
The above Detailed Description is not intended to be exhaustive or to limit the invention to the precise form disclosed above. While specific examples for the invention are described above for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative implementations may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed or implemented in parallel, or may be performed at different times. Further any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges.
The teachings of the invention provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various examples described above can be combined to provide further implementations of the invention.
Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the invention can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further implementations of the invention.
These and other changes can be made to the invention in light of the above Detailed Description. While the above description describes certain examples of the invention and describes the best mode contemplated, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the system may vary considerably in its specific implementation, while still being encompassed by the invention disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the invention should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the invention with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific examples disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the invention encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the invention under the claims.
While certain aspects of the invention are presented below in certain claim forms, the applicant contemplates the various aspects of the invention in any number of claim forms. Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the invention. For example, while only one aspect of the invention is recited as a means-plus-function claim under 35 U.S.C sec. 112, sixth paragraph, other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under 35 U.S.C. § 112, will begin with the words “means for”, but use of the term “for” in any other context is not intended to invoke treatment under 35 U.S.C. § 112, ¶6.
This application is a continuation of U.S. patent application Ser. No. 15/419,272, filed Jan. 30, 2017, entitled DATA RECOVERY OPERATIONS, SUCH AS RECOVERY FROM MODIFIED NETWORK DATA MANAGEMENT PROTOCOL DATA, which is a continuation of U.S. patent application Ser. No. 15/005,209, filed Jan. 25, 2016, entitled DATA RECOVERY OPERATIONS, SUCH AS RECOVERY FROM MODIFIED NETWORK DATA MANAGEMENT PROTOCOL DATA, now U.S. Pat. No. 9,557,929, which is a divisional of U.S. patent application Ser. No. 13/241,625, filed Sep. 23, 2011, entitled DATA RECOVERY OPERATIONS, SUCH AS RECOVERY FROM MODIFIED NETWORK DATA MANAGEMENT PROTOCOL DATA, now U.S. Pat. No. 9,244,779, which claims the benefit of U.S. Patent Application No. 61/388,554, filed Sep. 30, 2010, entitled DATA RECOVERY OPERATIONS, SUCH AS RECOVERY FROM MODIFIED NETWORK DATA MANAGEMENT PROTOCOL DATA, each of which is hereby incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4686620 | Ng | Aug 1987 | A |
| 4914656 | Dunphy, Jr. | Apr 1990 | A |
| 4989205 | Dunphy, Jr. | Jan 1991 | A |
| 4989206 | Dunphy, Jr. | Jan 1991 | A |
| 4995035 | Cole et al. | Feb 1991 | A |
| 5005122 | Griffin et al. | Apr 1991 | A |
| 5077736 | Dunphy, Jr. | Dec 1991 | A |
| 5093912 | Dong et al. | Mar 1992 | A |
| 5133065 | Cheffetz et al. | Jul 1992 | A |
| 5193154 | Kitajima et al. | Mar 1993 | A |
| 5212772 | Masters | May 1993 | A |
| 5226157 | Nakano et al. | Jul 1993 | A |
| 5239647 | Anglin et al. | Aug 1993 | A |
| 5241164 | Pavlidis et al. | Aug 1993 | A |
| 5241668 | Eastridge et al. | Aug 1993 | A |
| 5241670 | Eastridge et al. | Aug 1993 | A |
| 5265159 | Kung | Nov 1993 | A |
| 5276860 | Fortier et al. | Jan 1994 | A |
| 5276867 | Kenley et al. | Jan 1994 | A |
| 5287500 | Stoppani, Jr. | Feb 1994 | A |
| 5321816 | Rogan et al. | Jun 1994 | A |
| 5333315 | Saether et al. | Jul 1994 | A |
| 5347653 | Flynn et al. | Sep 1994 | A |
| 5367698 | Webber et al. | Nov 1994 | A |
| 5410700 | Fecteau et al. | Apr 1995 | A |
| 5412668 | Dewey | May 1995 | A |
| 5448724 | Hayashi | Sep 1995 | A |
| 5455926 | Keele et al. | Oct 1995 | A |
| 5491810 | Allen | Feb 1996 | A |
| 5495457 | Takagi | Feb 1996 | A |
| 5495607 | Pisello et al. | Feb 1996 | A |
| 5499364 | Klein et al. | Mar 1996 | A |
| 5504873 | Martin et al. | Apr 1996 | A |
| 5506986 | Healy | Apr 1996 | A |
| 5544345 | Carpenter et al. | Aug 1996 | A |
| 5544347 | Yanai et al. | Aug 1996 | A |
| 5548521 | Krayer et al. | Aug 1996 | A |
| 5559957 | Balk | Sep 1996 | A |
| 5608865 | Midgely et al. | Mar 1997 | A |
| 5619644 | Crockett et al. | Apr 1997 | A |
| 5638509 | Dunphy et al. | Jun 1997 | A |
| 5673381 | Huai et al. | Sep 1997 | A |
| 5677900 | Nishida et al. | Oct 1997 | A |
| 5699361 | Ding et al. | Dec 1997 | A |
| 5729743 | Squibb | Mar 1998 | A |
| 5751997 | Kullick et al. | May 1998 | A |
| 5758359 | Saxon | May 1998 | A |
| 5761677 | Senator et al. | Jun 1998 | A |
| 5764972 | Crouse et al. | Jun 1998 | A |
| 5778395 | Whiting et al. | Jul 1998 | A |
| 5812398 | Nielsen | Sep 1998 | A |
| 5813009 | Johnson et al. | Sep 1998 | A |
| 5813017 | Morris | Sep 1998 | A |
| 5815662 | Ong | Sep 1998 | A |
| 5832522 | Blickenstaff et al. | Nov 1998 | A |
| 5860068 | Cook | Jan 1999 | A |
| 5875478 | Blumenau | Feb 1999 | A |
| 5875481 | Ashton et al. | Feb 1999 | A |
| 5887134 | Ebrahim | Mar 1999 | A |
| 5893139 | Kamiyama et al. | Apr 1999 | A |
| 5898593 | Baca et al. | Apr 1999 | A |
| 5901327 | Ofek | May 1999 | A |
| 5924102 | Perks | Jul 1999 | A |
| 5950205 | Aviani, Jr. | Sep 1999 | A |
| 5958005 | Thorne et al. | Sep 1999 | A |
| 5974563 | Beeler, Jr. | Oct 1999 | A |
| 5978577 | Rierden et al. | Nov 1999 | A |
| 5983239 | Cannon et al. | Nov 1999 | A |
| 6014695 | Yamashita et al. | Jan 2000 | A |
| 6021415 | Cannon et al. | Feb 2000 | A |
| 6023705 | Bellinger et al. | Feb 2000 | A |
| 6026398 | Brown et al. | Feb 2000 | A |
| 6026414 | Anglin | Feb 2000 | A |
| 6052735 | Ulrich et al. | Apr 2000 | A |
| 6076148 | Kedem | Jun 2000 | A |
| 6088694 | Burns et al. | Jul 2000 | A |
| 6094416 | Ying | Jul 2000 | A |
| 6131095 | Low et al. | Oct 2000 | A |
| 6131099 | Johnson et al. | Oct 2000 | A |
| 6131147 | Takagi | Oct 2000 | A |
| 6131190 | Sidwell | Oct 2000 | A |
| 6137864 | Yaker | Oct 2000 | A |
| 6148412 | Cannon et al. | Nov 2000 | A |
| 6149316 | Harari et al. | Nov 2000 | A |
| 6154738 | Call | Nov 2000 | A |
| 6154787 | Urevig et al. | Nov 2000 | A |
| 6161111 | Mutalik et al. | Dec 2000 | A |
| 6167402 | Yeager | Dec 2000 | A |
| 6195794 | Buxton | Feb 2001 | B1 |
| 6212512 | Barney et al. | Apr 2001 | B1 |
| 6223205 | Harchol-Balter et al. | Apr 2001 | B1 |
| 6246882 | Lachance | Jun 2001 | B1 |
| 6260069 | Anglin | Jul 2001 | B1 |
| 6266678 | McDevitt et al. | Jul 2001 | B1 |
| 6266784 | Hsiao et al. | Jul 2001 | B1 |
| 6269382 | Cabrera et al. | Jul 2001 | B1 |
| 6269431 | Dunham | Jul 2001 | B1 |
| 6275953 | Vahalia et al. | Aug 2001 | B1 |
| 6301592 | Aoyama et al. | Oct 2001 | B1 |
| 6304880 | Kishi | Oct 2001 | B1 |
| 6308245 | Johnson et al. | Oct 2001 | B1 |
| 6324581 | Xu et al. | Nov 2001 | B1 |
| 6328766 | Long | Dec 2001 | B1 |
| 6330570 | Crighton | Dec 2001 | B1 |
| 6330572 | Sitka | Dec 2001 | B1 |
| 6330642 | Carteau | Dec 2001 | B1 |
| 6338006 | Jesionowski et al. | Jan 2002 | B1 |
| 6343324 | Hubis et al. | Jan 2002 | B1 |
| RE37601 | Eastridge et al. | Mar 2002 | E |
| 6353878 | Dunham | Mar 2002 | B1 |
| 6356801 | Goodman et al. | Mar 2002 | B1 |
| 6356901 | MacLeod et al. | Mar 2002 | B1 |
| 6366900 | Hu | Apr 2002 | B1 |
| 6374336 | Peters et al. | Apr 2002 | B1 |
| 6389432 | Pothapragada et al. | May 2002 | B1 |
| 6418441 | Call | Jul 2002 | B1 |
| 6418478 | Ignatius et al. | Jul 2002 | B1 |
| 6421711 | Blumenau et al. | Jul 2002 | B1 |
| 6434682 | Ashton et al. | Aug 2002 | B1 |
| 6457017 | Watkins et al. | Sep 2002 | B2 |
| 6484166 | Maynard | Nov 2002 | B1 |
| 6487561 | Ofek et al. | Nov 2002 | B1 |
| 6490666 | Cabrera et al. | Dec 2002 | B1 |
| 6496744 | Cook | Dec 2002 | B1 |
| 6502205 | Yanai | Dec 2002 | B1 |
| 6519679 | Devireddy et al. | Feb 2003 | B2 |
| 6538669 | Lagueux, Jr. et al. | Mar 2003 | B1 |
| 6542972 | Ignatius et al. | Apr 2003 | B2 |
| 6550057 | Bowman-Amuah | Apr 2003 | B1 |
| 6564228 | O'Connor | May 2003 | B1 |
| 6615349 | Hair | Sep 2003 | B1 |
| 6616047 | Catan | Sep 2003 | B2 |
| 6658436 | Oshinsky et al. | Dec 2003 | B2 |
| 6658526 | Nguyen et al. | Dec 2003 | B2 |
| 6662281 | Ballard et al. | Dec 2003 | B2 |
| 6669832 | Saito et al. | Dec 2003 | B1 |
| 6674924 | Wright et al. | Jan 2004 | B2 |
| 6704839 | Butterworth et al. | Mar 2004 | B2 |
| 6721334 | Ketcham | Apr 2004 | B1 |
| 6732293 | Schneider | May 2004 | B1 |
| 6757794 | Cabrera et al. | Jun 2004 | B2 |
| 6771595 | Gilbert et al. | Aug 2004 | B1 |
| 6785078 | Basham et al. | Aug 2004 | B2 |
| 6789161 | Blendermann et al. | Sep 2004 | B1 |
| 6799258 | Linde | Sep 2004 | B1 |
| 6802025 | Thomas et al. | Oct 2004 | B1 |
| 6820035 | Zahavi | Nov 2004 | B1 |
| 6851031 | Trimmer et al. | Feb 2005 | B2 |
| 6862622 | Jorgensen | Mar 2005 | B2 |
| 6909356 | Brown et al. | Jun 2005 | B2 |
| 6922687 | Vernon | Jul 2005 | B2 |
| 6934879 | Misra et al. | Aug 2005 | B2 |
| 6941370 | Boies et al. | Sep 2005 | B2 |
| 6950723 | Gallo et al. | Sep 2005 | B2 |
| 6968351 | Butterworth | Nov 2005 | B2 |
| 6968479 | Wyatt et al. | Nov 2005 | B2 |
| 6972918 | Kokami et al. | Dec 2005 | B2 |
| 6973369 | Trimmer et al. | Dec 2005 | B2 |
| 6973553 | Archibald, Jr. et al. | Dec 2005 | B1 |
| 6983351 | Gibble et al. | Jan 2006 | B2 |
| 7006435 | Davies et al. | Feb 2006 | B1 |
| 7010387 | Lantry et al. | Mar 2006 | B2 |
| 7012529 | Sajkowsky | Mar 2006 | B2 |
| 7034683 | Ghazarian | Apr 2006 | B2 |
| 7035880 | Crescenti et al. | Apr 2006 | B1 |
| 7055059 | Yanai | May 2006 | B2 |
| 7058649 | Ough et al. | Jun 2006 | B2 |
| 7069466 | Trimmer et al. | Jun 2006 | B2 |
| 7082441 | Zahavi et al. | Jul 2006 | B1 |
| 7085786 | Carlson et al. | Aug 2006 | B2 |
| 7085904 | Mizuno et al. | Aug 2006 | B2 |
| 7093089 | de Brebisson | Aug 2006 | B2 |
| 7096269 | Yamagami | Aug 2006 | B2 |
| 7096315 | Takeda et al. | Aug 2006 | B2 |
| 7103619 | Rajpurkar et al. | Sep 2006 | B1 |
| 7103731 | Gibble et al. | Sep 2006 | B2 |
| 7103740 | Colgrove et al. | Sep 2006 | B1 |
| 7107298 | Prahlad et al. | Sep 2006 | B2 |
| 7107395 | Ofek et al. | Sep 2006 | B1 |
| 7118034 | Baldassari et al. | Oct 2006 | B2 |
| 7120823 | Foster et al. | Oct 2006 | B2 |
| 7130970 | Devassy et al. | Oct 2006 | B2 |
| 7136720 | Deckers | Nov 2006 | B2 |
| 7139931 | Horn | Nov 2006 | B2 |
| 7146377 | Nowicki et al. | Dec 2006 | B2 |
| 7155465 | Lee et al. | Dec 2006 | B2 |
| 7155486 | Aoshima et al. | Dec 2006 | B2 |
| 7162496 | Amarendran et al. | Jan 2007 | B2 |
| 7162604 | Nourmohamadian et al. | Jan 2007 | B1 |
| 7162693 | Yamanaka et al. | Jan 2007 | B2 |
| 7165059 | Shah et al. | Jan 2007 | B1 |
| 7191283 | Amemiya et al. | Mar 2007 | B2 |
| 7197490 | English | Mar 2007 | B1 |
| 7200621 | Beck et al. | Apr 2007 | B2 |
| 7203944 | van Rietschote et al. | Apr 2007 | B1 |
| 7209949 | Mousseau et al. | Apr 2007 | B2 |
| 7213118 | Goodman et al. | May 2007 | B2 |
| 7216244 | Amano | May 2007 | B2 |
| 7237080 | Green | Jun 2007 | B2 |
| 7240238 | Yanai | Jul 2007 | B2 |
| 7246140 | Therrien et al. | Jul 2007 | B2 |
| 7246207 | Kottomtharayil et al. | Jul 2007 | B2 |
| 7246258 | Chen et al. | Jul 2007 | B2 |
| 7251218 | Jorgensen | Jul 2007 | B2 |
| 7275063 | Horn | Sep 2007 | B2 |
| 7277246 | Barbian et al. | Oct 2007 | B2 |
| 7277953 | Wils et al. | Oct 2007 | B2 |
| 7281032 | Kodama | Oct 2007 | B2 |
| 7287047 | Kavuri | Oct 2007 | B2 |
| 7293133 | Colgrove et al. | Nov 2007 | B1 |
| 7302539 | Korgaonkar | Nov 2007 | B2 |
| 7302540 | Holdman et al. | Nov 2007 | B1 |
| 7315923 | Retnamma et al. | Jan 2008 | B2 |
| 7343356 | Prahlad et al. | Mar 2008 | B2 |
| 7343453 | Prahlad et al. | Mar 2008 | B2 |
| 7343459 | Prahlad et al. | Mar 2008 | B2 |
| 7346623 | Prahlad et al. | Mar 2008 | B2 |
| 7346751 | Prahlad et al. | Mar 2008 | B2 |
| 7379850 | Sprogis et al. | May 2008 | B2 |
| 7395282 | Crescenti et al. | Jul 2008 | B1 |
| 7395387 | Berkowitz et al. | Jul 2008 | B2 |
| 7395446 | Luke et al. | Jul 2008 | B2 |
| 7398524 | Shapiro | Jul 2008 | B2 |
| 7401728 | Markham et al. | Jul 2008 | B2 |
| 7412433 | Anglin et al. | Aug 2008 | B2 |
| 7418464 | Cannon et al. | Aug 2008 | B2 |
| 7421312 | Trossell | Sep 2008 | B2 |
| 7434090 | Hartung et al. | Oct 2008 | B2 |
| 7434097 | Guha | Oct 2008 | B2 |
| 7447907 | Hart, III et al. | Nov 2008 | B2 |
| 7451283 | Chen et al. | Nov 2008 | B2 |
| 7454569 | Kavuri et al. | Nov 2008 | B2 |
| 7467167 | Patterson | Dec 2008 | B2 |
| 7472238 | Gokhale et al. | Dec 2008 | B1 |
| 7500053 | Kavuri et al. | Mar 2009 | B1 |
| 7529782 | Prahlad et al. | May 2009 | B2 |
| 7536424 | Barzilai et al. | May 2009 | B2 |
| 7539702 | Deshmukh et al. | May 2009 | B2 |
| 7539783 | Kochunni et al. | May 2009 | B2 |
| 7565340 | Herlocker et al. | Jul 2009 | B2 |
| 7581011 | Teng | Aug 2009 | B2 |
| 7584227 | Gokhale et al. | Sep 2009 | B2 |
| 7584298 | Klinker et al. | Sep 2009 | B2 |
| 7587749 | Leser et al. | Sep 2009 | B2 |
| 7596586 | Gokhale et al. | Sep 2009 | B2 |
| 7603518 | Kottomtharayil | Oct 2009 | B2 |
| 7613752 | Prahlad et al. | Nov 2009 | B2 |
| 7617262 | Prahlad et al. | Nov 2009 | B2 |
| 7617392 | Hair | Nov 2009 | B2 |
| 7627617 | Kavuri et al. | Dec 2009 | B2 |
| 7644245 | Prahlad et al. | Jan 2010 | B2 |
| 7653671 | Ikezawa et al. | Jan 2010 | B2 |
| 7657666 | Kottomtharayil et al. | Feb 2010 | B2 |
| 7659820 | Schnee et al. | Feb 2010 | B2 |
| 7660812 | Findlay et al. | Feb 2010 | B2 |
| 7680843 | Panchbudhe et al. | Mar 2010 | B1 |
| 7689510 | Lamkin et al. | Mar 2010 | B2 |
| 7693832 | Vargas et al. | Apr 2010 | B2 |
| 7702659 | Ban et al. | Apr 2010 | B2 |
| 7702831 | Ma et al. | Apr 2010 | B2 |
| 7707060 | Chainer et al. | Apr 2010 | B2 |
| 7712094 | Shapiro | May 2010 | B2 |
| 7720817 | Stager et al. | May 2010 | B2 |
| 7734669 | Kottomtharayil | Jun 2010 | B2 |
| 7739450 | Kottomtharayil | Jun 2010 | B2 |
| 7739544 | Yamato | Jun 2010 | B2 |
| 7747579 | Prahlad et al. | Jun 2010 | B2 |
| 7748610 | Bell et al. | Jul 2010 | B2 |
| 7751628 | Reisman | Jul 2010 | B1 |
| 7765167 | Prahlad et al. | Jul 2010 | B2 |
| 7765369 | Prahlad et al. | Jul 2010 | B1 |
| 7783608 | Shitomi | Aug 2010 | B2 |
| 7805416 | Compton et al. | Sep 2010 | B1 |
| 7809699 | Passmore et al. | Oct 2010 | B2 |
| 7809914 | Kottomtharayil et al. | Oct 2010 | B2 |
| 7818417 | Ginis et al. | Oct 2010 | B2 |
| 7818535 | Bono et al. | Oct 2010 | B1 |
| 7822715 | Petruzzo | Oct 2010 | B2 |
| 7831566 | Kavuri et al. | Nov 2010 | B2 |
| 7840537 | Gokhale et al. | Nov 2010 | B2 |
| 7844573 | Amarendran et al. | Nov 2010 | B2 |
| 7849266 | Kavuri et al. | Dec 2010 | B2 |
| 7861011 | Kottomtharayil et al. | Dec 2010 | B2 |
| 7873802 | Gokhale et al. | Jan 2011 | B2 |
| 7877351 | Crescenti et al. | Jan 2011 | B2 |
| 7877362 | Gokhale et al. | Jan 2011 | B2 |
| 7889847 | Gainsboro | Feb 2011 | B2 |
| 7890796 | Pawar et al. | Feb 2011 | B2 |
| 7904350 | Ayala et al. | Mar 2011 | B2 |
| 7917473 | Kavuri et al. | Mar 2011 | B2 |
| 7917695 | Ulrich et al. | Mar 2011 | B2 |
| 7934071 | Abe et al. | Apr 2011 | B2 |
| 7937365 | Prahlad et al. | May 2011 | B2 |
| 7937393 | Prahlad et al. | May 2011 | B2 |
| 7945810 | Soran et al. | May 2011 | B2 |
| 7953802 | Mousseau et al. | May 2011 | B2 |
| 7966293 | Owara et al. | Jun 2011 | B1 |
| 7969306 | Ebert et al. | Jun 2011 | B2 |
| 7975061 | Gokhale et al. | Jul 2011 | B1 |
| 7987319 | Kottomtharayil | Jul 2011 | B2 |
| 8005913 | Carlander | Aug 2011 | B1 |
| 8006052 | Benhanokh | Aug 2011 | B1 |
| 8006111 | Faibish et al. | Aug 2011 | B1 |
| 8010756 | Linde | Aug 2011 | B1 |
| 8019726 | Ueoka | Sep 2011 | B2 |
| 8032569 | Oshita et al. | Oct 2011 | B2 |
| 8040727 | Harari | Oct 2011 | B1 |
| 8051043 | Young | Nov 2011 | B2 |
| 8112605 | Kavuri | Feb 2012 | B2 |
| 8117355 | Hamasaki | Feb 2012 | B2 |
| 8140786 | Bunte et al. | Mar 2012 | B2 |
| 8156086 | Lu et al. | Apr 2012 | B2 |
| 8161318 | D'Souza et al. | Apr 2012 | B2 |
| 8170995 | Prahlad et al. | May 2012 | B2 |
| 8195800 | Tameshige et al. | Jun 2012 | B2 |
| 8200638 | Zheng et al. | Jun 2012 | B1 |
| 8204862 | Paulzagade et al. | Jun 2012 | B1 |
| 8209293 | Gokhale et al. | Jun 2012 | B2 |
| 8219524 | Gokhale | Jul 2012 | B2 |
| 8229954 | Kottomtharayil et al. | Jul 2012 | B2 |
| 8230066 | Heil | Jul 2012 | B2 |
| 8230171 | Kottomtharayil | Jul 2012 | B2 |
| 8230195 | Amarendran et al. | Jul 2012 | B2 |
| 8234417 | Kottomtharayil et al. | Jul 2012 | B2 |
| 8234468 | Deshmukh et al. | Jul 2012 | B1 |
| 8244841 | Shaji et al. | Aug 2012 | B2 |
| 8266406 | Kavuri | Sep 2012 | B2 |
| 8266615 | Shapiro | Sep 2012 | B2 |
| 8285681 | Prahlad et al. | Oct 2012 | B2 |
| 8285758 | Bono | Oct 2012 | B1 |
| 8285898 | Amit et al. | Oct 2012 | B2 |
| 8289641 | Emami | Oct 2012 | B1 |
| 8306926 | Prahlad et al. | Nov 2012 | B2 |
| 8307177 | Prahlad et al. | Nov 2012 | B2 |
| 8315982 | Ueoka | Nov 2012 | B2 |
| 8327050 | Amit et al. | Dec 2012 | B2 |
| 8335789 | Hull et al. | Dec 2012 | B2 |
| 8341182 | Muller et al. | Dec 2012 | B2 |
| 8346733 | Gokhale et al. | Jan 2013 | B2 |
| 8346734 | Muller et al. | Jan 2013 | B2 |
| 8347088 | Moore et al. | Jan 2013 | B2 |
| 8352433 | Crescenti et al. | Jan 2013 | B2 |
| 8364652 | Vijayan et al. | Jan 2013 | B2 |
| 8402000 | Gokhale et al. | Mar 2013 | B2 |
| 8407190 | Prahlad et al. | Mar 2013 | B2 |
| 8412848 | Therrien et al. | Apr 2013 | B2 |
| 8417678 | Bone et al. | Apr 2013 | B2 |
| 8422733 | Reisman | Apr 2013 | B2 |
| 8433679 | Crescenti et al. | Apr 2013 | B2 |
| 8463753 | Gokhale et al. | Jun 2013 | B2 |
| 8463994 | Kottomtharayil | Jun 2013 | B2 |
| 8478876 | Paul et al. | Jul 2013 | B2 |
| 8484164 | Sivakumar | Jul 2013 | B1 |
| 8484165 | Gokhale et al. | Jul 2013 | B2 |
| 8510573 | Muller et al. | Aug 2013 | B2 |
| 8527549 | Cidon | Sep 2013 | B2 |
| 8539118 | Kottomtharayil et al. | Sep 2013 | B2 |
| 8566371 | Bono | Oct 2013 | B1 |
| 8572330 | Kottomtharayil et al. | Oct 2013 | B2 |
| 8572706 | Lucovsky et al. | Oct 2013 | B2 |
| 8578120 | Attarde et al. | Nov 2013 | B2 |
| 8600998 | Chaudhary et al. | Dec 2013 | B1 |
| 8620286 | Stannard et al. | Dec 2013 | B2 |
| 8624549 | Sridhar et al. | Jan 2014 | B2 |
| 8626128 | Limont et al. | Jan 2014 | B2 |
| 8635204 | Xie et al. | Jan 2014 | B1 |
| 8656068 | Kottomtharayil et al. | Feb 2014 | B2 |
| 8661216 | Kavuri et al. | Feb 2014 | B2 |
| 8671209 | Awano | Mar 2014 | B2 |
| 8688641 | Cook et al. | Apr 2014 | B1 |
| 8695058 | Batchu et al. | Apr 2014 | B2 |
| 8700578 | Varadan et al. | Apr 2014 | B1 |
| 8706976 | Kottomtharayil et al. | Apr 2014 | B2 |
| 8712959 | Lim et al. | Apr 2014 | B1 |
| 8732133 | Attarde | May 2014 | B2 |
| 8756203 | Muller et al. | Jun 2014 | B2 |
| 8825591 | Lai et al. | Sep 2014 | B1 |
| 8832031 | Kavuri et al. | Sep 2014 | B2 |
| 8832044 | Gipp et al. | Sep 2014 | B1 |
| 8849761 | Prahlad et al. | Sep 2014 | B2 |
| 8849762 | Kumarasamy | Sep 2014 | B2 |
| 8850140 | De Atley et al. | Sep 2014 | B2 |
| 8886853 | Kottomtharayil et al. | Nov 2014 | B2 |
| 8924428 | Muller et al. | Dec 2014 | B2 |
| 8931107 | Brandwine | Jan 2015 | B1 |
| 8938481 | Kumarasamy et al. | Jan 2015 | B2 |
| 8966017 | Wipfel | Feb 2015 | B2 |
| 8996823 | Kottomtharayil et al. | Mar 2015 | B2 |
| 9015181 | Kottomtharayil | Apr 2015 | B2 |
| 9027076 | Roach | May 2015 | B2 |
| 9047219 | Daikokuya | Jun 2015 | B2 |
| 9069799 | Vijayan | Jun 2015 | B2 |
| 9183560 | Abelow | Nov 2015 | B2 |
| 9244779 | Littlefield | Jan 2016 | B2 |
| 9529871 | Vibhor et al. | Dec 2016 | B2 |
| 9557929 | Littlefield et al. | Jan 2017 | B2 |
| 10101913 | Kochunni | Oct 2018 | B2 |
| 10162712 | Gokhale | Dec 2018 | B2 |
| 10185670 | Litichever et al. | Jan 2019 | B2 |
| 10275318 | Littlefield et al. | Apr 2019 | B2 |
| 10303559 | Vijayan | May 2019 | B2 |
| 10318157 | Kochunni | Jun 2019 | B2 |
| 10318542 | Vibhor et al. | Jun 2019 | B2 |
| 10341285 | Warfield et al. | Jul 2019 | B2 |
| 10747436 | Kochunni | Aug 2020 | B2 |
| 20020010661 | Waddington et al. | Jan 2002 | A1 |
| 20020032613 | Buettgenbach et al. | Mar 2002 | A1 |
| 20020049778 | Bell et al. | Apr 2002 | A1 |
| 20020069324 | Gerasimov et al. | Jun 2002 | A1 |
| 20020087950 | Brodeur et al. | Jul 2002 | A1 |
| 20030055671 | Nassar | Mar 2003 | A1 |
| 20030065759 | Britt et al. | Apr 2003 | A1 |
| 20030101155 | Gokhale et al. | May 2003 | A1 |
| 20030134619 | Phillips et al. | Jul 2003 | A1 |
| 20030177145 | Lohn | Sep 2003 | A1 |
| 20030220901 | Carr et al. | Nov 2003 | A1 |
| 20040054607 | Waddington et al. | Mar 2004 | A1 |
| 20040073677 | Honma et al. | Apr 2004 | A1 |
| 20040073831 | Yanai | Apr 2004 | A1 |
| 20040083202 | Mu et al. | Apr 2004 | A1 |
| 20040107199 | Dalrymple et al. | Jun 2004 | A1 |
| 20040186847 | Rappaport et al. | Sep 2004 | A1 |
| 20040192260 | Sugimoto et al. | Sep 2004 | A1 |
| 20040193953 | Callahan et al. | Sep 2004 | A1 |
| 20040260967 | Guha | Dec 2004 | A1 |
| 20050008163 | Leser et al. | Jan 2005 | A1 |
| 20050021524 | Oliver | Jan 2005 | A1 |
| 20050033913 | Kottomtharayil et al. | Feb 2005 | A1 |
| 20050039069 | Prahlad et al. | Feb 2005 | A1 |
| 20050076264 | Rowan et al. | Apr 2005 | A1 |
| 20050102203 | Keong | May 2005 | A1 |
| 20050102328 | Ring | May 2005 | A1 |
| 20050102552 | Horn | May 2005 | A1 |
| 20050125807 | Brady et al. | Jun 2005 | A1 |
| 20050174869 | Kottomtharayil et al. | Aug 2005 | A1 |
| 20050177828 | Graham et al. | Aug 2005 | A1 |
| 20050210304 | Hartung et al. | Sep 2005 | A1 |
| 20050246342 | Vernon | Nov 2005 | A1 |
| 20060004639 | O'Keefe | Jan 2006 | A1 |
| 20060004675 | Bennett et al. | Jan 2006 | A1 |
| 20060005074 | Yanai | Jan 2006 | A1 |
| 20060011720 | Call | Jan 2006 | A1 |
| 20060069886 | Tulyani | Mar 2006 | A1 |
| 20060075007 | Anderson et al. | Apr 2006 | A1 |
| 20060095385 | Atkinson et al. | May 2006 | A1 |
| 20060100912 | Kumar et al. | May 2006 | A1 |
| 20060106881 | Leung | May 2006 | A1 |
| 20060161879 | Lubrecht et al. | Jul 2006 | A1 |
| 20060169769 | Boyarsky et al. | Aug 2006 | A1 |
| 20060224846 | Amarendran et al. | Oct 2006 | A1 |
| 20060242379 | Korgaonkar | Oct 2006 | A1 |
| 20060248165 | Sridhar et al. | Nov 2006 | A1 |
| 20060282194 | Schaefer et al. | Dec 2006 | A1 |
| 20060288044 | Kashiwagi et al. | Dec 2006 | A1 |
| 20070130105 | Papatla | Jun 2007 | A1 |
| 20070185912 | Gupta et al. | Aug 2007 | A1 |
| 20080077622 | Keith | Mar 2008 | A1 |
| 20080147621 | Newman | Jun 2008 | A1 |
| 20080177806 | Cannon et al. | Jul 2008 | A1 |
| 20080243795 | Prahlad et al. | Oct 2008 | A1 |
| 20090043828 | Shitomi | Feb 2009 | A1 |
| 20090234979 | Hamasaki | Sep 2009 | A1 |
| 20090300081 | Ueoka | Dec 2009 | A1 |
| 20090319534 | Gokhale | Dec 2009 | A1 |
| 20100030528 | Smith et al. | Feb 2010 | A1 |
| 20100070466 | Prahlad et al. | Mar 2010 | A1 |
| 20100070474 | Lad | Mar 2010 | A1 |
| 20100070726 | Ngo et al. | Mar 2010 | A1 |
| 20100077453 | Mohanty | Mar 2010 | A1 |
| 20100082672 | Kottomtharayil et al. | Apr 2010 | A1 |
| 20100269164 | Sosnosky et al. | Oct 2010 | A1 |
| 20100318500 | Murphy et al. | Dec 2010 | A1 |
| 20100333116 | Prahlad et al. | Dec 2010 | A1 |
| 20110040736 | Kalaboukis et al. | Feb 2011 | A1 |
| 20110093672 | Gokhale et al. | Apr 2011 | A1 |
| 20110167045 | Okamoto | Jul 2011 | A1 |
| 20110218964 | Hagan | Sep 2011 | A1 |
| 20110231852 | Gokhale et al. | Sep 2011 | A1 |
| 20110252071 | Cidon | Oct 2011 | A1 |
| 20110252207 | Janosik, Jr. | Oct 2011 | A1 |
| 20110270833 | von Kaenel et al. | Nov 2011 | A1 |
| 20110302139 | Ueoka | Dec 2011 | A1 |
| 20110306326 | Reed et al. | Dec 2011 | A1 |
| 20120078856 | Linde | Mar 2012 | A1 |
| 20120084523 | Littlefield et al. | Apr 2012 | A1 |
| 20120150818 | Vijayan Retnamma et al. | Jun 2012 | A1 |
| 20120150826 | Vijayan Retnamma et al. | Jun 2012 | A1 |
| 20120185657 | Gokhale et al. | Jul 2012 | A1 |
| 20120191930 | Brown | Jul 2012 | A1 |
| 20120240183 | Sinha | Sep 2012 | A1 |
| 20120254119 | Kumarasamy | Oct 2012 | A1 |
| 20130054533 | Hao et al. | Feb 2013 | A1 |
| 20130103649 | Linde | Apr 2013 | A9 |
| 20130238572 | Prahlad et al. | Sep 2013 | A1 |
| 20130262392 | Vibhor et al. | Oct 2013 | A1 |
| 20130275380 | Gokhale et al. | Oct 2013 | A1 |
| 20130311735 | Sivakumar | Nov 2013 | A1 |
| 20130318207 | Dotter | Nov 2013 | A1 |
| 20140040211 | Avery | Feb 2014 | A1 |
| 20140046900 | Kumarasamy et al. | Feb 2014 | A1 |
| 20140046904 | Kumarasamy | Feb 2014 | A1 |
| 20140122435 | Chavda et al. | May 2014 | A1 |
| 20140188812 | Vijayan et al. | Jul 2014 | A1 |
| 20140281306 | Nakajima et al. | Sep 2014 | A1 |
| 20140317444 | Kushihara | Oct 2014 | A1 |
| 20140380091 | Konishi | Dec 2014 | A1 |
| 20150012495 | Prahlad et al. | Jan 2015 | A1 |
| 20150269035 | Vijayan et al. | Sep 2015 | A1 |
| 20160100007 | Prahlad et al. | Apr 2016 | A1 |
| 20160292040 | Kumarasamy et al. | Oct 2016 | A1 |
| 20170060431 | Kochunni et al. | Mar 2017 | A1 |
| 20170091294 | Vibhor et al. | Mar 2017 | A1 |
| 20170139780 | Littlefield | May 2017 | A1 |
| 20180349032 | Kochunni et al. | Dec 2018 | A1 |
| 20190205215 | Littlefield et al. | Jul 2019 | A1 |
| 20190243729 | Vijayan | Aug 2019 | A1 |
| 20190250828 | Kochunni et al. | Aug 2019 | A1 |
| 20200257451 | Kochunni et al. | Aug 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 0259912 | Mar 1988 | EP |
| 0405926 | Jan 1991 | EP |
| 0467546 | Jan 1992 | EP |
| 0620553 | Oct 1994 | EP |
| 0757317 | Feb 1997 | EP |
| 0774715 | May 1997 | EP |
| 0809184 | Nov 1997 | EP |
| 0899662 | Mar 1999 | EP |
| 0981090 | Feb 2000 | EP |
| 7254204 | Oct 1995 | JP |
| 9044381 | Feb 1997 | JP |
| 9081424 | Mar 1997 | JP |
| WO-9513580 | May 1995 | WO |
| WO-9912098 | Mar 1999 | WO |
| WO-2005024573 | Mar 2005 | WO |
| WO-2008154448 | Dec 2008 | WO |
| Entry |
|---|
| About Backupify [retrieved on Aug. 1, 2014], Retrieved from internet: http://web.archive.org/web/20120122064518/https://www.backupify.com/about; published on Jan. 22, 2012 as per Wayback Machine. |
| Allen, “Probability, Statistics and Queuing Theory,” (1978), p. 370, col. 19, Lines 3-33, 2 pages. |
| Armstead et al., “Implementation of a Campwide Distributed Mass Storage Service: The Dream vs. Reality,” IEEE, Sep. 11-14, 1995, pp. 190-199. |
| Arneson, “Mass Storage Archiving in Network Environments,” Digest of Papers, Ninth IEEE Symposium on Mass Storage Systems, Oct. 31, 1988-Nov. 3, 1988, pp. 45-50, Monterey, CA. |
| Ashton et al., “Two Decades of policy-based storage management for the IBM mainframe computer”, www.research.ibm.com, published Apr. 10, 2003, printed Jan. 3, 2009, 19 pages. |
| Backup your social media content with MyCube Vault [retrieved on Oct. 30, 2014] Retrieved from internet; http://web.archive.org/web/20110606160223/http://www.kullin.net/2010/11/backup-your-social-media-content-with-mycube-vault/; published on Jun. 6, 2011 as per Wayback Machine. |
| Cabrera et al., “ADSM: A Multi-Platform, Scalable, Backup and Archive Mass Storage System,” Digest of Papers, Compcon '95, Proceedings of the 40th IEEE Computer Society International Conference, Mar. 5, 1995-Mar. 9, 1995, pp. 420-427, San Francisco, CA. |
| Campbell, C.: “Linux and Windows NT 4.0: Basic Administration—Part III” Internet Publication, [Online] Oct. 5, 2000, Retrieved from the Internet: URL: <http://linux.omnipotent.net/article.php?article_id=10933> [retrieved on Aug. 22, 2006], 6 pages. |
| Carrington, D.: “Backups Using The “at” Command”, Internet Publication, [Online] May 4, 1999, Retrieved from the Internet: URL: <http://groups.google.de/group/microsoft.public.windowsnt.misc/browse_thread/thread/d1406a9a8391afea/48bac300a0adcc7a?lnk=st&q=&rnum=12&h1=de#48bac300a0adcc7a> [retrieved on Aug. 22, 2006], 1 page. |
| CDDB , <https://en.wikipedia.org/w/index.php?title=CDDB&oldid=918171130>, 4 pages. |
| Cook, P.: “ntbackup: eject tape at end of backup?” Internet Publication, [Online] Oct. 18, 2000, Retrieved from the Internet: URL: <http://groups.google.de/group/microsoft.public.windowsnt.misc/browse...thread/thread/8f67f0cc96df42b7/0ab1d93a6f91b511?lnk=st&q=%22ntbackup+eject%22+at&rnum=1&h1=de#0ab1d93a6f91b511> [retrieved on Aug. 22, 2006], 1 page. |
| Eitel, “Backup and Storage Management in Distribued Heterogeneous Environments,” IEEE, Jun. 12-16, 1994, pp. 124-126. |
| Extended European Search Report in European Application No. 13767340.6, dated Aug. 19, 2015, 7 pages. |
| Gait, J., “The Optical File Cabinet: A Random-Access File System for Write-Once Optical Disks,” IEEE Computer, vol. 21, No. 6, pp. 11-22 (Jun. 1988). |
| Gonzalez-Seco, Jose, “A Genetic Algorithm as the Learning Procedure for Neural Networks,” International Joint Conference on Neural Networks, Jun. 1992, 356 pages. |
| International Search Report and Written Opinion for International Application No. PCT/US2013/029393; dated Jun. 27, 2013; 10 pages. |
| Jander, M., “Launching Storage-Area Net,” Data Communications, US, McGraw Hill, NY, vol. 27, No. 4 (Mar. 21, 1998), pp. 64-72. |
| MDM: “Automatically eject tape”, Internet Publication, [Online] Jun. 7, 1999, Retrieved from Internet: URL: <http://groups.google.de/group/microsoft.public.windowsnt.misc/browse_thread/thread66537271a88cebda/2f8b1b96dfc5f102?lnk=st&q=&rnum=11&h1=de#2f8b1b96dfc5f102> [retrieved on Jun. 22, 2006], 1 page. |
| PageFreezer Website Archiving & Social Media Archiving [retrieved on Aug. 1, 2014], Retrieved from internet: http://webarchive.org/web/20120303012345/http://pagefreezer.com/blog; published on Mar. 3, 2012 as per Wayback Machine. |
| Recycle Bin (Windows), Aug. 2007, Wikipedia, pp. 1-3. |
| Rosenblum et al., “The Design and Implementation of a Log-Structured File System,” Operating Systems Review SIGOPS, vol. 25, No. 5, New York, US, pp. 1-15 (May 1991). |
| Savill, J., “Windows NT FAQ Single File Version—Section Backup's” Internet Publication, [Online] 2000, Retrieved from Internet: URL: <http://burks.bton.ac.uk/burks/pcinfo/osdocs/ntfaq/ntfaq_09.htm> [retrieved on Aug. 22, 2006], 8 pages. |
| Supplementary European Search Report in European Application No. 13767340.6, dated Sep. 4, 2015, 1 page. |
| U.S. Appl. No. 15/377,299 for Vibhor et al., filed Dec. 13, 2016. |
| Examination Report in European Patent Application No. 13767340.6, dated Mar. 23, 2018, 5 pages. |
| Indian First Examination Report, Application No. 3362/DELNP/2006, dated Jan. 21, 2013, 2 pages. |
| Littlefield, et al., U.S. Appl. No. 13/241,625, Published As 2012/0084523 A1 now U.S. Pat. No. 9,244,779, filed Sep. 23, 2011, Data Recovery Operations, Such As Recovery From Modified Network Data Management Protocol Data. |
| Littlefield, et al., U.S. Appl. No. 15/005,209 Published As 2016/0147472 A1 now U.S. Pat. No. 9,557,929, filed Jan. 25, 2016, Data Recovery Operations, Such As Recovery From Modified Network Data Management Protocol Data. |
| Littlefield, et al., U.S. Appl. No. 15/419,272 Published As 2017/0139780 A1 now U.S. Pat. No. 10275318, filed Jan. 30, 2017, Data Recovery Operations, Such As Recovery From Modified Network Data Management Protocol Data. |
| Number | Date | Country | |
|---|---|---|---|
| 20190205215 A1 | Jul 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61388554 | Sep 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13241625 | Sep 2011 | US |
| Child | 15005209 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15419272 | Jan 2017 | US |
| Child | 16297330 | US | |
| Parent | 15005209 | Jan 2016 | US |
| Child | 15419272 | US |
