US 7,809,914 B2Grant
Methods and system of pooling storage devices
Issue Date:2010-10-05
•16 Claims
•9 Drawing Sheets
Abstract
A system and method are provided for pooling storage devices in a virtual library for performing a storage operation. A storage management device determines a storage characteristic of a plurality of storage devices with respect to performing a storage operation. Based on a storage characteristic relating to performing the storage operation, the storage management device associates at least two storage devices in a virtual library. The storage management device may continuously monitor the virtual library and detect a change in storage characteristics of the storage devices. When changes in storage characteristics are detected, the storage management device may change associations of the storage device in the virtual library.
Metadata
Assignee
- CommVault Systems, Inc.
Inventors
- Rajiv Kottomtharayil
- Ho-Chi Chen
Application Information
Application Number:US 11/269,514
Filing Date:2005-11-07
Priority Date:2004-11-05
Art Unit:2185
Classifications
IPC:
G06F12/00G06F13/00G06F13/28
Patent Drawings (9 sheets)
Description
Priority Applications
[0001] This application claims the benefit of U.S. provisional application No. 60/626,076 titled SYSTEM AND METHOD FOR PERFORMING STORAGE OPERATIONS IN A COMPUTER NETWORK, filed Nov. 8, 2004, and U.S. provisional application No. 60/625,746 titled STORAGE MANAGEMENT SYSTEM filed Nov. 5, 2004, each of which is incorporated herein by reference in its entirety.
Copyright Notice
[0002] A portion of the disclosure of this patent document contains material which 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 reserves all copyright rights whatsoever.
Other Related Applications
[0003] This application is related to the following pending applications, each of which is hereby incorporated herein by reference in its entirety:
-
- [0004] Application Ser. No. 09/610,738, titled Modular Backup And Retrieval System Used In Conjunction With A Storage Area Network, filed Jul. 6, 2000;
- [0005] Application Ser. No. 10/658,095, titled Dynamic Storage Device Pooling In A Computer System, filed Sep. 9, 2003;
- [0006] Application Ser. No. 10/819,102, titled Method And System For Controlling A Robotic Arm In A Storage Device, filed Apr. 5, 2004;
- [0007] Application Ser. No. 10/818,749, titled System And Method For Dynamically Performing Storage Operations In A Computer Network, filed Apr. 5, 2004;
- [0008] Application Ser. No. 10/877,831, titled Hierarchical System And Method For Performing Storage Operations In A Computer Network, filed Jun. 25, 2004;
- [0009] Application Ser. No. 60/567,178, titled Hierarchical System And Method For Performing Storage Operations In A Computer Network, filed Apr. 30, 2004;
- [0010] Application Ser. No. 11/120,619 titled Hierarchical Systems And Methods For Providing A Unified View Of Storage Information, filed May 2, 2005;
- [0011] Application Ser. No. 11/269,520, titled System And Method For Performing Multistream Storage Operations, filed Nov. 7, 2005;
- [0012] Application Ser. No. 11/269,512, titled System And Method To Support Single Instance Storage Operations, filed Nov. 7, 2005;
- [0013] Application Ser. No. 11/269,521, titled Method And System For Selectively Deleting Stored Data, filed Nov. 7, 2005;
- [0014] Application Ser. No. 11/269,519, titled Method And System For Grouping Storage System Components, filed Nov. 7, 2005;
- [0015] Application Ser. No. 11/269,515, titled Systems And Methods For Recovering Electronic Information From A Storage Medium, filed Nov. 7, 2005; and
- [0016] Application Ser. No. 11/269,513, titled Method And System For Monitoring A Storage Network, filed Nov. 7, 2005.
Background of the Invention
[0017] The invention disclosed herein relates generally to data storage systems in computer networks and, more particularly, to improvements to storage management systems that allocate use of storage devices for performing storage operations.
[0018] There are many different computing architectures for storing electronic data. Individual computers typically store electronic data in volatile storage devices such as Random Access Memory (RAM) and one or more nonvolatile storage devices such as hard drives, tape drives, or optical disks, that form a part of or are directly connectable to the individual computer. In a network of computers such as a Local Area Network (LAN) or a Wide Area Network (WAN), storage of electronic data is typically accomplished via servers or storage devices accessible via the network. A storage device may be, for example, any device capable of storing and retrieving electronic data in a computer network, for example, a storage device in a computing device, such as a general-purpose computing device, a server, a legacy server, production server, a storage device used to perform a local storage operation, a storage library, tape drives, optical libraries, Redundant Arrays of Inexpensive Disks (RAID), CD-ROM jukeboxes, or other storage devices. Such storage devices may be used to perform a storage operation using removable media, such as tapes, disks, or other media. Removable media is widely utilized in performing storage operations in storage devices. In general, only one media item may be placed in a storage device storage drive for use in a storage operation. If a storage device has only one storage drive, any storage operations performed in the storage drive may cause the storage device to be unavailable for other uses. In addition, if the storage device has only one storage drive, and more than one media item may be required to perform a storage operation, a second media item may be used to replace a first media item in the storage drive. In this scenario, without a robotic arm or a person to manually swap tapes between drives, the storage operation could not be performed once the first media item has been utilized. This may cause inefficiencies in running common storage operations.
Brief Summary of the Invention
[0019] The present invention disclosed herein provides a method and system for creating a virtual library that may be used to perform storage operations.
[0020] In one embodiment of the invention, a method is provided for creating a virtual library of at least two storage devices by selecting a first storage device and a second storage device and associating the first and second storage devices in a virtual library. The storage devices may be storage devices such as a tape drive, optical drive or a hard drive. The first and second storage devices may be selected in accordance with a storage characteristic, such as storage device availability, network pathway between system components, media capacity, user preference, storage policy, or other characteristic as further described herein. The first and second storage devices satisfying the storage characteristic may be detected by a media management component, which may also determine the characteristic of the storage device and logically associate the first and second storage device in the virtual library. The media management component may include an index which can be used to store data indicating a logical association of the virtual library. The virtual library may be maintained by detecting a third storage device that satisfies the storage characteristic and substituting the third storage device for the first (or second) storage device by disassociating the first (or second) storage device with the virtual library and associating the third storage device with the virtual library.
[0021] In another embodiment, a method is provided for performing a storage operation using a virtual library of at least two storage devices by receiving a request to perform a storage operation, associating a first and second storage device in a virtual library and performing the storage operation to the virtual library. In one embodiment, the first and second storage device are determined to have a storage characteristic appropriate for the storage operation.
[0022] In another embodiment, a method for updating a virtual library of at least two storage devices may be provided by receiving a first value of a storage characteristic of a first storage device in the virtual library and detecting a change in the storage characteristic of the first storage device. A third storage device may be detected that has a storage characteristic similar to the first value and the third storage device may be substituted with the first storage device in the virtual library by disassociating the first storage device with the virtual library and associating the third storage device with the virtual library. Data indicating the association of a storage device with the virtual library may be stored in an index.
[0023] In another embodiment, a method for managing a plurality of storage devices is provided by receiving a request to perform a storage operation and a storage characteristic (related to performing the storage operation) of a storage device. A media management component may detect at least two storage devices, among a plurality of storage devices, that include the storage characteristic. The at least two storage devices are associated with a virtual library for performing storage operations. Data indicating the association of the storage devices with the virtual library may be stored in an index.
[0024] In another embodiment, a method for pooling at least two storage devices is provided in which at least two storage devices may be identified that have a common storage characteristic. The common storage characteristic may be related to performing a storage operation. The at least two storage devices may be associated with a virtual library. Data indicating the association of the storage devices with the virtual library may be stored in an index.
[0025] In another embodiment, a method for storing data using a virtual library is provided in which a request to perform a data storage operation is received and a virtual library is selected which has at least two associated storage devices that are capable of performing the data storage operation. The data storage operation is performed using the virtual library.
[0026] In another embodiment, a virtual library for performing a storage operation is provided which includes at least two storage devices. The at least two storage devices have a storage characteristic for performing a storage operation. A media management component is communicatively coupled to the at least two storage devices, and also communicatively coupled to a storage manager and an index. The media management component is programmed to coordinate performing the storage operation in the virtual library. The index includes data that indicates an association of the at least two devices with the virtual library.
[0027] In another embodiment, a method for maintaining an index for a virtual library is provided in which identifiers for two or more storage devices capable of performing a data storage operation and satisfying at least one common storage characteristic are stored in the index. Association data establishing a logical relationship of the two or more storage devices in the virtual library may also be stored in the index. The association data may be modified in response to a change in the common storage characteristic of a given one of the storage devices by disassociating the given one storage device from the virtual library and associating a third storage device satisfying the common storage characteristic with the virtual library.
[0028] In another embodiment, a system for performing a storage operation using at least two storage devices is provided in which one or more storage devices in a first computing device and one or more storage devices in a second computing device are associated with a virtual library. Each of the first and second computing devices comprises a processor which may be used to process a storage operation. The system also includes an index for storing data indicating an association of the first and second computing devices with a virtual library.
[0029] In another embodiment, a method for performing a storage operation in a computer network is provided in which a storage manager or other system component may identify a request to perform a storage operation, for example, based on a storage policy. The storage manager (or other system component, such as a virtual library controller) may select, in response to a selection criteria associated with performing the storage operation, a first computing device having a central processing unit and one or more removable media storage devices. The selection criteria may be related to one or more storage characteristics relating to performing the storage operation. The storage manager (or other system component, such as a virtual library controller) may select, in response to the selection criteria associated with performing the storage operation, a second computing device having a central processing unit and one or more removable media storage devices. One or more index entries may be created which associate the one or more storage devices of the first computing device and the one or more storage devices of the second computing device with a single logical network pathway to a network storage device in the computer network. The storage operation may be performed using the single logical network pathway.
Brief Description of the Drawings
[0030] 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:
[0031] FIG. 1 is a block diagram showing a high-level view of the network architecture and components of one possible embodiment of the invention;
[0032] FIG. 1A is a block diagram showing an aspect of the network architecture and components of one possible embodiment of the invention;
[0033] FIG. 2 is a table depicting virtual libraries in one embodiment of the invention;
[0034] FIG. 3 is a user interface depicting available virtual libraries in one embodiment of the invention;
[0035] FIG. 4 is a flow diagram presenting a method of creating a virtual library in one embodiment of the invention;
[0036] FIG. 5 is a flow diagram of a method for performing a storage operation in one embodiment of the invention;
[0037] FIG. 6 is a flow diagram presenting a method for monitoring a virtual library in one embodiment of the present invention; and
[0038] FIG. 7 is a flow diagram presenting a method for performing a storage operation in another embodiment of the invention.
Detailed Description of the Preferred Embodiments
[0039] The present invention relates to creating a virtual library of storage devices for performing a storage operation. A virtual library may be a logical collection of one or more storage devices. The storage devices in a virtual library may be similar or heterogeneous, and may be logically grouped together to appear, for example, from the perspective of a user or system component, to be a single device. For example, two storage devices, such as a server or other first computing device having a tape drive and a stand-alone tape library connected to or otherwise controlled by a second computing device may be configured in a virtual library and logically associated in an index.
[0040] Another virtual library may include two separate storage devices having robotic arms, and data indicating the logical association of the two storage devices may be stored in an index. The index may indicate that the storage devices in a virtual library (e.g.—the tape drive in the first storage device and the one or more drives of the tape library of the second computing device) are represented by and accessed via a single common logical network pathway, for example g:/virtual library 1. Thus, from the perspective of other components in a storage management system, virtual library components have one logical network pathway and appear to be a single device. Such other storage management system components may perform storage operations using the virtual library via the single logical network pathway.
[0041] The configuration of and devices used in a virtual library may vary. For example, a virtual library may include one or more storage devices in one computing device, such as a hard drive, and one or more storage devices in another computing device, such as a server. By combining more than one storage device in a virtual library, drives in each of the storage devices may be used to perform storage operations, for example, by tape spanning across more than one tape drive, streaming data to more than one drive, etc.
[0042] Embodiments of the invention are now described with reference to the drawings. An embodiment of the system of the present invention is shown in FIG. 1 . As shown, a system 35 may include client 20, a data store 30, a data agent 40, storage manager component 50, storage manager component index 52, a jobs agent 55, media management components 60 and 70, media management component indexes 62 and 72, and virtual library controllers 75 and 85. Each component may be communicatively coupled to storage devices 120, 130, 140, 150 and 160 via media management components 60 and 70. Although FIG. 1 depicts a system having two media management components 60 and 70, the invention may include one or a plurality of media management components providing communication between system components and storage devices.
[0043] Client 20 may include at least one attached data store 30. Data store 30 may be any memory device or local data storage device known in the art, such as a hard drive, CD-ROM drive, tape drive, RAM, or other types of magnetic, optical, digital and/or analog local storage. Client 20 includes at least one data agent 40, which may be a software module that is generally responsible for performing storage operations for data of client 20, e.g., on data stored in data store 30 or other memory location. Storage operations include, but are not limited to, creation, storage, retrieval, migration, deletion, and tracking of electronic data including primary or production volume data, as well as secondary volume data, primary copies, secondary copies, auxiliary copies, snapshot copies, backup copies, incremental copies, differential copies, synthetic copies, HSM copies, archive copies, Information Lifecycle Management (“ILM”) copies, and other types of copies and versions of electronic data. System 35 includes at least one, and typically a plurality of data agents 40 for each client. Each data agent 40 is intended to perform a storage operation relating to data associated with a different application. For example, client 20 may have different individual data agents 40 designed to handle MICROSOFT EXCHANGE data, LOTUS NOTES data, MICROSOFT WINDOWS file system data, MICROSOFT ACTIVE DIRECTORY OBJECTS data, and other types of data known in the art.
[0044] The storage manager 50 is generally a software module or application that coordinates and controls system components, for example, the storage manager 50 manages and controls storage operations performed by the system 35. The storage manager 50 may communicate with all components of the system 35 including client 20, data agent 40, media management components 60 and 70, and storage devices 120, 130, 140, 150 and 160 to initiate and manage system storage operations. The storage manager 50 may have an index 52, further described herein, for storing data related to storage operations.
[0045] The media management components 60 and 70 are generally a software module that conducts data, as directed by the storage manager 50, between the client 20 and storage devices 120, 130, 140, 150 and 160. These storage devices 120, 130, 140, 150 and 160 can be storage devices such as a tape library, a hard drive, a magnetic media storage device, an optical media storage device, or other storage device. The media management components 60 and 70 are communicatively coupled with and control the storage devices 120, 130, 140, 150 and 160. For example, the media management components 60 and 70 might instruct a storage device 120, 130, 140, 150 and 160 to perform a storage operation. The media management components 60 and 70 generally communicate with the storage device 120, 130, 140, 150 and 160 directly via a local bus such as a SCSI adaptor, or via a network pathway such as a LAN, WAN, etc.
[0046] Each media management component 60, 70 maintains an index cache 62, 72 which stores index data that the system 35 generates during storage operations as further described herein. For example, storage operations for MICROSOFT EXCHANGE data generate index data. Media management component index data includes, for example, logical network pathways of virtual libraries, information associating one or more devices of a virtual library, information regarding the location of the stored data on a particular media, the location of the particular media, such as in a storage device in a current or previous configuration of a virtual library, information regarding the content of the data stored such as, file names, sizes, creation dates, formats, application types, and other file-related criteria, information regarding one or more clients associated with the data stored, information regarding one or more storage policies, storage criteria, or storage preferences associated with the data stored, compression information, retention-related information, encryption-related information, stream-related information, and other types of information. Thus, a media management component index 62, 72 (or storage manager index 52) may be consulted in connection with performing a storage operation on a particular data item to identify the media to which the data is written, the storage device in which the media is located, a current or previous configuration of a virtual library that includes the storage device, or other information relating to performing the storage operation. Index data thus provides the system 35 with an efficient mechanism for performing storage operations including locating user files for recovery operations and for managing and tracking stored data. In some embodiments, a storage manager index 52 may contain the same information stored in a media management component index 62, 72, or the media management component index 62, 72 information may instead be stored in a storage manager index 52.
[0047] The system 35 generally maintains two copies of the media management component index data regarding particular stored data. A first copy is generally stored with the data copied to a storage device 120, 130, 140, 150, or 160. Thus, a tape may contain the stored data as well as index information related to the stored data. In the event of a system restore, the index data stored with the stored data can be used to rebuild a media management component index 62, 72 or other index useful in performing storage operations. In addition, the media management component 60, 70 that controls the storage operation also generally writes an additional copy of the index data to its index cache 62, 72. The data in the media management component index cache 62, 72 is generally stored on faster media, such as magnetic media, and is thus readily available to the system 35 for use in storage operations and other activities without having to be retrieved from a storage device 120, 130, 140, 150, or 160.
[0048] The storage manager 50 also maintains an index cache 52, database, or other data structure. Storage manager index data may be used to indicate, track, and associate logical relationships and associations between components of the system 35, such as virtual libraries and virtual library components, user preferences, management tasks, and other useful data. Some of this information may be stored in a media management component index 62 or other local data store according to some embodiments. For example, the storage manager 50 might use its index cache 52 to track storage devices 120, 130, 140, 150, or 160, logical associations between media management components 60, 70 and the storage devices 120, 130, 140, 150, or 160, and logical associations of virtual libraries 100, 110. In another example, index data may be used to track client data including client archive files, storage policies and sub-client with one or more pointers to an associated virtual library. Some of the index data relating to the logical association of the virtual libraries 100, 110 may be information relating to the virtual library and the individual storage devices associated with the virtual library, such as the logical network pathways or addresses of the storage devices, current, previous and future virtual library configurations, storage characteristics of storage devices in a virtual library, storage operations performed in a previous or current configuration of a virtual library, or other information. The storage manager 50 may also use its index cache 52 to track the status of storage operations performed (and to be performed) using a virtual library, storage patterns associated with the system components such as media use, storage growth, network bandwidth, service level agreement (“SLA”) compliance levels, data protection levels, storage policy information, storage criteria associated with user preferences, retention criteria, storage operation preferences, and other storage-related information.
[0049] Index caches 52 and 62, 72 typically reside on its corresponding storage component's hard disk or other fixed storage device. For example, the jobs agent 55 of a storage manager component 50 may retrieve storage manager index 52 data regarding a storage policy and storage operation to be performed or scheduled for a particular client 20. The jobs agent 55, either directly or via another system module, communicates with the data agent 40 at the client 20 regarding the storage operation. Jobs agent 55 may also retrieve from the index cache 52 a storage policy associated with the client 20 and uses information from the storage policy to communicate to the data agent 40 one or more media management components 60, 70 associated with performing storage operations for that particular client 20 as well as other information regarding the storage operation to be performed such as retention criteria, encryption criteria, streaming criteria, etc. The data agent 40 then packages or otherwise manipulates the client data stored in the client data store 52 in accordance with the storage policy information and/or according to a user preference, and communicates this client data to the appropriate media management component(s) 60, 70 for processing. The media management component(s) 60, 70 store the data according to storage preferences associated with the storage policy including storing the generated index data with the stored data, as well as storing a copy of the generated index data in the media management component index cache 62, 72.
[0050] A storage policy is generally a data structure or other information which 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, 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. A storage policy may be stored to a storage manager index, to archive media as metadata for use in restore operations or other storage operations, or to other locations or components of the system.
[0051] In general, system 35 may include many configurations of virtual libraries, e.g., 100 and 110, each of which may be configured, managed and controlled by a media management components 60, 70. Libraries 100 and 110 depict storage devices arranged in virtual libraries. For example, library 100 includes each of the storage devices SD1-SDn depicted in FIG. 1 , namely 120, 130, 140, 150 and 160. Library 110 includes storage devices SD2, SD3 and SDn, or 130, 140 and 160, respectively. Each virtual library may be a logical grouping of physical storage devices in a network. A virtual library can also include system components other than a storage device, e.g., client, a server, a media management component, other storage device, or other system component. A virtual library generally comprises a one or more storage devices that are logically associated, pooled, or otherwise grouped in a library. As explained herein, storage devices included in the virtual library may be any type of storage device, such as a storage device in a computing device, such as a general-purpose computing device, a server, a legacy server, production server, a storage device used to perform a local storage operation, a storage library, tape drives, optical libraries, Redundant Arrays of Inexpensive Disks (RAID), CD-ROM jukeboxes, or other storage device. The storage devices grouped in the virtual library are logically associated in an index. For example, the storage devices in the virtual library may be assigned one logical network pathway, which is stored in the index. Thus, a system component that consults the index for a storage library may obtain a single logical network pathway for a virtual library which may comprise one or more individual storage devices. The virtual library appears from the perspective of the system, a user, or administrator to be a single library, which has, for example, multiple drives. In reality, the virtual library may include several individual storage devices, typically each having a different logical network pathway, and each of which may have only one storage drive. In some embodiments, a virtual library controller 75 directs scheduling, actual (rather than virtual) data path selection, and transfer of electronic information between clients 20 and components of a virtual library 120, 130, 140, 150 and 160. For example, while a virtual library 120, 130, 140, 150 and 160 may logically appear as a single drive or storage device to the system, a virtual library controller 75 may select actual data paths for transfer of electronic information to and from the various individual storage device components of the virtual library 120, 130, 140, 150 and 160.
[0052] In one example of a virtual library, a screen or other user interface may present a list of system components including a logical entry for a virtual library that includes drives A, B and C, each of which drive may be located in a separate storage device, associated together in a library. In addition, each of drives A, B and C can also be presented individually. Configuring the storage devices 120, 130, 140, 150 and 160 in a virtual library provides, among other advantages, the ability to perform storage operations which may exceed the capacity of one storage device by sharing the storage operation across more than one storage device, e.g., data can be streamed across several storage devices 120, 130, 140, 150 and 160.
[0053] Storage manager 50 or media management components 60, 70 may configure, manage and control the virtual libraries 100, 110. Both of the storage manager 50 and media management components 60, 70 may configure, manage and control the virtual libraries 100, 110. Each of the storage manager 50 and media management components 60, 70 may configure the virtual libraries 100, 110 as a single logical entity by associating the drives of the virtual library by providing a single logical network pathway for the virtual library. Each of the associated drives in the virtual library may be accessed via the single logical network pathway. Association of drives or storage devices or other components in a virtual library may be achieved by creating a table, such as in index 52, 62 and 72, which includes a virtual library identifier and information about the storage devices or components associated in the virtual library, such as a single logical network address.
[0054] Referring to FIG. 1A , a virtual library 170, 172 may also be provided in other storage management system architectures, for example, without a storage manager or media management component. As shown, a virtual library controller 75, in communication with a client, may manage client 20 storage operations to a virtual library 170, 172. The virtual library controller 75 may be a software module that may be a component of a client 20, or communicatively coupled to and separate from the client 20. The virtual library controller 75 generally communicates with a virtual library agent 126, 128, 136 and 138 to provide storage operation instructions. For example, the virtual library controller 75 may direct, manage and configure one or more virtual libraries 170, 172 by communicating with a virtual library agent 126, 128, 136, 138 for a storage device 120, 130 or computing device 125, 135. Each storage device 120, 130 or computer device 125, 135 may have its own virtual library agent 126, 128, 136, 138 for logically associating components in the virtual library and performing storage operations in the virtual library. Information relating to the virtual libraries 170, 172, such as identifiers for each of the components of a virtual library, such as SD1 120, CD1 125, and SD2 130 (and respective drives) of virtual library 170 and SD2 130 and CD2 135 of virtual library 172, and a logical network pathway for the virtual library 170, 172 may be stored in VLC index 77.
[0055] One example of a table that may be stored in a database or in an index that includes virtual library information is depicted in FIG. 2 . As shown in table 175, Virtual Library 1180 includes storage devices 120, 130, 140, 150 and 160 and Virtual Library n 190 includes storage devices 130, 140 and 160. Virtual Library 1180 is shown having a logical network pathway at F:/Virtual Lib 1. Thus, a system component communicating with or performing a storage operation to Virtual Library 1180 may use an F drive pathway. Virtual Library n 190 is shown having a logical network pathway at G:/Virtual Lib n, and correspondingly, may be accessed via a G drive pathway. As shown, the individual components included in Virtual Libraries 180, 190 may be located at other drives as listed in areas 182 and 192 of the table 175. Areas 182, 192 include index entries for logical network pathways of components of a virtual library. The logical network pathway information for a virtual library may be obtained by a virtual library controller, storage manager, or other system component and translated into the actual network pathways to each of the storage devices included in the virtual library. For example, Virtual Library 1180 accessed via logical network pathway F:/Virtual Lib 1 may be translated into network pathways e:/ for storage device 120, h:/ for storage device 130, etc. Table 175 can be updated as necessary to provide information about virtual libraries such as current and previous configurations. One skilled in the art may recognize other ways to map index entries for virtual library configurations and logical network pathways, which may also be used.
[0056] Referring again to FIG. 1 , virtual library controller 75 or 85 of the media management components 60, 70 may communicate directly with the storage devices 120, 130, 140, 150 or 160 in a virtual library 100, 110. Virtual library controller 75, 85 may be a software module or component of the media management component 60, 70 that communicates with virtual library agent 128, 138, 148, 158, or 168, for example, providing instructions relating to a storage operation. Virtual library agent 128, 138, 148, 158, or 168 may be a software module or component associated with a storage device 120, 130, 140, 150 or 160, that may be a separate component, or part of the storage device 120, 130, 140, 150 or 160, and that works together with virtual library controller 75, 85 to command and control a virtual library 100, 110 to facilitate storage operations. For example, when a media management component 60, 70 communicates with a virtual library 100, 110, the media management components 60, 70 may communicate its instructions to a virtual library agent 128, 138, 148, 158, or 168 associated with storage devices 120, 130, 140, 150 or 160 of virtual library 100, 110, such as by sending the virtual library agent 128, 138, 148, 158 and 168 streams of data related to a storage operation. The virtual library controllers 75, 85 may also be programmed to regularly, or in accordance with a storage policy or storage preference, monitor virtual libraries 100, 110 and storage devices 120, 130, 140, 150 or 160 to determine storage characteristics of components associated in a virtual library 100, 110. For example, a virtual library controller 75, 85 may detect a change in the availability of a storage device, the capacity of media in a drive, network pathways, or other storage characteristic, further described herein.
[0057] Each storage device in the virtual library 100, 110 may include at least one drive, such as the tape drives (SD1T1 and SD1T2, labeled 122 and 124, respectively) shown in SD1 120. For example, a storage device may be a server with a single drive, or a hard drive, single tape drive, a tape library with or without a robotic arm, or other storage device. Each storage device may be grouped together with similar or heterogeneous components in a virtual library 100, 110. Data indicating an association of the virtual library 100, 110 components and a respective logical network pathway is stored in an index 52, 62, or 72 used to represent logical a storage location to a user or system component. The virtual library 100, 110, thus generally appears from the perspective of a user or system component to be a single storage device such as a library having one or more drives. In reality, the virtual library 100, 110 comprises one or more storage devices grouped in a virtual arrangement. Data relating to the associations of each virtual library 100, 110 may be stored, for example, in the media management component index 62, 72, or in the storage manager index 52.
[0058] Referring to FIG. 3 , there is shown an example of a graphical user interface 200. Storage resources, such as available libraries 210 may be presented to a user, including virtual libraries: library 1, library 2 and library n, labeled 220, 230 and 260, respectively. The virtual libraries may be made available via one or more servers. The available drives of each storage device, such as tape drives shown as SD1T1, SD1T2 and SDnTn, 240, 250 and 270, respectively may also be presented to a user. Storage operations can be performed utilizing any of the available libraries 210, such as 220, 230 or 260. Alternatively, storage operations can be performed directly to an available drive, such as 240, 250 or 270.
[0059] Components of the system 35 may reside and execute on the same computer. A client component such as a data agent 40, a media management component 60, 70, or a storage manager 50 coordinates and directs storage operations as further described in application Ser. No. 09/610,738. This client component can function independently or together with other similar client components.
[0060] A method for creating a virtual library is described in connection with the flow diagram of FIG. 4 . The method could use, for example, the system architecture shown in FIG. 1 , or other storage manager system architecture. A user may initiate the process for creating a virtual library by making a request to a storage manager. Alternatively, a virtual library may be created automatically without a user request. For example, a storage manager may automatically initiate creation of a virtual library in accordance with a storage policy, storage operation template, a storage preference, or other selection criteria, condition, or characteristic. Thus, the storage manager (or media management component or other system component) may receive a storage policy which indicates that a particular storage operation is to be performed at a particular time or frequency interval and that the storage operation will likely require a certain storage characteristic or selection criteria, such as media capacity, network pathway, component availability, network bandwidth or other network performance criteria, number of streams, media type, schedule, or other characteristic. The storage manager may monitor system components and resources to determine a particular configuration of storage devices, e.g., in a virtual library, which satisfy the storage characteristic and may be capable of performing the storage operation.
[0061] Storage devices may be scanned to detect availability, step 300. A storage manager may be programmed to scan (or direct the scanning of) system components for available storage devices periodically, upon a request to perform a storage operation, or prior to a request to perform a storage operation. The availability of storage devices may be obtained by querying a media management component or storage manager or a virtual library controller and virtual library agent. The media management component or storage manager may consult its index data or the virtual library controller and virtual library agent to determine which storage devices are available and which storage devices are not available. Alternatively, a storage manager or media management component may perform a test read or write operation in a storage device drive to determine media capacity, or other indication of availability of a storage device. For example, the system may write or read a small quantity of data to or from one or more storage devices associated with a virtual library. In some instances, a storage device may be unavailable for one or more reasons, such as the storage device is offline, is damaged, no longer contains media, a logical network pathway is inaccessible, a media or tape is full, a storage device may be in use in another storage operation, or other reason. A threshold may be specified having a minimum availability requirement for example, that a storage device must not be in use for another storage operation, that a certain quantity of network bandwidth be available for a storage operation using the virtual library component, etc.
[0062] Characteristics of the available storage devices are identified, step 310, by communicating information regarding the available storage devices between the media management component and storage device, or via system components including a virtual library controller, media management component, or virtual library agent. Characteristics of a storage device may include, for example, media capacity, network pathway, storage capacity, streaming ability, processor capacity or speed of a storage device, ability to run storage operations in parallel, authorization, security requirements or permissions of a storage device, present or scheduled future uses of the storage device, storage policies, schedules or preferences associated with a storage device or client, user preferences or other metrics or storage criteria. A characteristic relating to media capacity may be a required volume of media to perform a storage operation. A characteristic relating to network pathways may include pathways between a media management component, client, storage device or other storage component, and indications of bottlenecks or network congestion, which may affect performance of a storage operation. A storage capacity characteristic of a storage device may relate to a capacity of media or drives a storage device. Streaming ability is a characteristic of a storage device which may refer to the ability of a storage device to perform a storage operation by streaming data using one or more data streams, e.g., across one or more drives to one or more media items. Characteristics relating to processor capacity or speed of a storage device can indicate the relative speed in which a storage operation can be performed by a storage device and also a volume of data that can be handled by a processor or simply a certain processor speed of a computing device associated with a component of a virtual library. Some storage devices have a characteristic which allows it to perform storage operations in parallel, for example, as further described in patent application Ser. No. 10/818,749. Characteristics relating to security, permissions and authorization may limit or open up a storage device to perform certain secure storage operations. Scheduling characteristics of a storage operation, such as present or future uses of a storage device may indicate that a storage device is available at discrete times and unavailable at other times to perform storage operations. A storage policy characteristic of a storage device may be that a particular storage policy for a particular client may be set to perform storage operation at a particular or associated storage device. Other characteristics of a storage device may be various preferences, metrics or storage criteria. Such storage device characteristics may be used to select a storage device or other component for a virtual library based on a criteria to perform storage operation which may require a particular characteristic.
[0063] Indications of the characteristics or availability of a storage device may be presented to a user, step 320. A screen may be automatically generated by a client GUI based on information received from a media management component index. The screen may provide a user with views of available virtual libraries, storage devices, or drives and the characteristics of each. A storage manager and/or a media management component may also generate library profile information, which generally includes information about the library devices, and may include additional information, such as media capacity, logical or real network pathway to the library, or other characteristic. Such a screen may be similar to the graphical user interface depicted in FIG. 3 with indication information added in reference to each of Lib 1, Lib 2, SD1T1, SD1T2, or Lib n, numbered 220, 230, 240, 250, 260, respectively, such as a storage device characteristic, as further described herein.
[0064] Alternatively, a system component, such as a storage manager, may consult the indications of storage characteristics or availability without user input. For example, in place of user input, a storage manager may have a template for creating a virtual library that sets advantageous characteristics of a storage device, e.g. capacity, bandwidth, streaming capability, availability, future scheduled uses, including duration of future scheduled uses and network pathways for scheduled operations, and other characteristics as further described herein. For example, in a template for performing a copy operation, a characteristic may be set for a template that a storage device should have no scheduled uses daily between 2:30 am and 3:30 am and have at least two drives which are capable of performing a read or write operation on media having a particular capacity. Thus, the template may establish a minimum resource threshold required for a storage device to be included in a virtual library and storage devices meeting or exceeding the threshold are indicated as available. Alternatively the template sets forth that all available devices having a particular characteristic may be associated in a virtual library.
[0065] Based on the storage characteristics, storage devices may be selected for association in a virtual library, step 330. A user may select storage devices to associate in a virtual library. Or, alternatively, a storage manager or other virtual library controller, may select storage devices based on a template and storage characteristics. Selected storage devices may be associated with a virtual library, step 340. In general, a decision to select storage devices for association may be based on the indications of availability or characteristics. For example, a storage device may be selected because it has appropriate media capacity, less congested network pathway or other characteristic, e.g., as further described herein. Selection of a storage device to be included in a virtual library may cause an instruction to be communicated to the applicable media management component to associate a storage device with a virtual library. When a storage device is associated with a virtual library, a media management component updates index data relating to the storage device with a logical network pathway for the virtual library. The virtual library controller and virtual library agent may also receive the association instruction from a media management component and store the association data. The virtual library controller and virtual library agent may use the association data to direct and facilitate storage operations in an appropriate virtual library.
[0066] The virtual library is created, step 350, by associating the storage devices in the virtual library. Data relating to the association of the storage device in a virtual library and which indicates a logical network pathway for the virtual library may be stored to a media management component index or other index in a table, such as the table depicted in FIG. 2 . In general, when a virtual library is created, a default storage policy may be applied to or used by the virtual library. Data relating to the default storage policy may be stored to the index.
[0067] A virtual library may be used to perform a storage operation, for example, as described in reference with FIG. 5 . A request is received to perform a storage operation, step 400. In general, the request may be initiated by a user or automatically without user input according to a storage schedule, a storage policy, a user preference, or other initiator or criteria.
[0068] When a request is received by a system to perform a storage operation, components of a specified virtual library may be checked by identifying devices in the virtual library, and identifying media to handle in a storage operation. For example, a system component may verify whether one or more storage devices are available in a virtual library, step 410. In general, a media management component verifies whether a storage device may be available in a virtual library by consulting its index data to identify the storage devices associated in a virtual library. Availability of the storage device includes determining, for example, whether a storage device is online, whether the storage device is functioning or powered on, or other indicator of availability. The storage manager may consult its index to determine which media management component is associated with the storage device, or enabled to manage and control the storage device in performing the storage operation, and communicates via the media management component to determine availability of a storage device. The media management component then checks to determine whether the storage device storage characteristics satisfy a criteria, step 420. Storage characteristics include for example, requirements for performing a particular storage operation, the specifications of the storage device, or other characteristics, as further described herein.
[0069] Determining whether the storage device satisfies a storage criteria can include, for example, determining a storage characteristic of the storage device, such as checking each of the available storage devices to determine whether there is adequate media capacity, such as sufficient disk or tape space, e.g., a tape less than half written to or between half written to and full. If a tape is less than half full and the media required for a storage operation is half of a tape, there is adequate media to perform the storage operation. If the tape is between half full and full and the media required for a storage operation is at least half a tape, there is inadequate media to perform the storage operation. Other characteristics may also be considered in this step, including characteristics further described herein: network pathway between the media management component, client, storage device or other storage component, e.g. whether the network pathway is currently congested, likelihood of congestion in a future scheduled storage operation, bandwidth necessary for a storage operation, processor capacity and speed of the storage device, ability of the storage device to run storage operations in parallel with other storage devices in the network, authorization or security requirements or permissions of the storage device, present or scheduled future uses of the storage device, such as present or future storage operations scheduled which utilize the storage device, storage policies, schedules, or preferences associated with the storage device or client, user preferences, other metric, storage criteria, or characteristic. These characteristics may be used to predict availability of storage components as necessary for a storage operation and to provide a comparison of efficiency of components or resources used in performing storage operations.
[0070] If the available storage devices do not satisfy the storage criteria, the storage operation fails, or the situation may be remedied, step 430. For example, if one or more storage devices do not satisfy the storage criteria because there may be insufficient free or available storage media in the storage devices, the storage manager or media management component will communicate instructions to an administrator or system user, via email, pager, warning message, etc., to change the storage media in the storage devices. Alternatively, the media management component may query the available storage devices to determine whether a partial storage operation can be performed on the available storage devices that do not otherwise satisfy each of the storage criteria. For example, a storage operation can be performed in parts so that a portion of the storage operation is allocated to a first virtual library and another portion to a second or nth virtual library, storage device or other system component. Alternatively, a storage operation may be performed in which one or more tapes in separate drives or separate storage devices, are used in a tape-spanning configuration to perform a storage operation. In another example, a storage manager may predict storage criteria requirements to perform the storage operation and identify other storage device(s) that may perform the storage operation and dynamically allocate and associate such storage devices to the virtual library.
[0071] If the storage manager or media management component determines that there are available storage devices and media which satisfy the storage criteria, the available storage devices may be associated, or pooled with a virtual library, step 440. The association of the storage device with a virtual library may be accomplished by storing data indicating the association of the virtual library in an index, such as data indicating a logical network pathway of a virtual library. Even though the storage devices associated in a virtual library may be physical devices that are separate geographically or mechanically, from a user's and system perspective these devices are associated with a single logical network pathway and thus appear to be a single storage device, such as a storage library and not a collection of individual storage devices.
[0072] Storage devices are associated in a virtual library, such as Library 1, shown in FIG. 1 , which may be used to perform a storage operation, step 450. Configuring the storage devices in a virtual library provides the ability to perform storage operations which may exceed the capacity at one storage device by sharing the storage operation across more than one individual storage device and streaming data across several storage devices. This configuration of the virtual library can be used for load balancing, e.g., performing storage operations using more than on storage device, media spanning, e.g., performing storage operations storing electronic data across more than one piece of media or drive, and other high data volume storage operations.
[0073] A method for creating a virtual library described herein may be initiated at the time a request for a storage operation is received, or alternatively, the method is initiated at other times, such as when a storage manager regularly checks and maintains system resources to determine whether system components are available for storage operations. For example, a storage manager may create one or more virtual libraries in advance of a request for performing a storage operation in accordance with predicting resource requirements for performing storage operations according to storage policies, schedules jobs, storage preferences, etc, and determining available resources to perform the storage operations. The system check can be triggered by user preferences, storage policy, user instructions, or in accordance with storage system readiness verification, further described in provisional application Ser. No. 60/626,076 titled SYSTEM AND METHOD FOR PERFORMING STORAGE OPERATIONS IN A COMPUTER NETWORK, filed Nov. 8, 2004.
[0074] A virtual library may be monitored, maintained and updated according to the method depicted in FIG. 6 . System components may be monitored or maintained in accordance with a storage policy, step 500, to determine system health, capacity of system components, or other aspects of the system. For example, a storage manager, media management component, virtual library controller or other system component may monitor availability of storage devices, virtual libraries and other system components and check storage policies and schedules to determine whether there are adequate system resources to perform future scheduled storage jobs. Monitoring of the system can be active and dynamic, e.g. initiated in accordance with a monitoring schedule set according to storage policies, such as by full time virtual library agents performing heartbeat assessments or constant monitoring of system components, job schedules, storage preference, storage policy, or passively initiated, e.g., by user request. Reports of system resources can be generated based on information obtained in monitoring and delivered to an administrator or user by email, pager or other message.
[0075] In a virtual library monitoring operation, a storage manager, media management component, virtual library controller or other monitoring component verifies storage devices and virtual libraries. For example, a virtual library controller detects whether there have been any changes in a characteristic of a storage device in a virtual library, step 510. A change in a characteristic may be detected by a media management component that communicates with a storage device, for example, via a virtual library agent or virtual library controller. In the event that a characteristic of a storage device changes, data relating to the change in characteristic may be communicated to the virtual library agent associated with the storage device and communicated to the virtual library controller, storage manager, or media management component. Alternatively, a storage device, virtual library controller or other system component can report to the media management component that a storage device is unavailable according to a threshold range of unavailability. Changes in characteristics can include, for example, scheduled storage operations, media capacity, availability, network pathway, or other characteristics. Some changes in characteristics are immaterial with respect to system resource requirements, e.g., a storage device may be scheduled for maintenance and taken offline for 30 minutes during a time period in which no storage operations are scheduled, a media change has occurred which increases the capacity of the media, or other change in characteristic which either improves the general characteristics of the storage device, or which may not adversely impact future storage operations. Such changes may be considered to be above a minimum threshold requirement for a storage characteristic for performing a storage operation. Some changes, however, may be material to system resource requirements necessary for a particular storage operation, such as failure of a storage device, scheduling conflicts, such as a future storage operation schedule that entirely utilizes all of the storage device media capacity or that is scheduled for the same time, or other characteristic that worsens the general characteristics of the storage device, or which will significantly impact a future storage operation. Such material changes may not satisfy or meet a minimum storage characteristic or criteria requirement threshold. A characteristic threshold between a material and immaterial difference may be set forth such that storage devices having characteristics exceeding the threshold are considered to be available and appropriate for performing a particular storage operation. In general, a difference between a material and immaterial characteristic may be relative and may be related to general requirements for storage operations, or set forth in threshold ranges for storage characteristic requirements.
[0076] A change in a characteristic may be determined to satisfy the threshold characteristic, step 520. If the changed characteristic is determined to fall above a threshold the system monitor or check routine exits, step 530. In the event that there may be a change in a storage device characteristic that is not significant, there is generally no need to update the virtual library, thus the update check is completed and the existing virtual library configuration is maintained. If a changed characteristic is determined to because the characteristic to fail to meet the threshold, other storage devices are scanned to determine whether another storage device may be available to be substituted into a virtual library for an unavailable storage device, step 540. If the changed characteristic is significant, the virtual library generally must be updated by changing a virtual library configuration.
[0077] Availability of an alternate storage device is detected, step 540, by consulting a storage manager index, media management component index or other index, or by communicating with a virtual library or storage devices. A storage manager or media management component determines whether an alternate storage device is available based on satisfying a criteria requirement, step 550. If the storage device is not available, the update fails, step 560 or supplies an error message, such as an email, page or other warning message to a user or system administrator. If a storage device is determined to be available, the storage manager or the media management component updates the configuration and association of devices with the virtual library to include the available alternate storage device, step 570, and data relating to the update is stored to the media management index, storage manager index or other index.
[0078] Index data stored in the storage manager index or media management component index maintains information, including point-in-time information about current, future and previous virtual library configurations, media, and component associations. Since virtual library configurations can change, in the event that a storage operation such as a data restore operation is performed after a change in a virtual library configuration, the storage device in which the data to be restored is located may need be to be identified. Referring to FIG. 7 which depicts a flowchart for determining a virtual library association, a storage operation request, such as a data restore request is received, step 600. Such request may be initiated by a user's input, according to storage policies, or other initiator. Information about the data relating to the storage operation, such as information about data to be restored, is also received, such as a data type, data identifier or other information. A storage manager index, media management component index or other index may be consulted to determine a virtual library associated with the data requested in the storage operation request, step 610. In general, index data relating to a virtual library configuration is stored for current virtual library configurations and previous virtual library configurations to track data locations and other information relating to virtual libraries. An indication of the virtual library including the data with the storage operation request may be presented to a user, step 620. The indication may be presented in a graphical user interface, such as the screen depicted in FIG. 2 . The virtual library indication may be presented to the user so that the user may view information relating to the location of data to be restored, such as a previous and present virtual library configuration, however, this step is optional. In general, the system will perform the storage request, step 630, without input from the user with respect to the location of the data in a virtual library.
[0079] 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.
[0080] 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
What is claimed is:
1. A method for performing a storage operation using at least two physical storage devices, the method comprising:
receiving a request to perform a first storage operation to store first data, the first storage operation having at least a first storage characteristic associated therewith;
identifying a first virtual library with dynamically allocated physical storage devices that are allocated based on characteristics associated with different storage operations, wherein the first virtual library comprises a first configuration with at least first and second physical storage devices, wherein a single logical network pathway is associated with the first configuration of the first virtual library such that the first and second physical storage devices appear as a single device;
performing the first storage operation using the first virtual library;
storing the first configuration of the first virtual library;
receiving a request to perform a second storage operation to store second data, the second storage operation having at least a second storage characteristic associated therewith that is different than the first storage characteristic, wherein the second storage operation requires more storage than exists in the first configuration of the first virtual library;
automatically determining that the second storage operation requires more storage than exists in the first and second physical storage devices associated with the first configuration of the first virtual library;
automatically detecting with one or more computer processors, at least a third physical storage device associated with a second virtual library, wherein the third physical storage is adequate to satisfy both the second storage characteristic associated with the second storage operation for the first virtual library and one or more future scheduled storage operations associated with the second virtual library, and wherein detection of the third storage device is based at least in part on the likelihood of congestion in one or more of the future scheduled storage operations;
automatically allocating with one or more computer processors the third physical storage device with both the first virtual library and the second virtual library without the need of user intervention, wherein the first virtual library comprises a second configuration with at least the first physical storage device, the second physical storage device and the third physical storage device, and wherein the single logical network pathway is associated with the second configuration of the first virtual library such that the first, second and third physical storage devices of the second configuration appear to be the single device, and wherein the second configuration of the first virtual library and the first configuration of the first virtual library share the single logical network pathway;
performing the second storage operation using the second configuration comprising third storage device in association with the first virtual library;
performing one or more of the future scheduled storage operations using the third storage device in association with second virtual library while the third storage device remains in association with the first virtual library;
storing the second configuration of the first virtual library;
receiving a first request for data via the single logical network pathway at the first virtual library wherein the first request is for data associated with the first configuration of the first virtual library;
receiving a second request for data via the single logical network pathway at the first virtual library wherein the second request is for data associated with the second configuration of the first virtual library; and
automatically determining the location of the data associated with the first and second requests by accessing the stored first and second configurations of the first virtual library.
2. The method of claim 1, wherein creating the first configuration of the first virtual library further comprises storing data indicating an association of the first and second physical storage device with the first virtual library in an index.
3. The method of claim 1, further comprising:
detecting a fourth physical storage device among a plurality of physical storage devices, the fourth physical storage device satisfying a storage characteristic associated with a third storage operation;
disassociating the first physical storage device with the first virtual library;
associating the fourth physical storage device with the first virtual library wherein the first virtual library comprises a third configuration with at least the second physical storage device, the third physical storage device and the fourth physical storage device;
performing the fourth storage operation; and
storing the third configuration of the first virtual library.
4. The method of claim 3, wherein the third physical storage device comprises a different type of storage media than the first physical storage device.
5. The method of claim 1, further comprising:
receiving a first value of a characteristic of the first physical storage device, the first physical storage device being associated in the first virtual library;
detecting a change in the characteristic of the first physical storage device, wherein the change in the characteristic of the first physical storage device causes the first physical storage device to not satisfy a storage characteristic threshold;
identifying that the third physical storage device has a storage characteristic satisfying the storage characteristic threshold;
disassociating the first physical storage device from the first virtual library; and
associating the third physical storage device in the first virtual library.
6. The method of claim 5 wherein detecting a change in the characteristic of the first physical storage device comprises examining the first physical storage device prior to receiving the request to perform the storage operation.
7. The method of claim 5 wherein
disassociating the first physical storage device from the first virtual library comprises updating an index with data indicating a disassociation of the first physical storage device with the first virtual library; and
wherein associating the third physical storage device in the first virtual library comprises updating the index with data indicating an association of the third physical storage device with the first virtual library.
8. The method of claim 1, wherein the storage characteristic comprises a security requirement.
9. The method of claim 1, wherein the storage characteristic comprises a frequency interval for performing the requested storage operation.
10. The method of claim 1, wherein the storage characteristic comprises a media type for performing the requested storage operation.
11. A method for storing data using a virtual library, the method comprising:
receiving a request to perform a first data storage operation;
identifying a first virtual library comprising at least two physical storage devices that satisfy a storage characteristic associated with the first data storage operation and that are capable of storing data associated with the first data storage operation and wherein the first virtual library comprises a first configuration with the at least two physical storage devices;
performing the first storage operation using the first configuration of the first virtual library;
storing the first configuration of the first virtual library;
receiving a request to perform a second storage operation;
automatically determining that the second storage operation requires more storage than exists in the first and second physical storage devices associated with the first configuration of the first virtual library;
automatically detecting, among a plurality of physical storage devices, at least a third physical storage device associated with a second virtual library, wherein the third physical storage is adequate to satisfy both the second storage operation for the first virtual library and one or more future scheduled storage operations associated with the second virtual library, and wherein detection of the third storage device is based at least in part on the likelihood of congestion in one or more of the future scheduled storage operations;
automatically associating the third physical storage device with both the first virtual library and the second virtual library wherein the first virtual library includes at least three physical storage devices capable of performing the second data storage operation and wherein the first virtual library comprises a second configuration;
performing the second data storage operation using the second configuration of the first virtual library; and
storing the second configuration of the first virtual library.
12. The method of claim 11 further comprising:
detecting that a given one of the at least two physical storage devices becomes incapable of performing the data storage operation;
disassociating the given one of the at least two physical storage devices with the first virtual library; and
associating another physical storage device capable of performing the storage operation with the first virtual library.
13. The method of claim 12 wherein disassociating the given one of the at least two physical storage devices with the first virtual library comprises storing data in an index indicating a disassociation of the given one of the at least two physical storage devices with the first virtual library and storing data in an index indicating a previous configuration of the first virtual library.
14. The method of claim 12 wherein associating a third physical storage device capable of performing the storage operation with the first virtual library comprises storing data in an index indicating an association of the third physical storage device with the first virtual library and storing data in an index indicating a current configuration of the first virtual library.
15. The method of claim 12 further comprising consulting the index to identify the current configuration of the first virtual library for performing the storage operation.
16. A computer readable storage medium including computer executable code for a method for performing a storage operation using at least two physical storage devices, the method comprising:
receiving with one or more processors a request to perform a first storage operation;
determining a storage characteristic related to performing the storage operation;
identifying a first virtual library comprising a first configuration with at least a first physical storage device and a second physical storage device;
automatically determining that the first and second physical storage devices associated with the first configuration of the first virtual library do not have adequate storage capacity to perform the storage operation;
automatically modifying the first virtual library to include at least a third physical storage device associated with a second virtual library, wherein the third physical storage device is adequate to satisfy both the data storage operation for the first virtual library and one or more future scheduled storage operations associated with the second virtual library, and wherein selection of the third storage device is based at least in part on the likelihood of congestion in one or more of the future scheduled storage operations, and wherein modifying the first virtual library comprises associating a second configuration with the first virtual library that comprises at least the first, second and third physical storage devices; and
performing the storage operation using the second configuration of the first virtual library.
Patent Citations (226)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| 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 |
| 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 |
| 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 |
| US5388243(A) | 1995-02-01 | Glider et al. | Applicant |
| US5410700(A) | 1995-04-01 | Fecteau et al. | Applicant |
| US5448724(A) | 1995-09-01 | Hayashi et al. | Applicant |
| US5465359(A) | 1995-11-01 | Allen 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 |
| US5559957(A) | 1996-09-01 | Balk | Applicant |
| US5619644(A) | 1997-04-01 | Crockett et al. | Applicant |
| US5638509(A) | 1997-06-01 | Dunphy et al. | Applicant |
| US5673381(A) | 1997-09-01 | Huai et al. | Applicant |
| US5699361(A) | 1997-12-01 | Ding et al. | Applicant |
| US5729743(A) | 1998-03-01 | Squibb | Applicant |
| US5737747(A) | 1998-04-01 | Vishlitsky 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 |
| US5764972(A) | 1998-06-01 | Crouse et al. | Applicant |
| US5778395(A) | 1998-07-01 | Whiting et al. | Applicant |
| US5812398(A) | 1998-09-01 | Nielsen | Applicant |
| US5813008(A) | 1998-09-01 | Benson et al. | Applicant |
| US5813009(A) | 1998-09-01 | Johnson et al. | Applicant |
| US5813017(A) | 1998-09-01 | Morris | Applicant |
| US5829023(A) | 1998-10-01 | Bishop | Examiner |
| US5829046(A) | 1998-10-01 | Tzelnic et al. | Applicant |
| US5875478(A) | 1999-02-01 | Blumenau | Applicant |
| US5875481(A) | 1999-02-01 | Ashton et al. | Applicant |
| US5887134(A) | 1999-03-01 | Ebrahim | Applicant |
| US5890159(A) | 1999-03-01 | Sealby et al. | Applicant |
| US5901327(A) | 1999-05-01 | Ofek | Applicant |
| US5924102(A) | 1999-07-01 | Perks | Applicant |
| US5950205(A) | 1999-09-01 | Aviani, Jr. | Applicant |
| US5958005(A) | 1999-09-01 | Thorne et al. | Applicant |
| US5974563(A) | 1999-10-01 | Beeler, Jr. | Applicant |
| US6021415(A) | 2000-02-01 | Cannon et al. | Applicant |
| US6026414(A) | 2000-02-01 | Anglin | Applicant |
| US6035306(A) | 2000-03-01 | Lowenthal et al. | Examiner |
| US6052735(A) | 2000-04-01 | Ulrich et al. | Applicant |
| US6076148(A) | 2000-06-01 | Kedem et al. | Applicant |
| US6094416(A) | 2000-07-01 | Ying | Applicant |
| US6131095(A) | 2000-10-01 | Low et al. | Applicant |
| US6131190(A) | 2000-10-01 | Sidwell | Applicant |
| US6137864(A) | 2000-10-01 | Yaker | 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 |
| US6167402(A) | 2000-12-01 | Yeager | Applicant |
| US6212512(B1) | 2001-04-01 | Barney et al. | Applicant |
| US6260069(B1) | 2001-07-01 | Anglin | Applicant |
| US6269431(B1) | 2001-07-01 | Dunham | Applicant |
| US6275953(B1) | 2001-08-01 | Vahalia et al. | Applicant |
| US6295541(B1) | 2001-09-01 | Bodnar | Applicant |
| US6301592(B1) | 2001-10-01 | Aoyama et al. | Applicant |
| US6304880(B1) | 2001-10-01 | Kishi | 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 |
| US6330572(B1) | 2001-12-01 | Sitka | 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 |
| US6374266(B1) | 2002-04-01 | Shnelvar | Applicant |
| US6374336(B1) | 2002-04-01 | Peters et al. | Applicant |
| US6385673(B1) | 2002-05-01 | DeMoney | Applicant |
| US6389432(B1) | 2002-05-01 | Pothapragada et al. | Applicant |
| US6418478(B1) | 2002-07-01 | Ignatius et al. | Applicant |
| US6421711(B1) | 2002-07-01 | Blumenau et al. | Applicant |
| US6438586(B1) | 2002-08-01 | Hass et al. | Applicant |
| US6487561(B1) | 2002-11-01 | Ofek et al. | Applicant |
| US6487644(B1) | 2002-11-01 | Huebsch et al. | Applicant |
| US6505307(B1) | 2003-01-01 | Stell et al. | Applicant |
| US6519679(B2) | 2003-02-01 | Devireddy et al. | Applicant |
| US6538669(B1) | 2003-03-01 | Lagueux, Jr. 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 |
| US6571310(B1) | 2003-05-01 | Ottesen | Applicant |
| US6581143(B2) | 2003-06-01 | Gagne et al. | Applicant |
| US6631442(B1) | 2003-10-01 | Blumenau | Applicant |
| US6631493(B2) | 2003-10-01 | Ottesen et al. | Applicant |
| US6658436(B2) | 2003-12-01 | Oshinsy et al. | Applicant |
| US6658526(B2) | 2003-12-01 | Nguyen et al. | Applicant |
| US6757794(B2) | 2004-06-01 | Cabrera et al. | Applicant |
| US6789161(B1) | 2004-09-01 | Blendermann et al. | Applicant |
| US6791910(B1) | 2004-09-01 | James et al. | Examiner |
| US6859758(B1) | 2005-02-01 | Prabhakaran et al. | Applicant |
| US6886020(B1) | 2005-04-01 | Zahavi et al. | Applicant |
| US6952758(B2) | 2005-10-01 | Chron et al. | Applicant |
| US6965968(B1) | 2005-11-01 | Touboul et al. | Applicant |
| US6973553(B1) | 2005-12-01 | Archibald, Jr. et al. | Applicant |
| US7003641(B2) | 2006-02-01 | Prahlad et al. | Applicant |
| US7035880(B1) | 2006-04-01 | Crescenti et al. | Applicant |
| US7062761(B2) | 2006-06-01 | Slavin et al. | Applicant |
| US7069380(B2) | 2006-06-01 | Ogawa 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 |
| US7117246(B2) | 2006-10-01 | Christenson et al. | Applicant |
| US7120757(B2) | 2006-10-01 | Tsuge | Applicant |
| US7130970(B2) | 2006-10-01 | Devassy et al. | Applicant |
| US7155465(B2) | 2006-12-01 | Lee et al. | Applicant |
| US7155633(B2) | 2006-12-01 | Tuma et al. | Applicant |
| US7159110(B2) | 2007-01-01 | Douceur et al. | Applicant |
| US7174433(B2) | 2007-02-01 | Kottomtharayil et al. | Applicant |
| US7246140(B2) | 2007-07-01 | Therrien et al. | Applicant |
| US7246207(B2) | 2007-07-01 | Kottomtharayil et al. | Applicant |
| US7246272(B2) | 2007-07-01 | Cabezas et al. | Applicant |
| US7269612(B2) | 2007-09-01 | Devarakonda et al. | Applicant |
| US7278142(B2) | 2007-10-01 | Bandhole et al. | Applicant |
| US7287047(B2) | 2007-10-01 | Kavuri | Applicant |
| US7287252(B2) | 2007-10-01 | Bussiere et al. | Applicant |
| US7293133(B1) | 2007-11-01 | Colgrove et al. | Applicant |
| US7380072(B2) | 2008-05-01 | Kottomtharayil et al. | Applicant |
| US7467167(B2) | 2008-12-01 | Patterson | Applicant |
| US7472238(B1) | 2008-12-01 | Gokhale | Applicant |
| US7490207(B2) | 2009-02-01 | Amarendran | Applicant |
| US7500053(B1) | 2009-03-01 | Kavuri et al. | Applicant |
| US7536291(B1) | 2009-05-01 | Retnamma et al. | Applicant |
| US2001/0034812(A1) | 2001-10-01 | Ignatius et al. | Applicant |
| US2002/0004883(A1) | 2002-01-01 | Nguyen et al. | Applicant |
| US2002/0029281(A1) | 2002-03-01 | Zeidner et al. | Applicant |
| US2002/0040405(A1) | 2002-04-01 | Gold | Applicant |
| US2002/0049778(A1) | 2002-04-01 | Bell et al. | Applicant |
| US2002/0049803(A1) | 2002-04-01 | Bandhole et al. | Applicant |
| US2002/0069369(A1) | 2002-06-01 | Tremain | Applicant |
| US2002/0087822(A1) | 2002-07-01 | Butterworth | Applicant |
| US2002/0107877(A1) | 2002-08-01 | Whiting et al. | Applicant |
| US2002/0194340(A1) | 2002-12-01 | Ebstyne et al. | Applicant |
| US2003/0014433(A1) | 2003-01-01 | Teloh et al. | Applicant |
| US2003/0014607(A1) | 2003-01-01 | Slavin et al. | Applicant |
| US2003/0016609(A1) | 2003-01-01 | Rushton et al. | Examiner |
| US2003/0033308(A1) | 2003-02-01 | Patel et al. | Applicant |
| US2003/0051097(A1) | 2003-03-01 | Ottesen et al. | Applicant |
| US2003/0061491(A1) | 2003-03-01 | Jaskiewicz et al. | Applicant |
| US2003/0126361(A1) | 2003-07-01 | Slater et al. | Examiner |
| US2003/0163652(A1) | 2003-08-01 | Tsuge | Applicant |
| US2003/0169733(A1) | 2003-09-01 | Gurkowski et al. | Applicant |
| US2003/0188114(A1) | 2003-10-01 | Lubbers et al. | Examiner |
| US2003/0196036(A1) | 2003-10-01 | Gibble et al. | Applicant |
| US2003/0204700(A1) | 2003-10-01 | Biessener et al. | Examiner |
| US2003/0225801(A1) | 2003-12-01 | Devarakonda et al. | Applicant |
| US2004/0010487(A1) | 2004-01-01 | Prahlad et al. | Applicant |
| US2004/0073716(A1) | 2004-04-01 | Boom et al. | Applicant |
| US2004/0090788(A1) | 2004-04-01 | Kottomtharayil | Applicant |
| US2004/0088432(A1) | 2004-05-01 | Hubbard et al. | Applicant |
| US2004/0107199(A1) | 2004-06-01 | Dairymple et al. | Applicant |
| US2004/0167941(A1) | 2004-08-01 | Prahlad et al. | Applicant |
| US2004/0193953(A1) | 2004-09-01 | Callahan et al. | Applicant |
| US2004/0230829(A1) | 2004-11-01 | Dogan et al. | Applicant |
| US2005/0033755(A1) | 2005-02-01 | Gokhale et al. | Applicant |
| US2005/0033756(A1) | 2005-02-01 | Kottomtharayil et al. | Applicant |
| US2005/0033800(A1) | 2005-02-01 | Kavuri et al. | Applicant |
| US2005/0044114(A1) | 2005-02-01 | Kottomtharayil et al. | Applicant |
| US2005/0086443(A1) | 2005-04-01 | Mizuno et al. | Applicant |
| US2005/0114406(A1) | 2005-05-01 | Borthakur et al. | Applicant |
| US2005/0114477(A1) | 2005-05-01 | Willging et al. | Applicant |
| US2005/0131900(A1) | 2005-06-01 | Palliyll et al. | Applicant |
| US2005/0144520(A1) | 2005-06-01 | Tuma et al. | Applicant |
| US2005/0166011(A1) | 2005-07-01 | Burnett et al. | Examiner |
| US2005/0172093(A1) | 2005-08-01 | Jain | Examiner |
| US2005/0246568(A1) | 2005-11-01 | Davies | Applicant |
| US2005/0256972(A1) | 2005-11-01 | Cochran et al. | Applicant |
| US2005/0262296(A1) | 2005-11-01 | Peake | Examiner |
| US2006/0005048(A1) | 2006-01-01 | Osaki et al. | Applicant |
| US2006/0010227(A1) | 2006-01-01 | Atluri | Applicant |
| US2006/0044674(A1) | 2006-03-01 | Martin et al. | Applicant |
| US2006/0053305(A1) | 2006-03-01 | Wahlert | Applicant |
| US2006/0224846(A1) | 2006-10-01 | Amarendran et al. | Applicant |
| US2006/0224852(A1) | 2006-10-01 | Kottomtharayil et al. | Applicant |
| US2006/0230244(A1) | 2006-10-01 | Amarendran et al. | Applicant |
| US2006/0242489(A1) | 2006-10-01 | Brockway et al. | Applicant |
| US2007/0130430(A1) | 2007-06-01 | Devassy et al. | Applicant |
| US2007/0186042(A1) | 2007-08-01 | Kottomtharayil et al. | Applicant |
| US2008/0016126(A1) | 2008-01-01 | Kottomtharayil et al. | Applicant |
| US2008/0229037(A1) | 2008-09-01 | Bunte et al. | Applicant |
| US2008/0243879(A1) | 2008-10-01 | Gokhale 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 |
| EP259912 | 1988-03-01 | Applicant | |
| EP259912 | 1988-03-01 | Applicant | |
| EP405926 | 1991-01-01 | Applicant | |
| EP405926 | 1991-01-01 | Applicant | |
| EP467546 | 1992-01-01 | Applicant | |
| EP467546 | 1992-01-01 | Applicant | |
| EP774715 | 1997-05-01 | Applicant | |
| EP809184 | 1997-11-01 | Applicant | |
| EP809184 | 1997-11-01 | Applicant | |
| EP899662 | 1999-03-01 | Applicant | |
| EP899662 | 1999-03-01 | Applicant | |
| EP981090 | 2000-02-01 | Applicant | |
| EP981090 | 2000-02-01 | Applicant | |
| EP1174795 | 2002-01-01 | Applicant | |
| EP1115064(A3) | 2004-12-01 | Applicant | |
| GB2366048 | 2002-02-01 | Applicant | |
| WO95/13580 | 1995-05-01 | Applicant | |
| WO-95/13580 | 1995-05-01 | Applicant | |
| WO-99/12098 | 1999-03-01 | Applicant | |
| WO99/12098 | 1999-03-01 | Applicant | |
| WO99/14692 | 1999-03-01 | Applicant | |
| WO99/17204 | 1999-04-01 | Applicant | |
| WO2005/055093 | 2005-06-01 | Applicant |
Non-Patent Literature (40)
- U.S. Appl. No. 11/269,519, Kavuri et al.Applicant
- U.S. Appl. No. 11/269,136, Retnamma et al.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
- 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
- International Search Report; dated Mar. 1, 2007; 1 page.Applicant
- U.S. Appl. No. 11/269,521, filed Nov. 7, 2005, Prahlad et al.Applicant
- U.S. Appl. No. 11/269,250, filed Nov. 7, 2005, Gokhale et al.Applicant
- U.S. Appl. No. 11/269,515, filed Nov. 7, 2005, Gokhale et al.Applicant
- U.S. Appl. No. 11/269,513, filed Nov. 7, 2005, Prahlad et al.Applicant
- Armstead et al., “Implementation of a Campus-wide Distributed Mass Storage Service: The Dream vs. Reality,” IEEE, 1995, pp. 190-197 and 199.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-15 and 18-22 (1988) (see in particular figure 5 in p. 15 and recitation in claim 5).Applicant
- U.S. Appl. No. 11/269,521, filed Nov. 7, 2005, Prahlad et al.Applicant
- U.S. Appl. No. 12/145,342, filed Jun. 24, 2008, Gokhale.Applicant
- U.S. Appl. No. 12/145,347, filed Jun. 24, 2008, Gokhale.Applicant
- U.S. Appl. No. 12/167,933, filed Jul. 3, 2008, Gokhale.Applicant
- Armstead et al., “Implementation of a Campus-wide Distributed Mass Storage Service: The Dream vs. Reality,” IEEE, 1995, pp. 190-199.Applicant
- Arneson, “Mass Storage Archiving in Network Environments,” IEEE, 1998, pp. 45-50.Applicant
- Cabrera et al., “ADSM: A Multi-Platform, Scalable, Backup and Archive Mass Storage System,” Digest of Papers of the Computer Society Conference, IEEE Comp. Soc. Press, vol. Conf. (Mar. 5, 1995), pp. 420-427.Applicant
- Eitel, “Backup and Storage Management in Distributed Heterogeneous Environments,” IEEE, 1994, pp. 124-126.Applicant
- Farley, “Building Storage Networks,” pp. 328-331, Osborne/McGraw-Hill, 2000.Applicant
- Gibson et al., “Network Attached Storage Architecture,” pp. 37-45, ACM, Nov. 2000.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 (1998).Applicant
- Written Opinion; International Application No. PCT/US05/40606; mailed Feb. 14, 2007; 5 pages.Applicant
- U.S. Appl. No. 11/269,119, filed Nov. 7, 2005, Amarendran et al.Applicant
- U.S. Appl. No. 11/950,376, filed Dec. 4, 2007, Bunte et al.Applicant
- U.S. Appl. No. 11/963,623, filed Dec. 21, 2007, Gokhale et al.Applicant
- U.S. Appl. No. 12/058,178, filed Mar. 28, 2008, Prahlad et al.Applicant
- U.S. Appl. No. 12/058,317, filed Mar. 28, 2008, Prahlad et al.Applicant
- U.S. Appl. No. 12/058,367, filed Mar. 28, 2008, Prahlad et al.Applicant
- Commvault Systems, Inc., Continuous Data Replicator 7.0, Product Data Sheet, 2007.Applicant
- Farley, “Building Storage Networks,” pp. 328-331, Osborne/McGraw-Hill, 2000.Applicant
- Gibson et al., “Network Attached Storage Architecture,” pp. 37-45, ACM, Nov. 2000.Applicant
- Recycle Bin (Windows), Aug. 2007, Wikipedia, pp. 1-3.Applicant
- Written Opinion; International Application No. PCT/US05/40606; mailed Feb. 14, 2007; 5 pages.Applicant
- Ashton, et al., “Two Decades of policy-based storage management for the IBM mainframe computer”, www.research.ibm.com <http://www.research.ibm.com/>, 19 pages, published Apr. 10, 2003, printed 3 Jan. 2009—cited in U.S. Appl. No. 12/276,868., www.research.ibm.com, Apr. 10, 2003, pp. 19.Applicant