US20160134507A1 - System and method of network diagnosis - Google Patents
System and method of network diagnosis Download PDFInfo
- Publication number
- US20160134507A1 US20160134507A1 US15/000,888 US201615000888A US2016134507A1 US 20160134507 A1 US20160134507 A1 US 20160134507A1 US 201615000888 A US201615000888 A US 201615000888A US 2016134507 A1 US2016134507 A1 US 2016134507A1
- Authority
- US
- United States
- Prior art keywords
- data
- drive
- network
- transfer rate
- data transfer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0876—Network utilisation, e.g. volume of load or congestion level
- H04L43/0888—Throughput
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
- H04L63/0471—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload applying encryption by an intermediary, e.g. receiving clear information at the intermediary and encrypting the received information at the intermediary before forwarding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
Definitions
- Networks can be comprised of a multiplicity of network devices such as servers, routers, hosts, switches, repeaters, hubs, encryption devices and backup devices such as media libraries.
- data may be sent over a network from multiple hosts on the network to a library for storage.
- hosts may include computers, servers or other devices.
- the data is routed to the library through a multiplicity of network devices which may include one or more switches, routers, servers, hubs, encryption devices or other network devices.
- a host or other device may also request data from a library and this data may be routed to the host or other device through the network.
- a tape drive in a library reads from or writes to magnetic tape contained in a cartridge utilizing a sensor which may comprise a read head and a write head.
- a sensor which may comprise a read head and a write head.
- magnetic tape is pulled past the sensor comprising the read head and the write head such that the read head can read data from the tape and the write head can write data to the tape.
- Reading and writing to a cartridge inherently causes the degradation of the tape comprising the cartridge because the tape is pulled past the read and write heads. Pulling the tape past the read and write heads may strain the tape and the tape may collide with the read or the write heads at read or write speed. Especially deleterious to tape life is starving a drive of data to write to a tape. In particular, if data is received at a drive at below the drive's ability to write data (i.e. at below the drive's streaming rate), then the movement of magnetic tape may have to be slowed or reversed in order to write data with the necessary density, wearing the tape. Such back and forth pulling of tape past the read and write heads of a drive is referred to as “shoe-shining” and has the potential to accelerate tape degradation. Consequently, bottlenecks or other decreases in data transfer rates caused by network devices can have a deleterious effect at the library.
- Embodiments provide systems and methods for network diagnosis and the identification of problem devices in a network or other issues.
- a system for network diagnosis can include a library comprising a drive, a network coupled to the drive and operable to transmit data to the drive, an infusion device coupled to the network upstream of a portion of the network relative to the drive and operable to infuse control data into the network and a monitoring appliance coupled to the network and operable to send commands to the drive over the network, wherein the monitoring appliance is further operable to calculate the data transfer rate at the drive based on drive data returned in response to the commands.
- two or more infusion devices may be coupled to the network, each infusion device upstream or downstream of a network portion.
- the monitoring appliance can communicate with the infusion device(s) over the network to cause the infusion device(s) to begin infusing data into the network.
- Embodiments of methods and systems for network diagnosis can include a method comprising infusing control data into a network coupled to a drive at known location(s) upstream and downstream of a portion of the network relative to the drive, querying the drive at intervals over time for drive data by sending one or more Log Sense (LS) commands or Inquiry commands to the drive and determining the data transfer rates at the drive for data infused upstream and downstream of the portion of the network based on returned drive data.
- LS Log Sense
- Embodiments of methods and systems for network diagnosis can include one or more computer readable media comprising computer instructions executable to perform the above method.
- Such computer readable media may be contained in a monitoring appliance or an infusion device.
- FIG. 1 is a diagrammatic representation of one embodiment of a library
- FIG. 3 is a diagrammatic representation of one embodiment of a network
- 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.”
- Embodiments of systems and methods may be used to diagnose networks such that bottlenecks, inefficiencies or problem devices in the network can be identified.
- Data sent over a network to be stored in magnetic tapes at a library may encounter bottlenecks, inefficiencies or problem devices in the network which may slow the transmission of the data or reduce the data transfer rate (which can be expressed in MB/s) to the library, reducing the amount of data received by a library drive to below a library drive's streaming rate.
- Starving a drive of data in such a manner can cause the movement of magnetic tape being written to by a drive to be slowed or reversed in order to write data with the necessary density, wearing the tape in a so-called shoe-shine fashion.
- data sent from a drive to a host or other device over a network may also encounter bottlenecks or problem devices.
- data may be requested from a specific drive of a library at two or more known locations in a network and the difference in the data transfer rates of data sent to different locations from the drive may be monitored at the drive utilizing the monitoring device. Differences in the data transfer rates may be used to determine problem network devices or portions of the network which act as a bottleneck.
- a monitoring appliance can query a library or library components over a network utilizing commands.
- the library or library drives may return data associated with a particular command to the monitoring appliance.
- a monitoring appliance can query a library drive over a network utilizing SCSI commands such as the Log Sense Command, Inquiry Command and other commands.
- 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 media contained in the drive.
- data might include: utilization and performance data such as, for example, data transfer rates, media loaded, the amount of data received by the drive, the amount of data sent or transmitted by the drive, the amount of data written by the drive, the amount of data read by the drive or other data.
- the drive returns the current count of bytes transferred since a cartridge was loaded. 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 the serial number of components of a library such as a drive or a media changer.
- Embodiments of Inquiry commands query individual library components. That is, an individual Inquiry command may query a particular drive for its serial number. 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 drive can utilize a monitoring appliance which can be a Read Verify Appliance (RVA).
- the monitoring appliance queries a library or drives by sending LS, Inquiry commands and/or other commands to the library or library components at intervals.
- Data returned in response to the commands may be used to determine the data transfer rate of data to (or from) a drive and whether the data transfer rate is below the drive's streaming rate, causing shoe-shining. It should be noted that determining the data transfer rate of data may comprise one or more calculations.
- Data returned in response to the commands may be saved to a repository and information or data calculated from returned data (for example, the data transfer rate at the drive) may also be saved to the repository.
- a LS command may be sent to a drive periodically, such as, for example, every 30 seconds, such that when data is being received by a drive from the network and written to magnetic tape, the amount of data received by the drive within the period between LS commands may be returned to the monitoring appliance in response to the LS commands.
- This returned data specifying the amount of data received at the drive may be used to determine the data transfer rate at which the drive receives data or the rate at which the drive writes data to magnetic tape. Based on the data transfer rate, it can be determined whether the drive is receiving data at a desired data transfer rate, above the streaming rate of the drive or below the streaming rate of the drive.
- LS commands can be used to determine the data transfer rate of data sent over a network from a drive.
- a device such as an infusion device located at a known location in a network can send commands to one or more library drives.
- the commands used to infuse data into a network may be Write commands or Read commands.
- a Read command is a command which can be used to read tape cartridges (or other library media such as laser discs, hard drives or any other media). That is, a requesting device-which may in one embodiment be an infusion device-sends a Read command to a specified drive and in response, the drive reads data stored on the cartridge and the read data is returned to the requesting device.
- a Read command can be used to retrieve data from a tape cartridge in a drive and transmit the retrieved data over a network or portion thereof. Examples of a Read command can be found in “SCSI Block Commands-3 (SBC-3)”, (Project T10/1799-D), Revision 6, 24 Jul. 2006, propagated by the T10 Technical Committee of the InterNational Committee on Information Technology Standards (INCITS), which is hereby incorporated by reference.
- Methods and systems for sending data over a network to a drive can include sending multiple Write commands to a specified drive from a known location in a network utilizing a device which may be an infusion device.
- the infusion device may be connected to the network at the known location and may send a Write command to the specified drive.
- the specified drive may return an indication such as a command complete message to the infusion device, in response to which the infusion device sends another Write command.
- the above process may be repeated multiple times such that data is infused into the network at a known location and sent to the specified drive at a data transfer rate supported by the network portion downstream of the known location of the infusion device and upstream of the library drive.
- Methods and systems for sending data over a network from a drive can include sending multiple Read commands to a specified drive from a known location in a network utilizing a device which may be an infusion device.
- the infusion device may be connected to the network at the known location and may send a Read command to the specified drive.
- the specified drive may return read data to the infusion device, in response to which the infusion device sends another Read command.
- the above process may be repeated multiple times such that data is infused into the network and sent to a known location from the specified drive at a data transfer rate supported by the network portion downstream of the known location of the infusion device and upstream of the library drive.
- Data sent from hosts 290 a and 290 b over network 210 to be stored at library 100 may traverse a path which includes any number of network devices, including switch 220 , router 230 , hub 240 , repeater 250 , server 260 or encryption device 270 , alone or in combination.
- One or more network devices comprising network 210 may slow the transfer of data from hosts 290 a or 290 b to library 100 , thus reducing the data transfer rate to drives in library 100 , potentially starving the drives of data, causing drives to receive data at or below a streaming rate.
- Network devices may slow the transfer of data to library 100 because they are not properly configured, because they are not working properly, because they are poorly-performing devices or any one of a number of other reasons.
- encryption device 270 encrypts data sent over network 210 to drive 140 a of library 100 .
- Encryption device 270 receives data destined for drive 140 a and encrypts the data before transmitting the encrypted data to drive 140 a .
- Drive 140 a receives the encrypted data and writes the encrypted data to magnetic tape. If drive 140 a receives the encrypted data at or below its streaming rate, the magnetic tape may have to be slowed or reversed while writing in order to write data with the necessary density.
- infusion devices 330 may be coupled to network 210 .
- Infusion device 330 a is coupled to network 210 upstream of encryption device 270 such that infusion device 330 a is operable to infuse known data, such as, for example, data with a known compressibility, known data sequences or with other known parameters, into network 210 such that the infused data traverses a network path including encryption device 270 before the infused data reaches drive 140 a .
- known data such as, for example, data with a known compressibility, known data sequences or with other known parameters
- monitoring appliance 320 can query the amount of data received at drive 140 a over time by sending LS commands over network 210 to drive 140 a , in response to which drive 140 a returns the amount of data received, the amount of data written, the speed at which data was written or other data. Based on the returned amount of data received, the monitoring appliance can determine the data transfer rate at the drive and thus the data transfer rate (i.e. throughput) through encryption device 270 .
- multiple LS commands may be sent to a drive at a predetermined frequency while the drive is writing the artificially infused data to tape.
- the data returned may include the amount of data transferred to the drive over the network in the interim between the last LS command, thus the data transfer rate at the drive can be calculated by dividing the amount of data (which may be in MB) received by the drive over the network between LS commands by the duration between the LS commands (which may be in seconds).
- the differential between the data transfer rates of data infused by infusion device 330 a and data infused by infusion device 330 b can be used to diagnose whether encryption device 270 acts as a bottleneck or otherwise hinders the transmission of data to drive 140 a over network 210 . For example, if encryption device 270 encrypts data at below a certain rate and is consequently not able to transfer data at an adequate data transfer rate to drive 140 a , drive 140 a may be starved of data.
- data may be infused upstream of encryption device 270 by infusion device 330 a , if the data transfer rate of the data infused by infusion device 330 a is lower than the data transfer rate of the data infused by infusion device 330 b , than encryption device 270 may be acting as a bottleneck and reducing throughput through the network.
- infusion devices 330 a and 330 b may send Read commands to drive 140 a over network 210 .
- Monitoring appliance 320 can use LS commands to determine the data transfer rates of data sent from drive 140 a to infusion devices 330 a and 330 b : if the data transfer rate is higher at infusion device 330 b than 330 a , encryption device 270 may be acting as a bottleneck and reducing throughput through the network.
- infusion device(s) 330 may be manually activated.
- an infusion device may have multiple connections and each of the multiple connections may be coupled to different known locations in the network.
- the infusion device may be able to infuse data at multiple points in the network.
- the infusion device may have one connection upstream of encryption device 270 and another connection downstream of encryption device 270 .
- monitoring appliance may include an infusion device or an infusion device module which may be connected to one or more known location in a network, allowing the monitoring appliance to diagnose the network.
- Multiple network devices in a network may reduce throughput, the use of multiple infusion devices or moving an infusion device to multiple locations in a network may allow the degree to which individual network devices reduce throughput to be determined.
- the source of network bottlenecks can be inferred.
- Infusion devices may be operable to infuse different sets of known data with different properties.
- sets of known data may include data sets of different compression ratios.
- a monitoring appliance can send one or more commands to an infusion device to select a particular set of data to infuse into a network.
- Sets of data sent from an infusion device may contain data allowing the data to be correlated with the infusion device that infused the data.
- infusion devices may be portable devices which may be removed and coupled to different locations in a network to diagnose different devices or network sections.
- FIG. 4 is a flow chart illustrating a method 410 for identifying network bottlenecks or other network or network device issues.
- one or more steps of method 410 can be implemented as a set of computer executable instructions stored on computer readable media at, for example, monitoring appliance 320 and infusion device 330 of FIG. 3 .
- the set of computer executable instructions can, when executed, be utilized to identify network bottlenecks.
- known data destined for a known drive is infused upstream of a known device or network section. For example, 2:1 compressible data may be infused into a network upstream of an encryption device.
- the drive receiving the data infused at step 420 may be queried at known intervals to determine the amount of data transferred to a drive between intervals.
- the data transfer rate of the known data at the drive is determined. For example, LS commands may be sent to the drive every 30 seconds and the amount of data received at the drive in a 30 second interval divided by 30 seconds to determine the data transfer rate to the drive.
- known data destined for a known drive is infused downstream of a known device or network section.
- a known device or network section For example, 2:1 compressible data may be infused into a network downstream of an encryption device.
- the drive receiving the data infused at step 450 may be queried at known intervals to determine the amount of data transferred to a drive between intervals.
- the data transfer rate of the known data at the drive is determined. For example, LS commands may be sent to the drive every 30 seconds and the amount of data received at the drive in a 30 second interval divided by 30 seconds to determine the data transfer rate to the drive.
- the data transfer rate of data infused upstream of the known device or network section (determined at step 440 ) is compared to the data transfer rate of data infused downstream of the known device or network section (determined at step 470 ). If the data transfer rates are the same (or within some acceptable difference), then the device or network section is functioning correctly or not overly decreasing throughput. If, however, the data transfer rate of data infused upstream of the device or network section is lower than the data transfer rate of data infused downstream of the device or network section, the device or network section is reducing throughput and acting as a bottleneck to the transfer of data. Thus, problem devices may be identified and the degree to which problem devices reduce throughput can be determined. Method 410 or one or more steps of method 410 may be repeated to diagnose multiple devices or sections comprising a network to identify throughput losses and device performance issues throughout the network.
- FIG. 6 is one example of a graphical user interface displaying a graphical representation 600 of the data transfer rate at a drive over time.
- Data transfer rate 610 is the data transfer rate of data received by a drive.
- Graphical representation 600 includes streaming rate indicator threshold line 620 , which indicates the streaming level of the drive.
- Graphical representation 600 also includes ideal data transfer rate indicator line 630 , which indicates the ideal data transfer rate for the drive and maximum data transfer rate indicator line 640 , which indicates the maximum data transfer rate for the drive.
- Data transfer rate 610 can be compared with lines 620 , 630 and 640 by a user viewing graphical representation 600 .
- data transfer rate 610 may graph the data transfer rate of data infused into a network by an infusion device at a known location.
- Secondary memory 704 can store a variety of computer instructions that include, for example, an operating system such as a Windows or Linux 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 interfaces with devices (which may be, for example, drives or infusion devices) over a network and determines the data transfer rate at one or more drives. During execution by processor 702 , portions of program 730 can be stored in secondary memory 704 and/or primary memory 703 .
- an operating system such as a Windows or Linux operating system (Windows is a trademark of Redmond, Wash. based Microsoft Corporation)
- applications that run on the operating system
- secondary memory 704 can store a software program 730 that interfaces with devices (which may be, for example, drives or infusion devices) over a network and determines the data transfer rate at one or more drives.
- portions of program 730 can be stored in secondary memory 704 and/or
Abstract
Embodiments provide systems and methods for diagnosing a network and identifying problems in a network which reduce the data transfer rate of data through the network. One embodiment of a method for network diagnosis may include infusing data into a network upstream and downstream of a portion of the network relative to a library drive, querying the drive at intervals over time for drive data to determine the data transfer rate at the drive and comparing the data transfer rate of the data infused upstream of the device or network portion with the data transfer rate of the data infused downstream of the device or network portion to determine throughput. By comparing the data transfer rate of data infused upstream and downstream of a network device or network portion, problem devices in a network may be identified.
Description
- This application is a continuation of, and claims a benefit of priority under 35 U.S.C. 120 of the filing date of U.S. patent application Ser. No. 14/144,077 filed Dec. 30, 2013, entitled “SYSTEM AND METHOD OF NETWORK DIAGNOSIS”, by inventor Robert C. Sims, which is a continuation of, and claims a benefit of priority under 35 U.S.C. 120 of the filing date of U.S. patent application Ser. No. 13/091,877, filed Apr. 21, 2011, entitled “SYSTEM AND METHOD OF NETWORK DIAGNOSIS”, by inventor Robert C. Sims, issued as U.S. Pat. No. 8,644,185, on Feb. 4, 2014, which is a continuation of, and claims a benefit of priority under 35 U.S.C. 120 of the filing date of U.S. patent application Ser. No. 12/025,322, filed Feb. 4, 2008, entitled “SYSTEM AND METHOD OF NETWORK DIAGNOSIS”, by inventor Robert C. Sims, issued as U.S. Pat. No. 7,974,215 on Jul. 5, 2011, the entire contents of which are hereby expressly incorporated by reference for all purposes.
- This disclosure describes systems and methods of network diagnosis. More particularly, embodiments of methods and systems regard infusing data at known locations to diagnose network performance. In one embodiment, the performance of devices in the network and the data transfer rate through network devices can be determined such that the performance of devices in the context of a network can be diagnosed.
- Networks can be comprised of a multiplicity of network devices such as servers, routers, hosts, switches, repeaters, hubs, encryption devices and backup devices such as media libraries.
- In many systems, data may be sent over a network from multiple hosts on the network to a library for storage. Such hosts may include computers, servers or other devices. In many instances, the data is routed to the library through a multiplicity of network devices which may include one or more switches, routers, servers, hubs, encryption devices or other network devices. A host or other device may also request data from a library and this data may be routed to the host or other device through the network.
- One example of a library commonly used for data storage 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 data is to be written to or read from the library, a host device determines which cartridge slot contains the tape cartridge that is to be written to or read from. 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.
- A tape drive in a library reads from or writes to magnetic tape contained in a cartridge utilizing a sensor which may comprise a read head and a write head. In one embodiment of a drive, magnetic tape is pulled past the sensor comprising the read head and the write head such that the read head can read data from the tape and the write head can write data to the tape.
- Reading and writing to a cartridge inherently causes the degradation of the tape comprising the cartridge because the tape is pulled past the read and write heads. Pulling the tape past the read and write heads may strain the tape and the tape may collide with the read or the write heads at read or write speed. Especially deleterious to tape life is starving a drive of data to write to a tape. In particular, if data is received at a drive at below the drive's ability to write data (i.e. at below the drive's streaming rate), then the movement of magnetic tape may have to be slowed or reversed in order to write data with the necessary density, wearing the tape. Such back and forth pulling of tape past the read and write heads of a drive is referred to as “shoe-shining” and has the potential to accelerate tape degradation. Consequently, bottlenecks or other decreases in data transfer rates caused by network devices can have a deleterious effect at the library.
- Embodiments provide systems and methods for network diagnosis and the identification of problem devices in a network or other issues. A system for network diagnosis can include a library comprising a drive, a network coupled to the drive and operable to transmit data to the drive, an infusion device coupled to the network upstream of a portion of the network relative to the drive and operable to infuse control data into the network and a monitoring appliance coupled to the network and operable to send commands to the drive over the network, wherein the monitoring appliance is further operable to calculate the data transfer rate at the drive based on drive data returned in response to the commands. In some embodiments, two or more infusion devices may be coupled to the network, each infusion device upstream or downstream of a network portion. In embodiments of a system for network diagnosis, the monitoring appliance can communicate with the infusion device(s) over the network to cause the infusion device(s) to begin infusing data into the network.
- Embodiments of methods and systems for network diagnosis can include a method comprising infusing control data into a network coupled to a drive at known location(s) upstream and downstream of a portion of the network relative to the drive, querying the drive at intervals over time for drive data by sending one or more Log Sense (LS) commands or Inquiry commands to the drive and determining the data transfer rates at the drive for data infused upstream and downstream of the portion of the network based on returned drive data.
- Embodiments of methods and systems for network diagnosis can include one or more computer readable media comprising computer instructions executable to perform the above method. Such computer readable media may be contained in a monitoring appliance or an infusion device.
- By diagnosing a network and identifying problem devices or other issues which reduce throughput through the network or otherwise reduce the data transfer rate of data through the network, networks problems can be discovered and addressed, improving throughput through the network and preventing network devices from reducing the data transfer rate. Furthermore, because issues which reduce the data transfer rate through a network are resolved, data transfer rates which cause the starving of data to a drive of a library and the consequent shoe-shining of magnetic tape in cartridges being written to by the drive may be avoided, extending the life and enhancing the reliability of magnetic tape cartridges.
- 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:
-
FIG. 1 is a diagrammatic representation of one embodiment of a library; -
FIG. 2 is a diagrammatic representation of one embodiment of a network; -
FIG. 3 is a diagrammatic representation of one embodiment of a network; -
FIG. 4 is a flowchart illustrating a method for collecting and compiling network device data; -
FIG. 5 is an XML representation of an example of data returned in response to a LS command; -
FIG. 6 is one example of a graphical user interface; and -
FIG. 7 is a diagrammatic representation of one embodiment of a controller which can be used in a monitoring appliance. - Embodiments 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, process, 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, process, 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.”
- This disclosure describes systems and methods for diagnosing networks. Embodiments of systems and methods may be used to diagnose networks such that bottlenecks, inefficiencies or problem devices in the network can be identified. Data sent over a network to be stored in magnetic tapes at a library may encounter bottlenecks, inefficiencies or problem devices in the network which may slow the transmission of the data or reduce the data transfer rate (which can be expressed in MB/s) to the library, reducing the amount of data received by a library drive to below a library drive's streaming rate. Starving a drive of data in such a manner can cause the movement of magnetic tape being written to by a drive to be slowed or reversed in order to write data with the necessary density, wearing the tape in a so-called shoe-shine fashion. Similarly, data sent from a drive to a host or other device over a network may also encounter bottlenecks or problem devices.
- To detect bottlenecks, inefficiencies or problem devices in a network that reduce the data transfer rate to a drive to below the drive's streaming rate, data may be artificially infused into a network at known locations upstream or downstream of specified devices or network portions and the data transfer rate of the infused data at a drive may be monitored. For example, known data may be artificially infused upstream of an encryption appliance utilizing an infusion device and the data transfer rate of the artificially infused data may be monitored at a library drive utilizing a monitoring appliance which may be a Read Verify Appliance (RVA). Known data may also be artificially infused downstream of the encryption appliance utilizing another or the same infusion device and the data transfer rate of the artificially infused data may be monitored at a library drive utilizing the monitoring appliance. If the monitoring appliance detects that the data transfer rate of the data infused upstream of the encryption appliance is slower at a library drive than data infused downstream of the encryption appliance, it may be determined that the encryption appliance is acting as a bottleneck, lowering the data transfer rate, reducing the throughput of the network and perhaps contributing to starving one or more drives in a network of data.
- Similarly, data may be requested from a specific drive of a library at two or more known locations in a network and the difference in the data transfer rates of data sent to different locations from the drive may be monitored at the drive utilizing the monitoring device. Differences in the data transfer rates may be used to determine problem network devices or portions of the network which act as a bottleneck.
-
FIG. 1 is a diagrammatic representation of one embodiment of a tape library, as would be understood by one of ordinary skill in the art.Library 100 can comprisedrives 140 a-140 e,media changer 125 and associatedrobot 130, import/export element(s) 145 and slots 135 a-135 j.Drives 140 a-140 e can read/write data from/to magnetic tape (contained within cartridges), eject tape cartridges and perform other operations. Slots 135 a-135 j store the magnetic tape cartridges when they are not in a drive androbot 130 moves the magnetic tape cartridges betweendrives 140 a-140 e and slots 135 a-135 j. For example,robot 130 may move a tape cartridge stored atslot 135 a to drive 140 b so that data can be read from the tape cartridge. It should be noted that some libraries may employ a single robot or multiple robots in an expandable or modular configuration. - To collect data associated with a library or library components such as, for example, drives, a monitoring appliance can query a library or library components over a network utilizing commands. In response to received commands, the library or library drives may return data associated with a particular command to the monitoring appliance. In one embodiment, a monitoring appliance can query a library drive over a network utilizing SCSI commands such as the Log Sense Command, Inquiry Command and other commands.
- 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 media contained in the drive. For example, such data might include: utilization and performance data such as, for example, data transfer rates, media loaded, the amount of data received by the drive, the amount of data sent or transmitted by the drive, the amount of data written by the drive, the amount of data read by the drive or other data. In one embodiment, the drive returns the current count of bytes transferred since a cartridge was loaded. 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 the serial number of components of a library such as a drive or a media changer. Embodiments of Inquiry commands query individual library components. That is, an individual Inquiry command may query a particular drive for its serial number. 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 drive can utilize a monitoring appliance which can be a Read Verify Appliance (RVA). The monitoring appliance queries a library or drives by sending LS, Inquiry commands and/or other commands to the library or library components at intervals. Data returned in response to the commands may be used to determine the data transfer rate of data to (or from) a drive and whether the data transfer rate is below the drive's streaming rate, causing shoe-shining. It should be noted that determining the data transfer rate of data may comprise one or more calculations. Data returned in response to the commands may be saved to a repository and information or data calculated from returned data (for example, the data transfer rate at the drive) may also be saved to the repository. For example, a LS command may be sent to a drive periodically, such as, for example, every 30 seconds, such that when data is being received by a drive from the network and written to magnetic tape, the amount of data received by the drive within the period between LS commands may be returned to the monitoring appliance in response to the LS commands. This returned data specifying the amount of data received at the drive may be used to determine the data transfer rate at which the drive receives data or the rate at which the drive writes data to magnetic tape. Based on the data transfer rate, it can be determined whether the drive is receiving data at a desired data transfer rate, above the streaming rate of the drive or below the streaming rate of the drive. Similarly, LS commands can be used to determine the data transfer rate of data sent over a network from a drive.
- To write data to media contained in a drive of a library or read data from media contained in a drive of a library, thereby infusing data into a network, a device such as an infusion device located at a known location in a network can send commands to one or more library drives. In one embodiment, the commands used to infuse data into a network may be Write commands or Read commands.
- A Write command is a command which can be used to transfer data to specified drives and write data to tape cartridges (or other library media such as laser discs, hard drives or any other media). That is, a device, which may be an infusion device, sends a Write command which may contain data to a drive and in response, the drive writes the data contained in that Write command to a cartridge. Thus a Write command can be used to send data to a drive over a network or portion thereof. Examples of a Write command can be found in “SCSI Block Commands-3 (SBC-3)”, (Project T10/1799-D), Revision 6, 24 Jul. 2006, propagated by the T10 Technical Committee of the InterNational Committee on Information Technology Standards (INCITS), which is hereby incorporated by reference.
- A Read command is a command which can be used to read tape cartridges (or other library media such as laser discs, hard drives or any other media). That is, a requesting device-which may in one embodiment be an infusion device-sends a Read command to a specified drive and in response, the drive reads data stored on the cartridge and the read data is returned to the requesting device. Thus a Read command can be used to retrieve data from a tape cartridge in a drive and transmit the retrieved data over a network or portion thereof. Examples of a Read command can be found in “SCSI Block Commands-3 (SBC-3)”, (Project T10/1799-D), Revision 6, 24 Jul. 2006, propagated by the T10 Technical Committee of the InterNational Committee on Information Technology Standards (INCITS), which is hereby incorporated by reference.
- Methods and systems for sending data over a network to a drive can include sending multiple Write commands to a specified drive from a known location in a network utilizing a device which may be an infusion device. The infusion device may be connected to the network at the known location and may send a Write command to the specified drive. In response to receiving the Write command or processing the Write command (for example, by writing data contained in the Write command to media), the specified drive may return an indication such as a command complete message to the infusion device, in response to which the infusion device sends another Write command. The above process may be repeated multiple times such that data is infused into the network at a known location and sent to the specified drive at a data transfer rate supported by the network portion downstream of the known location of the infusion device and upstream of the library drive.
- Methods and systems for sending data over a network from a drive can include sending multiple Read commands to a specified drive from a known location in a network utilizing a device which may be an infusion device. The infusion device may be connected to the network at the known location and may send a Read command to the specified drive. In response to receiving the Read command and processing the Read command (for example, by reading data from media), the specified drive may return read data to the infusion device, in response to which the infusion device sends another Read command. The above process may be repeated multiple times such that data is infused into the network and sent to a known location from the specified drive at a data transfer rate supported by the network portion downstream of the known location of the infusion device and upstream of the library drive.
-
FIG. 2 is a diagrammatic representation of one embodiment of asystem 200. Insystem 200, hosts 290 a and 290 b, which may be personal computers, andlibrary 100 are coupled to network 210 such that hosts 290 a and 290 b may send data overnetwork 210 to a drive atlibrary 100, namely drive 140 a. InFIG. 2 ,network 210 may be a fibre channel network, IP network or any other network or combination of networks.Network 210 can comprise network devices such asswitch 220,router 230,hub 240,repeater 250,server 260,encryption device 270 or other network devices. Data sent fromhosts network 210 to be stored atlibrary 100 may traverse a path which includes any number of network devices, includingswitch 220,router 230,hub 240,repeater 250,server 260 orencryption device 270, alone or in combination. One or more networkdevices comprising network 210, including network devices 220-270, may slow the transfer of data fromhosts library 100, thus reducing the data transfer rate to drives inlibrary 100, potentially starving the drives of data, causing drives to receive data at or below a streaming rate. Network devices may slow the transfer of data tolibrary 100 because they are not properly configured, because they are not working properly, because they are poorly-performing devices or any one of a number of other reasons. -
FIG. 3 is an embodiment of a system operable to artificially infuse data into a network such that the network can be diagnosed and problem network devices or other issues identified.System 300 ofFIG. 3 comprises infusion devices 330 andmonitoring appliance 320, all of which are coupled tonetwork 210.Monitoring appliance 320 is coupled tonetwork 210 such thatmonitoring appliance 320 can send commands to and receive data from the devices comprising library 100 (for example, drive 140 a) overnetwork 210. In response to the commands,monitoring appliance 320 can receive information that allows monitoringappliance 320 to determine the data transfer rate of data received at (or sent from)library 100. By infusing data with infusion device(s) 330 at known locations and known data transfer rates, and evaluating the data received fromlibrary 100, the location and magnitude of bottlenecks and other inefficiencies can be determined. - As an initial example, inefficiencies caused by
encryption device 270 can be identified. Innetwork 210,encryption device 270 encrypts data sent overnetwork 210 to drive 140 a oflibrary 100.Encryption device 270 receives data destined fordrive 140 a and encrypts the data before transmitting the encrypted data to drive 140 a. Drive 140 a receives the encrypted data and writes the encrypted data to magnetic tape. Ifdrive 140 a receives the encrypted data at or below its streaming rate, the magnetic tape may have to be slowed or reversed while writing in order to write data with the necessary density. - To determine the performance of
encryption device 270, infusion devices 330 may be coupled tonetwork 210. Infusion device 330 a is coupled tonetwork 210 upstream ofencryption device 270 such that infusion device 330 a is operable to infuse known data, such as, for example, data with a known compressibility, known data sequences or with other known parameters, intonetwork 210 such that the infused data traverses a network path includingencryption device 270 before the infused data reaches drive 140 a. During processing of the infused data (which may, in one embodiment, comprise writing the data to tape) atdrive 140 a,monitoring appliance 320 can query the amount of data received atdrive 140 a over time by sending LS commands overnetwork 210 to drive 140 a, in response to which drive 140 a returns the amount of data received, the amount of data written, the speed at which data was written or other data. Based on the returned amount of data received, the monitoring appliance can determine the data transfer rate at the drive and thus the data transfer rate (i.e. throughput) throughencryption device 270. -
Infusion device 330 b is coupled tonetwork 210 downstream ofencryption device 270 such thatinfusion device 330 b is operable to infuse known data (for example, data with a known compressibility, known data sequences or with other known parameters) intonetwork 210 such that the infused data traverses a network path which does not includeencryption device 270. During processing of the infused data (which may, in one embodiment, comprise writing the data to tape) atdrive 140 a,monitoring appliance 320 can query the amount of data received atdrive 140 a over time by sending LS commands overnetwork 210 to drive 140 a, in response to which drive 140 a returns the amount of data received, the amount of data written, the speed at which data was written or other data. Based on the returned amount of data received, the monitoring appliance can determine the data transfer rate at the drive and thus the data transfer rate (i.e. throughput) throughnetwork 210 downstream ofencryption device 270. - In one embodiment, to determine the data transfer rate of infused data, multiple LS commands may be sent to a drive at a predetermined frequency while the drive is writing the artificially infused data to tape. The data returned may include the amount of data transferred to the drive over the network in the interim between the last LS command, thus the data transfer rate at the drive can be calculated by dividing the amount of data (which may be in MB) received by the drive over the network between LS commands by the duration between the LS commands (which may be in seconds).
- The differential between the data transfer rates of data infused by infusion device 330 a and data infused by
infusion device 330 b (i.e. the difference in throughput) can be used to diagnose whetherencryption device 270 acts as a bottleneck or otherwise hinders the transmission of data to drive 140 a overnetwork 210. For example, ifencryption device 270 encrypts data at below a certain rate and is consequently not able to transfer data at an adequate data transfer rate to drive 140 a, drive 140 a may be starved of data. Thus, to detect such an issue or problem or similar issues or problems, data may be infused upstream ofencryption device 270 by infusion device 330 a, if the data transfer rate of the data infused by infusion device 330 a is lower than the data transfer rate of the data infused byinfusion device 330 b, thanencryption device 270 may be acting as a bottleneck and reducing throughput through the network. - In another example,
infusion devices 330 a and 330 b may send Read commands to drive 140 a overnetwork 210.Monitoring appliance 320 can use LS commands to determine the data transfer rates of data sent fromdrive 140 a toinfusion devices 330 a and 330 b: if the data transfer rate is higher atinfusion device 330 b than 330 a,encryption device 270 may be acting as a bottleneck and reducing throughput through the network. - In one embodiment,
monitoring appliance 320 can communicate with infusion devices 330 overnetwork 210 to turn on or off data infusion from infusion device 330 a orinfusion device 330 b intonetwork 210.Monitoring appliance 320 may also select the data to be infused intonetwork 210, for example, non-compressible data or compressible date having a known compression ratio. It may also be possible to activate infusion devices 330 utilizing a host which sends commands to infusion devices 330 overnetwork 210.Monitoring appliance 320 may be notified overnetwork 210 that an infusion device 330 has been activated and is infusing data intonetwork 210.Monitoring appliance 320 may synchronize with an infusion device 330 through communications with the infusion device 330 overnetwork 210. In another embodiment, infusion device(s) 330 may be manually activated. In another embodiment, an infusion device may have multiple connections and each of the multiple connections may be coupled to different known locations in the network. Thus, the infusion device may be able to infuse data at multiple points in the network. For example, the infusion device may have one connection upstream ofencryption device 270 and another connection downstream ofencryption device 270. In a still further embodiment, monitoring appliance may include an infusion device or an infusion device module which may be connected to one or more known location in a network, allowing the monitoring appliance to diagnose the network. - While in
FIG. 3 , a single pair of infusion devices are shown, multiple infusion devices may be utilized in a network to diagnose different devices or sections of a network. For example, inFIG. 3 , an additional infusion device may be located upstream ofhub 240 and infusion device 330 a. If data from the additional infusion device is received at a drive at a lower data transfer rate than data infused by infusion device 330 a, this implies that the network portion downstream of the additional infusion device but upstream of infusion device 330 a is limiting throughput, acting as a bottleneck and consequently reducing the data transfer rate. Thus, multiple infusion devices may be used in conjunction to diagnose a network for problem devices. Multiple network devices in a network may reduce throughput, the use of multiple infusion devices or moving an infusion device to multiple locations in a network may allow the degree to which individual network devices reduce throughput to be determined. Depending on the data transfer rates of data received from particular infusion devices and the locations of the infusion devices, the source of network bottlenecks can be inferred. - Infusion devices may be operable to infuse different sets of known data with different properties. For example, such sets of known data may include data sets of different compression ratios. In one embodiment, a monitoring appliance can send one or more commands to an infusion device to select a particular set of data to infuse into a network. Sets of data sent from an infusion device may contain data allowing the data to be correlated with the infusion device that infused the data. Furthermore, infusion devices may be portable devices which may be removed and coupled to different locations in a network to diagnose different devices or network sections.
-
FIG. 4 is a flow chart illustrating amethod 410 for identifying network bottlenecks or other network or network device issues. According to one embodiment, one or more steps ofmethod 410 can be implemented as a set of computer executable instructions stored on computer readable media at, for example,monitoring appliance 320 and infusion device 330 ofFIG. 3 . The set of computer executable instructions can, when executed, be utilized to identify network bottlenecks. Atstep 420, known data destined for a known drive is infused upstream of a known device or network section. For example, 2:1 compressible data may be infused into a network upstream of an encryption device. Atstep 430, the drive receiving the data infused atstep 420 may be queried at known intervals to determine the amount of data transferred to a drive between intervals. Atstep 440, the data transfer rate of the known data at the drive is determined. For example, LS commands may be sent to the drive every 30 seconds and the amount of data received at the drive in a 30 second interval divided by 30 seconds to determine the data transfer rate to the drive. - At
step 450, known data destined for a known drive is infused downstream of a known device or network section. For example, 2:1 compressible data may be infused into a network downstream of an encryption device. Atstep 460, the drive receiving the data infused atstep 450 may be queried at known intervals to determine the amount of data transferred to a drive between intervals. Atstep 470, the data transfer rate of the known data at the drive is determined. For example, LS commands may be sent to the drive every 30 seconds and the amount of data received at the drive in a 30 second interval divided by 30 seconds to determine the data transfer rate to the drive. - At
step 480, the data transfer rate of data infused upstream of the known device or network section (determined at step 440) is compared to the data transfer rate of data infused downstream of the known device or network section (determined at step 470). If the data transfer rates are the same (or within some acceptable difference), then the device or network section is functioning correctly or not overly decreasing throughput. If, however, the data transfer rate of data infused upstream of the device or network section is lower than the data transfer rate of data infused downstream of the device or network section, the device or network section is reducing throughput and acting as a bottleneck to the transfer of data. Thus, problem devices may be identified and the degree to which problem devices reduce throughput can be determined.Method 410 or one or more steps ofmethod 410 may be repeated to diagnose multiple devices or sections comprising a network to identify throughput losses and device performance issues throughout the network. - While
method 410 ofFIG. 4 regards sending data to a drive, in other embodiments, data can be sent from a drive and received at known locations in a network. The data transfer rates of data received upstream and downstream of network devices or network portions can be compared to identify problem devices or problem network portions and the corresponding reduction in throughput. - In one embodiment, a monitoring appliance can compile data returned in response to LS or Inquiry commands in defined structures (which may be, in one embodiment, XML structures or other structures). A structure may contain data associated with a library component returned in response to one or more commands (which may be, in one embodiment, LS or Inquiry commands). For example, a XML structure can include the amount of data received by (or sent from) a drive at a point in time from a LS command and the unique serial number of the drive determined from an Inquiry command issued to the drive. Such structures may be contained in a repository and compared such that data transfer rates can be determined for a drive. For example, a structure associated with a point in time may be compared with a structure associated with a subsequent point in time. The difference between the amount of data received by (or sent from) a drive can be determined through a comparison of the two structures and based on the difference in time between the two structures, an approximate data transfer rate for a point in time can be determined.
-
FIG. 5 is an XML representation of an example of data returned in response to a LS command. The data may include the amount of data received by a drive at a point in time. For example, MB read 510 is the amount of data received by a drive at a point in time. Data returned in response to LS commands sent at different times may include the amounts of data received by a drive at different times. The difference in the amounts of data received by a drive at two points in time may be divided by the duration between the two points in time to determine the data transfer rate at the drive at an approximate point in time. - Based on the determined data transfer rate at the drive, it can be ascertained whether the drive is being starved of data and whether and to what extent shoe-shining is occurring. Furthermore, because the data transfer rate is monitored over continuous intervals of time, data transfer rates over time can be stored (for example, in a repository), giving a user (virtual or otherwise) a relatively accurate data transfer rate history over time. For example, when the data transfer rate is determined over periodic 30 second intervals, the data transfer rate at the drive is up-to-date on at least a 30 second interval. Thus, the current data transfer rate may be presented to a user or a data transfer rate history may be presented to a user utilizing a user interface. In one embodiment, a graph of the data transfer rate over time may be presented to a user utilizing a user interface.
-
FIG. 6 is one example of a graphical user interface displaying agraphical representation 600 of the data transfer rate at a drive over time.Data transfer rate 610 is the data transfer rate of data received by a drive.Graphical representation 600 includes streaming rateindicator threshold line 620, which indicates the streaming level of the drive.Graphical representation 600 also includes ideal data transferrate indicator line 630, which indicates the ideal data transfer rate for the drive and maximum data transferrate indicator line 640, which indicates the maximum data transfer rate for the drive.Data transfer rate 610 can be compared withlines graphical representation 600. In one embodiment,data transfer rate 610 may graph the data transfer rate of data infused into a network by an infusion device at a known location. -
FIG. 7 is a diagrammatic representation of a monitoring appliance controller 700 (“controller 700”).Controller 700 can include aprocessor 702, such as anIntel Pentium 4 based processor (Intel and Pentium are trademarks of Intel Corporation of Santa Clara, Calif.), a primary memory 703 (which may be, for example, RAM, ROM, Flash Memory, EEPROM or other computer readable medium known in the art) and a secondary memory 704 (which may be, for example, a hard drive, disk drive, optical drive or other computer readable medium known in the art). Amemory controller 707 can control access tosecondary memory 704.Controller 700 can comprise a communications interface 706 (which may be, for example, fibre channel interface, Ethernet port or other communications interface known in the art) to connectcontroller 700 to a network (for example, network 110 ofFIG. 2 ). An I/O controller 712 can control interactions with the network. Similarly, an I/O controller 714 can control interactions over I/O interfaces 708 and 710.Controller 700 can include a variety of input devices. Various components ofcontroller 700 can be connected by abus 726. -
Secondary memory 704 can store a variety of computer instructions that include, for example, an operating system such as a Windows or Linux 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 asoftware program 730 that interfaces with devices (which may be, for example, drives or infusion devices) over a network and determines the data transfer rate at one or more drives. During execution byprocessor 702, portions ofprogram 730 can be stored insecondary memory 704 and/orprimary memory 703. - While systems and methods have 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 systems and methods disclosed above are described with regard to a physical library, further embodiments of systems and methods described above may be used in the context of virtual tape libraries, optical jukeboxes, archive systems such as MAID systems or other archive systems and other mass storage systems using a variety of storage media. 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.
Claims (6)
1. A computer program product comprising one or more non-transitory computer readable media embodying computer executable instructions implementing a method for network diagnosis, comprising:
sending a command to an infusion device to initiate infusing of control data by the infusion device;
periodically sending commands to a drive of a media library over the network while the control data is being transferred at the drive to collect data generated by the drive;
receiving responses to the commands from the drive, the responses specifying amounts of data; and
determining a measure of network performance for a portion of the network between the infusion device and drive based on the responses from the drive.
2. The computer program product of claim 1 , wherein the measure of network performance comprises an actual data transfer rate at the drive.
3. The computer program product of claim 2 , the method further comprising comparing the actual data transfer rate to a desired data transfer rate.
4. The computer program product of claim 2 , wherein the actual data transfer rate comprises a rate at which drive received the control data.
5. The computer program product of claim 2 , wherein the actual data transfer rate comprises a rate at which the drive wrote the control data.
6. The computer program product of claim 1 , wherein the commands sent to the drive comprise SCSI commands.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/000,888 US20160134507A1 (en) | 2008-02-04 | 2016-01-19 | System and method of network diagnosis |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/025,322 US7974215B1 (en) | 2008-02-04 | 2008-02-04 | System and method of network diagnosis |
US13/091,877 US8644185B2 (en) | 2008-02-04 | 2011-04-21 | System and method of network diagnosis |
US14/144,077 US9699056B2 (en) | 2008-02-04 | 2013-12-30 | System and method of network diagnosis |
US15/000,888 US20160134507A1 (en) | 2008-02-04 | 2016-01-19 | System and method of network diagnosis |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/144,077 Continuation US9699056B2 (en) | 2008-02-04 | 2013-12-30 | System and method of network diagnosis |
Publications (1)
Publication Number | Publication Date |
---|---|
US20160134507A1 true US20160134507A1 (en) | 2016-05-12 |
Family
ID=44202432
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/025,322 Expired - Fee Related US7974215B1 (en) | 2008-02-04 | 2008-02-04 | System and method of network diagnosis |
US13/091,877 Expired - Fee Related US8644185B2 (en) | 2008-02-04 | 2011-04-21 | System and method of network diagnosis |
US14/144,077 Expired - Fee Related US9699056B2 (en) | 2008-02-04 | 2013-12-30 | System and method of network diagnosis |
US15/000,888 Abandoned US20160134507A1 (en) | 2008-02-04 | 2016-01-19 | System and method of network diagnosis |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/025,322 Expired - Fee Related US7974215B1 (en) | 2008-02-04 | 2008-02-04 | System and method of network diagnosis |
US13/091,877 Expired - Fee Related US8644185B2 (en) | 2008-02-04 | 2011-04-21 | System and method of network diagnosis |
US14/144,077 Expired - Fee Related US9699056B2 (en) | 2008-02-04 | 2013-12-30 | System and method of network diagnosis |
Country Status (1)
Country | Link |
---|---|
US (4) | US7974215B1 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9501348B2 (en) | 2007-05-11 | 2016-11-22 | Kip Cr P1 Lp | Method and system for monitoring of library components |
US9699056B2 (en) | 2008-02-04 | 2017-07-04 | Kip Cr P1 Lp | System and method of network diagnosis |
US9866633B1 (en) | 2009-09-25 | 2018-01-09 | Kip Cr P1 Lp | System and method for eliminating performance impact of information collection from media drives |
US9864652B2 (en) | 2009-12-16 | 2018-01-09 | Kip Cr P1 Lp | System and method for archive verification according to policies |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8650241B2 (en) * | 2008-02-01 | 2014-02-11 | Kip Cr P1 Lp | System and method for identifying failing drives or media in media library |
US8645328B2 (en) * | 2008-02-04 | 2014-02-04 | Kip Cr P1 Lp | System and method for archive verification |
US9015005B1 (en) | 2008-02-04 | 2015-04-21 | Kip Cr P1 Lp | Determining, displaying, and using tape drive session information |
WO2014068352A2 (en) | 2012-10-31 | 2014-05-08 | Freescale Semiconductor, Inc. | Method and apparatus for driving a power transistor gate |
US10771369B2 (en) * | 2017-03-20 | 2020-09-08 | International Business Machines Corporation | Analyzing performance and capacity of a complex storage environment for predicting expected incident of resource exhaustion on a data path of interest by analyzing maximum values of resource usage over time |
US10445129B2 (en) * | 2017-10-31 | 2019-10-15 | Vmware, Inc. | Virtual computing instance transfer path selection |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040015755A1 (en) * | 2002-07-22 | 2004-01-22 | Finisar Corporation | Scalable scatter/gather I/O testing tool |
US20050091369A1 (en) * | 2003-10-23 | 2005-04-28 | Jones Michael D. | Method and apparatus for monitoring data storage devices |
US20060085595A1 (en) * | 2004-10-14 | 2006-04-20 | Slater Alastair M | Identifying performance affecting causes in a data storage system |
US8387054B1 (en) * | 2007-09-28 | 2013-02-26 | Symantec Corporation | Method and apparatus of scheduling data movers |
Family Cites Families (136)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US566800A (en) * | 1896-09-01 | Magnetic traction apparatus for motor-cars | ||
US3704363A (en) | 1971-06-09 | 1972-11-28 | Ibm | Statistical and environmental data logging system for data processing storage subsystem |
US3984923A (en) * | 1974-09-06 | 1976-10-12 | Searle Medidata, Inc. | System and process for preschool screening of children |
DE3405073A1 (en) * | 1984-02-13 | 1985-08-14 | Siemens AG, 1000 Berlin und 8000 München | STORAGE PROCESS FOR A STORAGE DEVICE USED IN TELECOMMUNICATION SYSTEMS, ESPECIALLY TELEPHONE SWITCHING SYSTEMS |
US4932826A (en) * | 1987-01-27 | 1990-06-12 | Storage Technology Corporation | Automated cartridge system |
US4899230A (en) | 1987-12-22 | 1990-02-06 | Idb Corporation | Taped data copying utilizing multiple addressable memories |
US4958235A (en) * | 1989-01-05 | 1990-09-18 | Appalachian Computer Services | System and method for rapidly conveying document images between distant locations |
US5004393A (en) | 1989-09-29 | 1991-04-02 | Storage Technology Corporation | Autoloader magazine for tape cartridges and method therefor |
US5253126A (en) | 1991-04-03 | 1993-10-12 | Archive Corporation | Raw error monitoring and reporting |
EP0511189B1 (en) * | 1991-04-26 | 1997-07-30 | MONSANTO p.l.c. | Automation of test instruments |
US5303214A (en) | 1992-01-03 | 1994-04-12 | International Business Machines Corporation | Multi-media-type automatic libraries |
US5386324A (en) * | 1993-07-30 | 1995-01-31 | International Business Machines Corporation | Apparatus and method for anticipated error recovery using debris profiles |
US5668800A (en) * | 1994-05-02 | 1997-09-16 | International Business Machines Corporation | Path testing in communications networks |
DE69522924T2 (en) * | 1994-10-11 | 2002-04-11 | Koninkl Philips Electronics Nv | METHOD AND ARRANGEMENT FOR TRANSMITTING AN INTERACTIVE AUDIOVISUAL PROGRAM |
JP3612375B2 (en) | 1995-02-13 | 2005-01-19 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Media library with internal media sort and media drive |
US5657443A (en) | 1995-05-16 | 1997-08-12 | Hewlett-Packard Company | Enhanced test system for an application-specific memory scheme |
US5781703A (en) | 1996-09-06 | 1998-07-14 | Candle Distributed Solutions, Inc. | Intelligent remote agent for computer performance monitoring |
US6453345B2 (en) * | 1996-11-06 | 2002-09-17 | Datadirect Networks, Inc. | Network security and surveillance system |
US5881221A (en) | 1996-12-31 | 1999-03-09 | Compaq Computer Corporation | Driver level diagnostics |
US5883864A (en) * | 1997-02-24 | 1999-03-16 | Quantum Corporation | Media library having locally vectored drive addressing |
US6272648B1 (en) * | 1997-05-13 | 2001-08-07 | Micron Electronics, Inc. | System for communicating a software-generated pulse waveform between two servers in a network |
US6058092A (en) | 1997-09-30 | 2000-05-02 | Compaq Computer Corporation | Optical tape drive that includes redundant optical heads to perform failure recovery |
IL121898A0 (en) * | 1997-10-07 | 1998-03-10 | Cidon Israel | A method and apparatus for active testing and fault allocation of communication networks |
US6304880B1 (en) * | 1997-12-12 | 2001-10-16 | International Business Machines Corporation | Automated reclamation scheduling override in a virtual tape server |
US6052341A (en) * | 1997-12-16 | 2000-04-18 | International Business Machines Corporation | Device element allocation manager and method for a multi-library system for multiple host connections |
US6052264A (en) * | 1997-12-18 | 2000-04-18 | International Business Machines Corporation | Method and apparatus for predicting capstan slip in tape drives utilizing belt-driven tape cartridges |
US6195663B1 (en) * | 1998-04-30 | 2001-02-27 | Zenith Electronics Corporation | Data server for high speed data transfer over an SCSI bus |
US6065087A (en) * | 1998-05-21 | 2000-05-16 | Hewlett-Packard Company | Architecture for a high-performance network/bus multiplexer interconnecting a network and a bus that transport data using multiple protocols |
JP3371396B2 (en) | 1998-09-24 | 2003-01-27 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Error recovery method and device |
RU2001117235A (en) * | 1998-11-24 | 2003-05-27 | Никсан | DEVICE AND METHOD FOR COLLECTING AND ANALYSIS OF COMMUNICATION DATA |
US6578083B2 (en) * | 1999-02-05 | 2003-06-10 | Pluris, Inc. | Method for monitoring data flow at a node on a network facilitating data transfer on at least one link having at least one class of service |
JP2001176036A (en) | 1999-12-10 | 2001-06-29 | Sony Corp | Magnetic tape drive device, and cleaning method of magnetic head |
US6636981B1 (en) | 2000-01-06 | 2003-10-21 | International Business Machines Corporation | Method and system for end-to-end problem determination and fault isolation for storage area networks |
US6654902B1 (en) | 2000-04-11 | 2003-11-25 | Hewlett-Packard Development Company, L.P. | Persistent reservation IO barriers |
US6624958B1 (en) | 2000-06-27 | 2003-09-23 | Hewlett-Packard Development Company, L.P. | Debris detection and error recovery method for tape drives |
JP4505110B2 (en) | 2000-06-28 | 2010-07-21 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Test method and apparatus for magnetic tape recording apparatus |
US6950871B1 (en) * | 2000-06-29 | 2005-09-27 | Hitachi, Ltd. | Computer system having a storage area network and method of handling data in the computer system |
US8032701B1 (en) | 2004-03-26 | 2011-10-04 | Emc Corporation | System and method for managing provisioning of storage resources in a network with virtualization of resources in such a network |
US6725394B1 (en) * | 2000-10-02 | 2004-04-20 | Quantum Corporation | Media library with failover capability |
US20030097439A1 (en) | 2000-10-23 | 2003-05-22 | Strayer William Timothy | Systems and methods for identifying anomalies in network data streams |
JP4328459B2 (en) * | 2000-10-27 | 2009-09-09 | Necエンジニアリング株式会社 | Network service quality measurement system and method |
US6490253B1 (en) * | 2000-11-22 | 2002-12-03 | Seagate Technology Llc | Peer to peer interconnect diagnostics |
US6854071B2 (en) | 2001-05-14 | 2005-02-08 | International Business Machines Corporation | Method and apparatus for providing write recovery of faulty data in a non-redundant raid system |
US7075874B2 (en) | 2001-07-17 | 2006-07-11 | Hewlett-Packard Development Company, L.P. | Data storage device monitoring system, method and removable data carrier use with data storage systems |
US6813698B2 (en) * | 2001-10-05 | 2004-11-02 | International Business Machines Corporation | Concurrent configuration of drives of a data storage library |
US7958199B2 (en) | 2001-11-02 | 2011-06-07 | Oracle America, Inc. | Switching systems and methods for storage management in digital networks |
US6839824B2 (en) * | 2001-12-28 | 2005-01-04 | Hewlett-Packard Development Company, L.P. | System and method for partitioning a storage area network associated data library employing element addresses |
US6715031B2 (en) * | 2001-12-28 | 2004-03-30 | Hewlett-Packard Development Company, L.P. | System and method for partitioning a storage area network associated data library |
US7064913B2 (en) | 2002-01-09 | 2006-06-20 | Quantum Corporation | Enhanced read margining using dither enhanced write marginalization for mass data storage applications |
US6799156B1 (en) * | 2002-04-26 | 2004-09-28 | Unisys Corporation | Method and design for a DVD SCSI tape controller |
US7149800B2 (en) * | 2002-05-29 | 2006-12-12 | Seventh Knight | Auditing computer systems components in a network |
US7194538B1 (en) | 2002-06-04 | 2007-03-20 | Veritas Operating Corporation | Storage area network (SAN) management system for discovering SAN components using a SAN management server |
US8549114B2 (en) * | 2002-06-12 | 2013-10-01 | Bladelogic, Inc. | Method and system for model-based heterogeneous server configuration management |
US7120728B2 (en) | 2002-07-31 | 2006-10-10 | Brocade Communications Systems, Inc. | Hardware-based translating virtualization switch |
US7363546B2 (en) | 2002-07-31 | 2008-04-22 | Sun Microsystems, Inc. | Latent fault detector |
US20040022263A1 (en) * | 2002-08-02 | 2004-02-05 | Xiaodong Zhao | Cross point switch with out-of-band parameter fine tuning |
US7200546B1 (en) | 2002-09-05 | 2007-04-03 | Ultera Systems, Inc. | Tape storage emulator |
US7076391B1 (en) * | 2002-10-31 | 2006-07-11 | Western Digital Technologies, Inc. | Methods and systems for asynchronously testing a plurality of disk drives |
US7263596B1 (en) | 2002-12-17 | 2007-08-28 | Advanced Digital Information Corporation | Logical library architecture for data storage applications and methods of use |
US7275103B1 (en) | 2002-12-18 | 2007-09-25 | Veritas Operating Corporation | Storage path optimization for SANs |
JP3776884B2 (en) * | 2002-12-27 | 2006-05-17 | 株式会社東芝 | Recording / reproduction control apparatus suitable for verification of erasure correction function, recording / reproduction apparatus equipped with the same, and method for verifying erasure correction function |
US6971046B1 (en) * | 2002-12-27 | 2005-11-29 | Unisys Corporation | System and method for performing input/output diagnostics |
US6816917B2 (en) | 2003-01-15 | 2004-11-09 | Hewlett-Packard Development Company, L.P. | Storage system with LUN virtualization |
US6823401B2 (en) * | 2003-01-15 | 2004-11-23 | Hewlett-Packard Development Company, L.P. | Monitor for obtaining device state by intelligent sampling |
FR2851707B1 (en) * | 2003-02-21 | 2005-06-24 | Cit Alcatel | QUALITY OF SERVICE PARAMETER MEASUREMENT PROBE FOR A TELECOMMUNICATION NETWORK |
US7277246B2 (en) | 2003-07-18 | 2007-10-02 | Quantum Corporation | Methods and systems for providing predictive maintenance, preventative maintenance, and/or failure isolation in a tape storage subsystem |
US7676445B2 (en) * | 2003-08-20 | 2010-03-09 | International Business Machines Corporation | Apparatus, system and method for developing failure prediction software |
JP2005108098A (en) * | 2003-10-01 | 2005-04-21 | Hitachi Ltd | Data i/o device and control method of data i/o device |
US7286967B2 (en) | 2003-10-20 | 2007-10-23 | Hewlett-Packard Development Company, L.P. | Retrieving performance data from devices in a storage area network |
GB2424297B (en) * | 2003-11-13 | 2007-06-27 | Commvault Systems Inc | System and method for data storage and tracking |
US7613748B2 (en) * | 2003-11-13 | 2009-11-03 | Commvault Systems, Inc. | Stored data reverification management system and method |
US7440982B2 (en) * | 2003-11-13 | 2008-10-21 | Commvault Systems, Inc. | System and method for stored data archive verification |
KR101086397B1 (en) * | 2003-12-02 | 2011-11-23 | 삼성전자주식회사 | IP packet error handling apparatus and method using the same, and computer readable medium on which program executing the method is recorded |
US8244903B2 (en) * | 2003-12-22 | 2012-08-14 | Emc Corporation | Data streaming and backup systems having multiple concurrent read threads for improved small file performance |
US20050210161A1 (en) * | 2004-03-16 | 2005-09-22 | Jean-Pierre Guignard | Computer device with mass storage peripheral (s) which is/are monitored during operation |
TWI258661B (en) | 2004-03-30 | 2006-07-21 | Infortrend Technology Inc | Efficient media scan operations for storage systems |
US20050231846A1 (en) * | 2004-04-14 | 2005-10-20 | International Business Machines Corporation | Write-once read-many hard disk drive using a WORM pointer |
US20050246509A1 (en) | 2004-04-28 | 2005-11-03 | Andrew Topham | Tape drive apparatus, method and computer program product |
US7596096B2 (en) * | 2004-04-29 | 2009-09-29 | Avaya Inc | Method and apparatus for providing trace route and timing information for media streams |
US7278067B1 (en) | 2004-04-30 | 2007-10-02 | Network Appliance, Inc. | Method and an apparatus for aggressively detecting media errors on storage devices with negligible performance impact |
US7898969B2 (en) * | 2004-05-07 | 2011-03-01 | France Telecom | Performance measurement in a packet transmission network |
FR2870064A1 (en) * | 2004-05-07 | 2005-11-11 | France Telecom | PERFORMANCE MEASUREMENT IN A PACKET TRANSMISSION NETWORK |
US7353454B2 (en) * | 2004-05-21 | 2008-04-01 | International Business Machines Corporation | Web based device management and monitoring interface |
US7200722B2 (en) | 2004-05-24 | 2007-04-03 | International Business Machines Corporation | Reducing inventory after media access in an automated data storage library |
US7483810B2 (en) * | 2004-06-29 | 2009-01-27 | Honeywell International Inc. | Real time event logging system |
US7443801B2 (en) * | 2004-10-28 | 2008-10-28 | Telcordia Technologies, Inc. | Remote estimation of round-trip delays in a data network |
US7573664B2 (en) | 2004-12-03 | 2009-08-11 | International Business Machines Corporation | Integrated multiple channel data reliability testing for a magnetic tape drive |
JP2006164445A (en) * | 2004-12-09 | 2006-06-22 | Fujitsu Ltd | Monitoring device |
GB2422475A (en) * | 2005-01-21 | 2006-07-26 | Hewlett Packard Development Co | Tape error log identifiying location of errors |
US20060168499A1 (en) | 2005-01-27 | 2006-07-27 | Edwards Jathan D | Data archive verify software |
US7971006B2 (en) | 2005-01-28 | 2011-06-28 | Crossroads Systems, Inc. | System and method for handling status commands directed to partitioned media library |
US7451291B2 (en) | 2005-01-28 | 2008-11-11 | Crossroads Systems, Inc. | System and method for mode select handling for a partitioned media library |
US8046187B2 (en) | 2005-02-24 | 2011-10-25 | International Business Machines Corporation | Test systems for media drives of data storage systems |
US7484040B2 (en) | 2005-05-10 | 2009-01-27 | International Business Machines Corporation | Highly available removable media storage network environment |
EP1913506A4 (en) | 2005-07-11 | 2008-08-13 | Brooks Automation Inc | Intelligent condition monitoring and fault diagnostic system for predictive maintenance |
US7206156B2 (en) | 2005-07-27 | 2007-04-17 | Hewlett-Packard Development Company, L.P. | Tape drive error management |
US7539786B2 (en) | 2005-08-17 | 2009-05-26 | International Business Machines Corporation | Method for simulating cartridge changes in import/export station slots in an automated data storage library |
US7523289B2 (en) * | 2005-09-30 | 2009-04-21 | Spectra Logic Corporation | Random access storage system capable of performing storage operations intended for alternative storage devices |
US7386667B2 (en) | 2005-11-09 | 2008-06-10 | International Business Machines Corporation | Storing information regarding operation of an automated data storage library to memory and to a reserved cartridge |
US7421551B2 (en) | 2006-02-03 | 2008-09-02 | Emc Corporation | Fast verification of computer backup data |
JP4755510B2 (en) | 2006-03-10 | 2011-08-24 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Data recording apparatus and method for evaluating performance of host data transfer of data recording apparatus |
US8438346B2 (en) * | 2006-04-27 | 2013-05-07 | Hewlett-Packard Development Company, L.P. | Synchronization of a virtual storage system and an actual storage system |
US7890813B2 (en) | 2006-05-11 | 2011-02-15 | Oracle America, Inc. | Method and apparatus for identifying a failure mechanism for a component in a computer system |
US7627786B2 (en) | 2006-09-26 | 2009-12-01 | International Business Machines Corporation | Tracking error events relating to data storage drives and/or media of automated data storage library subsystems |
US8041807B2 (en) | 2006-11-02 | 2011-10-18 | International Business Machines Corporation | Method, system and program product for determining a number of concurrent users accessing a system |
JP2008123414A (en) | 2006-11-15 | 2008-05-29 | Hitachi Ltd | Storage managing device, computer system and storage managing method |
US8035911B2 (en) * | 2007-02-15 | 2011-10-11 | Hewlett-Packard Development Company, L.P. | Cartridge drive diagnostic tools |
US7653840B1 (en) | 2007-04-27 | 2010-01-26 | Net App, Inc. | Evaluating and repairing errors during servicing of storage devices |
US8832495B2 (en) | 2007-05-11 | 2014-09-09 | Kip Cr P1 Lp | Method and system for non-intrusive monitoring of library components |
US8024426B2 (en) | 2007-05-11 | 2011-09-20 | Texas Memory Systems, Inc. | Non-disruptive data path upgrade using target mobility |
US7870427B2 (en) * | 2007-08-10 | 2011-01-11 | International Business Machines Corporation | Accessing removable storage management services to obtain replacement instructions indicating whether to replace removable storage |
US8009539B2 (en) * | 2007-08-27 | 2011-08-30 | International Business Machines Corporation | Monitoring and analyzing the storage quality and the drive hardware performance of a media library |
US7885805B2 (en) * | 2007-09-12 | 2011-02-08 | International Business Machines Corporation | Apparatus, system, and method for simulating multiple hosts |
US8145572B2 (en) * | 2007-10-19 | 2012-03-27 | Kabushiki Kaisha Toshiba | Information processing apparatus, content processing method, and computer program product thereof |
US9349410B2 (en) | 2008-01-08 | 2016-05-24 | International Business Machines Corporation | Automated data storage library with target of opportunity recognition |
US7908366B2 (en) | 2008-02-01 | 2011-03-15 | Crossroads Systems, Inc. | Media library monitoring system and method |
JP2009181536A (en) * | 2008-02-01 | 2009-08-13 | Dainippon Screen Mfg Co Ltd | Software fault management device, test management device and program therefor |
US8650241B2 (en) | 2008-02-01 | 2014-02-11 | Kip Cr P1 Lp | System and method for identifying failing drives or media in media library |
US7974215B1 (en) | 2008-02-04 | 2011-07-05 | Crossroads Systems, Inc. | System and method of network diagnosis |
US9015005B1 (en) | 2008-02-04 | 2015-04-21 | Kip Cr P1 Lp | Determining, displaying, and using tape drive session information |
US8645328B2 (en) | 2008-02-04 | 2014-02-04 | Kip Cr P1 Lp | System and method for archive verification |
US8195986B2 (en) * | 2008-02-25 | 2012-06-05 | International Business Machines Corporation | Method, system and computer program product for processing error information in a system |
US8370466B2 (en) | 2008-07-23 | 2013-02-05 | International Business Machines Corporation | Method and system for providing operator guidance in network and systems management |
US8000052B2 (en) * | 2008-08-11 | 2011-08-16 | International Business Machines Corporation | Cartridge refresh and verify |
US7874215B2 (en) * | 2008-09-29 | 2011-01-25 | General Electric Company | Accelerometer including diaphragm and power generator and motor including same |
US20100125740A1 (en) | 2008-11-19 | 2010-05-20 | Accenture Global Services Gmbh | System for securing multithreaded server applications |
US8108544B2 (en) * | 2008-12-10 | 2012-01-31 | At&T Intellectual Property I, Lp | System and method for content validation |
US20100174878A1 (en) | 2009-01-06 | 2010-07-08 | Crawford Communications | Systems and Methods for Monitoring Archive Storage Condition and Preventing the Loss of Archived Data |
JP4734663B2 (en) | 2009-01-23 | 2011-07-27 | 富士通株式会社 | Virtual library apparatus and physical drive diagnosis method |
US8180824B2 (en) * | 2009-02-23 | 2012-05-15 | Trane International, Inc. | Log collection data harvester for use in a building automation system |
US8255476B2 (en) | 2009-03-30 | 2012-08-28 | International Business Machines Corporation | Automated tape drive sharing in a heterogeneous server and application environment |
US20100275219A1 (en) | 2009-04-23 | 2010-10-28 | International Business Machines Corporation | Scsi persistent reserve management |
US8099624B1 (en) | 2009-09-10 | 2012-01-17 | Network Appliance, Inc. | Recovery mechanism for I/O module using out-of-band control path |
US8230255B2 (en) | 2009-12-15 | 2012-07-24 | International Business Machines Corporation | Blocking write acces to memory modules of a solid state drive |
US8843787B1 (en) | 2009-12-16 | 2014-09-23 | Kip Cr P1 Lp | System and method for archive verification according to policies |
US8839446B2 (en) | 2011-09-12 | 2014-09-16 | Microsoft Corporation | Protecting archive structure with directory verifiers |
-
2008
- 2008-02-04 US US12/025,322 patent/US7974215B1/en not_active Expired - Fee Related
-
2011
- 2011-04-21 US US13/091,877 patent/US8644185B2/en not_active Expired - Fee Related
-
2013
- 2013-12-30 US US14/144,077 patent/US9699056B2/en not_active Expired - Fee Related
-
2016
- 2016-01-19 US US15/000,888 patent/US20160134507A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040015755A1 (en) * | 2002-07-22 | 2004-01-22 | Finisar Corporation | Scalable scatter/gather I/O testing tool |
US20050091369A1 (en) * | 2003-10-23 | 2005-04-28 | Jones Michael D. | Method and apparatus for monitoring data storage devices |
US20060085595A1 (en) * | 2004-10-14 | 2006-04-20 | Slater Alastair M | Identifying performance affecting causes in a data storage system |
US8387054B1 (en) * | 2007-09-28 | 2013-02-26 | Symantec Corporation | Method and apparatus of scheduling data movers |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9501348B2 (en) | 2007-05-11 | 2016-11-22 | Kip Cr P1 Lp | Method and system for monitoring of library components |
US9699056B2 (en) | 2008-02-04 | 2017-07-04 | Kip Cr P1 Lp | System and method of network diagnosis |
US9866633B1 (en) | 2009-09-25 | 2018-01-09 | Kip Cr P1 Lp | System and method for eliminating performance impact of information collection from media drives |
US9864652B2 (en) | 2009-12-16 | 2018-01-09 | Kip Cr P1 Lp | System and method for archive verification according to policies |
Also Published As
Publication number | Publication date |
---|---|
US9699056B2 (en) | 2017-07-04 |
US7974215B1 (en) | 2011-07-05 |
US8644185B2 (en) | 2014-02-04 |
US20140112185A1 (en) | 2014-04-24 |
US20110194451A1 (en) | 2011-08-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9699056B2 (en) | System and method of network diagnosis | |
US9092138B2 (en) | Media library monitoring system and method | |
US9501348B2 (en) | Method and system for monitoring of library components | |
US9317358B2 (en) | System and method for archive verification according to policies | |
US7908366B2 (en) | Media library monitoring system and method | |
US8645328B2 (en) | System and method for archive verification | |
US20110191644A1 (en) | Method and apparatus for SAS speed adjustment | |
US9015005B1 (en) | Determining, displaying, and using tape drive session information | |
KR20120052158A (en) | A method for deterministic sas discovery and configuration | |
US11137918B1 (en) | Administration of control information in a storage system | |
US7073025B2 (en) | Disk array apparatus and control method for the same | |
US8161316B1 (en) | Managing loop interface instability | |
US8090881B1 (en) | Method and system for minimizing unnecessary topology discovery operations by managing physical layer state change notifications in storage systems | |
US9866633B1 (en) | System and method for eliminating performance impact of information collection from media drives |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CROSSROADS SYSTEMS, INC., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SIMS, ROBERT C.;REEL/FRAME:037526/0358 Effective date: 20080310 Owner name: KIP CR P1 LP, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CROSSROADS SYSTEMS, INC.;REEL/FRAME:037526/0363 Effective date: 20130722 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |