Method, system, and product for maintaining within a virtualization system a historical performance database for physical devices

[0001] 1. Field of the Invention

[0002] The present invention relates to data processing systems, and more particularly to a data processing system, method, and computer program product for maintaining a relational database in a virtualization system of usage information of multiple, different physical devices in a system that implements virtual storage devices.

[0003] 2. Background of the Invention

[0004] In some known data processing systems, a server computer system is coupled directly to its storage devices, such as tape drives and/or disk drives. To perform a backup operation to a tape drive, for example, the server computer system commands the tape library to mount a specific physical tape cartridge into a specific physical tape drive. The application running on the server can then directly access the physical tape drive. Any warning or errors encountered can be managed by the server through the application. It is possible for this error information to be used by the application to perform preventative maintenance on the physical storage devices. The problem with this environment is that the storage administration resides on the server. The server has access to only its own storage devices. These storage devices cannot be shared with other servers.

[0005] Storage virtualization has been used to overcome the limitations that arise when a server is coupled directly to its storage devices. In a system that implements storage virtualization, the server computer systems are isolated from the physical storage devices by a virtual representation of the storage system. The storage system is a pool of physical storage devices, such as disk drives and tape drives. This approach permits the sharing of the physical storage devices among the server computer systems. Each server has access to one or more virtual storage devices. These virtual storage devices are logical devices maintained by the virtual interface. The virtual interface maps the virtual storage devices to physical devices. When an application running on one of the servers wants to access data on ore of its virtual interfaces, the server identifies the virtual interface. For example, when a server wants to perform a backup, the application commands the tape library to mount a physical tape cartridge into a virtual tape drive. The virtual interface then intercepts the command, modifies the request to translate this virtual tape drive to a physical tape drive, and creates a mapping from this physical device to the virtual interface.

[0006] Storage virtualization hides warnings and errors from the server, however. The server knows about only the virtual interface. Usage information about the physical device is not available to the server. Although, the virtual interface logs some limited information about what occurs with the physical storage devices, the log is a continuous event log that combines very minimal information about events that occurred in the physical devices. The log is a single, sequential string of events occurring in various physical devices kept in the log in the sequential order in which the events occurred. Events are placed in the log in the order in which they occur without regard to where the event occurred. Thus, an event occurring in a first storage device may be logged followed by an event occurring in a second storage device followed by an event occurring back in the first storage device. It does not maintain a separate log for each device. Further, information about which physical device was used and the history of usage is not recorded. This log is not available to the servers. They may not access it.

[0007] The StorageNet 6000, available from Storage Technology Corporation, is an example of a system that implements a virtual interface. The SN6000 presents a virtualization system for tape drives. The system presents virtual tape drives to servers, and dynamically maps these virtual interfaces to the physical tape drives as needed. When errors occur in the system, it is very difficult for the server to determine where the error occurred since it does not have information about which physical device was being used. When an error occurs, a host attributes the error to the virtual interface that the host is coupled to, and not the physical device.

[0008] Therefore, a need exists for a method, system, and product for maintaining a relational database within the virtual interface of information about usage of physical storage devices in a system that implements virtual storage devices.

[0009] A data processing system, method, and product are disclosed for maintaining a relational database of usage information of multiple, different physical devices. A virtualization system is provided interposed between a host computer system and the physical devices. The host computer system is capable of accessing only virtual interfaces and is incapable of directly accessing any of the physical devices. A relational database is established within the virtualization system for storing information. Information is stored in the database about transactions processed by the virtualization system utilizing the physical devices. The information stored in the database includes error information and information about the usage of the physical devices. The information in the database may be accessed by the host computer system.

[0010] The above as well as additional objectives, features, and advantages of the present invention will become apparent in the following detailed written description.

[0015] A preferred embodiment of the present invention and its advantages are better understood by referring to the figures, like numerals being used for like and corresponding parts of the accompanying figures.

[0016] The present invention is a system, method, and computer program product for maintaining a relational database of usage information of multiple, different physical storage devices. The system implements virtual storage devices utilizing a virtualization system interposed between host computer systems and the physical storage devices. The host computer systems are capable of accessing only virtual interfaces and are incapable of directly accessing any of the physical storage devices.

[0017] In the example depicted in the preferred embodiment, the term “virtual interface” is used to mean a virtual storage device. However, those skilled in the art will recognize that a virtual interface may include any type of virtual interface between a host and any type of physical device. For example, a virtual interface can be a file, a library, a drive, a volume, or any other type of interface. Further, a combination of different types of virtual interfaces can be simultaneously used in a single virtualization system. In addition, the physical device is not limited to a physical storage device, but may include any other type of physical device.

[0018] A relational database is implemented within the virtualization system. The virtualization system receives transactions from a host computer system to access virtual storage devices. For each transaction, the virtualization system modifies the transaction to translate the virtual storage device to the physical storage device that has been mapped to the virtual storage device. Information is collected from each transaction processed by the virtualization system and is stored in the database.

[0019] The data in the relational database is associated such that transactions can be tracked by searching on a particular physical device, a particular connection from a host to a virtual interface, a particular data movement such as several transactions, or other data. By searching on one type of data item, for example one particular physical device, data associated with all other transactions for which data was stored for that type of data item will be returned.

[0020] For example, if a search is performed for information about a particular physical device, all information stored about that physical device will be returned. This information will typically have been stored in response to many different transactions.

[0021] The information collected for each transaction includes, but is not limited to, one or more of the following: an identification of the transaction, an identification of the virtual storage device accessed by the transaction, an identification of the physical storage device that is mapped to this virtual storage device, a particular physical device such as a tape cartridge, hub, or switch, usage information such as the date, time of day, and/or duration of the data access, data information such as amount of data read from or written to the physical storage device, and/or the data rate, and/or any other information associated with the transaction and/or physical devices.

