Systems and methods for allocating control of storage media in a network environment

Information

  • Patent Grant
  • 7827363
  • Patent Number
    7,827,363
  • Date Filed
    Tuesday, July 22, 2008
    16 years ago
  • Date Issued
    Tuesday, November 2, 2010
    14 years ago
Abstract
A method for dynamically allocating control of a storage device, the method comprising receiving an access request from a first computer requesting access to a storage device; directing, based upon the access request, a first storage controller computer to assume an inactive state with respect to control of the storage device; and directing, based upon the access request, a second storage controller computer to assume an active state with respect to control of the storage device.
Description
COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosures, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever.


BACKGROUND OF THE INVENTION

The invention disclosed herein relates generally to data storage systems in computer networks and, more particularly, to improvements to storage systems which provide dynamic reallocation of storage device control.


There are many different computing architectures for storing electronic data. Individual computers typically store electronic data in volatile storage devices such as Random Access Memory (RAM) and one or more nonvolatile storage devices such as hard drives, tape drives, or optical disks, that form a part of or are directly connectable to the individual computer. In a network of computers such as a Local Area Network (LAN) or a Wide Area Network (WAN), storage of electronic data is typically accomplished via servers or stand-alone storage devices accessible via the network. These individual network storage devices may be networkable tape drives, optical libraries, Redundant Arrays of Inexpensive Disks (RAID), CD-ROM jukeboxes, and other devices. Common architectures include drive pools which serve as logical collections of storage drives with associated media groups which are the tapes or other storage media used by a given drive pool.


Stand-alone storage devices are connected to individual computers or a network of computers via serial, parallel, Small Computer System Interface (SCSI), or other cables. Each individual computer on the network controls the storage devices that are physically attached to that computer and may also access the storage devices of the other network computers to perform backups, transaction processing, file sharing, and other storage-related applications.


Network Attached Storage (NAS) is another storage architecture using stand-alone storage devices in a LAN or other such network. In NAS, a storage controller computer owns or controls a particular stand-alone storage device to the exclusion of other computers on the network, but the SCSI or other cabling directly connecting that storage device to the individual controller or owner computer is eliminated. Instead, storage devices are directly attached to the network itself.


A common feature shared by many or all existing network architectures is the static relationship between storage controller computers and storage devices. In existing network architectures, storage devices can each only be connected, virtually or physically, to a single storage controller computer. Only the storage controller computer to which a particular device is physically connected has read/write access to that device. A drive pool and its associated media group, for example, can only be controlled by the computer to which it is directly connected. Therefore, all backup from other storage controller computers needs to be sent via the network before it can be stored on the storage device connected to the first storage controller computer.


One problem associated with these storage architectures relates to overloading network traffic during certain operations associated with use of storage devices on the network. Network cables have a limited amount of bandwidth that must be shared among all the computers on the network. The capacity of most LAN or network cabling is measured in megabits per second (mbps), with 10 mbps and 100 mbps currently being standard. During common operations such as system backups, transaction processing, file copies, and other similar operations, network traffic often becomes overloaded as hundreds of megabytes (MB) and gigabytes (GB) of information are sent over the network to the associated storage devices. The capacity of the network computers to stream data over the network to the associated storage devices in this manner is greater than the bandwidth capacity of the cabling itself, thus substantially slowing ordinary network and storage activity and communications.


A Storage Area Network (SAN) is a network architecture designed to facilitate transport of electronic data and address this bandwidth issue. SAN architecture requires at least two networks. First, a traditional network described above such as a LAN transports ordinary traffic between networked computers. A SAN serves as a second network that is attached to the servers of the first network. The SAN is generally a separate network reserved for bandwidth-intensive operations such as backups, transaction processing, and the like. The cabling used in the SAN is usually of much higher bandwidth capacity than that used in the first network such as the LAN, and the communication protocols used over the SAN cabling are optimized for bandwidth-intensive traffic. The storage devices used by the networked computers for the bandwidth-intensive operations are attached to the SAN rather than the LAN. Thus, when the bandwidth-intensive operations are required, they take place over the SAN and the LAN remains unaffected.


Even with a SAN, however, the static relationship between individual storage controller computers and individual storage devices or drive pools causes bandwidth difficulties during data storage or retrieval operations. Under the current architectures, when a storage device is assigned to a storage controller computer, that storage controller computer owns and controls the device indefinitely and to the exclusion of other computers on the network. Thus, one computer on a network cannot control the drive pool and media group being controlled by another, and requests to store and retrieve data from such a drive pool and media group would have to first pass through the controlling computer. This relationship between storage controller computer and storage device continues to lead to bandwidth difficulties.


In addition, the current architectures result in inefficient use of resources and the need for extra storage devices or pools beyond the actual storage needs of the network. As an illustrative example, if each storage controller computer needs access to two storage devices and there are five storage controller computers in the network, then a total of ten storage devices will be required. The actual amount of work each of the ten storage devices performs might be much less than the workload capacity of each storage device.


There is thus a need for a method and system which addresses this inefficiency and the associated continued bandwidth problems.


SUMMARY OF THE INVENTION

The present invention addresses the problems discussed above, and includes a method for dynamically reallocating control of a storage device accessible via a computerized network. The method involves directing a first computer controlling the storage device to assume an inactive state with respect to the storage device and directing a second computer to assume an active state of control with respect to the storage device. The second computer may be selected to assume an active state of control based on a priority of a storage operation to be performed, on a manual selection of a user, or any other desired criteria. The method further involves storing control data indicating a change in control of the storage device. In accordance with some embodiments, the first computer demounts the storage device in response to the direction to assume an inactive state, and the second computer mounts the storage device in response to the direction to assume an active state.


In some embodiments, the first computer is identified as being in a state of control with respect to the storage device prior to sending direction to the first computer to assume an inactive state. This may be accomplished by retrieving previously stored control data with respect to the storage device which identifies the first computer as being in control. In accordance with some embodiments, if state data is received indicating unavailability of the second computer, a third computer is directed to assume an active state of control with respect to the storage device in lieu of the second computer.


In accordance with some embodiments, the second computer generates path data representing a network access path to the storage device. This path data is passed to a computer program requesting access to the storage device, and may further be stored in a database entry with the control data corresponding to the storage device.


The present invention further includes a system for managing a storage system comprising a plurality of storage devices which may be single drives or drive pools or a mix thereof. The system includes a plurality of storage controllers each capable of controlling the storage devices and a storage manager configured to receive a request to access a first storage device in the storage system and to send directions to activate one of the storage controllers with respect to the first storage device and deactivate other storage controllers with respect to the storage device. The system further includes a database stored in memory accessible to the storage manager for storing control data indicating a state of control over the first storage device.


In some embodiments, the storage controllers are capable of generating path data with respect to the first storage device and sending the path data to the storage manager. The database stores the path data received from the storage controller, and the storage manager passes the path data to a computer requesting access to the first storage device.


The present invention further includes methods and systems operating in conjunction with a SAN and a modular storage system to enable computers on a network to share storage devices on a physical and logical level. An exemplary modular storage system is the GALAXY backup and retrieval system available from CommVault Systems of New Jersey. The modular architecture underlying this system is described in the above referenced patent applications, incorporated herein. Each media agent or storage controller computer contains device management software (DMS) which can control storage devices on the network by communicating instructions from the media agent or storage controller computer to the storage devices. Dynamic device pooling can be achieved by controlling which DMS instance “owns” a storage device at a particular time. Although in a given network, there may be multiple DMS instances running on many MediaAgents or storage controller computers that are able to control a particular storage device, only one of those DMS instances is “active” with respect to a particular storage device and can control that device at any time. Accordingly, if a storage controller computer controlled a particular drive pool and media group, that computer could not directly store and retrieve data from drive pools and media groups controlled by other storage controller computers in a network. The CommServer or storage manager computer monitors and instructs the MediaAgents or storage controller computers regarding which MediaAgent's DMS controls a particular storage device at a given time.


In some embodiments, the CommServer or storage manager computer allocates control of a particular storage device by a MediaAgent or storage controller computer's DMS based on the priority of the storage operation to be performed.


In some embodiments, the storage administrator or user may also manually assign control of a particular storage device or devices to a MediaAgent or storage controller computer's DMS.


In some embodiments, the SAN may be a high-speed network topology with optimized storage transport protocols such the CommVault DataPipe™ described above.


In some embodiments, error recovery protocols exist such that if a particular storage controller computer or storage controller computer's DMS is unavailable, then the storage manager computer assigns control of a particular storage device to a different storage controller computer. Such reassignment by the storage manager computer creates a more fault-tolerant storage architecture and ensures that the malfunctioning or lack of availability of a particular storage controller computer or storage controller computer's DMS does not affect the other storage controller computers and their DMSs.


In some embodiments, an access path or logical network route to a particular storage device when that storage device is switched is obtained by the storage manager computer from the DMS currently in control of that storage device. The access path to a particular storage device is used by storage controller computers and their DMSs to contact that device and issue instructions regarding storage procedures. Obtaining the access path to the storage device from the DMS currently in control of the storage device in this manner is error free against any hardware changes to the storage controller computer or MediaAgent on which the DMS is running. Any hardware changes on a storage controller computer will involve reconfiguration of the storage controller computer and that DMS will either manually or automatically detect and reflect these changes. Storing the access paths to storage devices on the storage manager computer would be error prone in cases where the storage manager computer was unaware of changes made to storage controller computers and the resultant change in access paths to any affected storage devices.


In some embodiments, the access paths to storage devices could also be stored in a database or other data structure on the storage manager computer instead of being stored on the storage controller computers. Those skilled in the art will recognize that the DMS of the storage controller computer for a particular storage resource could either manually or automatically detect any hardware changes or other changes that would affect the access path to that storage resource and inform the storage manager computer of these changes. The storage manager computer would then update its record of the access path to that particular storage device.





BRIEF DESCRIPTION OF THE DRAWINGS

The invention is illustrated in the figures of the accompanying drawings which are meant to be exemplary and not limiting, in which like references are intended to refer to like or corresponding parts, and in which:



FIG. 1 is block diagram showing a high-level view of the network architecture and components of one possible embodiment of the invention; and



FIG. 2 is a block diagram showing the SAN-related components of a simplified embodiment of the invention; and



FIG. 3 is a block diagram showing an abstracted or logical view of two DMS's relationship to a given storage device in one possible embodiment of the invention; and



FIG. 4 is a flow diagram presenting a method to achieve dynamic device pooling in one embodiment of the present invention.





DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Preferred embodiments of the invention are now described with reference to the drawings. An embodiment of the system of the present invention is shown in FIG. 1. As shown, the system includes a Local Area Network 100 and a Storage Area Network 105. The LAN will typically use 10/100 mbps Ethernet or other similar cable and communicate using TCP/IP. The SAN will typically use higher-bandwidth cabling such as a fiber channel and will use a different network communication protocol such as SCSI-3, CommVault Systems' DataPipe™, or other similar protocol optimized for network storage and retrieval of electronic data.


Network clients 110 are connected to the LAN 100 and in some embodiments also connected to the SAN 105. These network clients 110 contain the electronic data that the will travel over the network and be stored on or retrieved from the storage devices 115 attached to the SAN 105. The storage devices 115 may be tape drives, optical libraries, RAID, CD-ROM jukeboxes, or other storage devices known in the art.


A storage manager computer 120 is connected to both the LAN 100 and the SAN 105. Storage Management Software (SMS) 125 designed to direct the high level operations of the invention also resides on the storage manager computer 120. This storage management software 125 communicates with storage controller computers 130 and manages which Device Management Software 135 instance on which storage controller computer 130 shall control or own a particular storage device 115 at a given instance.



FIG. 2 shows a more detailed view of the SAN-related components of the invention. The SAN 205 is the primary pathway for transport of electronic data to and from client computers 210, one of which is shown, and storage devices 215, one of which is shown. In this embodiment, the client computer 210 is connected to the SAN, but those skilled in the art will recognize that the client computer 210 could also be connected only to a LAN, WAN, or other type of computer network with minimal reconfiguration of the invention.


When the client computer 210 needs to transfer or retrieve electronic data from a storage device 215 on the SAN 205, a request to access the storage device 215 is passed from the client computer 210 to the storage controller computer 240, 255. The storage controller computer 240, 255 then contacts the storage manager computer 220 to request access to the storage device 215 requested by the client computer 210. Alternatively, in some embodiments the client computer 210 may directly communicate the access request to the storage manager computer 220. The storage manager computer 220 contains Storage Management Software 225 which controls the overall flow of operations pertaining to storage and retrieval of electronic data from storage devices on the SAN to which the storage manager computer is connected.


The storage manager computer 220 also has a database 230, table, or other data structure which contains information useful in managing the flow of electronic information to and from the various storage devices 215 on the SAN 205. In this embodiment, for example, there is a first storage controller computer 240 and a second storage controller computer 255. The storage manager computer 220 storage management database 230 contains information detailing which storage controller computer 240/255 controls a storage device 215 at a given instance. The storage management database 230 also contains information regarding the logical network pathway or access route to each storage device 215 on the SAN 205.


The first storage controller computer 240 contains a DMS instance 245 and a related storage controller database 250, table or other data structure containing useful information regarding the first storage controller computer 240 and any storage device 215 which it controls. The second storage controller computer 255 contains a Device Management Software instance 260 and a related storage controller database 265, table or other data structure containing useful information regarding the second storage controller computer 255 and any storage device 215 which it controls. Information stored in the storage controller databases 250 and 265 of the first storage controller computer 240 and the second storage controller computer 255 respectively, includes the network pathways to the storage device 215 being controlled and whether the respective DMS instance 245 and 260 is active or deactivated with respect to control of any given storage device 215.



FIG. 3 shows an abstracted or logical view of the relationship between two DMSs and a given storage device. In this simplified view, there is a first storage controller computer 325 with a DMS instance 330 and a second storage controller computer 335 with a DMS instance 340. When a client computer 305 needs to transfer or retrieve electronic data from a storage device 310, the client computer 305 first communicates this request with a storage controller software instance 330, 340 located on a storage controller computer 325, 335. The client computer 305 decides which storage controller computer 325, 335 to contact based on the type of data that is being stored or retrieved. Data is associated with a particular storage controller computer 325, 335 when the system is configured. All future requests pertaining to storage and retrieval of that data are then passed from the client computer 305 to the appropriate storage controller computer 330, 340. The storage manager computer 320 directs the high-level operations of the invention with respect to electronic information storage and retrieval procedures. As previously discussed, in some embodiments, the client computers 305 directly communicate access requests to the storage manager computer 320.


Since only one DMS can control the storage device 310 at any given time, the storage manager software 315 directs which DMS instance 330, 340 is in control of the storage device 310 at any given time. If the first DMS 330 is in control of the storage device 310, then the SMS 315 deactivates the second DMS 340 with respect to control of the storage device 310. Conversely, if the second DMS 340 is in control of the storage device 310, then the SMS 315 deactivates the first DMS 330 with respect to control of the storage device 310. Regardless of the actual physical connections described in FIG. 1 and FIG. 2, the storage device 310 is logically connected to and controlled by both the first DMS instance 330 and the second DMS instance 340 as if the storage device 310 were a mere external storage device directly connected to a storage controller computer in a traditional LAN storage architecture. This process if more fully explained below according to the flow diagram depicted in FIG. 4.



FIG. 4 is a flow diagram showing how dynamic device pooling is accomplished in one embodiment of the invention. A client application initiates a request to the storage controller software to store or retrieve electronic data from a storage device on the network and the storage controller software passes this request to the storage manager software by requesting access to a storage device, step 405. When the client computer is configured, data that is to be stored and retrieved is associated with a particular storage controller computer software instance. When that data must be stored or retrieved in the future, the client computer passes these requests on to the storage controller computer. The storage controller computer associates that data with a particular media group which is a collection of tapes or other storage media used by a drive pool. Using dynamic device sharing, the storage controller computer can store and retrieve data among multiple tapes in a media group spanning multiple drive pools if necessary.


When the client application request is received from the storage controller software, the SMS first verifies that a storage device is available that can be switched to accommodate the request, step 410. The SMS maintains a storage management database, table, or other data structure populated with information about the available storage devices and their respective storage controller computers. Access paths across the network to storage controller computers and then on to their appurtenant storage devices are also stored in this database.


Upon identifying an appropriate storage device, the SMS directs the DMS currently controlling the storage device to go into a deactivated state with respect to that storage device, step 415. Even though there are multiple DMSs executing on various hosts for the same storage device, the relationship is static and only one of them can control a storage device at a given instant. The other DMSs are said to be in a deactivated state with respect to that storage device.


The deactivated DMSs run a listening process waiting for a message from the SMS directing them to become active. Once the first DMS has been deactivated with respect to the storage device, the SMS communicates with the listening process of a second DMS on which the storage device will be mounted to change from a deactivated state to an activated state with respect to that storage device, step 420. At this point, the SMS also updates its storage management database to reflect that control of the storage device has been shifted from the first DMS to the second DMS and that the first DMS is now deactivated and that the second DMS is now activated with respect to that storage device, step 425.


The second DMS communicates with the storage device and executes procedures necessary to mount the storage device to the second DMS, step 430. Once the mount is performed, the storage device is logically connected to the second DMS computer and this access path is stored by the second DMS in its storage controller database, step 435. The DMS stores the access path to the storage device in its storage controller database because a storage device connected to multiple DMS storage controller computers may have multiple access paths. Mounting the storage device to the DMS computer and the resultant access path produced is in large part related to the hardware configuration of the DMS. The DMS is best-suited to store and delegate management of the access path to the storage device it controls. The alternative is to have the storage management computer store and track the individual hardware configurations of all the network DMS computers in the SMS storage management database and then pass the resultant access paths to the network storage devices on to the DMS computers when necessary.


Once the DMS has completed the mount of the storage device and stored the access path to the storage device in its own storage controller database, then the access path to the storage device is returned by the DMS to the SMS where it is also stored in the storage management database of the SMS for future recall, step 440. While a DMS communicates with storage devices, the SMS communicates with client applications. The SMS now returns this storage device access path to the client application that initially requested access to the storage device, step 445. The client application is then free to initiate storage or retrieval as appropriate, step 450.


Systems and modules described herein may comprise software, firmware, hardware, or any combination(s) of software, firmware, or hardware suitable for the purposes described herein. Software and other modules may reside on servers, workstations, personal computers, computerized tablets, PDAs, and other devices suitable for the purposes described herein. Software and other modules may be accessible via local memory, via a network, via a browser or other application in an ASP context, or via other means suitable for the purposes described herein. Data structures described herein may comprise computer files, variables, programming arrays, programming structures, or any electronic information storage schemes or methods, or any combinations thereof, suitable for the purposes described herein. User interface elements described herein may comprise elements from graphical user interfaces, command line interfaces, and other interfaces suitable for the purposes described herein. Screenshots presented and described herein can be displayed differently as known in the art to generally input, access, change, manipulate, modify, alter, and work with information.


While the invention has been described and illustrated in connection with preferred embodiments, many variations and modifications as will be evident to those skilled in this art may be made without departing from the spirit and scope of the invention, and the invention is thus not to be limited to the precise details of methodology or construction set forth above as such variations and modification are intended to be included within the scope of the invention.

Claims
  • 1. A method for allocating control of one or more storage devices, the method comprising: receiving with a first controller module a request from a client module for access to a storage device, the first controller module being configured to direct storage operations performed on data stored on the storage device;forwarding the client access request to a manager module;directing, with the manager module, a second controller module to assume an inactive state with respect to control of the storage device;directing, with the manager module, the first controller module to assume an active state with respect to control of the storage device;mounting the storage device with the first controller module; andgenerating storage path data indicating a path to the storage device.
  • 2. The method of claim 1, additionally comprising selecting the first controller module, from among a plurality of controller modules, to receive the client access request.
  • 3. The method of claim 2, wherein said selecting is based at least in part on the type of data associated with the client access request.
  • 4. The method of claim 1, wherein said generating storage path data is performed by the first controller module.
  • 5. The method of claim 4, additionally comprising storing the storage path data in a first database associated with the first controller module.
  • 6. The method of claim 5, additionally comprising forwarding the storage path data to the manager module.
  • 7. The method of claim 6, additionally comprising forwarding, with the manager module, the storage path data to the client module.
  • 8. The method of claim 1, wherein said acts of directing are based at least in part on a priority of a storage operation associated with the client access request.
  • 9. The method of claim 1, additionally comprising identifying, with the manager module, if the storage device is available to accommodate the client access request.
  • 10. The method of claim 1, additionally comprising sending the client access request to the first controller module based at least on a type of data associated with the client access request.
  • 11. A system for allocating control of storage media, the system comprising: storage media;a first module configured to direct first storage operations performed on data stored on the storage media;a second module configured to direct second storage operations performed on the data stored on the storage media; anda third module configured to receive a request from a client module to access the storage media and to determine whether the first module or the second module is available to perform at least one storage operation, and wherein the third module is further configured to direct the first module to assume an inactive state with respect to control of the storage media and to direct the second module to assume an active state with respect to control of the storage media when the first module is not available to perform the at least one storage operation.
  • 12. The system of claim 11, wherein the third module is further configured to allocate control of the storage media based at least in part on a priority of the at least one storage operation.
  • 13. The system of claim 11, wherein the second module is further configured to generate path data indicating a network path to the storage media.
  • 14. The system of claim 13, wherein the storage media is coupled to the first and second modules through a storage area network (SAN).
  • 15. The system of claim 11, further comprising a management database configured to store information indicative of the availability of at least the first and second modules.
  • 16. The system of claim 15, wherein the third module is further configured to maintain the management database.
  • 17. The system of claim 11, wherein the storage media comprises a plurality of storage devices, and wherein the third module is further configured to determine an availability of one or more of the plurality of storage devices to be controlled by the second module during the performance of the at least one storage operation.
  • 18. The system of claim 11, wherein the availability of the first and second modules comprises a bandwidth availability.
  • 19. A system for allocating control of one or more storage devices, the system comprising: first means for directing first storage operations performed on a storage device;second means for directing second storage operations performed on the storage device;means for receiving a request from a client module for access to the storage device for the performance of at least one storage operation, for instructing said first directing means to assume an inactive state with respect to control of the storage device, and for instructing said second directing means to assume an active state with respect to control of the storage device and to mount the storage device; andmeans for storing data indicative of an availability of each of the first and second directing means to perform the at least one storage operation.
  • 20. The system of claim 19, wherein said receiving means is further configured to determine a priority of the at least one storage operation among a plurality of storage operations.
RELATED APPLICATIONS

The present application is a continuation of U.S. patent application Ser. No. 11/582,152, filed Oct. 17, 2006, now U.S. Pat. No. 7,409,509, issued Aug. 5, 2008, which is a continuation of U.S. patent application Ser. No. 10/658,095, filed Sep. 9, 2003, now U.S. Pat. No. 7,130,970, issued Oct. 31, 2006, which claims the benefit of priority under 35 U.S.C. §119(e) from U.S. Provisional Patent Application No. 60/409,183, titled DYNAMIC STORAGE DEVICE POOLING IN A COMPUTER SYSTEM, filed Sep. 9, 2002, each of which is hereby incorporated herein by reference in its entirety. This application is also related to the following pending applications, each of which is hereby incorporated herein by reference in its entirety: U.S. patent application Ser. No. 09/610,738, titled MODULAR BACKUP AND RETRIEVAL SYSTEM USED IN CONJUNCTION WITH A STORAGE AREA NETWORK, filed Jul. 6, 2000, now U.S. Pat. No. 7,035,880, issued Apr. 25, 2006;U.S. patent application Ser. No. 09/609,977, titled MODULAR BACKUP AND RETRIEVAL SYSTEM WITH AN INTEGRATED STORAGE AREA FILING SYSTEM, filed Aug. 5, 2000;U.S. patent application Ser. No. 09/354,058, titled HIERARCHICAL BACKUP AND RETRIEVAL SYSTEM, filed Jul. 15, 1999, now U.S. Pat. No. 7,395,282, issued Jul. 1, 2008; andU.S. patent application Ser. No. 09/038,440, titled PIPELINED HIGH-SPEED DATA TRANSFER MECHANISM, filed Mar. 11, 1998, now U.S. Pat. No. 6,418,478, issued Jul. 9, 2002.

