This disclosure describes various embodiments of methods and systems for identifying failing drives or media in a media library.
Data represents a significant asset for many entities. Consequently, data loss, whether accidental or caused by malicious activity, can be costly in terms of wasted manpower, loss of goodwill from customers, loss of time and potential legal liability. To ensure proper protection of data for business and legal purposes, many entities back up data to a physical storage media such as magnetic tapes or optical disks. Traditionally, backup would occur at each machine controlled by an entity. As the sophistication of network technology increased, many entities turned to enterprise level backup in which data from multiple machines on a network is backed up to a remote library. Typically, a library includes a variety of components which include a plurality of media for data storage, such as, for example, multiple magnetic tapes. Centralized data backup has the advantage of increased volume, efficiency and redundancy.
In many systems, the data to be backed up and backup commands are sent over a network from multiple machines on the network to a library. In many instances, the data to be backed up and the backup commands are routed to the library through a switch.
One example of a library commonly used in enterprise backup systems is a magnetic tape library. A magnetic tape library can comprise components such as tape cartridges (containing magnetic tape), robots, tape slots and tape drives. A typical magnetic tape library contains multiple cartridge slots in which tape cartridges can be stored. Tape cartridges, commonly referred to as tapes, are physically moved between cartridge slots and tape drives by a robot. The robot is controlled by commands received from the host devices on the network. When specific data is required, a host device determines which cartridge slot contains the tape cartridge that holds the desired data. The host device then transmits a move-element command to the robot and the robot moves the tape cartridge to a tape drive which reads the desired data from the tape cartridge.
In a SCSI tape library, devices that are part of the library are typically addressed by target number. Thus, each drive and robot of a tape library typically has a target number. Cartridge slots, on the other hand, are addressed by element numbers that are used by the robot to locate the slots. Because the robot also places tape cartridges in the drives, each drive is also associated with an element number.
Components of a library are subject to wear and other forms of degradation. The degradation of library components can deleteriously affect the reliability of the library. It can be difficult to identify the source of particular errors, however. Previous solutions to reducing errors include replacing drives and media without in-depth of analysis of why errors occurred. Consequently, time and money are spent replacing tapes and drives that are good. Likewise, drives and media that are actually failing may be retained, leading to continuing errors.
Embodiments described herein provide systems and methods for identifying failing drives and tapes. According to one embodiment, tapes that experienced error rates of interest can be identified. A set of drive impact data can be recorded that indicates whether each tape in the identified set of tapes would still have experienced an error rate of interest had that tape not been loaded in various drives. This information can used to determine whether for each tape/drive combination, the tape or drive or both are suspected of causing the errors.
According to one embodiment, tapes having an error rate of interest can be identified by comparing the error rates for the tapes to a threshold. One embodiment can determine, based on the threshold, whether each tape in the identified set of tapes would still have experienced an error rate of interest had that tape not been loaded in various drives. The results can be recorded in drive impact data and used to identify whether tapes and/or drives are failing.
A more complete understanding of embodiments of methods and systems and the advantages thereof may be acquired by referring to the following description, taken in conjunction with the accompanying drawings in which like reference numbers indicate like features and wherein:
Embodiments of systems and methods for library monitoring and identifying sources of errors are illustrated in the FIGURES, like numerals being used to refer to like and corresponding parts of the various drawings.
As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, product, article, or apparatus that comprises a list of elements is not necessarily limited only those elements but may include other elements not expressly listed or inherent to such process, product, article, or apparatus. Further, unless expressly stated to the contrary, “or” refers to an inclusive or and not to an exclusive or. For example, a condition A or B is satisfied by any one of the following: A is true (or present) and B is false (or not present), A is false (or not present) and B is true (or present), and both A and B are true (or present).
Additionally, any examples or illustrations given herein are not to be regarded in any way as restrictions on, limits to, or express definitions of, any term or terms with which they are utilized. Instead these examples or illustrations are to be regarded as being described with respect to one particular embodiment and as illustrative only. Those of ordinary skill in the art will appreciate that any term or terms with which these examples or illustrations are utilized will encompass other embodiments which may or may not be given therewith or elsewhere in the specification and all such embodiments are intended to be included within the scope of that term or terms. Language designating such nonlimiting examples and illustrations includes, but is not limited to: “for example,” “for instance,” “e.g.,” “in one embodiment.”
Media library monitoring systems can collect data associated with a media library and components of the media library. Data may be collected over time and stored in the repository such that the repository contains data associated with individual library components such as, for example, drives, media changers or other library components. Because the repository contains data associated with different library components and because the data in the repository extends over time, the data in the repository may be organized such that the data is organized with respect to time and with respect to the individual library components or according to other parameters. Additionally, the data can be analyzed to identify failing drives and/or tapes.
A user interface may be used to display the collected and organized data to a user and the user may select data to view utilizing the user interface. Thus, collecting data in a repository over time and organizing the data allows a library and individual library components to be monitored and problems with the library or library components to be identified and rectified, for example, by allowing unreliable or unacceptably degraded components to be identified and bypassed or replaced, thereby enhancing the reliability of the library and proactively preventing data loss. According to one embodiment, reports can be presented to a user that allow the user to quickly identify failing drives and/or tapes.
To collect data associated with a library or library components, a monitoring appliance can query a library or library components over a network utilizing commands. In response to received commands, the library or library components may return data associated with a particular command to the monitoring appliance. In one embodiment, a monitoring appliance can query a library over a network utilizing SCSI commands such as the Read Element Status command, Log Sense Command, Inquiry Command and other commands.
A Read Element Status (RES) command is a command which is used to query the state of a library. A RES command is sent to a media changer and in response, the media changer returns data associated with the library or the media changer. Such data may include the locations of individual tape cartridges. Thus a RES command provides a snapshot of a library at any one time. Examples of a RES command can be found in “SCSI Media Changer Commands-2 (SMC-2)”, (INCITS T10 Project 1383D), Revision 7, Nov. 18, 2003, propagated by the T10 Technical Committee of the InterNational Committee on Information Technology Standards (INCITS), which is hereby incorporated by reference.
A Log Sense (LS) command is a command which is used to obtain data associated with a particular drive. A LS command is sent to a particular drive of a library and in response, the drive returns data associated with the drive and/or the media contained in the drive depending on the actual LS command. For example, such data might include: read errors, write errors, utilization and performance data, data regarding the data written and read to a media, media loaded, detail tables or other data. In one embodiment, the amount of data written over a period of time may be derived from data returned in response to one or more LS commands. More specifically, data returned in response to an LS command may include Log Sense page 0xC, 0x32 or 0x39 which may include data from which the amount of data written by a particular drive over a period of time may be derived. In one embodiment, deriving the amount of data written by a particular drive over a period of time may comprise one or more calculations. Examples of a LS command can be found in “SCSI Primary Commands-3 (SPC-3)”, (Project T10/1416-D), Revision 22a, Mar. 25, 2005, propagated by the T10 Technical Committee of the InterNational Committee on Information Technology Standards (INCITS), which is hereby incorporated by reference.
An Inquiry command is a command that is used to query relatively static information (which may include, for example, serial number, manufacturer or other relatively static information) from components of a library such as a drive or a media changer. According to one embodiment, Inquiry commands are used to query individual library components. That is, an individual Inquiry command may query a particular library component. Examples of an Inquiry command can be found in “SCSI Primary Commands-3 (SPC-3)”, (Project T10/1416-D), Revision 22a, Mar. 25, 2005, propagated by the T10 Technical Committee of the InterNational Committee on Information Technology Standards (INCITS), referenced above.
Methods and systems for collecting data from a library or library components can utilize a monitoring appliance which can be a Read Verify Appliance (RVA). The monitoring appliance queries a library or library components over time by sending RES, LS, Inquiry commands and/or other commands to the library or library components at intervals. Data returned in response to the commands is collected in a repository such that the repository may contain data associated with a plurality of library components of a library. For example, the repository may contain data regarding all the drives in a library. Data within the repository may be organized to allow a user to monitor various library components. For example, data may be organized in a chronological order so that a user can monitor the incidence of errors (for example, soft and hard read or write errors) over time. The data may further be organized such that superfluous data is removed. For example, redundant data might not be displayed to a user or might be purged from the repository. Likewise, unnecessary data or data that the system is configured not to monitor might be purged from the repository or not saved to the repository in the first place.
Switch 207 is connected to library 100. Thus switch 207 can forward commands (such as, for example, RES, LS or Inquiry commands) from monitoring appliance 220 to library 100. Switch 207 receives data generated in response to the commands from library 100 and forwards the data to monitoring appliance 220 which collects the data in a repository. Thus monitoring appliance 220 can continually query library 100 and components of library 100 for data which can be stored in a repository, allowing a user to monitor the components of library 100. Because monitoring appliance 220 collects data by sending commands to a library, monitoring appliance 220 does not need to intercept commands or responses from network 205 to obtain data associated with a library or library components. Thus, in one embodiment, monitoring appliance 220 can be an out-of-band appliance. This allows monitoring appliance 220 to be a non-intrusive device which does not monitor or interfere with commands from and responses to hosts 202a-202d. Consequently, monitoring appliance 220 can be a compartmentalized device which can be connected to a switch and which does not have to be integrated into network 205. An advantage of this out-of-band methodology is that a monitoring appliance can be used to monitor library components without cumbersome configuring.
While a particular network topology is shown in
For example,
While shown as a physical media library in
The monitoring appliance, at compile data step 320, can compile the returned data. For example, the monitoring appliance can compile the data in defined structures which, in one embodiment, may include XML structures or other structures or equivalents. A structure may contain data associated with a library component returned in response to one or more commands (such as, for example, RES, LS or Inquiry commands). For example, a XML structure can include data from RES commands and serial numbers of library components determined from Inquiry commands issued to corresponding library components. At store data step 330, the monitoring appliance stores the returned data in a repository. Storing data in a repository may comprise storing structures in the repository or may comprise unpacking returned data compiled at compile step 320 and storing the data in the repository. In one embodiment, the data may be stored in records in a database at the repository.
At organize data step 340, the data in the repository is organized. As part of step 340, data in the repository can be arranged in chronological order and/or superfluous or redundant data can be purged. Corresponding data can be grouped together. For example, data structures corresponding to a particular drive may be arranged in chronological order within the repository.
At process data step 350, data in the repository may be processed to display desired data to a user. For example, a user may only want to see data corresponding to a particular library component. At process data step 350, the data in the repository is processed such that the desired data is selected to be displayed to a user. Similarly, data may be processed into graphs or charts, or in accordance with any number of purposes or user desires.
In one embodiment, processing data in the repository can comprise comparing returned library states or data regarding the locations of individual tape cartridges stored in the repository to track the movement of one or more tape cartridges. For example, data in the repository corresponding to different times can be compared and the movement of tape cartridges in a library tracked by differencing the locations of tape cartridges in a library at different times. In embodiments in which data is stored in records in a database, records associated with different times may be compared to track the movement of tape cartridges. Processing data can further comprise correlating errors with a particular library component based on the movement of one or more tape cartridges within the library.
As described above, tracking the movement of tape cartridges or other media allows sources of errors to be identified. For example, a tape cartridge may encounter errors when used with a tape drive A but may encounter no errors when used with other tape drives. If other tape cartridges encounter errors when used with tape drive A, but encounter no errors when used with other tape drives, this implies that tape drive A is unreliable. Accordingly, tape drive A may be bypassed or replaced. Thus, by tracking the movement of one or more tape cartridges, errors can be correlated to a particular tape or drive. Tracking cartridges in a library and correlating data (such as, for example, errors or other data) with cartridges or drives is described in U.S. patent application Ser. No. 11/801,809, entitled METHOD AND SYSTEM FOR NON-INTRUSIVE MONITORING OF LIBRARY COMPONENTS, which is hereby incorporated by reference.
Returning to
Data Engine 640 of
Collecting data associated with a library or library components in repository 660 and organizing the data allows a user to view the data to monitor library components. In
While in the above example, data engine 640, storage engine 650, repository 660, interface engine 670 or user interface 690 are described as being part of a monitoring device, data engine 640, storage engine 650, repository 660, interface engine 670 or user interface 690 may be contained in a component that is not physically part of the monitoring appliance. For example, data could be collected and compiled at the monitoring device but stored in memory coupled to the monitoring appliance. In one embodiment, interface engine 670 or user interface 690 run on a host computer which is coupled to repository 660 over a network. User 680 can access data in repository 660 utilizing interface engine 670 or user interface 690 which may be running on the host computer. Thus, a user may access the data in repository 660 over a network. Collected and compiled data may be partially stored in the monitoring appliance and partially stored in separate memory. In one example, a portion of collected data may be stored in a memory which is a component of data engine 640 or storage engine 650, while a portion of collected data may be stored in a memory which is a component of repository 660 or interface engine 670. Repository 660 of
It should be noted that the intervals between querying a library or library components can be fixed periods of time or of variable duration or a combination of the two. Individual library components may also be queried at different intervals: for example, a drive that is being heavily used may be queried more frequently than a drive which is not being used. In one embodiment, the data engine queries a library or library component every 30 seconds. In another embodiment, the time duration between querying is less than the backup time or the tape movement time. In further embodiments, the intervals can be determined by computer algorithm or user input.
It should further be noted that data may be derived from collected data and stored in the repository or other data storage. More specifically, collected data returned in response to one or more commands may be used to derive derived data which may be stored in the repository. Deriving derived data may comprise one or more calculations. The derived data may be organized. For example, derived data may be stored in particular records in a database. Examples of derived data may include, for example, the bits read by a drive over time (which may be, for example, in bits/second), the data transfer rate of a drive or other data. Statistical analysis may be performed on data stored in a repository. For example, statistical analysis may be performed on collected data or derived data and may be used to predict device or cartridge failure based on read errors or write errors or other data.
Secondary memory 704 can store a variety of computer instructions that include, for example, an operating system such as a Windows operating system (Windows is a trademark of Redmond, Wash. based Microsoft Corporation) and applications that run on the operating system, along with a variety of data. More particularly, secondary memory 704 can store a software program 730 that collects, compiles, stores, organizes or processes data associated with a library or library components. During execution by processor 702, portions of program 730 can be stored in secondary memory 704 and/or primary memory 703.
Because a repository may contain data associated with a library and library components spanning a period, a user may access the data to monitor the library or library components over a period of time. For example, a user may use a user interface to display data associated with a library component for a desired period of time. The data may be displayed in a graphical format.
Tapes that experienced error rates of interest can be identified from the data in repository 660 (
A set of drive impact data can be determined and recorded that indicates whether a tape would still have experienced an error rate of interest had the tape not been loaded in particular drives. For example, if Drive 4 is removed from consideration for Tape 1, the highest error rate for Tape 1 will drop to 5.204, an error rate that is still of interest. In the case of Tape 3, as another example, removing Drive 1 causes the error rate to drop to 0.012. This indicates that Tape 3 would not have been of interest had it not been loaded in Drive 1. While, in these examples, the highest error rate experienced by a tape is used to determine if the tape experienced an error rate of interest in the absence of a drive, in other embodiments the average error rate experienced by the tape across drives, or other measure of error rate can be used.
The impact of a drive on the error rate of a tape can be recorded. For example, in the case of Tape 1, the impact of not considering Drive 1 can be recorded to indicate that Tape 1 would still have been of interest even if it had not been loaded in Drive 1. Similarly, in the case of Tape 3, the impact of not considering Drive 1 can be recorded to indicate that Tape 3 would not have been of interest had Tape 3 not been loaded in Drive 1.
Other impacts can also be recorded. As an example, it is possible that a tape cartridge may only have been loaded in one drive (e.g., Tape 2 was only loaded in Drive 4). Therefore, removing the drive from the consideration of the error rate of will naturally drop the error rate to 0. It is unclear, in this case, whether Tape 2 should still be considered of interest. The uncertain impact of not considering Drive 4 can be recorded.
In other cases, a tape may still have experienced an error rate of interest when a particular drive is not considered, but the error rate of interest may be lower than when that drive was considered. Additional thresholds can be used to categorize the drop in error rate when not considering a particular drive. For example, if the highest error rate for a tape drops enough to bring it halfway between the threshold from where it had been, the tape may still be of interest, but less so. Using the example of
Any number of different defined impacts can be recorded in the drive impact data. The drive impact data can be stored in memory, in a database or otherwise stored for analysis. In one embodiment, the drive impact data can be presented to a user in a format that allows the user to easily determine if a drive or tape should be considered suspect.
The background of Cell 1450 represents that the error rate for a tape dropped below the threshold when that drive was not considered. That is, the tape would not have been of interest had it not been loaded in that drive. For example, Cell 1450 indicates that Tape 3 would not be of interest had it not been loaded in Drive 1. This can indicate that Drive 1 is suspected of being responsible for the error rate in cell 1450.
The background of Cell 1455 indicates that the impact of the drive on the error rate is inconclusive because the tape was not used in any other drives. For example, Cell 1455 indicates that while an error rate of 1.473 errors per gigabyte occurred with the Tape 4/Drive 1 combination, but Tape 4 was not used in any other drives. It is therefore unclear what impact Drive 1 had on the error rate of Tape 4.
The background of Cell 1460 indicates that the tape would still have been of interest in the absence of a drive, but significantly less so. For example, Cell 1460 indicates that the error rate of Tape 8 is still of interest in the absence of Drive 1, but by less than half of when Drive 1 is considered.
Looking at report 1430, a user can quickly identify that Drives 1 and 2 may be failing and that Drive 3 is likely good. The state of Drive 4 is more uncertain because a number of tapes experienced above the threshold error rates in Drive 4, but most of those tapes would still have been of interest in the absence of Drive 4. Similarly, the user can easily identify potentially failing Tapes. For example, the user can see that Tape 1 experienced errors in a number of drives, including at least one drive that is otherwise considered good. Therefore, the user can easily identify Tape 1 as failing. The user can do a similar review of the other tapes to determine whether to check or remove tapes.
The visual indicators provided above are provided by way of example and not limitation. The visual indictors can include icons, color coding, text and/or visual indicators that correspond to the drive impact data for the tape/drive combination. The visual indicators may also convey other information, including, but not limited to whether all the operations performed on a tape for a particular Tape/Drive combination were READ errors or WRITE errors, or other information. While, in the above example, drive impact data is presented to a user for review, in other embodiments the drive impact data can be analyzed by a program according to a set of criteria to identify failing tapes and or drives.
According to one embodiment, to determine if a drive is suspect of causing the errors for a tape/drive combination, the drive of that combination is removed from determination of the highest error rate for the tape (step 1520). If the highest error rate for the tape drops below the threshold, as determined at step 1525, the drive can be considered as being suspect (step 1530) because the tape would no longer have been of interest. Otherwise the drive can be identified as not having a sufficient impact on the error rate of the tape (step 1535). Steps 1520-1535 can be repeated for each drive in which a tape was loaded and for each tape having experienced a greater than the threshold error rate.
It should be noted that the impact of a drive on the error rate of a tape can be otherwise categorized to identify, for example, whether a drive is suspected as being the cause of errors and the level of certainty. For example, if it is determined that the highest error rate for a tape drops below the threshold in step 1525, but the tape was only loaded in one drive, the impact of the drive on the error rate is inconclusive. As another example, if the highest error rate for a tape is still greater than the threshold, as determined at step 1525, but there is a sufficient drop in the highest error rate of the tape, the drive can be considered suspect with a reduced level of certainty. In some embodiments, the drive can be considered more suspect the greater the drop or greater the percentage drop in the error rate for the tape.
A report can be output that visually identifies the impact of drives on the error rates of tapes (step 1540). The visual indicators can depict the level of certainty that a drive is suspected of causing errors or other information. According to one embodiment, the report can be formatted as a chart with cells for each tape/drive combination being considered. Each cell can include a visual indication of whether the tape would have been of interest if it had not been loaded in that drive. The chart can be formatted in manner that allows a user to easily identify potentially failing tapes and drives.
Management station 1600 can include a set of instructions 1655 that are executable to retrieve data 1660 from a data storage medium 1665, such as a repository of media library data, error data, local storage or other data storage. Instructions 1655 can be executed to analyze data 1660 to determine a set of drive impact data and generate reports to users. In some embodiments, instructions 1655 can also process drive impact data to identify failing media and/or drives. Instructions 1655 can also be implemented on a monitoring appliance or be distributed. Management station 1600 can be any suitable computer system that can execute instructions 1655 as software or firmware or can include an ASIC or other hardware to perform operations.
Embodiments can also be implemented with respect to libraries of media other than magnetic tapes. For example, the library can comprise a plurality of optical disks (i.e., an optical jukebox) or removable hard drives. Other libraries can utilize a combination of different storage media such as hard drives, magnetic media or optical media. Furthermore, the error rates analyzed can include, but are not limited to, hard errors, soft errors, a combination thereof or other error rates.
While systems and methods been described with reference to particular embodiments, it should be understood that the embodiments are illustrative and that the scope of the invention is not limited to these embodiments. For example, while embodiments described above have been described with regard to RES, LS and Inquiry commands, this is by way of illustration and not limitation. In some embodiments, other commands may be used to collect data associated with a library or library components. Many variations, modifications, additions and improvements to the embodiments described above are possible. It is contemplated that these variations, modifications, additions and improvements fall within the scope of the invention as detailed in the following claims.
This application is a continuation of and claims the benefit of priority of U.S. patent application Ser. No. 12/692,403 entitled “System and Method for Identifying Failing Drives or Media in Media Library,” by Moody et al., filed Jan. 22, 2010, which is a continuation-in-part of and claims the benefit of priority of U.S. patent application Ser. No. 12/024,755, entitled “Media Library Monitoring System and Method,” by Sims, filed Feb. 1, 2008, issued as U.S. Pat. No. 7,908,366, on Mar. 15, 2011, which are hereby fully incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
3704363 | Salmassy et al. | Nov 1972 | A |
3984923 | Rawson et al. | Oct 1976 | A |
4754345 | Karlstetter | Jun 1988 | A |
4932826 | Moy et al. | Jun 1990 | A |
4958235 | Sims et al. | Sep 1990 | A |
5253126 | Richmond | Oct 1993 | A |
5309768 | Mathews et al. | May 1994 | A |
5386324 | Fry et al. | Jan 1995 | A |
5668800 | Stevenson | Sep 1997 | A |
5781703 | Desai et al. | Jul 1998 | A |
5822516 | Krech, Jr. | Oct 1998 | A |
5881221 | Hoang et al. | Mar 1999 | A |
5883864 | Saliba | Mar 1999 | A |
6052264 | Curtis | Apr 2000 | A |
6052341 | Bingham et al. | Apr 2000 | A |
6163853 | Findlay et al. | Dec 2000 | A |
6269330 | Cidon et al. | Jul 2001 | B1 |
6304880 | Kishi | Oct 2001 | B1 |
6490253 | Miller et al. | Dec 2002 | B1 |
6624958 | Alva | Sep 2003 | B1 |
6715031 | Camble et al. | Mar 2004 | B2 |
6725394 | Bolt | Apr 2004 | B1 |
6799156 | Rieschl et al. | Sep 2004 | B1 |
6823401 | Feather, Jr. et al. | Nov 2004 | B2 |
6839824 | Camble et al. | Jan 2005 | B2 |
6950871 | Honma et al. | Sep 2005 | B1 |
6971046 | Johnson et al. | Nov 2005 | B1 |
7076391 | Pakzad et al. | Jul 2006 | B1 |
7200546 | Nourmohamadian et al. | Apr 2007 | B1 |
7200722 | Goodman et al. | Apr 2007 | B2 |
7310745 | Schnapp et al. | Dec 2007 | B2 |
7346801 | Brunelle et al. | Mar 2008 | B2 |
7386667 | Estelle et al. | Jun 2008 | B2 |
7443801 | Neidhardt et al. | Oct 2008 | B2 |
7444469 | Estelle et al. | Oct 2008 | B2 |
7483810 | Jackson et al. | Jan 2009 | B2 |
7492720 | Pruthi et al. | Feb 2009 | B2 |
7573664 | Bentley et al. | Aug 2009 | B2 |
7583604 | Couturier | Sep 2009 | B2 |
7596096 | Crawford et al. | Sep 2009 | B2 |
7627786 | Bello et al. | Dec 2009 | B2 |
7653840 | Taylor et al. | Jan 2010 | B1 |
7809990 | Sasaki | Oct 2010 | B2 |
7885805 | Dickens et al. | Feb 2011 | B2 |
7908366 | Sims | Mar 2011 | B2 |
7971006 | Justiss et al. | Jun 2011 | B2 |
7974215 | Sims | Jul 2011 | B1 |
8035911 | Ballard et al. | Oct 2011 | B2 |
8108544 | Ramakrishnan et al. | Jan 2012 | B2 |
8117501 | Taniyama et al. | Feb 2012 | B2 |
8145572 | Ito | Mar 2012 | B2 |
8180824 | McCoy et al. | May 2012 | B2 |
8195986 | Meaney et al. | Jun 2012 | B2 |
8495432 | Dickens et al. | Jul 2013 | B2 |
8631127 | Sims | Jan 2014 | B2 |
8631281 | Stripling et al. | Jan 2014 | B1 |
8639807 | Sims | Jan 2014 | B2 |
8644185 | Sims | Feb 2014 | B2 |
8645328 | Sims | Feb 2014 | B2 |
8650241 | Moody, II et al. | Feb 2014 | B2 |
8832495 | Foster et al. | Sep 2014 | B2 |
8843787 | Foster et al. | Sep 2014 | B1 |
8949667 | Foster et al. | Feb 2015 | B2 |
9015005 | Stripling | Apr 2015 | B1 |
20010039579 | Trcka et al. | Nov 2001 | A1 |
20010040748 | Nagai et al. | Nov 2001 | A1 |
20020006004 | Miyamura | Jan 2002 | A1 |
20020055999 | Takeda | May 2002 | A1 |
20030070053 | Gallo et al. | Apr 2003 | A1 |
20030097439 | Strayer et al. | May 2003 | A1 |
20030126395 | Camble et al. | Jul 2003 | A1 |
20030128448 | Gunderson et al. | Jul 2003 | A1 |
20030225865 | Koestler | Dec 2003 | A1 |
20030233431 | Reddy et al. | Dec 2003 | A1 |
20040022263 | Zhao et al. | Feb 2004 | A1 |
20040078697 | Duncan | Apr 2004 | A1 |
20040139195 | Feather et al. | Jul 2004 | A1 |
20040139240 | DiCorpo et al. | Jul 2004 | A1 |
20040168102 | Tsunoda | Aug 2004 | A1 |
20050044451 | Fry et al. | Feb 2005 | A1 |
20050052772 | Barbian et al. | Mar 2005 | A1 |
20050076263 | Tomita | Apr 2005 | A1 |
20050086554 | Simes | Apr 2005 | A1 |
20050091369 | Jones | Apr 2005 | A1 |
20050138195 | Bono | Jun 2005 | A1 |
20050149829 | Lee | Jul 2005 | A1 |
20050174869 | Kottomtharayil et al. | Aug 2005 | A1 |
20050210161 | Guignard et al. | Sep 2005 | A1 |
20050231846 | Winarski et al. | Oct 2005 | A1 |
20050246376 | Lu et al. | Nov 2005 | A1 |
20050246509 | Topham et al. | Nov 2005 | A1 |
20050262231 | Lowe et al. | Nov 2005 | A1 |
20060085595 | Slater | Apr 2006 | A1 |
20060092850 | Neidhardt et al. | May 2006 | A1 |
20060126211 | Sasaki | Jun 2006 | A1 |
20060170238 | Justiss et al. | Aug 2006 | A1 |
20060174071 | Justiss et al. | Aug 2006 | A1 |
20060190205 | Klein et al. | Aug 2006 | A1 |
20060242489 | Brockway et al. | Oct 2006 | A1 |
20070025008 | Ballard | Feb 2007 | A1 |
20070067678 | Hosek et al. | Mar 2007 | A1 |
20070079048 | Starr et al. | Apr 2007 | A1 |
20070106840 | Estelle | May 2007 | A1 |
20070226336 | Katagiri et al. | Sep 2007 | A1 |
20070253088 | Clarke et al. | Nov 2007 | A1 |
20070255920 | Gold | Nov 2007 | A1 |
20070294591 | Usynin et al. | Dec 2007 | A1 |
20080019283 | Emile | Jan 2008 | A1 |
20080098168 | Estelle | Apr 2008 | A1 |
20080109547 | Bao et al. | May 2008 | A1 |
20080115015 | Ikezawa et al. | May 2008 | A1 |
20080259809 | Stephan et al. | Oct 2008 | A1 |
20080282265 | Foster et al. | Nov 2008 | A1 |
20090044047 | Bates et al. | Feb 2009 | A1 |
20090059757 | Haustein et al. | Mar 2009 | A1 |
20090070092 | Dickens et al. | Mar 2009 | A1 |
20090106816 | Ito | Apr 2009 | A1 |
20090113129 | Deicke et al. | Apr 2009 | A1 |
20090177314 | Greco et al. | Jul 2009 | A1 |
20090198650 | Sims | Aug 2009 | A1 |
20090198737 | Sims | Aug 2009 | A1 |
20090199045 | Kasubuchi et al. | Aug 2009 | A1 |
20100023604 | Verma et al. | Jan 2010 | A1 |
20100033863 | Fry et al. | Feb 2010 | A1 |
20100125740 | Grechanik | May 2010 | A1 |
20100182887 | Moody et al. | Jul 2010 | A1 |
20100228805 | McCoy et al. | Sep 2010 | A1 |
20100250698 | Haustein et al. | Sep 2010 | A1 |
20100275219 | Carlson et al. | Oct 2010 | A1 |
20110194451 | Sims | Aug 2011 | A1 |
20120185589 | Sims | Jul 2012 | A1 |
20120221597 | Sims | Aug 2012 | A1 |
20140085744 | Stripling et al. | Mar 2014 | A1 |
20140095815 | Sims, Robert C. | Apr 2014 | A1 |
20140112185 | Sims | Apr 2014 | A1 |
20140122438 | Sims | May 2014 | A1 |
20140325284 | Foster et al. | Oct 2014 | A1 |
20140359369 | Foster et al. | Dec 2014 | A1 |
20150106654 | Foster et al. | Apr 2015 | A1 |
Number | Date | Country |
---|---|---|
0726570 | Aug 1996 | EP |
2419198 | Apr 2006 | GB |
Entry |
---|
Notice of Allowance for U.S. Appl. No. 11/801,809, mailed Mar. 25, 2014, 4 pgs. |
Weber, Ralph O. (ed.) Information Technology—SCSI Primary Commands-4 (SPC-4), Project T10/1731-D, Working Draft, rev. 2, Sep. 15, 2005, ENDL Texas, Dallas, TX, 499 pgs. |
Penokie, George (ed.) Information Technology—SCSI Block Commands-3 (SBC-3), T10/1799-D, Working Draft, Rev. 6, Jul. 24, 2006, IBM Corp., Rochester, MN, 169 pgs. |
Weber, Ralph O. (ed.) Information Technology—SCSI Primary Commands-4 (SPC-4), Project T10/1731-D, Working Draft, rev. 10, Apr. 21, 2007, ENDL Texas, Dallas, TX, 551 pgs. |
Weber, Ralph O.(ed.) Information Technology—SCSI Primary Commands-3 (SPC-3), Project T10/1416-D, Working Draft, rev. 22a, Mar. 25, 2005, ENDL Texas, Dallas, TX, 496 pgs. |
Oetting, Erich (ed.) Information Technology—SCSI Media Changer Commands-2 (SMC-2), INCITS T10 Project 1383D, Working Draft, rev. 7, Nov. 18, 2003, Storage Tech Corp., Louisville, CO, 68 pgs. |
International Search Report and Written Opinion for International Patent Application No. PCT/US2008/63227, mailed Aug. 29, 2008, 7 pgs. |
International Search Report and Written Opinion for International Patent Application No. PCT/US2009/032402, mailed Jun. 29, 2009, 11 pgs. |
International Search Report and Written Opinion for International Patent Application No. PCT/US2009/032390, mailed Jul. 3, 2009, 13 pgs. |
Boehler, Paul, “Common SCSI/ATAPI Command Set for Streaming Tape” QIC 157, Revision D, Quarter-Inch Cartridge Drive Standards, Santa Barbara, CA, Dec. 13, 1995, 50 pgs. |
Office Action for U.S. Appl. No. 12/025,322, mailed Dec. 30, 2009, 11 pgs. |
Office Action for U.S. Appl. No. 12/025,436, mailed Mar. 30, 2010, 15 pgs. |
Office Action for U.S. Appl. No. 12/024,755, mailed Jun. 23, 2010, 11 pgs. |
Office Action for U.S. Appl. No. 12/025,322, mailed Jul. 8, 2010, 15 pgs. |
International Preliminary Report on Patentability (Ch. I) for International Application No. PCT/US2009/032402, issued on Aug. 3, 2010, 8 pgs. |
International Preliminary Report on Patentability (Ch. I) for International Application No. PCT/US2009/032390 issued on Aug. 10, 2010, 8 pgs. |
Office Action for U.S. Appl. No. 12/025,436, mailed Sep. 15, 2010, 21 pgs. |
“SCSI DDS Tape Expert Tool (mstm Online Help),” Hewlett Packard, updated Apr. 29, 2002 and printed on Aug. 30, 2010, 8 pgs. at http://docs.hp.com/hpux/onlinedocs/diag/stm/help/expert/scsi—ddsm.htm. |
Office Action for U.S. Appl. No. 11/801,809, mailed Sep. 23, 2010, 31 pgs. |
Notice of Allowance for U.S. Appl. No. 12/024,755, mailed Dec. 10, 2010, 14 pgs. |
Office Action for U.S. Appl. No. 11/801,809, mailed Feb. 16, 2011, 23 pgs. |
Notice of Allowance for U.S. Appl. No. 12/025,322, mailed Feb. 17, 2011, 5 pgs. |
Office Action for U.S. Appl. No. 12/025,436, mailed Mar. 11, 2011, 25 pgs. |
International Search Report and Written Opinion for International Patent Application No. PCT/US2011/021517, mailed Apr. 19, 2011, 12 pgs. |
Office Action for U.S. Appl. No. 11/801,809, mailed Jun. 7, 2011, 16 pgs. |
Office Action for U.S. Appl. No. 12/025,436, mailed Aug. 22, 2011, 32 pgs. |
International Preliminary Report on Patentability (Ch. II) for International Patent Application No. PCT/US08/63227, mailed Oct. 31, 2011, Patent Cooperation Treaty, 25 pgs. |
Corrected International Preliminary Report on Patentability (Ch. II) for International Patent Application No. PCT/US08/63227, mailed Feb. 2, 2012, Patent Cooperation Treaty, 22 pgs. |
Office Action for U.S. Appl. No. 13/459,720, mailed Aug. 1, 2012, 16 pgs. |
Office Action for U.S. Appl. No. 13/430,429, mailed Aug. 2, 2012, 15 pgs. |
Office Action for U.S. Appl. No. 12/025,300, mailed Aug. 6, 2012, 30 pgs. |
Office Action for U.S. Appl. No. 12/861,609, mailed Aug. 7, 2012, 10 pgs. |
Office Action for U.S. Appl. No. 13/091,877, mailed Oct. 11, 2012, 14 pgs. |
Office Action for U.S. Appl. No. 12/025,436, mailed Nov. 9, 2012, 34 pgs. |
Office Action for U.S. Appl. No. 11/801,809, mailed Mar. 27, 2013, 13 pgs. |
Notice of Allowance for U.S. Appl. No. 13/459,720, mailed May 7, 2013, 2 pgs. |
Notice of Allowance for U.S. Appl. No. 13/430,429, mailed May 14, 2013, 4 pgs. |
Notice of Allowance for U.S. Appl. No. 12/692,403, mailed May 14, 2013, 5 pgs. |
Office Action for U.S. Appl. No. 12/861,612, mailed Jun. 11, 2013, 12 pgs. |
Notice of Allowance for U.S. Appl. No. 13/091,877, mailed Jun. 11, 2013, 7 pgs. |
Notice of Allowance for U.S. Appl. No. 11/801,809, mailed Jun. 20, 2013, 4 pgs. |
Office Action for U.S. Appl. No. 12/025,300, mailed Jul. 30, 2013, 29 pgs. |
Notice of Allowance for U.S. Appl. No. 13/430,429, mailed Aug. 1, 2013, 3 pgs. |
Notice of Allowance for U.S. Appl. No. 13/459,720, mailed Aug. 5, 2013, 3 pgs. |
Notice of Allowance for U.S. Appl. No. 12/692,403, mailed Aug. 16, 2013, 3 pgs. |
Office Action for U.S. Appl. No. 12/861,612, mailed Nov. 27, 2012, 12 pgs. |
Office Action for U.S. Appl. No. 12/888,954, mailed Dec. 13, 2012, 14 pgs. |
Office Action for U.S. Appl. No. 12/861,609, mailed Jan. 4, 2013, 12 pgs. |
Notice of Allowance for U.S. Appl. No. 13/430,429, mailed Feb. 11, 2013, 6 pgs. |
Notice of Allowance for U.S. Appl. No. 13/459,720, mailed Feb. 11, 2013, 6 pgs. |
Office Action for U.S. Appl. No. 12/025,300, mailed Feb. 15, 2013, 35 pgs. |
Office Action for U.S. Appl. No. 12/692,403, mailed Feb. 20, 2013, 35 pgs. |
IBM et al., Hardware and Volume Statistical Analysis and Reporting System for Detecting and Isolating Media and Hardware Errors on the Magstar Family of Tape Drives, Dec. 1, 1999, 4 pgs (IP.com No. IPCOM000013086D). |
International Preliminary Report on Patentability (Ch. I) for International Patent Application No. PCT/US2011/021517, mailed Aug. 2, 2012, 8 pgs. |
Notice of Allowance for U.S. Appl. No. 13/091,877, mailed Feb. 27, 2013, 10 pgs. |
Notice of Allowance for U.S. Appl. No. 12/025,436, mailed Mar. 8, 2013, 10 pgs. |
Notice of Allowance for U.S. Appl. No. 11/801,809, mailed Aug. 22, 2013, 5 pgs. |
Office Action for U.S. Appl. No. 12/888,954, mailed Aug. 23, 2013, 16 pgs. |
Office Action for U.S. Appl. No. 12/861,609, mailed Sep. 6, 2013, 11 pgs. |
Notice of Allowance for U.S. Appl. No. 12/861,612, mailed Sep. 30, 2013, 12 pgs. |
Notice of Allowance for U.S. Appl. No. 12/025,436, mailed Oct. 4, 2013, 5 pgs. |
Notice of Allowance for U.S. Appl. No. 13/091,877, mailed Oct. 8, 2013, 5 pgs. |
Notice of Allowance for U.S. Appl. No. 13/430,429, mailed Oct. 30, 2013, 3 pgs. |
Notice of Allowance for U.S. Appl. No. 13/459,720, mailed Oct. 30, 2013, 3 pgs. |
Office Action for U.S. Appl. No. 11/801,809, mailed Dec. 17, 2013, 8 pgs. |
Office Action for U.S. Appl. No. 12/025,300, mailed Jan. 2, 2014, 33 pgs. |
Notice of Allowance for U.S. Appl. No. 12/861,609, mailed Feb. 5, 2014, 3 pgs. |
Notice of Allowance for U.S. Appl. No. 14/324,980, mailed Aug. 25, 2014, 6 pgs. |
Notice of Allowance for U.S. Appl. No. 12/025,300, mailed Sep. 24, 2014, 10 pgs. |
Office Action for U.S. Appl. No. 14/099,591, mailed Oct. 1, 2014, 5 pgs. |
Office Action for U.S. Appl. No. 12/025,300, mailed Apr. 23, 2014, 29 pgs. |
Office Action for U.S. Appl. No. 14/099,591, mailed Jun. 2, 2014, 13 pgs. |
Notice of Allowance for U.S. Appl. No. 11/801,809, mailed Jun. 27, 2014, 4 pgs. |
Corrected Notice of Allowability for U.S. Appl. No. 14/324,980, mailed Oct. 24, 2014, 4 pgs. |
Office Action for U.S. Appl. No. 14/464,034, mailed Nov. 5, 2014, 8 pgs. |
Notice of Allowance for U.S. Appl. No. 14/324,980, mailed Nov. 24, 2014, 5 pgs. |
Notice of Allowance for U.S. Appl. No. 14/464,034, mailed Dec. 19, 2014, 2 pgs. |
Office Action for U.S. Appl. No. 14/092,729, mailed Dec. 24, 2014, 8 pgs. |
Office Action for U.S. Appl. No. 12/888,954, mailed Jan. 5, 2015, 15 pgs. |
Notice of Allowance for U.S. Appl. No. 12/025,300, mailed Jan. 16, 2015, 7 pgs. |
Office Action for U.S. Appl. No. 14/574,077, mailed Feb. 25, 2015, 15 pgs. |
Notice of Allowance for U.S. Appl. No. 14/099,591, mailed Feb. 27, 2015, 10 pgs. |
Notice of Allowance for U.S. Appl. No. 14/464,034, mailed Mar. 9, 2015, 2 pgs. |
Number | Date | Country | |
---|---|---|---|
20140112118 A1 | Apr 2014 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12692403 | Jan 2010 | US |
Child | 14143046 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12024755 | Feb 2008 | US |
Child | 12692403 | US |