[0022] The information stored in the database may be accessed by any one of the hosts coupled to the virtualization system in order to perform a performance analysis of one or more of the physical storage devices. In addition, other hosts, which are not coupled to the virtual interfaces, may also access the database in order to perform a performance analysis. Thus, preventative maintenance may be performed using this information by any host, whether or not the host is coupled to a virtual interface.

[0023] Error information may also be stored in the database. When an error occurs, the virtualization system will identify one of the transactions it has or is processing that is associated with the error, i.e. the virtualization system will determine which transaction was processed that resulted in the error. Information about the error is collected and stored in the database. The information collected includes an identification of the type of error, the device in which the error occur, and any other information typically collected when an error occurs.

[0024] FIG. 1 depicts a block diagram of a data processing system 10 that includes a plurality of host computer systems coupled to a plurality of physical drives utilizing a storage device virtual interface. Hosts 12, 14, 16, 18, 20, and 22 are coupled to a storage device interface 24. Physical drives 26, 28, 30, and 32 are also coupled to storage device interface 24. These hosts may be homogeneous, i.e. similar systems executing the same operating system, or they may be heterogenous, i.e. different physical platforms executing different operating systems, or any combination of physical platforms and operating systems. In addition, the physical drives may be any combination of disk drives and/or tape drives and may be homogeneous or heterogeneous.

[0025] Storage device virtual interface 24 is interposed between the hosts and the physical storage devices.

[0026] The physical drives are dynamically managed by the virtual interface 24 as a pool of resources. These physical drives are shared among the various hosts. The virtual interface 24 maps the virtual interfaces 34, 36, 38, 40, 42, and 44 to a pool of physical devices 26, 28, 30, and 32. Virtual interface 24 receives access requests for a particular virtual interface, identifies the physical device mapped to the virtual interface, and assigns the request to the appropriate physical device.

[0027] Included within virtual interface 24 is a processor 48, volatile memory 50, non-volatile memory 52, and other devices 56. Within non-volatile memory 52 is a relational database 54.

[0028] Database 54 includes information about each transaction processed by virtual interface 24. The information includes a transaction identifier, an identifier of the virtual interface identified by the transaction, and an identifier of one or more physical devices including the physical device assigned to this virtual interface, and other physical devices such as a cartridge, a hub, switch and other physical devices that are accessed or used during the transaction. The information also includes usage information, such as the date, time, and duration of the transaction. Data information, such as amount of data read from or written to the physical device, and the data rate are maintained in the database. Any other information about the transaction and/or virtual and physical devices involved is obtained and stored in the database.

[0029] Error, warning, failure, exception, and/or fault information is also stored in database 54.

[0030] The information stored in database 54 may be accessed by a host and may be used to monitor device usage, tape media usage, warning, and error conditions to perform preventative maintenance. The information may be accessed by a host coupled to a virtual interface, such as host 12, 14, 16, 18, 20, or 22, or a host, such as host 58, which is coupled to interface 24 but which is not coupled to a virtual interface. For example, consider a physical tape cartridge that has a marginal error that only exhibits itself in a specific tape drive. If this tape cartridge is used in another tape device, that data is read correctly. If another tape cartridge is used in the tape drive in question, data can be read without error. A problem occurs only when the two are used together. This type of condition cannot be captured in a system that uses storage virtualization without the database of the present invention. The present invention captures this condition in the database because all of the information about the tape cartridges and physical tape drives are stored.

[0031] FIG. 2 is a high level flow chart which depicts storing data in a database within a storage device virtual interface in accordance with the present invention. The process starts as depicted by block 200 and thereafter passes to block 202 which illustrates monitoring a transaction processed by the virtual interface. Next, block 204 depicts the logging in a relational database for each transaction information about the transaction. The information includes a transaction identifier, an identifier of the virtual interface identified by the transaction, and an identifier of one or more physical devices including one or more physical devices assigned to this virtual interface, and other physical devices such as a cartridge, a hub, switch and other physical devices that are accessed or used during the transaction. The information also includes usage information, such as the date, time, and duration of the transaction. Data information, such as amount of data read from or written to the physical device, and the data rate are maintained in the database. Any other information about the transaction and/or virtual and physical devices involved is obtained and maintained in the database. The process then passes back to block 202.

[0032] FIG. 3 is a high level flow chart which depicts storing error information in a database within a storage device virtual interface in accordance with the present invention. The process starts as depicted by block 300 and thereafter passes to block 302 which illustrates a determination of whether or not an error in a physical device has been encountered. If a determination is made that an error has not occurred, the process passes back to block 302. Referring again to block 302, if a determination is made that an error has occurred, the process passes to block 304 which depicts identifying the transaction associated with this error. Block 306, then, illustrates logging information about this error in the relational database. The information logged about the error will include information about the physical and virtual interfaces identified by the transaction. The information may also include the type of error, date and time the error occurred, and any other information that may be obtained about the error. The process then terminates as depicted by block 308.

[0033] It is important to note that while the present invention has been described in the context of a fully functioning data processing system, those of ordinary skill in the art will appreciate that the processes of the present invention are capable of being distributed in the form of a computer readable medium of instructions and a variety of forms and that the present invention applies equally regardless of the particular type of signal bearing media actually used to carry out the distribution. Examples of computer readable media include recordable-type media such a floppy disc, a hard disk drive, a RAM, CD-ROMs, and transmission-type media such as digital and analog communications links.

[0034] The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiment was chosen and described in order to best explain the principles of the invention, the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.