US Referenced Citations (195)
Number Name Date Kind
4686620 Ng Aug 1987 A
4995035 Cole et al. Feb 1991 A
5005122 Griffin et al. Apr 1991 A
5093912 Dong et al. Mar 1992 A
5133065 Cheffetz et al. Jul 1992 A
5193154 Kitajima et al. Mar 1993 A
5212772 Masters May 1993 A
5226157 Nakano et al. Jul 1993 A
5239647 Anglin et al. Aug 1993 A
5241668 Eastridge et al. Aug 1993 A
5241670 Eastridge et al. Aug 1993 A
5276860 Fortier et al. Jan 1994 A
5276867 Kenley et al. Jan 1994 A
5287500 Stoppani, Jr. Feb 1994 A
5321816 Rogan et al. Jun 1994 A
5333315 Saether et al. Jul 1994 A
5347653 Flynn et al. Sep 1994 A
5388243 Glider et al. Feb 1995 A
5410700 Fecteau et al. Apr 1995 A
5448724 Hayashi Sep 1995 A
5465359 Allen et al. Nov 1995 A
5491810 Allen Feb 1996 A
5495607 Pisello et al. Feb 1996 A
5504873 Martin et al. Apr 1996 A
5544345 Carpenter et al. Aug 1996 A
5544347 Yanai et al. Aug 1996 A
5559957 Balk Sep 1996 A
5619644 Crockett et al. Apr 1997 A
5638509 Dunphy et al. Jun 1997 A
5673381 Huai et al. Sep 1997 A
5699361 Ding et al. Dec 1997 A
5729743 Squibb Mar 1998 A
5737747 Vishlitzky et al. Apr 1998 A
5751997 Kullick et al. May 1998 A
5758359 Saxon May 1998 A
5761677 Senator et al. Jun 1998 A
5764972 Crouse et al. Jun 1998 A
5778395 Whiting et al. Jul 1998 A
5812398 Nielsen Sep 1998 A
5813008 Benson et al. Sep 1998 A
5813009 Johnson et al. Sep 1998 A
5813017 Morris Sep 1998 A
5829023 Bishop Oct 1998 A
5829046 Tzelnic et al. Oct 1998 A
5875478 Blumenau Feb 1999 A
5875481 Ashton et al. Feb 1999 A
5887134 Ebrahim Mar 1999 A
5890159 Sealby et al. Mar 1999 A
5901327 Ofek May 1999 A
5924102 Perks Jul 1999 A
5950205 Aviani, Jr. Sep 1999 A
5958005 Thorne et al. Sep 1999 A
5974563 Beeler, Jr. Oct 1999 A
6021415 Cannon et al. Feb 2000 A
6026414 Anglin Feb 2000 A
6052735 Ulrich et al. Apr 2000 A
6076148 Kedem Jun 2000 A
6094416 Ying Jul 2000 A
6105136 Cromer et al. Aug 2000 A
6131095 Low et al. Oct 2000 A
6131190 Sidwell Oct 2000 A
6137864 Yaker Oct 2000 A
6148412 Cannon et al. Nov 2000 A
6154787 Urevig et al. Nov 2000 A
6154852 Amundson et al. Nov 2000 A
6161111 Mutalik et al. Dec 2000 A
6167402 Yeager Dec 2000 A
6212512 Barney et al. Apr 2001 B1
6260069 Anglin Jul 2001 B1
6269431 Dunham Jul 2001 B1
6275953 Vahalia et al. Aug 2001 B1
6295541 Bodnar Sep 2001 B1
6301592 Aoyama et al. Oct 2001 B1
6304880 Kishi Oct 2001 B1
6324581 Xu et al. Nov 2001 B1
6328766 Long Dec 2001 B1
6330570 Carteau Dec 2001 B1
6330572 Sitka Dec 2001 B1
6330642 Carteau Dec 2001 B1
6343324 Hubis et al. Jan 2002 B1
6350199 Williams et al. Feb 2002 B1
RE37601 Eastridge et al. Mar 2002 E
6353878 Dunham Mar 2002 B1
6356801 Goodman Mar 2002 B1
6374266 Shnelvar Apr 2002 B1
6374336 Peters et al. Apr 2002 B1
6385673 DeMoney May 2002 B1
6389432 Pothapragada et al. May 2002 B1
6418478 Ignatius et al. Jul 2002 B1
6421711 Blumenau et al. Jul 2002 B1
6438586 Hass et al. Aug 2002 B1
6487561 Ofek et al. Nov 2002 B1
6487644 Huebsch et al. Nov 2002 B1
6505307 Stell et al. Jan 2003 B1
6519679 Devireddy et al. Feb 2003 B2
6538669 Lagueux, Jr. et al. Mar 2003 B1
6542909 Tamer et al. Apr 2003 B1
6542972 Ignatius et al. Apr 2003 B2
6564228 O'Connor May 2003 B1
6571310 Ottesen May 2003 B1
6581143 Gagne et al. Jun 2003 B2
6631442 Blumenau Oct 2003 B1
6631493 Ottesen et al. Oct 2003 B2
6658436 Oshinsky et al. Dec 2003 B2
6658526 Nguyen et al. Dec 2003 B2
6732124 Michihiko et al. May 2004 B1
6757794 Cabrera et al. Jun 2004 B2
6789161 Blendermann et al. Sep 2004 B1
6791910 James et al. Sep 2004 B1
6859758 Prabhakaran et al. Feb 2005 B1
6886020 Zahavi et al. Apr 2005 B1
6952758 Chron et al. Oct 2005 B2
6965968 Touboul et al. Nov 2005 B1
6968351 Butterworth Nov 2005 B2
6973553 Archibald, Jr. et al. Dec 2005 B1
6983351 Gibble et al. Jan 2006 B2
7003641 Prahlad et al. Feb 2006 B2
7035880 Crescenti et al. Apr 2006 B1
7062761 Slavin et al. Jun 2006 B2
7069380 Ogawa et al. Jun 2006 B2
7103731 Gibble et al. Sep 2006 B2
7103740 Colgrove et al. Sep 2006 B1
7107298 Prahlad et al. Sep 2006 B2
7107395 Ofek et al. Sep 2006 B1
7117246 Christenson et al. Oct 2006 B2
7120757 Tsuge Oct 2006 B2
7130970 Devassy et al. Oct 2006 B2
7155465 Lee et al. Dec 2006 B2
7155633 Tuma et al. Dec 2006 B2
7159110 Douceur et al. Jan 2007 B2
7174433 Kottomtharayil et al. Feb 2007 B2
7246140 Therrien et al. Jul 2007 B2
7246207 Kottomtharayil et al. Jul 2007 B2
7246272 Cabezas et al. Jul 2007 B2
7269612 Devarakonda et al. Sep 2007 B2
7278142 Bandhole et al. Oct 2007 B2
7287047 Kavuri Oct 2007 B2
7287252 Bussiere et al. Oct 2007 B2
7380072 Kottomtharayil et al. May 2008 B2
7467167 Patterson Dec 2008 B2
7472238 Gokhale Dec 2008 B1
7490207 Amarendran Feb 2009 B2
7500053 Kavuri et al. Mar 2009 B1
7536291 Retnamma et al. May 2009 B1
20010034812 Ignatius et al. Oct 2001 A1
20020029281 Zeidner et al. Mar 2002 A1
20020040405 Gold Apr 2002 A1
20020049778 Bell et al. Apr 2002 A1
20020049803 Bandhole et al. Apr 2002 A1
20020069369 Tremain Jun 2002 A1
20020107877 Whiting et al. Aug 2002 A1
20020194340 Ebstyne et al. Dec 2002 A1
20030014433 Teloh et al. Jan 2003 A1
20030014607 Slavin et al. Jan 2003 A1
20030016609 Rushton et al. Jan 2003 A1
20030033308 Patel et al. Feb 2003 A1
20030051097 Ottesen et al. Mar 2003 A1
20030061491 Jaskiewicz et al. Mar 2003 A1
20030163652 Tsuge Aug 2003 A1
20030169733 Gurkowski et al. Sep 2003 A1
20030188114 Lubbers et al. Oct 2003 A1
20030225801 Devarakonda et al. Dec 2003 A1
20040010487 Prahlad et al. Jan 2004 A1
20040073716 Boom et al. Apr 2004 A1
20040088432 Hubbard et al. May 2004 A1
20040090788 Kottomtharayil May 2004 A1
20040107199 Dairymple et al. Jun 2004 A1
20040167941 Prahlad et al. Aug 2004 A1
20040193953 Callahan et al. Sep 2004 A1
20040230829 Dogan et al. Nov 2004 A1
20050033755 Gokhale et al. Feb 2005 A1
20050033756 Kottomtharayil et al. Feb 2005 A1
20050033800 Kavuri et al. Feb 2005 A1
20050044114 Kottomtharayil et al. Feb 2005 A1
20050086443 Mizuno et al. Apr 2005 A1
20050114406 Dhrubajyoti et al. May 2005 A1
20050114477 Willging et al. May 2005 A1
20050131900 Palliyll et al. Jun 2005 A1
20050144520 Tuma et al. Jun 2005 A1
20050166011 Burnett et al. Jul 2005 A1
20050172093 Jain Aug 2005 A1
20050246568 Davies Nov 2005 A1
20050256972 Cochran et al. Nov 2005 A1
20050262296 Peake Nov 2005 A1
20060005048 Osaki et al. Jan 2006 A1
20060010227 Atluri Jan 2006 A1
20060044674 Martin et al. Mar 2006 A1
20060053305 Wahlert et al. Mar 2006 A1
20060224846 Amarendran et al. Oct 2006 A1
20060224852 Kottomtharayil et al. Oct 2006 A1
20060230244 Amarendran et al. Oct 2006 A1
20060242489 Brockway et al. Oct 2006 A1
20070130430 Devassy et al. Jun 2007 A1
20070186042 Kottomtharayil et al. Aug 2007 A1
20080016126 Kottomtharayil et al. Jan 2008 A1
Foreign Referenced Citations (15)
Number Date Country
0 259 912 Mar 1988 EP
0 405 926 Jan 1991 EP
0 467 546 Jan 1992 EP
0 774 715 May 1997 EP
0 809 184 Nov 1997 EP
0 899 662 Mar 1999 EP
0 981 090 Feb 2000 EP
1 174 795 Jan 2002 EP
1 115 064 Dec 2004 EP
2366048 Feb 2002 GB
WO 9513580 May 1995 WO
WO 9912098 Mar 1999 WO
WO 9914692 Mar 1999 WO
WO 9917204 Apr 1999 WO
WO 2005055093 Jun 2005 WO
Related Publications (1)
Number Date Country
20080276055 A1 Nov 2008 US
Provisional Applications (1)
Number Date Country
60409183 Sep 2002 US
Continuations (2)
Number Date Country
Parent 11582152 Oct 2006 US
Child 12177718 US
Parent 10658095 Sep 2003 US
Child 11582152 US