US 8,024,294 B2Grant
Systems and methods for performing replication copy storage operations
Issue Date:2011-09-20
•18 Claims
•7 Drawing Sheets
Abstract
A system and method are provided for performing storage operations relating to a first secondary copy of electronic data. A storage policy or storage preferences may dictate that a replication copy should be used in storage operations performed to a particular client, sub-client, data, media or other item. Based on the storage policy, when a new client, sub-client, data, media or other item is received, a media agent determines whether there is a replication copy of the item. In the absence of a replication copy, one may be created. The replication copy may be provided by a third party application, or created by the client or a storage management system component. Information regarding the replication copy and its corresponding first secondary copy may be stored in a database. To optimize use of system resources, storage operations relating to the first secondary copy may be performed using the replication copy instead of the first secondary copy.
Metadata
Assignee
- CommVault Systems, Inc.
Inventor
- Rajiv Kottomtharayil
Application Information
Application Number:US 12/581,297
Filing Date:2009-10-19
Priority Date:2005-12-19
Art Unit:2162
Classifications
IPC:
G06F7/00G06F17/00
Patent Drawings (7 sheets)
Description
Related Application
[0001] This application is a continuation of U.S. patent application Ser. No. 11/313,257, filed Dec. 19, 2005, now U.S. Pat. No. 7,606,844, which is hereby incorporated herein by reference in its entirety to be considered part of this specification.
Copyright Notice
[0002] A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosures, as it appears in the Patent and Trademark Office patent files or records, but otherwise expressly reserves all other rights to copyright protection.
Background
[0003] 1. Field of the Invention
[0004] The invention disclosed herein relates generally to performing storage operations on electronic data in a computer network. More particularly, the present invention relates to using a replication copy or other copy of primary storage production data for performing storage operations.
[0005] 2. Description of the Related Art
[0006] 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 or in secondary storage as various types of secondary copies including, a backup copy, a snapshot copy, a hierarchical storage management copy (“HSM”), as an archive copy, and as other types of copies.
[0007] A primary copy of data is generally a production copy or other “live” version of the data which 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 if necessary. Such 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 that a problem occurred with the data stored in primary storage.
[0008] 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, for example, as specified in a storage policy as further described herein) before some or all of the data is moved to other storage or discarded. Secondary copies may be indexed so that users can browse and restore the data at another point in time. After certain primary copy data is migrated to secondary storage, 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.
[0009] In conventional storage management systems, a secondary copy is typically produced by performing a storage operation, such as a backup, of production data, such as a primary copy. Creating such secondary copies typically requires taking the production data or primary copy offline so that it is inaccessible or unavailable to a client or other system component. In general, it is preferable to avoid taking a primary copy, and any components associated therewith, offline, however, if it is unavoidable, it is preferable to minimize the duration that the copies or components are offline. Storage operations that require the primary copy are typically scheduled overnight when the primary copy is less likely to be used by a client, which typically accesses the primary copy during daytime hours. Thus, the primary copy may often be unavailable, or access to the primary copy may be difficult to provide because it is frequently in use. In addition, storage management system components using the primary copy for storage operations may also be unavailable to perform other concurrent storage operations. Such systems may encounter bottlenecks in allocation of system resources to perform storage operations.
Summary
[0010] Systems and methods are provided for performing a storage operation using a replication copy or other data source. In one embodiment, a method for performing a storage operation using a replication copy is provided in which a data item for a storage operation is identified, a storage policy associated with the data item is identified, and a data source of the data item may be determined to be available. The data source for performing the storage operation may be selected according to a criterion and the storage operation may be performed. The data source may be a first secondary copy or a replication copy. In general, the data source is determined by consulting a schedule of storage operations involving the data source. A storage manager or other system component may select the data source according to a criterion by calculating a metric weighing one or more priorities for storage operation preferences.
[0011] In another embodiment, a method for performing a storage operation using a replication copy is provided, in which a storage operation instruction is received. The storage operation instruction may include data identifying a data item with which to perform the storage operation. A storage policy may be received. The storage policy may indicate that a storage operation relating to the data item should be performed using a replication copy. The replication copy may be determined to be available and the storage operation may be performed using the replication copy.
[0012] In another embodiment, a method for optimizing storage operations in a storage management system is provided, in which, a storage operation request is received, the storage operation request identifying a data item with which to perform the storage operation. A database may be consulted to determine whether a replication copy of the data item is available. Using the replication copy of the data item to perform the storage operation may be determined to optimize resource use in the storage management system; and the storage operation may be performed using the replication copy.
[0013] In another embodiment, a storage management system for performing a storage operation, is provided including a storage management component communicatively coupled to a database; wherein the database includes a storage policy; a media agent communicatively coupled to the storage management component, a first secondary copy and a replication copy; wherein the storage management component is programmed to receive a storage operation request relating to the first secondary copy, consult the database to identify the replication copy that corresponds to the first secondary copy, and determine whether using the replication copy to perform the storage operation optimizes use of system resources; and wherein the media agent is programmed to perform the storage operation using the replication copy.
Brief Description of the Drawings
[0014] The invention is illustrated in the figures of the accompanying drawings which are meant to be exemplary and not limiting, in which like references are intended to refer to like or corresponding parts, and in which:
[0015] FIG. 1A is a block diagram of a storage management system for creating a replication copy according to an embodiment of the invention;
[0016] FIG. 1B is a diagram of a log and a file according to an embodiment of the invention;
[0017] FIG. 2 is a block diagram of a storage management system according to an embodiment of the invention;
[0018] FIG. 3 is a high level block diagram of a storage management system according to an embodiment of the invention;
[0019] FIG. 4 is a storage operation schedule according to an embodiment of the invention;
[0020] FIG. 5 is a database table for tracking copy volumes according to an embodiment of the invention; and
[0021] FIG. 6 is a flow diagram of a method for performing a storage operation according to an embodiment of the invention.
Detailed Description of the Preferred Embodiments
[0022] Systems and methods are provided herein for performing a storage operation using a replication copy. A replication copy may be a copy of a first secondary copy of production data (e.g., a primary volume), but may also be a copy of production data or a primary copy. A first secondary copy is an initial or first secondary copy of production data, or some other initial copy of the primary volume. The first secondary copy may be considered for data storage management purposes to include the same data as a primary copy. The first secondary copy may be stored to primary storage, which is a storage medium which provides relatively faster access than secondary storage, however, secondary storage medium may also be used for the first secondary copy. The first secondary copy may alternatively refer to any copy of electronic data which may be frequently accessed by one or more system components for client use or storage operation purposes, and for which utilization may need to be restricted, e.g., to avoid bottlenecks, to avoid interrupting client use, etc. In this case, the first secondary copy may be considered equivalent to a primary copy in that storage management systems may wish to minimize system utilization of the first secondary copy as it would for a primary copy.
[0023] There are several ways to create a replication copy, such as by performing a copy operation, such as a snapshot copy, point in time copy, mirror copy, synchronous replication copy or asynchronous replication copy, or other copy operation. A replication copy is typically made of a first secondary copy and continuously updated. One example of a system for creating a replication copy is shown in FIG. 1A , but other system architectures may be used. As shown in FIG. 1A , a system for creating a replication copy may include system components such as a memory or data store 10, log filter driver 20, primary mass storage 40, logs 30, replication agent 87 and storage manager 100 and storage management index or database 111 and a replication copy 200.
[0024] In general, a replication copy 200 may be created at the direction of a replication agent 87, storage manager 100 or other system component, and information relating to the replication copy 200 may be stored in an index 111. The replication agent 87 may obtain the electronic data, such as from production data or a first secondary copy stored in memory 10, for the replication copy continuously via one or more data streams, or use logs 30 which include a production data log or change information obtained by the log filter driver 20, to update a replication copy periodically. The replication agent 87 may communicate with the log filter driver 20 to acknowledge receipt of logs 31 from a logs store or cache 30 or directly from the logs filter driver 20, and confirm that the replication copy 200 is updated with the received logs 31.
[0025] Memory 10 may be a data store which is attached to a client or other data generator or data producer and which is capable of storing electronic data, such as production data or a first secondary copy, etc. A log filter driver 20 may be a module which monitors an interaction or change of electronic data in memory 10. The log filter driver 20 may be programmed to monitor particular or specific data changes, such as changes to a sub-client, application type, client folder, or other aspect of electronic data. Referring to FIG. 1B , the interaction or change may be stored in a log 31 which includes metadata, such as a file ID 32 and offset 34 and the changed data payload 36. A file ID 32 may be any file identifier and may correspond to a file 35. The offset 34 is the point at which the change to the file data occurs. Payload 36 typically includes the changed data. Thus, the file log 31 relates to the file 35 in that the payload 36 of the log 31 fits in the file 35 at a certain offset point, for example, between portions of the file 38A and 38B.
[0026] Referring again to FIG. 1A , the log filter driver 20 monitors the production data stored in memory 10 for interactions or changes to the electronic data and when a change occurs, the log filter driver 20 creates a log, such as log 31, which is stored in logs 30. A log file 31 may be cached temporarily in logs 30 or transmitted immediately to the replication copy 200 for updating the replication copy 200. Logs 30 may be any data store capable of storing the logs 31 generated by the log filter driver 20, and is generally in communication with a replication agent 87, replication copy 200, or other system component. The log filter driver 20 may also create logs 31 which may be used to create a primary copy or first secondary copy, stored in mass storage 40. The mass storage 40 may be any data store capable of storing electronic data, such as a primary copy, first secondary copy or other copy.
[0027] FIG. 2 illustrates a block diagram of a storage operation cell 80 that may perform storage operations on electronic data in a computer network in accordance with an embodiment of the present invention. As shown, storage operation cell 80 may generally include a storage manager 100, a data agent 95, a media agent 105, a storage device 115, and, in some embodiments, may include certain other components such as a client 85, a replication agent 87, a data or information store 90, databases or indexes 110 and 111, jobs agent 120, an interface module 125, and a management agent 130. Such system and elements thereof are exemplary of a modular storage management system such as the CommVault QINETIX system, and the CommVault GALAXY storage management system, available from CommVault Systems, Inc. of Oceanport, N.J., and further described in U.S. patent application Ser. No. 09/610,738 which is incorporated herein by reference in its entirety. A storage operation cell, such as cell 80, may generally include combinations of hardware and software components associated with performing storage operations on electronic data.
[0028] In accordance with certain embodiments of the present invention, storage operations performed by storage operation cells may include creating, storing, retrieving, and migrating primary data copies and secondary data copies (which may include, for example, snapshot copies, backup copies, HSM copies, archive copies, and other types of copies of electronic data). In some embodiments, storage operation cells may also 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.
[0029] In some embodiments, storage operations may be performed according to a storage policy. A storage policy is generally a data structure or other information source that includes a set of preferences and other storage criteria for performing a storage operation. The preferences and storage criteria may include, but are not limited to, a storage location, relationships between system components, relationships between system components and use of a third party application, network pathway to utilize, retention policies, data characteristics, compression or encryption requirements, preferred system components to utilize in a storage operation, and other criteria relating to a storage operation. Thus, a storage policy may indicate that certain data is to be stored in a specific storage device, retained for a specified period of time before being aged to another tier of secondary storage, copied to secondary storage using a replication copy or a specified number of streams, etc. A storage policy may be stored to a storage manager database or index 111, to archive media as metadata for use in restore operations or other storage operations, or to other locations or components of the system.
[0030] A schedule policy may specify when and how often to perform storage operations and may also specify performing certain storage operations on sub-clients of data and how to treat those sub-clients. A sub-client may represent static or dynamic associations of portions of data of a volume and are mutually exclusive. Thus, a portion of data may be given a label and the association is stored as a static entity in an index, database or other storage location used by the system. Sub-clients may also be used as an effective administrative scheme of organizing data according to data type, department within the enterprise, storage preferences, etc. For example, a sub-client may be all media in an associated storage device and the sub-client is associated with a storage policy which requires that a replication copy be created or provided to perform secondary storage operations.
[0031] 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 80 may be configured to perform a storage operation, such as data backup or other types of data migration, and may include a variety of physical components including a storage manager 100 (or management agent 130), a media agent 105, a client component 85, 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 other storage operations, such as monitoring a primary copy, first secondary copy, or replication copy volume or performing other known storage operations.
[0032] A storage preference may be a storage policy, user preference or other storage preference. In some embodiments the storage preference is defined by a system user or system administrator. In other embodiments, the storage preference is a default preference. Examples of storage preferences can include: using a particular data source for performing a storage operation, such as a replication copy, assigning priorities to performance of a storage operation, data security settings, encryption settings, data retention requirements, frequency of storage operations, such as frequency of backups, types of data for storage operations, such as data types for backups, types of storage operations to perform in the component group, network pathways, such as preferred network pathways to perform a storage operation, scheduling, such as a schedule of storage operations, reports, such as automatic generation of system reports regarding the group, which can include, for example the storage operations performed by the group, or other storage preference.
[0033] Replication agent 87 may be a software module or part of a software module that may be used to manage and direct creation and maintenance of a replication copy 200. For example, a replication agent 87 may communicate or direct communication of electronic data, such as production data for creating a replication copy 200. The replication copy 200 may be created synchronously or asynchronously, using a mirror, or other copy technique. The replication agent 87 may be a software module associated with a client 85 that generates the production data used to create replication copy 200. Alternatively, replication agent 87 may be provided by a third party software component which may interface with a client 85 and production data in, for example, data store 90, to create replication copy 200.
[0034] Data agent 95 may be a software module or part of a software module that is generally responsible for archiving, migrating, and recovering data from client computer 85 stored in an information store 90, or other memory location. Each client computer 85 may have at least one data agent 95 and the system can support multiple client computers 85. In some embodiments, data agents 95 may be distributed between client 85 and storage manager 100 (and any other intermediate components (not shown)) or 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 95.
[0035] Embodiments of the present invention may employ multiple data agents 95 each of which may backup, migrate, and recover data associated with a different application. For example, different individual data agents 95 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 95 that can handle and process multiple data types rather than using the specialized data agents described above.
[0036] Generally speaking, storage manager 100 may be a software module or other application that coordinates and controls storage operations performed by storage operation cell 80. Storage manager 100 may communicate with some or all elements of storage operation cell 80 including client computers 85, data agents 95, media agents 105, and storage devices 115, to initiate and manage system storage operations.
[0037] Storage manager 100 may include a jobs agent 120 that monitors the status of some or all storage operations previously performed, currently being performed, or scheduled to be performed by storage operation cell 80. Jobs agent 120 may be communicatively coupled with an interface agent 125 (typically a software module or application). Interface agent 125 may include information processing and display software, such as a graphical user interface (“GUI”), an application program interface (“API”), or other interactive interface through which users and system processes can retrieve information about the status of storage operations. Through interface 125, users may optionally issue instructions to various storage operation cells 80 regarding performance of the storage operations as described and contemplated by the present invention. 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). As a further example, interface 125 may display the cost metrics associated with a particular type of data storage and may allow a user to determine overall and target cost metrics associated with a particular data type, or certain storage operation cell 80 or other storage operation as predefined or user-defined.
[0038] Storage manager 100 may also include a management agent 130 that is typically implemented as a software module or application program. In general, management agent 130 provides an interface that allows various management components 100 in other storage operation cells 80 to communicate with one another. For example, assume a certain network configuration includes multiple cells 80 adjacent to one another or otherwise logically related in a WAN or LAN configuration (not shown). With this arrangement, each cell 80 may be connected to the other through each respective interface module 125. This allows each cell 80 to send and receive certain pertinent information from other cells 80 including status information, routing information, information regarding capacity and utilization, etc. These communication paths may also be used to convey information and instructions regarding storage operations.
[0039] Storage manager 100 may also maintain an index cache, a database, or other data structure 111. The data stored in database 111 may be used to indicate logical associations between components of the system, user preferences, management tasks, some SRM or HSM data or other useful data. As further described herein, some of this information may be stored in a media agent database 110 or other local data store according to some embodiments. For example, the storage manager 110 may use data from database 111 to track logical associations of primary copies of data, first secondary copies of data and corresponding replication copies, between media agents 105 and storage devices 115 or between other components of the system.
[0040] Generally speaking, a media agent 105 may be implemented as a software module that conveys data, as directed by a storage manager 100, between a client computer 85 and one or more storage devices 115 such as a tape library, a magnetic media storage device, an optical media storage device, or any other suitable storage device. In one embodiment, media agents 105 may be communicatively coupled with and control a storage device 115 associated with that particular media agent. A media agent 105 may be considered to be associated with a particular storage device 115 if that media agent 105 is capable of routing and storing data to a particular storage device 115.
[0041] In operation, a media agent 105 associated with a particular storage device 115 may instruct the storage device to use a robotic arm or other retrieval means to load or remove a certain storage media, and to subsequently archive, migrate, or restore data to or from that media. Media agents 105 may communicate with a storage device 115 via a suitable communications path such as a SCSI or fiber channel communications link. In some embodiments, the storage device 115 may be communicatively coupled to a data agent 105 via a Storage Area Network (“SAN”).
[0042] Each media agent 105 may maintain an index cache, a database, or other data structure 110 which stores index data generated during backup, migration, and restore and other storage operations as described herein. For example, performing storage operations on MICROSOFT EXCHANGE data may generate index data. Such index data provides a media agent 105 or other external device with a fast and efficient mechanism for locating data stored or backed up. Thus, in some embodiments, a storage manager database 111 may store data associating a client 85 with a particular media agent 105 or storage device 115, for example, as specified in a storage policy, while media agent database 110 may indicate where specifically the client 85 data is stored in storage device 115, what specific files were stored, and other information associated with storage of client 85 data. In some embodiments, such index data may be stored along with the data backed up in a storage device 115, with an additional copy of the index data written to index cache 110. The data in index cache 110 is thus readily available for use in storage operations and other activities without having to be first retrieved from the storage device 115.
[0043] In some embodiments, certain components may reside and execute on the same computer. For example, in some embodiments, a client computer 85 such as a data agent 95, a media agent 105, or a storage manager 100 coordinates and directs local archiving, migration, and retrieval application functions as further described in U.S. patent application Ser. No. 09/610,738. This client computer 85 can function independently or together with other similar client computers 85.
[0044] As described herein, storage operations may be performed by one or more media agents 105 at the direction of a storage manager 100 via the storage manager 100 or directly in communication with a client 85. Employing multiple media agents 105 in a storage system allows flexibility in associating one or more media agents 105 with a client 85, or other component. For example, one media agent 105 may be associated with a first client 85 and perform storage operations in regard to the associated client 85, e.g., using a primary copy of the first client 85, and another media agent 105 may be associated with a second client 85 and perform storage operations in regard with the second client 85, e.g., using a replication copy 200 of the second client 85. Thus, in the event that one or more system components fails or is unavailable, another system component, e.g., a media agent 105, may be used to perform a storage operation.
[0045] Referring to FIG. 3 , a replication copy 200 of a first secondary copy 90 may be created by a third party application 150 or by cell components such as a media agent 105b, according to storage policies or at the direction of a storage manager 100. First secondary copy 90 is a first secondary copy or other initial copy of a primary copy 86 of data generated by client 85. First secondary copy 90 may be created via media agent 105a (which may be the same component as media agent 105b, or a separate component). As shown in FIG. 3 , the replication copy 200 may be coupled to a media agent 105b and hosted by host 201. Media agent 105b or replication software on the first secondary copy 90 may be used to create replication copy 200, e.g., using known replication techniques. If the replication copy 200 is created by a third party application 150, the media agent 105b may interface with the third party application 150 to access the replication copy 200. The third party application 150 may be a software module which may communicate with a media agent 105 and replication copy 200. The media agent 105 may access the replication copy 200 to perform storage operations, such as creating secondary copies stored to secondary storage 200. Although, the media agent 105 may access first secondary copy 90 to perform storage operations, such configuration is not ideal because first secondary copy 90 is preferably free for use by other system components and for other storage operations.
[0046] One storage operation that the media agent 105 may perform in connection with the replication copy 200 or first secondary copy 90 is creation of a secondary copy or other backup operation. The media agent 105 may create, in accordance with a storage policy, a secondary copy 220 that may be created using data of a replication copy 200 or first secondary copy 90. In general, a secondary copy 220, such as an auxiliary copy, backup copy, or other copy, is stored to media that is slower than media used to store a first secondary copy 90 and the secondary copy 220 may be created to migrate electronic data to storage, such as at an offsite facility.
[0047] A storage policy stored in an index or database 110 or 111 may initiate a secondary copy operation and the media agent 105 may determine which copy to use for the copy operation. For example, the media agent 105 may check network and cell resources, storage policies, job scheduling or other storage characteristic to determine whether the first secondary copy 90 or replication copy 200 should be used. For example, a media agent 105 (or storage manager, jobs agent or other system component) may consult a job schedule, such as a storage operation schedule 250 depicted in FIG. 4 . The storage operation schedule 250 may include a schedule or timeline for storage operations performed, currently in operation or scheduled in the future. Information about storage operation scheduling may be obtained from a storage policy, communicated from one or more system components, or provided by a system user or administrator.
[0048] In addition, preferences as to use of a replication copy, first secondary copy or other source data may be established for performing a storage operation, for example, in a storage policy or other preference associated with one or more cells, system components, scheduling policy, retention policy, or other preference. A user may set a preference or other criteria which may be used to select a replication copy or first secondary copy to perform a storage operation, or alternatively, a default template setting in a storage policy or other selection criteria, or a user preference may be that new media added to a storage device should use a replication copy in performing a storage operation, or a particular cell may include a client for which a replication copy may be used to perform storage operations, or other storage preference or selection criteria.
[0049] As shown, a first storage operation 252 may be scheduled to occur from T.sub.0 to T.sub.2. The first storage operation 252 may be any storage operation and may be associated with a storage policy, storage preference or other criteria which may indicate a preference for using or selecting a first secondary copy or a replication copy to perform the storage operation. During the time period T.sub.0 and T.sub.2, a second storage operation 254 is scheduled to occur from T.sub.1 to T.sub.4. The second storage operation 254 may also be associated with a storage policy or storage preference regarding a copy to use to perform the storage operation. Overlapping with the second storage operation 254, a third storage operation 256 is scheduled for T.sub.3 to T.sub.5. As with the first and second storage operations 252 and 254, respectively, the third storage operation 256 may be associated with one or more storage preferences or a storage policy. Such storage preferences may also include a relative priority weighting for performing the storage operation, and a priority weighting for using a particular copy for performing the storage operation, such as the first secondary copy or replication copy. Weighting each storage preference provides the ability to calculate an overall metric for selection of one or more aspects of performing the storage operation.
[0050] A storage manager, jobs agent, media agent or other system component, may consult the storage operation schedule 250 and/or an index to identify criteria for selecting a data source, or determine a priority of or availability to use a first secondary copy or a replication copy for a storage operation. For example, the first storage operation 252 may be associated with a storage preference that indicates that a first secondary copy or a replication copy may be used to perform a storage operation, and have a medium priority level. The second storage operation 254 may be associated with a storage preference that indicates that a first secondary copy is preferably used to perform a storage operation and it has a higher priority than first storage operation 252. The third storage operation 256 may be associated with a storage preference which indicates that a first secondary copy is preferably used to perform a storage operation and has a medium priority level. In such a case, the storage manager (or jobs agent, media agent or other system component) may automatically select a replication copy for performing the first storage operation 252, and a first secondary copy for performing the second storage operation 254. The storage manager may calculate the storage operation priority, other preferences and first secondary copy availability and override the data source preference with respect to the third storage operation 256 and select or allocate the replication copy for use in performing the third storage operation 256 based on selection criteria, for example, the higher priority weighting of the second storage operation 254 and the availability of the first secondary copy which will be in use in the second storage operation 254 at the time the third storage operation 256 is to be initiated.
[0051] A media agent 105 may consult a database table in its index 110 or a storage manager index 111 to identify a replication copy 200 that corresponds to a first secondary copy 90. An example of such database table may be the table 305 depicted in FIG. 5 . As shown, table 305 includes information useful in performing storage operations, such as network pathways for primary copies 320 and corresponding replication copies 310. For example, first secondary copy 325 at c:/mydocuments/files corresponds to replication copy 345 at F:/mydocuments/files. First secondary copy 330 at c:/programfiles/files, however does not have a corresponding replication copy as shown by the empty record, 350. First secondary copy 335 at c:/database/files corresponds to g:/database/files 355. The table 305 may also include other information about the first secondary copies 320 and replication copies 310 such as a system component associated with each, media type, storage type, data content, data type, or other information. In addition, table 305 may include links or relational pointers between a production data set, primary copy, first secondary copy and a replication copy.
[0052] As described herein, using a replication copy to perform a storage operation, which may otherwise be performed using a first secondary copy, frees up the first secondary copy, and any system components that may be associated with the first secondary copy, for other uses. For example, a first media agent may be associated with a particular client and its respective data agent, data store or first secondary copy, and a second media agent may be associated with the same client and a replication copy associated with the client. In this case, the first secondary copy may be used to perform storage operations or other operations in connection with the first media agent, data agent or client, and concurrently, the replication copy could be used by the second media agent to perform a secondary copy operation or other storage operation.
[0053] A media agent or other system component may update a table regarding replication copy information, such as the table depicted in FIG. 5 , and direct a storage operation according to the flow diagram depicted in FIG. 6 . The table provides a convenient reference point for cell components to identify a replication copy associations or information about cell components. The table may be updated continuously as information about a replication copy becomes known to a media agent, storage manager or other cell component, such as a client.
[0054] A storage operation request may be received, such as a request to create a secondary copy or other which may include information for identifying data for performing a storage operation, step 410. The storage operation request may be user initiated or automatically initiated in accordance with a storage policy, job schedule, retention policy or other initiator. The storage operation request may include, among other information, data identifying the first secondary copy or corresponding client having source or production data to be used in the storage operation.
[0055] A storage policy may be identified that is associated with the data for performing the storage operation, step 420. In general, the storage policy is associated in an index or data table with a data source, such as a client, sub-client, or other system component or data classification. The storage policy may include one or more storage preferences which may indicate a priority for performing a storage operation, one or more criteria for selecting a component, data item, or data source with which to perform a storage operation, or other preference. The storage policy may be user defined, a default template, or other set of preferences.
[0056] A storage manager, media agent or other system component may determine whether a replication copy of data is available to perform a storage operation, step 430. In general, the replication copy information may be obtained by a media agent (or other component) by consulting a table, index or database to determine whether there is a replication copy that is associated with a first secondary copy of data targets, such as the identified data for performing the storage operation. Generally, the media agent will check the table for a replication copy if a storage preference or a user preference indicates that a replication copy should be used. However, even if the storage preference does not indicate that a replication copy should be used, a storage policy may have a default setting such that a media agent should determine whether to use a first secondary copy or replication copy in accordance with optimizing system resources, such as, for example, in accordance with availability of system components and network pathways, job scheduling, or other system characteristics, as described herein. Thus, a media agent may check for a replication copy whether or not a storage preference dictates use of a replication copy.
[0057] Availability of the replication copy may also include a determination that the replication copy is online or offline, the replication copy is in use for another storage operation, or otherwise available or unavailable. In addition to consulting the table to check for availability, a media agent may ping or communicate with the replication copy to determine if it is online and available.
[0058] In the event that no replication copy exists, a media agent or storage manager may direct the storage operation to be performed using a first secondary copy, step 440. Upon performance of the storage operation, the index is updated to reflect the completed storage operation, step 455. The index may be updated to include information about the completed storage operation, such as creation of a secondary copy, and information about the data source, e.g., the first secondary copy.
[0059] The media agent or storage manager may also determine whether a lack of a replication copy of data is causing inefficiencies in performing storage operations and may direct that in view of future storage operations, scheduled, or anticipated, for example, based on a storage policy, that a replication copy be produced for all, or particular types or data. For example, a replication copy may be created using a third party application, which may be interfaced directly by a media agent, or alternatively created by the media agent, replication agent, or other systems and methods described herein or known in the art.
[0060] If a replication copy exists, e.g., the media agent consults a table and finds a replication copy which is associated with a first secondary copy that is the data source for the storage operation, the media agent (or other system component) may calculate a selection criteria, step 445, for selecting a data source to perform the storage operation. For example, as described herein, a storage operation priority, storage preference, criteria, or other basis may be used to select a replication copy or first secondary copy to perform a storage operation. In one example, a first storage operation may be performed using a first secondary copy, step 440, if a selection criteria indicates that a first secondary copy should be used. For example, a criteria that a storage operation is a high priority storage operation, or concurrent storage operation scheduling, or other criteria, may cause a storage manager to select a first secondary copy to be used for a particular storage operation. In another example, a second storage operation having a medium priority which can use a replication copy may be performed using a replication copy, step 450.
[0061] In both scenarios, information about the completed storage operation may be stored to an index, step 455. Although a replication copy may have been used to create a secondary copy, the index may be updated with data indicating that a primary copy or a first secondary copy was used to create a secondary copy. Such an index entry is useful in the event that other components or modules may not recognize that a replication copy as an appropriate data source for creating a secondary copy, which may cause an error or other system failure.
[0062] 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. Software and other modules may be accessible via local memory, via a network, via a browser or other application in an ASP context, or via other means suitable for the purposes described herein. 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. Screenshots presented and described herein can be displayed differently as known in the art to input, access, change, manipulate, modify, alter, and work with information.
[0063] While the invention has been described and illustrated in connection with preferred embodiments, many variations and modifications as will be evident to those skilled in this art may be made without departing from the spirit and scope of the invention, and the invention is thus not to be limited to the precise details of methodology or construction set forth above as such variations and modification are intended to be included within the scope of the invention.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A method for performing a storage operation using a replication copy, the method comprising:
receiving from a management module executing on at least one processor an instruction to perform a storage operation on a first set of data stored on a first storage volume;
receiving a storage policy indicating that the storage operation should be performed, wherein rather than performing the storage operation on the first set of data stored on the first storage volume, the storage operation is performed on a replication copy of the first set of data if when a plurality of storage selection criteria is satisfied, wherein the plurality of storage selection criteria comprises at least one of a network pathway availability and a security requirement of the replication copy, wherein each of the plurality of storage selection criteria is assigned a corresponding priority weighting factor, the replication copy being stored on a second storage volume;
determining if the replication copy is available by consulting a schedule of storage operations involving the replication copy;
calculating an overall metric based on the priority weighting factors assigned to the network pathway availability and the security requirement of the replication copy; and
performing the storage operation on data of the replication copy on the second storage volume rather than the first set of data on the first storage volume, when the replication copy is available and when the overall metric is within a determined priority level.
2. The method of claim 1, additionally comprising updating an index to indicate completion of the storage operation.
3. The method of claim 2, wherein said updating comprises modifying the index to indicate that the storage operation was performed on the first set of data after the storage operation was performed on the replication copy.
4. The method of claim 1, additionally comprising generating the first set of data by creating a copy of a set of production data of a particular software application.
5. The method of claim 4, additionally comprising additionally comprising monitoring changes to the production data with a filter driver.
6. The method of claim 5, wherein said generating the first set of data comprises processing a log file containing a least a portion of the changes monitored by the filter driver.
7. The method of claim 1, additionally comprising generating the replication copy via a snapshot operation.
8. The method of claim 1, additionally comprising generating the replication copy via a mirroring operation.
9. The method of claim 1, additionally comprising performing a second storage operation on the first set of data, wherein the second storage operation at least partially overlaps the first storage operation.
10. The method of claim 1, wherein said determining further comprises determining if the replication is online or offline.
11. A storage management system for performing a storage operation, the system comprising:
a media agent component configured to access a first copy of production data stored in a first storage volume and a second copy of the production data stored in a second storage volume;
a storage management component communicatively coupled to the media agent component and configured to,
receive a storage operation request relating to the first copy of the production data, and
determine according to selection criteria of at least one storage policy if the second copy on the second storage volume should be used, in place of the first copy on the first storage volume, to perform the storage operation, wherein the selection criteria comprises at least one of a network pathway availability and a security requirement of the second copy, and wherein said determining includes calculating a metric based on a priority weighting of the network pathway availability and the security requirement of the second copy, and
and wherein the media agent component is further configured to perform the storage operation using the second copy on the second storage volume when the second copy on the second storage volume is available, and the metric is within a predetermined range.
12. The system of claim 11, wherein the storage management component is configured to instruct the media agent component to perform the storage operation.
13. The system of claim 11, wherein the storage operation request is further associated with a second priority weighting relative to other storage operation requests, and wherein the storage management component is further configured to compare the second priority weighting in said determining according to the selection criteria.
14. The system of claim 11, further comprising a replication agent configured to generate the second copy of the production data based on the first copy of the production data.
15. The system of claim 11, wherein the storage management component is configured to access a database to identify the second copy of the production data in response to said receiving the storage operation request relating to the first copy of the production data.
16. The system of claim 11, wherein the media agent is configured to access a storage operation schedule to determine the availability of the second copy of the production data.
17. The system of claim 11, wherein the media agent is configured to access at least one of the first and second sets of data via a small computer system interface (SCSI) communications link.
18. The system of claim 11, wherein the first storage volume comprise a faster access time than the second storage volume.
Patent Citations (428)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4296465(A) | 1981-10-01 | Lemak | Applicant |
| US4686620(A) | 1987-08-01 | Ng | Applicant |
| US4995035(A) | 1991-02-01 | Cole et al. | Applicant |
| US5005122(A) | 1991-04-01 | Griffin et al. | Applicant |
| US5093912(A) | 1992-03-01 | Dong et al. | Applicant |
| US5133065(A) | 1992-07-01 | Cheffetz et al. | Applicant |
| US5193154(A) | 1993-03-01 | Kitajima et al. | Applicant |
| US5212772(A) | 1993-05-01 | Masters | Applicant |
| US5226157(A) | 1993-07-01 | Nakano et al. | Applicant |
| US5239647(A) | 1993-08-01 | Anglin et al. | Applicant |
| US5241668(A) | 1993-08-01 | Eastridge et al. | Applicant |
| US5241670(A) | 1993-08-01 | Eastridge et al. | Applicant |
| US5263154(A) | 1993-11-01 | Eastridge et al. | Applicant |
| US5265159(A) | 1993-11-01 | Kung | Applicant |
| US5276860(A) | 1994-01-01 | Fortier et al. | Applicant |
| US5276867(A) | 1994-01-01 | Kenley et al. | Applicant |
| US5287500(A) | 1994-02-01 | Stoppani, Jr. | Applicant |
| US5301351(A) | 1994-04-01 | Jippo | Applicant |
| US5311509(A) | 1994-05-01 | Heddes et al. | Applicant |
| US5317731(A) | 1994-05-01 | Dias et al. | Applicant |
| US5321816(A) | 1994-06-01 | Rogan et al. | Applicant |
| US5333315(A) | 1994-07-01 | Saether et al. | Applicant |
| US5347653(A) | 1994-09-01 | Flynn et al. | Applicant |
| US5369757(A) | 1994-11-01 | Spiro et al. | Applicant |
| US5403639(A) | 1995-04-01 | Belsan et al. | Applicant |
| US5410700(A) | 1995-04-01 | Fecteau et al. | Applicant |
| US5448724(A) | 1995-09-01 | Hayashi et al. | Applicant |
| US5455926(A) | 1995-10-01 | Keele et al. | Applicant |
| US5491810(A) | 1996-02-01 | Allen | Applicant |
| US5495607(A) | 1996-02-01 | Pisello et al. | Applicant |
| US5504873(A) | 1996-04-01 | Martin et al. | Applicant |
| US5544345(A) | 1996-08-01 | Carpenter et al. | Applicant |
| US5544347(A) | 1996-08-01 | Yanai et al. | Applicant |
| US5555404(A) | 1996-09-01 | Torbjornsen et al. | Applicant |
| US5559957(A) | 1996-09-01 | Balk | Applicant |
| US5559991(A) | 1996-09-01 | Kanfi | Applicant |
| US5598546(A) | 1997-01-01 | Blomgren | Applicant |
| US5604862(A) | 1997-02-01 | Midgely et al. | Applicant |
| US5615392(A) | 1997-03-01 | Harrison et al. | Applicant |
| US5619644(A) | 1997-04-01 | Crockett et al. | Applicant |
| US5638509(A) | 1997-06-01 | Dunphy et al. | Applicant |
| US5642496(A) | 1997-06-01 | Kanfi | Applicant |
| US5673381(A) | 1997-09-01 | Huai et al. | Applicant |
| US5675511(A) | 1997-10-01 | Prasad et al. | Applicant |
| US5677900(A) | 1997-10-01 | Nishida et al. | Applicant |
| US5682513(A) | 1997-10-01 | Candelaria et al. | Applicant |
| US5687343(A) | 1997-11-01 | Fecteau et al. | Applicant |
| US5689706(A) | 1997-11-01 | Rao et al. | Applicant |
| US5699361(A) | 1997-12-01 | Ding et al. | Applicant |
| US5719786(A) | 1998-02-01 | Nelson et al. | Applicant |
| US5720026(A) | 1998-02-01 | Uemura et al. | Applicant |
| US5729743(A) | 1998-03-01 | Squibb | Applicant |
| US5737747(A) | 1998-04-01 | Vishlitsky et al. | Applicant |
| US5742792(A) | 1998-04-01 | Yanai et al. | Applicant |
| US5751997(A) | 1998-05-01 | Kullick et al. | Applicant |
| US5758359(A) | 1998-05-01 | Saxon | Applicant |
| US5761677(A) | 1998-06-01 | Senator et al. | Applicant |
| US5761734(A) | 1998-06-01 | Pfefffer et al. | Applicant |
| US5764972(A) | 1998-06-01 | Crouse et al. | Applicant |
| US5765173(A) | 1998-06-01 | Cane et al. | Applicant |
| US5778395(A) | 1998-07-01 | Whiting et al. | Applicant |
| US5790114(A) | 1998-08-01 | Geaghan et al. | Applicant |
| US5790828(A) | 1998-08-01 | Jost | Applicant |
| US5805920(A) | 1998-09-01 | Sprenkle et al. | Applicant |
| US5812398(A) | 1998-09-01 | Nielsen | Applicant |
| US5813009(A) | 1998-09-01 | Johnson et al. | Applicant |
| US5813017(A) | 1998-09-01 | Morris | Applicant |
| US5829046(A) | 1998-10-01 | Tzelnic et al. | Applicant |
| US5860104(A) | 1999-01-01 | Witt et al. | Applicant |
| US5875478(A) | 1999-02-01 | Blumenau | Applicant |
| US5875481(A) | 1999-02-01 | Ashton et al. | Applicant |
| US5878408(A) | 1999-03-01 | Van Huben et al. | Applicant |
| US5887134(A) | 1999-03-01 | Ebrahim | Applicant |
| US5901327(A) | 1999-05-01 | Ofek | Applicant |
| US5907621(A) | 1999-05-01 | Bachman et al. | Applicant |
| US5907672(A) | 1999-05-01 | Matze et al. | Applicant |
| US5924102(A) | 1999-07-01 | Perks | Applicant |
| US5926836(A) | 1999-07-01 | Blumenau | Applicant |
| US5933104(A) | 1999-08-01 | Kimura | Applicant |
| US5933601(A) | 1999-08-01 | Fanshier et al. | Applicant |
| US5950205(A) | 1999-09-01 | Aviani, Jr. | Applicant |
| US5956519(A) | 1999-09-01 | Wise et al. | Applicant |
| US5958005(A) | 1999-09-01 | Thorne et al. | Applicant |
| US5970233(A) | 1999-10-01 | Lie et al. | Applicant |
| US5970255(A) | 1999-10-01 | Tran et al. | Applicant |
| US5974563(A) | 1999-10-01 | Beeler, Jr. | Applicant |
| US5987478(A) | 1999-11-01 | See et al. | Applicant |
| US5991779(A) | 1999-11-01 | Bejar | Applicant |
| US5995091(A) | 1999-11-01 | Near et al. | Applicant |
| US6003089(A) | 1999-12-01 | Shaffer et al. | Applicant |
| US6009274(A) | 1999-12-01 | Fletcher et al. | Applicant |
| US6012090(A) | 2000-01-01 | Chung et al. | Applicant |
| US6021415(A) | 2000-02-01 | Cannon et al. | Applicant |
| US6021475(A) | 2000-02-01 | Nguyen et al. | Applicant |
| US6023710(A) | 2000-02-01 | Steiner et al. | Applicant |
| US6026414(A) | 2000-02-01 | Anglin | Applicant |
| US6052735(A) | 2000-04-01 | Ulrich et al. | Applicant |
| US6061692(A) | 2000-05-01 | Thomas et al. | Applicant |
| US6072490(A) | 2000-06-01 | Bates et al. | Applicant |
| US6076148(A) | 2000-06-01 | Kedem et al. | Applicant |
| US6094416(A) | 2000-07-01 | Ying | Applicant |
| US6105129(A) | 2000-08-01 | Meier et al. | Applicant |
| US6112239(A) | 2000-08-01 | Kenner et al. | Applicant |
| US6122668(A) | 2000-09-01 | Teng et al. | Applicant |
| US6131095(A) | 2000-10-01 | Low et al. | Applicant |
| US6131148(A) | 2000-10-01 | West et al. | Applicant |
| US6131190(A) | 2000-10-01 | Sidwell | Applicant |
| US6137864(A) | 2000-10-01 | Yaker | Applicant |
| US6148377(A) | 2000-11-01 | Carter et al. | Applicant |
| US6148412(A) | 2000-11-01 | Cannon et al. | Applicant |
| US6154787(A) | 2000-11-01 | Urevig et al. | Applicant |
| US6154852(A) | 2000-11-01 | Amundson et al. | Applicant |
| US6161111(A) | 2000-12-01 | Mutalik et al. | Applicant |
| US6163856(A) | 2000-12-01 | Dion et al. | Applicant |
| US6167402(A) | 2000-12-01 | Yeager | Applicant |
| US6175829(B1) | 2001-01-01 | Li et al. | Applicant |
| US6195695(B1) | 2001-02-01 | Cheston et al. | Applicant |
| US6205450(B1) | 2001-03-01 | Kanome et al. | Applicant |
| US6212512(B1) | 2001-04-01 | Barney et al. | Applicant |
| US6212521(B1) | 2001-04-01 | Minami et al. | Applicant |
| US6230164(B1) | 2001-05-01 | Rikieta et al. | Applicant |
| US6260069(B1) | 2001-07-01 | Anglin | Applicant |
| US6269431(B1) | 2001-07-01 | Dunham | Examiner |
| US6275953(B1) | 2001-08-01 | Vahalia et al. | Applicant |
| US6292783(B1) | 2001-09-01 | Rohler | Applicant |
| US6301592(B1) | 2001-10-01 | Aoyama et al. | Applicant |
| US6304880(B1) | 2001-10-01 | Kishi | Applicant |
| US6311193(B1) | 2001-10-01 | Sekido et al. | Applicant |
| US6324581(B1) | 2001-11-01 | Xu et al. | Applicant |
| US6328766(B1) | 2001-12-01 | Long | Applicant |
| US6330570(B1) | 2001-12-01 | Crighton et al. | Applicant |
| US6330642(B1) | 2001-12-01 | Carteau | Applicant |
| US6343324(B1) | 2002-01-01 | Hubis et al. | Applicant |
| US6350199(B1) | 2002-02-01 | Williams et al. | Applicant |
| USRE37601(E) | 2002-03-01 | Eastridge et al. | Applicant |
| US6353878(B1) | 2002-03-01 | Dunham | Applicant |
| US6356801(B1) | 2002-03-01 | Goodman et al. | Applicant |
| US6363464(B1) | 2002-03-01 | Mangione | Applicant |
| US6366986(B1) | 2002-04-01 | St. Pierre et al. | Applicant |
| US6366988(B1) | 2002-04-01 | Skiba et al. | Applicant |
| US6374336(B1) | 2002-04-01 | Peters et al. | Applicant |
| US6374363(B1) | 2002-04-01 | Wu et al. | Applicant |
| US6389432(B1) | 2002-05-01 | Pothapragada et al. | Applicant |
| US6397308(B1) | 2002-05-01 | Ofek et al. | Applicant |
| US6418478(B1) | 2002-07-01 | Ignatius et al. | Applicant |
| US6421711(B1) | 2002-07-01 | Blumenau et al. | Applicant |
| US6434681(B1) | 2002-08-01 | Amangau | Applicant |
| US6473775(B1) | 2002-10-01 | Kusters et al. | Applicant |
| US6487561(B1) | 2002-11-01 | Ofek et al. | Applicant |
| US6487644(B1) | 2002-11-01 | Huebsch et al. | Applicant |
| US6487645(B1) | 2002-11-01 | Clark et al. | Applicant |
| US6519679(B2) | 2003-02-01 | Devireddy et al. | Applicant |
| US6538669(B1) | 2003-03-01 | Lagueux, Jr. et al. | Applicant |
| US6539462(B1) | 2003-03-01 | Mikkelsen et al. | Applicant |
| US6542909(B1) | 2003-04-01 | Tamer et al. | Applicant |
| US6542972(B2) | 2003-04-01 | Ignatius et al. | Applicant |
| US6564228(B1) | 2003-05-01 | O'Connor | Applicant |
| US6581143(B2) | 2003-06-01 | Gagne et al. | Applicant |
| US6604118(B2) | 2003-08-01 | Kleinman et al. | Applicant |
| US6604149(B1) | 2003-08-01 | Deo et al. | Applicant |
| US6631477(B1) | 2003-10-01 | LeCrone et al. | Applicant |
| US6631493(B2) | 2003-10-01 | Ottesen et al. | Applicant |
| US6647396(B2) | 2003-11-01 | Parnell et al. | Applicant |
| US6647473(B1) | 2003-11-01 | Golds et al. | Applicant |
| US6651075(B1) | 2003-11-01 | Kusters et al. | Applicant |
| US6654825(B2) | 2003-11-01 | Clapp et al. | Applicant |
| US6658436(B2) | 2003-12-01 | Oshinsy et al. | Applicant |
| US6658526(B2) | 2003-12-01 | Nguyen et al. | Applicant |
| US6662198(B2) | 2003-12-01 | Satyanarayanan et al. | Applicant |
| US6665815(B1) | 2003-12-01 | Goldstein et al. | Applicant |
| US6681230(B1) | 2004-01-01 | Blott et al. | Applicant |
| US6721767(B2) | 2004-04-01 | De Meno et al. | Applicant |
| US6728733(B2) | 2004-04-01 | Tokui | Applicant |
| US6732124(B1) | 2004-05-01 | Koseki et al. | Applicant |
| US6732125(B1) | 2004-05-01 | Autrey et al. | Applicant |
| US6742092(B1) | 2004-05-01 | Huebsch et al. | Applicant |
| US6748504(B2) | 2004-06-01 | Sawdon et al. | Applicant |
| US6751635(B1) | 2004-06-01 | Chen et al. | Applicant |
| US6757794(B2) | 2004-06-01 | Cabrera et al. | Applicant |
| US6760723(B2) | 2004-07-01 | Oshinsky et al. | Applicant |
| US6763351(B1) | 2004-07-01 | Subramaniam et al. | Applicant |
| US6789161(B1) | 2004-09-01 | Blendermann et al. | Applicant |
| US6792518(B2) | 2004-09-01 | Armangau et al. | Applicant |
| US6799258(B1) | 2004-09-01 | Linde | Applicant |
| US6836779(B2) | 2004-12-01 | Poulin | Applicant |
| US6871163(B2) | 2005-03-01 | Hiller et al. | Applicant |
| US6871271(B2) | 2005-03-01 | Ohran et al. | Applicant |
| US6880051(B2) | 2005-04-01 | Timpanaro-Perrotta | Applicant |
| US6886020(B1) | 2005-04-01 | Zahavi et al. | Examiner |
| US6892211(B2) | 2005-05-01 | Hitz et al. | Applicant |
| US6938135(B1) | 2005-08-01 | Kekre et al. | Applicant |
| US6952758(B2) | 2005-10-01 | Chron et al. | Applicant |
| US6954834(B2) | 2005-10-01 | Slater et al. | Applicant |
| US6968351(B2) | 2005-11-01 | Butterworth | Applicant |
| US6973553(B1) | 2005-12-01 | Archibald, Jr. et al. | Applicant |
| US6978265(B2) | 2005-12-01 | Schumacher | Applicant |
| US6981177(B2) | 2005-12-01 | Beattie | Applicant |
| US6983351(B2) | 2006-01-01 | Gibble et al. | Applicant |
| US6993539(B2) | 2006-01-01 | Federwisch et al. | Applicant |
| US7003519(B1) | 2006-02-01 | Biettron et al. | Applicant |
| US7003641(B2) | 2006-02-01 | Prahlad et al. | Applicant |
| US7032131(B2) | 2006-04-01 | Lubbers et al. | Applicant |
| US7035880(B1) | 2006-04-01 | Crescenti et al. | Applicant |
| US7051050(B2) | 2006-05-01 | Chen et al. | Applicant |
| US7062761(B2) | 2006-06-01 | Slavin et al. | Applicant |
| US7065538(B2) | 2006-06-01 | Aronoff et al. | Applicant |
| US7082441(B1) | 2006-07-01 | Zahavi et al. | Applicant |
| US7085787(B2) | 2006-08-01 | Beier et al. | Applicant |
| US7085904(B2) | 2006-08-01 | Mizuno et al. | Applicant |
| US7086787(B2) | 2006-08-01 | Okada et al. | Applicant |
| US7096315(B2) | 2006-08-01 | Takeda et al. | Applicant |
| US7103731(B2) | 2006-09-01 | Gibble et al. | Applicant |
| US7103740(B1) | 2006-09-01 | Colgrove et al. | Applicant |
| US7107298(B2) | 2006-09-01 | Prahlad et al. | Applicant |
| US7107395(B1) | 2006-09-01 | Ofek et al. | Applicant |
| US7120757(B2) | 2006-10-01 | Tsuge | Applicant |
| US7130860(B2) | 2006-10-01 | Pachet | Applicant |
| US7130970(B2) | 2006-10-01 | Devassy et al. | Applicant |
| US7139932(B2) | 2006-11-01 | Watanabe | Applicant |
| US7155465(B2) | 2006-12-01 | Lee et al. | Applicant |
| US7155633(B2) | 2006-12-01 | Tuma et al. | Applicant |
| US7191198(B2) | 2007-03-01 | Asano et al. | Examiner |
| US7194454(B2) | 2007-03-01 | Hansen et al. | Applicant |
| US7203807(B2) | 2007-04-01 | Urabe et al. | Applicant |
| US7209972(B1) | 2007-04-01 | Ignatius et al. | Applicant |
| US7225204(B2) | 2007-05-01 | Manley et al. | Applicant |
| US7225208(B2) | 2007-05-01 | Midgley et al. | Applicant |
| US7225210(B2) | 2007-05-01 | Guthrie, II | Applicant |
| US7228456(B2) | 2007-06-01 | Lecrone et al. | Applicant |
| US7231544(B2) | 2007-06-01 | Tan et al. | Applicant |
| US7234115(B1) | 2007-06-01 | Sprauve et al. | Applicant |
| US7246140(B2) | 2007-07-01 | Therrien et al. | Applicant |
| US7246207(B2) | 2007-07-01 | Kottomtharayil et al. | Applicant |
| US7269612(B2) | 2007-09-01 | Devarakonda et al. | Applicant |
| US7272606(B2) | 2007-09-01 | Borthakur et al. | Applicant |
| US7275138(B2) | 2007-09-01 | Saika | Applicant |
| US7275177(B2) | 2007-09-01 | Armangau et al. | Applicant |
| US7278142(B2) | 2007-10-01 | Bandhole et al. | Applicant |
| US7287047(B2) | 2007-10-01 | Kavuri | Applicant |
| US7293133(B1) | 2007-11-01 | Colgrove et al. | Applicant |
| US7296125(B2) | 2007-11-01 | Ohran | Applicant |
| US7315923(B2) | 2008-01-01 | Retnamma et al. | Applicant |
| US7343356(B2) | 2008-03-01 | Prahlad et al. | Applicant |
| US7343365(B2) | 2008-03-01 | Farnham et al. | Applicant |
| US7343453(B2) | 2008-03-01 | Prahlad et al. | Applicant |
| US7343459(B2) | 2008-03-01 | Prahlad et al. | Applicant |
| US7346623(B2) | 2008-03-01 | Prahlad et al. | Applicant |
| US7346751(B2) | 2008-03-01 | Prahlad et al. | Applicant |
| US7356657(B2) | 2008-04-01 | Mikami | Applicant |
| US7359917(B2) | 2008-04-01 | Winter et al. | Applicant |
| US7380072(B2) | 2008-05-01 | Kottomtharayil et al. | Applicant |
| US7389311(B1) | 2008-06-01 | Crescenti et al. | Applicant |
| US7395282(B1) | 2008-07-01 | Crescenti et al. | Applicant |
| US7409509(B2) | 2008-08-01 | Devassy et al. | Applicant |
| US7430587(B2) | 2008-09-01 | Malone et al. | Applicant |
| US7433301(B2) | 2008-10-01 | Akahane et al. | Applicant |
| US7440982(B2) | 2008-10-01 | Lu et al. | Applicant |
| US7454569(B2) | 2008-11-01 | Kavuri et al. | Applicant |
| US7467167(B2) | 2008-12-01 | Patterson | Applicant |
| US7467267(B1) | 2008-12-01 | Mayock | Applicant |
| US7472238(B1) | 2008-12-01 | Gokhale | Applicant |
| US7484054(B2) | 2009-01-01 | Kottomtharayil et al. | Applicant |
| US7490207(B2) | 2009-02-01 | Amarendran | Applicant |
| US7496589(B1) | 2009-02-01 | Jain et al. | Applicant |
| US7496690(B2) | 2009-02-01 | Beverly et al. | Applicant |
| US7500053(B1) | 2009-03-01 | Kavuri et al. | Applicant |
| US7500150(B2) | 2009-03-01 | Sharma et al. | Applicant |
| US7509316(B2) | 2009-03-01 | Greenblatt et al. | Applicant |
| US7512601(B2) | 2009-03-01 | Cucerzan et al. | Applicant |
| US7519726(B2) | 2009-04-01 | Palliyll et al. | Applicant |
| US7529748(B2) | 2009-05-01 | Wen et al. | Applicant |
| US7529782(B2) | 2009-05-01 | Prahlad et al. | Applicant |
| US7532340(B2) | 2009-05-01 | Koppich et al. | Applicant |
| US7536291(B1) | 2009-05-01 | Retnamma et al. | Applicant |
| US7539707(B2) | 2009-05-01 | Prahlad et al. | Applicant |
| US7543125(B2) | 2009-06-01 | Gokhale | Applicant |
| US7546324(B2) | 2009-06-01 | Prahlad et al. | Applicant |
| US7581077(B2) | 2009-08-01 | Ignatius et al. | Applicant |
| US7596586(B2) | 2009-09-01 | Gokhale et al. | Applicant |
| US7606844(B2) | 2009-10-01 | Kottomtharayil | Applicant |
| US7613748(B2) | 2009-11-01 | Brockway et al. | Applicant |
| US7617253(B2) | 2009-11-01 | Prahlad et al. | Applicant |
| US7617262(B2) | 2009-11-01 | Prahlad et al. | Applicant |
| US7617541(B2) | 2009-11-01 | Plotkin et al. | Applicant |
| US7627598(B1) | 2009-12-01 | Burke | Applicant |
| US7627617(B2) | 2009-12-01 | Kavuri et al. | Applicant |
| US7636743(B2) | 2009-12-01 | Erofeev | Applicant |
| US7651593(B2) | 2010-01-01 | Prahlad et al. | Applicant |
| US7661028(B2) | 2010-02-01 | Erofeev | Applicant |
| US7668798(B2) | 2010-02-01 | Scanlon et al. | Applicant |
| US7685126(B2) | 2010-03-01 | Patel et al. | Applicant |
| US7716171(B2) | 2010-05-01 | Kryger | Applicant |
| US7734715(B2) | 2010-06-01 | Hyakutake et al. | Applicant |
| US7831553(B2) | 2010-11-01 | Prahlad et al. | Applicant |
| US7831622(B2) | 2010-11-01 | Prahlad et al. | Applicant |
| US7840537(B2) | 2010-11-01 | Gokhale et al. | Applicant |
| US2001/0029517(A1) | 2001-10-01 | De Meno et al. | Applicant |
| US2001/0044807(A1) | 2001-11-01 | Kleiman et al. | Applicant |
| US2002/0004883(A1) | 2002-01-01 | Nguyen et al. | Applicant |
| US2002/0040376(A1) | 2002-04-01 | Yamanaka et al. | Applicant |
| US2002/0042869(A1) | 2002-04-01 | Tate et al. | Applicant |
| US2002/0049626(A1) | 2002-04-01 | Mathias et al. | Applicant |
| US2002/0049718(A1) | 2002-04-01 | Kleiman et al. | Applicant |
| US2002/0049738(A1) | 2002-04-01 | Epstein | Applicant |
| US2002/0049778(A1) | 2002-04-01 | Bell et al. | Applicant |
| US2002/0069324(A1) | 2002-06-01 | Gerasimov et al. | Applicant |
| US2002/0083055(A1) | 2002-06-01 | Pachet et al. | Applicant |
| US2002/0103848(A1) | 2002-08-01 | Giacomini et al. | Applicant |
| US2002/0107877(A1) | 2002-08-01 | Whiting et al. | Applicant |
| US2002/0133511(A1) | 2002-09-01 | Hostetter et al. | Applicant |
| US2002/0133512(A1) | 2002-09-01 | Milillo et al. | Applicant |
| US2002/0161753(A1) | 2002-10-01 | Inaba et al. | Applicant |
| US2002/0174107(A1) | 2002-11-01 | Poulin | Applicant |
| US2002/0174416(A1) | 2002-11-01 | Bates et al. | Applicant |
| US2003/0018657(A1) | 2003-01-01 | Monday | Applicant |
| US2003/0028736(A1) | 2003-02-01 | Berkowitz et al. | Applicant |
| US2003/0061491(A1) | 2003-03-01 | Jaskiewicz et al. | Applicant |
| US2003/0131278(A1) | 2003-07-01 | Fujibayashi | Applicant |
| US2003/0135783(A1) | 2003-07-01 | Martin et al. | Applicant |
| US2003/0167380(A1) | 2003-09-01 | Green et al. | Applicant |
| US2003/0177149(A1) | 2003-09-01 | Coombs | Applicant |
| US2003/0177321(A1) | 2003-09-01 | Watanabe | Applicant |
| US2003/0187847(A1) | 2003-10-01 | Lubbers et al. | Applicant |
| US2003/0225800(A1) | 2003-12-01 | Kavuri | Applicant |
| US2004/0010487(A1) | 2004-01-01 | Prahlad et al. | Applicant |
| US2004/0015468(A1) | 2004-01-01 | Beier et al. | Applicant |
| US2004/0098425(A1) | 2004-05-01 | Wiss et al. | Examiner |
| US2004/0107199(A1) | 2004-06-01 | Dairymple et al. | Applicant |
| US2004/0117572(A1) | 2004-06-01 | Welsh et al. | Applicant |
| US2004/0139128(A1) | 2004-07-01 | Becker et al. | Applicant |
| US2004/0193953(A1) | 2004-09-01 | Callahan et al. | Applicant |
| US2004/0205206(A1) | 2004-10-01 | Naik et al. | Applicant |
| US2004/0230829(A1) | 2004-11-01 | Dogan et al. | Applicant |
| US2004/0236958(A1) | 2004-11-01 | Teicher et al. | Applicant |
| US2004/0250033(A1) | 2004-12-01 | Prahlad et al. | Applicant |
| US2004/0254919(A1) | 2004-12-01 | Giuseppini | Applicant |
| US2004/0260678(A1) | 2004-12-01 | Verbowski et al. | Applicant |
| US2004/0267836(A1) | 2004-12-01 | Amangau et al. | Applicant |
| US2005/0027892(A1) | 2005-02-01 | McCabe et al. | Applicant |
| US2005/0033800(A1) | 2005-02-01 | Kavuri et al. | Applicant |
| US2005/0044114(A1) | 2005-02-01 | Kottomtharayil et al. | Applicant |
| US2005/0080928(A1) | 2005-04-01 | Beverly et al. | Applicant |
| US2005/0108292(A1) | 2005-05-01 | Burton et al. | Applicant |
| US2005/0114406(A1) | 2005-05-01 | Borthakur et al. | Applicant |
| US2005/0144202(A1) | 2005-06-01 | Chen | Applicant |
| US2005/0187992(A1) | 2005-08-01 | Prahlad et al. | Applicant |
| US2005/0188254(A1) | 2005-08-01 | Urabe et al. | Applicant |
| US2005/0193026(A1) | 2005-09-01 | Prahlad et al. | Applicant |
| US2005/0246376(A1) | 2005-11-01 | Lu et al. | Applicant |
| US2005/0246510(A1) | 2005-11-01 | Retnamma et al. | Applicant |
| US2006/0005048(A1) | 2006-01-01 | Osaki et al. | Applicant |
| US2006/0010154(A1) | 2006-01-01 | Prahlad et al. | Applicant |
| US2006/0010227(A1) | 2006-01-01 | Atluri | Applicant |
| US2006/0020616(A1) | 2006-01-01 | Hardy et al. | Applicant |
| US2006/0136685(A1) | 2006-06-01 | Griv et al. | Applicant |
| US2006/0230244(A1) | 2006-10-01 | Amarendran et al. | Applicant |
| US2006/0242489(A1) | 2006-10-01 | Brockway et al. | Applicant |
| US2007/0043956(A1) | 2007-02-01 | El Far et al. | Applicant |
| US2007/0100867(A1) | 2007-05-01 | Celik et al. | Applicant |
| US2007/0112897(A1) | 2007-05-01 | Asano et al. | Examiner |
| US2007/0124347(A1) | 2007-05-01 | Vivian et al. | Examiner |
| US2007/0124348(A1) | 2007-05-01 | Claborn et al. | Examiner |
| US2007/0143371(A1) | 2007-06-01 | Kottomtharayil | Applicant |
| US2007/0143756(A1) | 2007-06-01 | Gokhale | Applicant |
| US2007/0183224(A1) | 2007-08-01 | Erofeev | Applicant |
| US2007/0185937(A1) | 2007-08-01 | Prahlad et al. | Applicant |
| US2007/0185938(A1) | 2007-08-01 | Prahlad et al. | Applicant |
| US2007/0185939(A1) | 2007-08-01 | Prahlad et al. | Applicant |
| US2007/0185940(A1) | 2007-08-01 | Prahlad et al. | Applicant |
| US2007/0186068(A1) | 2007-08-01 | Agrawal | Applicant |
| US2007/0226438(A1) | 2007-09-01 | Erofeev | Applicant |
| US2007/0244571(A1) | 2007-10-01 | Wilson et al. | Applicant |
| US2007/0288536(A1) | 2007-12-01 | Sen et al. | Applicant |
| US2008/0016293(A1) | 2008-01-01 | Saika | Applicant |
| US2008/0059515(A1) | 2008-03-01 | Fulton | Applicant |
| US2008/0183775(A1) | 2008-07-01 | Prahlad et al. | Applicant |
| US2008/0229037(A1) | 2008-09-01 | Bunte et al. | Applicant |
| US2008/0243914(A1) | 2008-10-01 | Prahlad et al. | Applicant |
| US2008/0243957(A1) | 2008-10-01 | Prahlad et al. | Applicant |
| US2008/0243958(A1) | 2008-10-01 | Prahlad et al. | Applicant |
| US2008/0244177(A1) | 2008-10-01 | Crescenti et al. | Applicant |
| US2009/0319534(A1) | 2009-12-01 | Gokhale | Applicant |
| US2009/0319585(A1) | 2009-12-01 | Gokhale | Applicant |
| US2010/0005259(A1) | 2010-01-01 | Prahlad | Applicant |
| US2010/0049753(A1) | 2010-02-01 | Prahlad et al. | Applicant |
| US2010/0094808(A1) | 2010-04-01 | Erofeev | Applicant |
| US2010/0100529(A1) | 2010-04-01 | Erofeev | Applicant |
| US2010/0122053(A1) | 2010-05-01 | Prahlad et al. | Applicant |
| US2010/0131461(A1) | 2010-05-01 | Prahlad et al. | Applicant |
| US2010/0145909(A1) | 2010-06-01 | Ngo | Applicant |
| US2010/0179941(A1) | 2010-07-01 | Agrawal et al. | Applicant |
| US2010/0205150(A1) | 2010-08-01 | Prahlad et al. | Applicant |
| AU2006331932 | 2006-12-01 | Applicant | |
| CA2632935 | 2006-12-01 | Applicant | |
| EP259912 | 1988-03-01 | Applicant | |
| EP405926 | 1991-01-01 | Applicant | |
| EP467546 | 1992-01-01 | Applicant | |
| EP774715 | 1997-05-01 | Applicant | |
| EP809184 | 1997-11-01 | Applicant | |
| EP862304 | 1998-09-01 | Applicant | |
| EP899662 | 1999-03-01 | Applicant | |
| EP981090 | 2000-02-01 | Applicant | |
| EP1174795 | 2002-01-01 | Applicant | |
| EP1349089 | 2003-01-01 | Applicant | |
| EP1349088 | 2003-10-01 | Applicant | |
| EP1974296 | 2008-10-01 | Applicant | |
| GB2256952 | 1992-12-01 | Applicant | |
| GB2411030 | 2005-08-01 | Applicant | |
| JP5189281 | 1993-07-01 | Applicant | |
| JP6274605 | 1994-09-01 | Applicant | |
| JP9016463 | 1997-01-01 | Applicant | |
| JP11259348 | 1999-09-01 | Applicant | |
| JP200347811 | 2000-12-01 | Applicant | |
| WO930549 | 1993-02-01 | Applicant | |
| WO9303549 | 1993-02-01 | Applicant | |
| WO-95/13580 | 1995-05-01 | Applicant | |
| WO-98/39707 | 1998-09-01 | Applicant | |
| WO98/39707 | 1998-09-01 | Applicant | |
| WO-99/12098 | 1999-03-01 | Applicant | |
| WO99/12098 | 1999-03-01 | Applicant | |
| WO99/14692 | 1999-03-01 | Applicant | |
| WO2/095632 | 2002-11-01 | Applicant | |
| WO-03028183 | 2003-04-01 | Applicant | |
| WO2004034197 | 2004-04-01 | Applicant | |
| WO2005/055093 | 2005-06-01 | Applicant | |
| WO2005/086032 | 2005-09-01 | Applicant | |
| WO2007/053314 | 2007-05-01 | Applicant | |
| WO2007/075587 | 2007-07-01 | Applicant |
Non-Patent Literature (39)
- Armstead et al., “Implementation of a Campus-wide Distributed Mass Storage Service: The Dream vs. Reality,” IEEE, 1995, pp. 190-199.Applicant
- Arneson, David A., Control Data Corporation, Development of Omniserver, Mass Storage Systems, 1990, pp. 88-93.Applicant
- 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.Applicant
- 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.Applicant
- Eitel, “Backup and Storage Management in Distributed Heterogeneous Environments,” IEEE, 1994, pp. 124-126.Applicant
- Jander, M., “Launching Storage-Area Net,” Data Communications, US, McGraw Hill, NY, vol. 27, No. 4 (Mar. 21, 1998), pp. 64-72.Applicant
- Jason Gait, “The Optical File Cabinet: A Random-Access File System for Write-Once Optical Disks,” IEEE Computer, vol. 21, No. 6, pp. 11-22 (1988).Applicant
- 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).Applicant
- U.S. Appl. No. 12/433,238, filed Apr. 30, 2009, Prahlad et al.Applicant
- Ashton, et al., “Two Decades of policy-based storage management for the IBM mainframe computer”, www.research.ibm.com, 19 pages, published Apr. 10, 2003, printed Jan. 3, 2009—cited in U.S. Appl. No. 12/276,868., www.research.ibm.com, Apr. 10, 2003, pp. 19.Applicant
- European Examination Report; Application No. 06848901.2, Apr. 1, 2009, pp. 7.Applicant
- Examiner's Report for Australian Application No. 2003279847, Dated Dec. 9, 2008, 4 pages.Applicant
- Gray, Jim, Reuter, Andreas: “Transaction Processing: Concepts and Techniques” 1994, Morgan Kaufmann Publisher, USA; pp. 646-655.Applicant
- http://en.wikipedia.org/wiki/Naive—Bayes—classifier.Applicant
- International Search Report and Written Opinion; dated Mar. 25, 2010; International Application No. PCT/US2009/066880; 10 pages.Applicant
- International Search Report from International Application No. PCT/US2006/048273, dated May 15, 2007.Applicant
- Lyon J., Design considerations in replicated database systems for disaster protection, COMPCON 1988, Feb. 29, 1988, pp. 428-430.Applicant
- Microsoft Corporation, “Microsoft Exchange Server: Best Practices for Exchange Database Management,” 1998.Applicant
- PCT International Search Report and Written Opinion for International Application No. PCT/US07/81681, Mail Date Nov. 13, 2009, 8 pages.Applicant
- The Oracle8 Replication Manual, Part No. A58245-01; Chapters 1-2; Dec. 1, 1997; obtained from website: http://download-west.oracle.com/docs/cd/A64702—01/doc/server.805/a58245/toc.htm on May 20, 2009.Applicant
- Veritas Software Corporation, “Veritas Volume Manager 3.2, Administrator's Guide,” Aug., 2001, 360 pages.Applicant
- Wiesmann M, Database replication techniques: a three parameter classification, Oct. 16, 2000, pp. 206-215.Applicant
- Canadian Office Action dated Dec. 29, 2010, Application No. 2,546,304.Applicant
- Canadian Office Action, Application No. CA2544063, dated Oct. 12, 2010.Applicant
- Final Office Action for Japanese Application No. 2003531581, Mail Date Mar. 24, 2009, 6 pages.Applicant
- First Office Action for Japanese Application No. 2003531581, Mail Date Jul. 8, 2008, 8 pages.Applicant
- Gray (#2 of 2, pp. 604-609), Jim; Reuter Andreas, Transaction Processing Concepts and Techniques, Morgan Kaufmann Publisher, USA 1994, pp. 604-609.Applicant
- International Search Report and Written Opinion, PCT/US2009/066880, dated Mar. 25, 2010.Applicant
- International Search Report, PCT/US2004/038324, dated Dec. 28, 2009.Applicant
- International Search Report, PCT/US2004/038455 dated Jan. 11, 2006.Applicant
- Jander, “Launching Storage-Area Net,” Data Communications, US, McGraw Hill, NY, vol. 27, No. 4(Mar. 21, 1998), pp. 64-72.Applicant
- Non-Final Office Action for U.S. Appl. No. 10/681,386, Mail Date Oct. 28, 2008, 16 pages.Applicant
- Non-Final Office Action for U.S. Appl. No. 10/990,353, Mail Date Sep. 15, 2008, 8 pages.Applicant
- Non-Final Office Action for U.S. Appl. No. 11/672,926, Mail Date Nov. 25, 2008, 21 pages.Applicant
- Notice of Allowance for U.S. Appl. No. 10/681,386, Mail Date Apr. 21, 2009, 10 pages.Applicant
- Notice of Allowance for U.S. Appl. No. 10/990,353, Mail Date Apr. 7, 2009, 11 pages.Applicant
- International Search Report and Written Opinion dated Jan. 11, 2006 , PCT/US2004/038455.Applicant
- International Search Report and Written Opinion dated Nov. 13, 2009, PCT/US2007/081681.Applicant
- Second Examination Report in EU Appl. No. 06 848 901.2-2201 dated Dec. 3, 2010.Applicant