Abstract:
A virtual electronic data library system has a plurality of storage elements. Each storage element is adapted to store a medium of a plurality of media. Preferably, a plurality of subsets of the media each have one format of a plurality of formats. A plurality of input/output elements are preferably adapted to receive and read the media stored in the storage elements. Each of the input/output elements is capable of operatively receiving media having at least one of the formats. A library controller has firmware wherein the subsets of the media are each assigned a logical unit number for use by the controller to partition the library. At least one transport is operable to remove the media from the storage elements and operatively deploy the media for use by one of the input/output elements. The transport deploys the media in an input/output element according to the logical unit numbers.

Description:
TECHNICAL FIELD  
         [0001]    The present invention relates to electronic data storage and more specifically to a virtual electronic data library that supports mixed drive types using virtual libraries within a single library.  
         BACKGROUND  
         [0002]    Existing data libraries typically employ a single drive type and one specific media format associated with the drive type. Generally, a data library is made up of a set of storage elements or slots housing tapes, disks or other media of a single type and format; one or more data input/output (I/O) elements of a single type and format, such as tape, disk or magneto-optical drives; and at least one transport for removing the media from the slots and inserting the media into the I/O elements. The transport generally takes the form of a robotic device that physically removes a medium from a slot, transports the medium to a drive element, and physically installs the medium in the drive. In larger libraries there may be more than one transport. Existing libraries generally have more than one tape drive, but all the drives and tapes are of the same type and format.  
           [0003]    Generally, a controller card in the library system, such as may use a small computer systems interface (SCSI) standard, directs operations employing the different elements in the library. SCSI is an industry standard general-purpose parallel interface designed for providing high speed connections between one or more computers and one or more peripherals. Depending on the SCSI standard, a total of four, eight, or sixteen devices may be connected to one bus. A great advantage of SCSI is the ability to chain together multiple devices on a single physical I/O interface with each device having a unique address. SCSI is an interface system that is focused on a host adapter. The host adapter provides a shared bus that attached peripherals use to pass data to and from the host system. Theoretically, any SCSI device may be attached to any SCSI controller. The original SCSI standards supported four to eight devices on a single host adapter, but newer standards support high-speed operation of up to sixteen devices and bus lengths of up to twenty-five meters. Many SCSI devices have their own control circuitry. Such devices may carry out assigned tasks without direct control, freeing up the bus for other functions.  
           [0004]    An existing method of extending the SCSI architecture employs a logical unit number (LUN) architecture. LlNs are assigned to SCSI devices deployed under the control of a primary SCSI device. Previously this has facilitated control of multiple devices, greater than the aforementioned limits, that are not connected directly to the SCSI bus. Thus, multiple devices under one SCSI device may be accessed through LUNs. However, since the SCSI bus has been widened from 8 to 16 devices, there has not been much need for such an extension. With overall performance targets in mind, the number of devices on the same SCSI bus has necessarily been minimized. Existing data libraries do not make use of LUNs.  
           [0005]    Advances in drive and media technology have encouraged migration to different drive types for library uses. Since existing libraries employ only one drive type, such a migration in a existing data library system requires purchase of an entire new data library, or format conversion of the existing library. A media and/or drive upgrade may be desirable or necessary to accommodate higher density media, higher transfer rates, different media suppliers or be necessary due to a purchase of data, assets or an entire enterprise. Unfortunately, older media oftentimes will not function in newer drives. Additionally, to partition an existing library or to break a library into virtual libraries, special software has typically been required.  
         SUMMARY OF THE INVENTION  
         [0006]    A virtual electronic data library system has a plurality of storage elements. Each of the storage elements is adapted to store a medium of a plurality of media. Preferably, a plurality of subsets of the media each have one format of a plurality of formats. A plurality of input/output elements are preferably adapted to receive and read the media stored in the storage elements. Each of the input/output elements is preferably capable of operatively receiving media having at least one of the formats. At least one transport is preferably adapted to remove the media from the storage elements and provide the media to the input/output elements. A library controller preferably has firmware wherein the subsets of the media are each assigned a logical unit number for use by the controller to partition the library. Preferably, at least one transport is operable to remove the media from the storage elements and operatively deploy the media for use by one of the input/output elements. The transport deploys the media to input/output elements according to the aforementioned logical unit numbers.  
           [0007]    Another embodiment of an electronic data library system has a plurality of storage elements. Each of the storage elements is adapted to store a medium of a plurality of media having a plurality of formats, each of the formats having a logical unit number. At least one transport is operable to remove the media from the storage elements and operatively deploy the media for use by one of at least one input/output elements. At least one transport deploys the media in at least one input/output elements according to the logical unit number. A library controller directs at least one transport to deploy the media in at least one input/output elements according to the logical unit number.  
       
    
    
     BRIEF DESCRIPTION OF THE DRAWING  
       [0008]    [0008]FIG. 1 shows a diagrammatic representation of deployment of a typical existing electronic data library capable of employing the present inventive system;  
         [0009]    [0009]FIG. 2 shows a diagrammatic representation of an electronic data library having two media and drive types employing the present inventive system; and  
         [0010]    [0010]FIG. 3 is a flow chart illustrating operation of a data library in accordance with the present inventive method. 
     
    
     DETAILED DESCRIPTION  
       [0011]    The present invention is directed to a system and method to support mixed drive types using virtual libraries within a single data library. Proliferation of drive types, with many associated advantages and improvements, creates a need for making drive types work together to provide a unitary library. Hence, it is desirable to allow a user to upgrade to newer archiving or I/O equipment without converting a library of existing data or archives to a new format and media. Additionally, it is desirable to provide a single library that will support more than one type of drive and/or media format and/or type, such as to provide backwards compatibility. Finally, it is desirable to offer a partitioning mechanism within the library itself to facilitate partitioning, particularly to facilitate the use of mixed drive types.  
         [0012]    An embodiment of the present inventive system and method allows host software applications to access one or more different drive types and/or formats in the same electronic data library using a logical addressing system such as small computer systems interface (SCSI) logical unit numbers (LUNs). The present invention preferably facilitates the use of standard backup software to control a library without the need for special software and promotes use by independent software vendors of a new media format for library purposes. As used hereinafter, “format” and “type”, shall interchangeably refer to either a media and drive type or the particular physical and data format used by the media and drive.  
         [0013]    Turning to FIG. 1, operation of an existing electronic library  10  is diagrammatically illustrated. A request from user application  11  is carried out by SCSI based library controller  12 . Such a request may result in transport  13  being directed to remove a medium  16 , such as a particular tape cartridge, from one of storage element slots  14  and insert it into one of I/O elements  15 , that is a tape drive or the like. A medium  16  may be inserted into or removed from existing library  10  via import/export element slots  17 . As discussed above, both of the drives in existing library  10  correspond to medium  16 &#39;s type and format and all media in the storage element slots  14  are of this same type and format.  
         [0014]    By way of example, as diagrammatically illustrated in FIG. 2, library  20  employing a system and method in accordance with the present invention may have more than one type of drive  21  and  22 . By way of example, library  20  may have originally only had type A drive(s)  21 ; type B drive(s)  22  may have later been added to library  20 . The media and drives for the two types of drives may not be compatible or the drives may only be backward compatible. For example, type A media  26  may work in type B drive  22 , providing backward compatibility. However, newer media, for example type B media  27 , typically will not function in older drives, such as type A drive  21 . Preferably, transport mechanism  23  in library  20  should not move type A media  26  to type B medium drive(s)  22  unless such backward compatibility exists. Regardless, type B media  27  should not typically be moved to type A drive(s)  21 .  
         [0015]    To provide transparency to library accessing software, library system  20  preferably uses a logical addressing system, such as logical unit numbering to address different portions of library  20 . Logical unit numbering is an addressing scheme of the SCSI specifications. By way of example, SCSI device ID number  1  could be assigned to entire library  20  and LUN  1 - 0  could be used for indication of what resources are available overall in library  20 , but not necessarily the format or media type of the resources. In the example illustrated in FIG. 2, type A drives  21  may be associated with LUN  1 - 1  and type B drives  22  may be associated with LUN  1 - 2 . So if the host software needs to utilize a type A element to perform an operation on the library, it would query the library through the element status command, using LUN  1 - 1 , what resources it has available. For example, what slots  24  have been assigned to type A media  26  and what I/O elements  21  may receive type A media  26 . Similarly, a host could command insertion of a type B medium  27  housed in slot  25  into type B drive  22 , via LUN  1 - 2 .  
         [0016]    Preferably, no hardware modifications to slots  24  and  25 , media  26  and  27 , transport  23  or drives  21  and  22  are required by the present invention. Additionally, it should be appreciated that a library configured according to the present inventive system and method may include multiple media types and formats. To provide the aforementioned transparency the present invention is preferably, at least in part, embodied in the firmware of SCSI library controller  28 . The controller firmware defines an ability to address multiple medium types or drive types making up library  20 , as a single library, for example as LUN  0 . The firmware also allows individual addressing of the media and drive types as LUNs  1 ,  2 , etc. Preferably a host computer employs SCSI commands to interact with SCSI library controller  28  having modified firmware. The library is the target for the host. Controller  28  directs the robotics of transport  23 .  
         [0017]    In an alternative embodiment, application software running on a host computer would address the library by addressing a specific LUN. This is a relatively straightforward modification compared to re-architecturing software to handle multiple drive types directly. Existing software uses SCSI addresses. A SCSI address is made up of host bus, adapter, port number and SCSI ID and LUN number. Most existing software uses the SCSI ID as a device identifier and does not typically support LUNs.  
         [0018]    Alternatively, to provide the aforementioned transparency, a post application program interface (API) may be used to directly interact with device drivers. Most library software applications use device drivers to interface with drives and device drivers for the library itself. An API employed by an embodiment of the present invention may interpret directions from the application software accessing the library. In other words, the device drivers may be changed to re-map device addressing. For instance, SCSI-ID  1  in an application program could be re-mapped to LUN  1 - 1  by the API, and SCSI-ID  2  could be re-mapped to LUN  1 - 2 . Thereby, the host application software does not necessarily need to be changed, only new remapped drivers installed to support the present invention.  
         [0019]    As pointed out above, the preferred embodiment controller card in the library system communicates using a SCSI interface and directs operations employing different elements in the library. Commands are directed to a SCSI address, for example, SCSI LUN  1 - 0  if the command is to be applied to all the resources in the library. As a further example, if the host application asked for the element status of the library at LUN  1 - 0 , and the library has twenty slots and two drives, it would report how many and which of the twenty slots were available. Likewise, it would report the availability of the transport and the drives. If accessing LUN  1 - 1 , the system would only report and do operations employing elements that are associated with LUN  1 - 1 . For example, if there were 20 slots total in the library but only the first 10 were associated with LUN  1 - 1 , a LUN  1 - 1  element status would report the status of the first 10 slots, which slots were full and which were available. The status of the import/export elements associated with LUN  1 - 1  would be reported. The LUN  1 - 1  element status would also report the status of the drives associated with LUN  1 - 1  and the status of the library transport or the transport associated with LUN  1 - 1 .  
         [0020]    Turning to FIG. 3, a preferred embodiment of the present invention for partitioning a data library employing SCSI LUNs is flow charted as method  30 . A request from a user calls for an operation on the library at box  31 . At  32  a determination is made whether the request is directed toward the entire library. This determination may be made by the nature of the request, for example a status request or a library content inquiry would typically call for a report on the entire library. If the request is directed toward the entire library, the library controller will use the SCSI ID for the entire library to carry out the request at box  33 , without the use of a specific LUN. If a determination is made at  32  that the request is directed to only a portion or specific elements of the library, the library controller uses the SCSI LUN assigned to the storage elements, media and I/O elements involved to carry out the request at box  34 . If the library employs more than one transport, LUN(s) corresponding to media types and formats to be handled by each transport may be assigned to the transports as well.  
         [0021]    Under the appropriate directions from the controller, the transport removes a medium from the storage elements at box  35 . The medium is inserted into the proper I/O element, or otherwise operatively deployed at box  36 , according to the LUN assigned to the slot/medium and the I/O element. Once the operation to be carried out by the I/O element with the medium is complete and/or the I/O element is needed for another operation, the medium is removed from the I/O element by the transport at box  37 . At box  38 , the medium is returned to a storage element corresponding to the LUN assigned to the media type and format.  
         [0022]    Typically only one transport is used by a library. Therefore, the transport may be shared across the resources of virtual libraries. In order to share a single transport, the present system preferably holds moves requested for another LUN element when moving or transporting a medium or other medium to or from an I/O element. Additionally, the SCSI standard may be used to direct the library controller to view the different LUN requests as coming from different initiators. In other words, instructions to a single transport serving multiple LUNs could be treated by the transport as multiple users making requests to a single library. Thereby, prioritizing actions based on the order received or other applicable criteria, holding actions for the completion of previous or higher priority instructions.  
         [0023]    In existing data libraries, a medium could be moved to the transport and held. However, in the present system, to facilitate sharing, requests to move to the transport would preferably be rejected as an illegal command or the subject media redirected to a holding slot. In this way the transport is always free after a move has been completed. This avoids a host application requesting that a medium be moved to the transport and left there resulting in a second host application, employing a different LUN, not being able to access the transport, because the transport is full. If the first application were allowed to issue a hold command, the second application would not recognize why the transport is full because it did not request that the medium be put in the transport and is unaware of the portion of the library operating under another LUN.  
         [0024]    However, larger libraries may have two or more transports. In that case, transports may be dedicated to a particular drive type and thus LUN. A library with different drive types could use a separate transport for each drive type, with slots allocated to only be associated with that transport and drive type. Thus, a transport, set of storage elements and a drive or drives would be assigned a LUN.  
         [0025]    An alternative component employed by most library systems is one or more import/export or mail slot elements  29   a  and  29   b,  FIG. 2. Mail slots  29   a  and  29   b  are used to introduce new media into library  20 . If a system using the present invention only employs one mail slot for all media types, the mail slot is preferably shared through the present invention. However, multiple mail slots may be employed by a library using the present invention, one slot being for one media format and another slot being for a second media format, etc. Preferably, the mail slots themselves will not physically allow the wrong media type to be inserted. Thereby, when a tape or other media is introduced through a particular mail slot, the system will preferably recognize in which library element slots the introduced media may be stored for use by the library. Alternatively, a single mail slot or import/export slot is used, and the transport mechanism is enabled to recognize the media. Such recognition may be based on several different criteria. For example, bar code labels or other markings may be employed; cartridge memory (CM) chips housed within a tape cartridge may identify the tape type; and/or, dimensions of a tape cartridge may be indicative of its format.  
         [0026]    Some tape formats use the same physical cartridge dimensions and configuration as previous types and/or formats. However, there is generally a physical stop in a drive to prevent loading an older format tape into a newer drive. These tapes appear identical from the exterior. There is no way to differentiate between the cartridges until one attempts to load a cartridge into a drive, and is physically unable to load the cartridge into the drive. However, the present system may be user-configured to set aside or partition the library through a user interface allowing the user to identify tapes as those of a particular type or format and appropriately allocate slots and drives using LUNs.