Virtual tape library device

[0001] 1. Field of the Invention

[0002] The present invention relates to a storage device system used in information processing systems and computer systems, and especially to a virtual tape device and a virtual tape library device.

[0003] 2. Related Background Art

[0004] Generally in computer systems, two types of storage media, magnetic disks and magnetic tapes, are used for data storage. Magnetic disks are devices in which data recorded at specified positions on magnetic disk devices can be directly accessed (i.e., random access), and are therefore used to record frequently used data. On the other hand, magnetic tapes are storage media in which data is written and read only in sequence from the beginning of the tapes (i.e., sequential access), and have therefore been used primarily for backup of data recorded on magnetic disks or for archiving old data to be stored long-term. The main reason for using magnetic tapes for backup and archiving purposes is that the bit cost of magnetic tapes is cheaper than that of magnetic disks, so that it costs less to store a large amount of data.

[0005] However, in recent years a rapid rise in the amount of data handled in computer systems has caused backup and restore processing to and from magnetic disks and magnetic tapes to take longer, such that making backups on magnetic tapes is beginning to be impractical. Backups are normally made when online operations do not take place, such as at night (off-line period); however, due to the fact that backups are taking too much time, there are instances where backup processing is not completed during off-line period. Furthermore, since the bit cost of magnetic disks are falling and approaching the bit cost of magnetic tapes, methods for using magnetic disks to store backup data are beginning to be considered.

[0006] For example, a device that uses a magnetic disk device and emulates a tape device has been proposed. With this device, when a command for the tape device is received from a host computer, the command is converted to a command for the magnetic disk, and data on the magnetic disk is accessed, such that the magnetic disk device can be used as a tape device. Such a device is called a virtual tape device.

[0007] The purpose of a virtual tape device is to be able to have such uses as making backups on virtual tape devices in existing computer environments that formerly used conventional tape devices, by replacing the conventional tape devices with virtual tape devices and without making any changes to host computers or backup software.

[0008] However, in such actual uses as making backups, a tape library device that maintains and manages a plurality of magnetic tapes also manages backups in many computer environments. In a backup operation to backup data that are distributed across a plurality of magnetic tapes, backup software operates the tape library device and thereby loads magnetic tapes into tape devices and replaces magnetic tapes without any human intervention. Consequently, in order to perform a backup processing that actually utilizes virtual tape devices in computer systems, a virtual library mechanism that realizes processing for loading virtual tape media into virtual tape devices and replacing virtual tapes is required.

[0009] The conventional technology teaches how to emulate a tape device but does not teach any technology regarding library mechanism, such as the operation of a library changer robot.

[0010] Furthermore, the virtual tape device only has functions of a tape device and cannot be used as a disk device. As a result, when making backups, data must be backed up on a virtual tape device from another disk device via a host computer. Consequently, even if the access speed of the magnetic disk is slightly faster than the access speed of the magnetic tape device, the backup speed does not improve significantly. Tape devices have reached higher read/write speeds especially in recent years, and this has made the performance of the tape devices comparable to the sequential read/write performance of disk devices. Consequently, even if a virtual tape device were used in place of a tape device, there would not be significant advantages in terms of performance.

[0011] The present invention relates to a device that realizes an emulation of a library device.

[0012] The present invention also relates to a storage device system having both the functions of a magnetic disk and a virtual tape library.

[0013] The present invention further relates to a storage device system that can perform a faster backup processing.

[0014] A storage device system in accordance with an embodiment of the present invention includes interfaces connected to computers, a plurality of magnetic disks, and a control device that controls the plurality of magnetic disks. When a command from one of the computers instructing a tape library device to load a magnetic tape into a tape device is received by one of the interfaces, the control device selects a storage region within one of the magnetic disks; and when one of the interfaces receives an access request from the computer to the tape device, the control device controls to access the storage region selected.

[0015] Other features and advantages of the invention will be apparent from the following detailed description, taken in conjunction with the accompanying drawings that illustrate, by way of example, various features of embodiments of the invention.

[0032] FIG. 1 shows an example of a computer system in accordance with an embodiment of the present invention.

[0033] A storage device system 0 includes a disk system 1 and a front end server 6.

[0034] The disk system 1 includes a network interface 11 (abbreviated “LAN I/F” in the drawing), a Fibre Channel interface 12 (abbreviated “FC I/F” in the drawing), a CPU 13, a memory 14, a disk interface 15 (abbreviated “disk I/F” in the drawing), and one or more disks 16. The disk system 1 is connected to the front end server 6 via the network interface 11 and the Fibre Channel interface 12.

[0035] The front end server 6 includes a network interface 61 connected to LAN, a network interface 65 connected to the disk system 1, a Fibre Channel interface 62 connected to a Fibre Channel switch, a Fibre Channel interface 66 connected to the disk system 1, a CPU 63 and a memory 64. The network interface 61 is connected to one or more NAS client computers (hereinafter also called “NAS clients”) 3 via a LAN switch 5 and provides file access service to the NAS clients 3. The Fibre Channel interface 62 is connected to a plurality of host computers (hereinafter also called “hosts”) 2 via a Fibre Channel switch 4 (abbreviated “FC switch” in the drawing) and provides disk access and tape access processing to the hosts 2.

[0036] A management console 7 is connected to the front end server 6 via the LAN switch 5 and the network interface 61 and performs setting processing of the front end server 6, as well as setting processing of the disk system 1 via the network interface 65 and the network interface 11. The details of the setting processing will be described later.

[0037] The front end server 6 receives disk access requests, tape access requests and file access requests from the hosts 2 and the NAS clients 3, reads data from the disk system 1, and writes data to the disk system 1. Programs for performing such processing are stored in the memory 64 and executed by the CPU 63.

[0038] The disk system 1 primarily receives disk access requests from the front end server 6 and executes processing accordingly. Programs required for processing executed by the disk system 1 are stored in the memory 14 and executed by the CPU 13. In addition to storing programs operated by the CPU 13, the memory 14 also serves as a cache memory for temporarily storing write data received from the hosts 2 and/or NAS clients 3 via the front end server 6. The disk interface 15 is an interface that uses such protocols as SCSI (Small Computer Systems Interface) or Fibre Channel, and the CPU 13 accesses the disks 16 via the disk interface 15.

[0039] Each of the disks 16 may be a physical magnetic disk drive or in a form that appears to be a single logical disk drive but consisting of a plurality of magnetic disk drives, such as a disk array device. In the description according to the present embodiment, each of the disks 16 is assumed to be a logical disk; unless otherwise noted, the term “disk” means a logical disk hereafter. Physical disks such as individual magnetic disks will be described as physical disks.

[0040] FIG. 2 shows an example of the logical configuration of the storage device system 0. The following mainly describes the contents of programs operated by the CPU 13 and the CPU 63.

[0041] A file service 67 is a program that provides functions of so-called NAS (Network Attached Storage); it manages files on the disks 16 and is executed when processing file access requests according to such protocols as NFS or CIFS are received from the NAS clients 3 by the front end server 6. Hereafter, data on the disks 16 managed by the file service 67 are called NAS data, and those disks 16 among all the disks 16 that store the NAS data are called NAS devices.

[0042] A backup service 69 is a program that specializes in backup processing of NAS data; it operates in response to backup/restore requests received by the front end server 6 from backup servers 31 of the NAS clients 3.

[0043] A block I/O receiving section 68 receives disk access requests, tape access requests and library control requests from the hosts 2; if a request is a disk access request, the block I/O receiving section 68 simply transfers the processing to the disk system 1; if a request is a tape access request or a library control request, the block I/O receiving section 68 transfers the processing to a virtual tape library section 114.

[0044] The virtual tape library section 114 receives commands for a tape device or a library device from the block I/O receiving section 68 and performs a processing for the command received. For example, if the virtual tape library section 114 receives a command requesting data read from a tape, the virtual tape library section 114 converts the command into a read command for a disk, issues a read request for the disks 16 to the disk system 1, receives read data from the disk system 1, and sends the read data to the block I/O receiving section 68.

[0045] A device management section 115 correlates the disks 16 to virtual tapes and prepares virtual tape devices and virtual library devices. The device management section 115 manages the disks 16 by dividing the disks 16 into four groups: a disk device group 161, a file system group 162, a virtual tape device group 163, and an unallocated device group 164. The disk device group 161 is a collection of disks accessed as magnetic disks by the hosts 2; the file system group 162 is a collection of disks storing NAS data, or a collection of NAS devices; the virtual tape device group 163 is a collection of disks storing data accessed when access requests for data on tapes are received from the hosts 2, i.e., a collection of disks that serve as virtual tapes to store data accessed; and the unallocated device group 164 is a collection of disks that do not belong to any of the previous three groups, or a collection of unused disks. Hereinafter, disks that belong to the disk device group 161 are called “disk devices.”

[0046] The file service 67 and the backup service 69 are stored in the memory 64 of the front end server 6, and are programs executed by the CPU 63. The block I/O receiving section 68, the device management section 115, and the virtual tape library section 114 are realized when corresponding programs stored in the memory 64 of the front end server 6 are executed by the CPU 63.

[0047] A disk access processing section 111 of the disk system 1 receives access requests to the disks 16 from the front end server 6 via the Fibre Channel interface 12, and performs read/write processing to and from the disks 16.

[0048] A mirror/split section 112 executes processing to create a copy of data stored on one of the disks 16 or a copy of data stored in a part of storage regions of one of the disks 16, and to store the data copy on another disk 16 within the disk system 1. In other words, when the mirror/split section 112 receives a copy instruction, data that was stored on the disk 16 that is the target of the instruction at the time the copy instruction was received (i.e., snapshot data) is copied and stored on a different disk 16. In the disk system 1, data can be read and/or written even during the copy operation. Known methods may be used for realizing the reception of data read or write commands while obtaining snapshot data.

[0049] The disk access processing section 111 and the mirror/split section 112 are realized when corresponding programs stored in the memory 14 of the disk system 1 are executed by the CPU 13.

[0050] Next, referring to FIGS. 3 through 6, information managed by the device management section 115 and the virtual tape library section 114 will be described.

[0051] First, FIG. 3 is a diagram of an example of a disk management table 200, which manages disks that belong to either the disk device group 161 or the file system group 162. The disk system 1 assigns a unique identifier to each of the disks 16 to manage the disks 16. Identifiers used are integer values of 0 or greater. Such identifiers are called device numbers.

[0052] In each row of the disk management table 200 are a device number 201, a size 202, an allocation type 203, a WWN 204, and an LUN 205 for the corresponding disk 16. The size 202 indicates the size of the disk 16 that corresponds to the device number 201. The allocation type 203 indicates which of the disk device group 161 and the file system group 162 each disk 16 belongs to; the disks 16 that belong to the disk device group 161 are assigned an identifier “FC,” while disks 16 that belong to the file system group 162 are assigned an identifier “LAN,” in order to manage the disks 16.

[0053] The WWN 204 and the LUN 205 are WWN (World Wide Name) and LUN (Logical Unit Number), respectively, assigned to each disk 16; these are used when accessing the disks 16 from the hosts 2 and when the block I/O receiving section 68 of the front end server 6 accesses the disks 16. According to this embodiment, the WWN designated when the hosts 2 access the disks 16 and the WWN designated when the front end server 6 accesses the disks 16 have the same value. The WWNs may be different in another embodiment of the present invention; in such a case, the WWN designated when the hosts 2 access the disks 16 and the WWN designated when the front end server 6 accesses the disks 16 shall both be managed by the disk management table 200.

[0054] A mounting name 206 is a directory name designated when the NAS clients 3 mount NAS devices; the mounting name 206 relates only to disks 16 that belong to the file system group 162. For this reason, in rows for disks 16 that belong to the disk device group 161, no values are entered under the mounting name 206.

[0055] FIG. 4 is an example of a virtual tape management table 210 that manages disks 16 that belong to the virtual tape device group 163.

[0056] Before describing the virtual tape management table 210, a general tape library device is first described. A tape library device comprises a plurality of slots to store magnetic tapes, a robot that carries magnetic tapes from the slots to a tape device or from the tape device to the slots, and the tape device (hereinafter also called a “tape drive”) in which the magnetic tapes are loaded. There may be one or more each of the tape device and the robot in one tape library device. In the tape library devices, identification information is assigned to each magnetic tape and each slot in order to uniquely specify each magnetic tape and each slot. The identification information assigned to each magnetic tape is called a “volume tag,” and the identification information assigned to each slot is called an “element address.”

[0057] According to the embodiment of the present invention, magnetic disks are used in place of actual magnetic tapes, and the disks are used to emulate magnetic tapes. The emulated magnetic tapes are called “virtual tapes.” According to the present embodiment, the slots, the robots and the tape devices are also emulated by the storage device system 0, such that the storage device system 0 can behave as a tape library device. A tape library device emulated by the storage device system 0 in this manner is called a “virtual tape library device.” In the virtual tape library device, when a write command and write data are sent from one of the hosts 2 to a tape device, the write data is stored in a designated region of one of the disks 16 that corresponds to the virtual tape designated in the write command. According to the present embodiment, the identification information assigned to each virtual tape is called a tape number 211, and the identification information assigned to each slot is called a slot number 212.

[0058] The storage device system 0 emulates one or more tape library devices and has one virtual tape management table 210 for each virtual tape library device. In each row of the virtual tape management table 210 are the tape number 211, the slot number 212, a size 213, a device number 214, a start LBA 215, an end LBA 216, a pointer 217, and an option flag 218.

[0059] The tape number 211 is the identification information created by the virtual tape library section 114 for each virtual tape. The slot number 212 is the number created by the virtual tape library section 114 and assigned to each slot of the virtual tape library device. The tape number 211 assigned to each virtual tape is an integer value of 1 or greater; if the tape number 211 column of the virtual tape management table 210 is 0, this indicates that no tape is stored in the slot that corresponds to the row. In each row whose value in the tape number 211 column is not 0, the virtual tape identified by the tape number 211 is stored in the slot with the number indicated in the corresponding slot number 212.

[0060] The size 213 indicates the capacity of the corresponding virtual tape. The device number 214 indicates the device number assigned to the disk 16 that actually stores data of the corresponding virtual tape; the start LBA 215 and the end LBA 216 indicate which region of the disk 16 indicated by the device number is used to emulate the corresponding virtual tape. The start LBA 215 indicates a head address of the storage region of the disk 16 that emulates the corresponding virtual tape, while the end LBA 216 indicates an end address thereof.

[0061] The pointer 217 indicates the position (LBA) at which data read/write begins when a read or write request is made to the corresponding virtual tape. In sequential access devices such as tape devices, the LBA of data to be accessed is not designated in read or write commands as in disks and data is instead accessed sequentially from the beginning of the tape. Consequently, whenever an access to a virtual tape ends, the last position to which the access was made must be recorded for the virtual tape; the pointer 217 is used for this purpose. Lastly, the option flag 218 is used on virtual tapes storing backup data of NAS data, and its specific usage will be described later.

[0062] FIG. 5 is a diagram of an example of an unallocated device management table 220, which manages disks 16 that belong to the unallocated device group 164. In each entry of the unallocated device management table 220 stores a device number 221, a size 222, a start LBA 223 and an end LBA 224 for the corresponding disk 16. The size 222 indicates the capacity of the disk 16 that corresponds to the device number 221, and the start LBA 223 and the end LBA 224 indicate regions not used as virtual tapes on the corresponding disk 16. In other words, according to the present embodiment of the present invention, a plurality of virtual tapes may be allocated to one disk 16. Furthermore, storage regions used as virtual tapes and unallocated storage regions may coexist on one disk 16. For each disk 16 in which no region is used, −1 is entered for both the start LBA 223 and the end LBA 224.

[0063] FIGS. 6(a) and (b) show diagrams of an example of a virtual tape drive table 230, which manages information regarding the virtual tape devices that are managed by the virtual tape library section 114, and an example of a virtual robot table 240, which manages information regarding the virtual robots. In the virtual tape library devices according to the present embodiment, each virtual tape device and each virtual robot has a WWN and an LUN, which allows the hosts 2 to access the virtual tape devices and the virtual robots as Fibre Channel devices.

[0064] Like the virtual tape management table 210, there are one virtual tape drive table 230 and one virtual robot table 240 created for each virtual tape library device.

[0065] First, the virtual tape drive table 230 is described. A drive number 231 is an identifier assigned to each virtual tape drive in the virtual tape library. Since there are four entries in the virtual tape drive table 230 in FIG. 6, this indicates that there are four virtual tape drives (i.e., virtual tape devices) in the virtual tape library device according to the present embodiment. A WWN 232 and an LUN 233 are a WWN and an LUN, respectively, of the corresponding virtual tape drive. A tape in 234 indicates which virtual tape is loaded when a virtual tape is loaded in the corresponding virtual tape drive. For virtual tape drives without any virtual tape loaded, 0 is entered in the corresponding entry of the tape in 234. The example in FIG. 6 indicates a situation where a virtual tape with the tape number 3 is loaded in a virtual tape drive whose drive number 231 is 1.

[0066] Next, the virtual robot table 240 is described. A robot number 241 is an identification number assigned to each virtual robot. A WWN 242 and an LUN 243 are a WWN and an LUN, respectively, of the corresponding virtual robot.

[0067] Each of the tables shown in FIGS. 3 through 6 is stored in the memory 64 of the front end server 6.

[0068] Next, referring to FIGS. 7 through 10, processing for setting or managing disks, virtual tape drives and virtual robots is described. The processing shown in FIGS. 7 through 10 begins when a user of the storage device system 0 issues instructions through the management console 7.

[0069] FIG. 7 is a diagram of an example of a processing to add a new physical disk to the disk system 1, form a logical disk from the physical disk added, and register the logical disk in the unallocated device group 164.

[0070] In the storage device system 0, all disks 16 initially belong to the unallocated device group 164. Any disk 16 added also initially belongs to the unallocated device group 164. Due to the fact that the disks 16 added to the disk system 1 are in reality physical disks, an operation to form logical disks from the physical disks must be performed first.

[0071] First, in step 1001, the user inputs from the management console 7 information for designating a physical disk added. Next, in step 1002, the user uses the management console 7 to designate the kind of logical disk to be formed from the physical disk designated in step 1001. Specifically, the capacity and redundant mode, such as RAID 1 or RAID 5, of the logical disk are designated.

[0072] When designating the logical disk in step 1002 is completed, an entry is added to the unallocated device management table 220, and the capacity of the logical disk designated is registered in the size 222 of the unallocated device management table 220. Furthermore, the value “−1” is entered in both the start LBA 223 and the end LBA 224. A device number is assigned to the logical disk and registered in the device number 221 column of the unallocated device management table 220 (step 1003). This ends the processing to register a new disk in the unallocated device group 164.

[0073] Registration of information in the unallocated device management table 220 is executed by the device management section 115 based on information inputted by the user through the management console 7. However, the device number 221, which is the identification information of the logical disk, may automatically be assigned and notified to the device management section 115 by the disk system 1, or the device number 221 may be designated by the user through the management console 7.

[0074] FIG. 8 is a diagram of an example of a processing to allocate one of the disks 16 registered in the unallocated device group 164 to one of the disk device group 161, the file system group 162, and the virtual tape device group 163.

[0075] First, the user designates to the storage device system 0 through the management console 7 whether the disk 16 that belongs to the unallocated device group 164 is to be allocated to one of the disk device group 161 and the file system group 162, or to the virtual tape device group 163. When the designation information is received by the storage device system 0, the device management section 115 determines whether the instruction from the user indicates the disk 16 is to be allocated as one of a disk device and NAS device, or as a virtual tape (step 1101); if it is an allocation as either a disk device or NAS device, the device management section 115 performs the processing beginning with step 1102.

[0076] In step 1102, the storage device system 0 receives from the user via the management console 7 the capacity of the disk 16 to be allocated, WWN and LUN information, and type information that indicates to which of the disk device group 161 and the file system group 162 the disk 16 that currently belongs to the unallocated device group 164 is to belong. The device management section 115 of the storage device system 0 checks to make sure that there are no problems with the designation information (step 1103); if there are no problems, the processing proceeds to step 1104. If there is any problem, such as a designation of an LUN already allocated to another disk 16, or a designation of capacity larger than the capacity of the disk 16 that currently belongs to the unallocated device group 164, such a disk device cannot be defined; consequently, the processing returns to step 1102 to have the user re-designate the capacity, WWN and LUN.

[0077] In step 1104, the device management section 115 searches the unallocated device management table 220 and selects an appropriate disk 16. The appropriate disk 16 may be a disk whose capacity is smaller than but closest to the capacity designated, for example. The device management section 115 then sets to the selected disk 16 the WWN and LUN designated in step 1102.

[0078] Next in step 1105, the device management section 115 sets in the disk management table 200 the device number of the disk 16 selected, as well as the capacity, type, WWN and LUN designated in step 1102. Furthermore, the device management section 115 deletes the entry corresponding to the disk 16 from the unallocated device management table 220 and ends the processing.

[0079] If the storage device system 0 determines in step 1101 that the user instructed the unallocated disk 16 to be allocated to the virtual tape device group 163, the device management section 115 performs the processing beginning with step 1111.

[0080] In step 1111, the storage device system 0 receives from the user via the management console 7 information regarding the number of virtual tapes to be newly allocated and their respective capacities; in step 1112, the device management section 115 checks to make sure that there are no problems with the information received. This checking is virtually identical to the processing that takes place in step 1103; if the total capacity of virtual tapes to be allocated is larger than the total capacity of the disks 16 in the unallocated device group 164, the virtual tapes cannot be formed as designated by the user; consequently, the processing returns to step 1111 to have the user re-designate the number of virtual tapes and their respective capacities.

[0081] In step 1113, the storage device system 0 receives from the user via the management console 7 the designation information regarding in which library the virtual tapes created should be entered. Due to the fact that a plurality of virtual tape libraries can be defined in the storage device system 0 and that one virtual tape management table 210 corresponds to each virtual tape library, the designation in step 1113 determines in which virtual tape management table 210 the virtual tapes are to be registered.

[0082] In step 1114, the device management section 115 searches the unallocated device management table 220 and selects the appropriate disk 16. The virtual tape library section 114 assigns tape numbers to the disk 16 selected, determines the start LBAs and end LBAs corresponding to the capacities designated by the user in step 1111, and allocates slots; in this way, the virtual tape library section 114 allocates the virtual tapes to the disk 16 selected.

[0083] In step 1115, the device management section 115 registers the tape numbers allocated to the virtual tapes in step 1114 in the virtual tape management table 210 that corresponds to the virtual tape library designated in step 1113. Furthermore, the device management section 115 registers in the virtual tape management table 210 the slot numbers allocated to the virtual tapes in step 1114, the sizes of the virtual tapes designated by the user in step 1111, the disk number of the disk 16 selected in step 1114, and the start LBAs and the end LBAs allocated in step 1114. In the pointer 217 of the virtual tape management table 210, an initial value “0” is stored. The device management section 115 updates the contents of the unallocated device management table 220 and ends the virtual tape allocation processing.

[0084] FIG. 9 is a diagram of an example of a processing to define a virtual tape library device. In the storage device system 0, virtual tape library devices that emulate actual tape library devices can be defined. Since each tape library device has a set number of tapes and a set number of tape drives that can be stored, as well as a set number of robots, depending on the product/model of various vendors, the user must first designate the name of the device to be emulated.

[0085] In step 1201, the user through the management console 7 designates the product name/model to be emulated, and the storage device system 0 receives the information. Since this determines the number of slots, the number of tape drives and the number of robots, the virtual tape library section 114 in step 1202 creates the virtual tape management table 210 based on the name of the device to be emulated it has received. In step 1203, the user designates via the management console 7 the WWNs and LUNs of the virtual tape drives and the virtual robots, and the storage device system 0 receives the information. In step 1204, the virtual tape library section 114 checks to make sure that there are no problems with the information; if there are no problems, the virtual tape library section 114 creates the virtual tape drive table 230 and the virtual robot table 240, registers the WWNs and LUNs designated in step 1203 (step 1205), and ends the processing.

[0086] In the storage device system 0, the disks 16 that belong to the disk device group 161 or the file system group 162, and virtual tapes that are no longer necessary can be reallocated to another group. For example, when there is an increase in the amount of write data from the NAS clients 3, the disks 16 that belong to the file system group 162 must be increased in number; however, if there are no disks 16 with the capacity required in the unallocated device group 164, a part of the disks 16 registered in the virtual tape device group 163 can be transferred to the file system group 162. In this case, one of the disks 16 that belongs to the virtual tape device group 163 is registered in the unallocated device group 164 first, and the allocation processing shown in FIG. 8 is executed.

[0087] FIG. 10 is a diagram of an example of a processing by the device management section 115 to return one of the disks 16 currently registered in the disk device group 161, the file system group 162 or the virtual tape device group 163 to the unallocated device group 164.

[0088] A return request takes place when the user instructs the return to the storage device system 0 via the management console 7.

[0089] First, in step 1301, based on the input information from the user, the device management section 115 determines whether the disk 16 that belongs to one of the disk device group 161 and the file system group 162 is to be returned to the unallocated device group 164; if so, the device management section 115 receives from the user via the management console 7 the device number of the disk device or the NAS device to be returned (step 1302).

[0090] Next, the device management section 115 deletes the entry that corresponds to the device number from the disk management table 200, registers the information of the disk 16 with the device number in the unallocated device management table 220, and ends the processing (step 1303).

[0091] If it is determined in step 1301 that the disk 16 to be returned is one of the disks 16 currently being used as a virtual tape, the processing proceeds to step 1305 and the device management section 115 receives the tape number from the user via the management console 7.

[0092] Next, the device management section 115 refers to the tape in 234 column of each entry in the virtual tape drive table 230 and determines whether the virtual tape is loaded in a tape drive (step 1306). If it is loaded, the device management section 115 determines that the virtual tape is currently being used and ends the processing due to error. If the virtual tape is not loaded, the device management section 115 deletes from the virtual tape management table 210 the entry corresponding to the tape number received in step 1305, registers the disk 16 that comprises the deleted virtual tape in the unallocated device management table 220, and ends the processing (step 1307).

[0093] If the virtual tape to be returned is a virtual tape that occupies only a part of the regions of the disk 16 and if an entry corresponding to the disk 16 already exists in the unallocated device management table 220, the device management section 115 updates the start LBA 223 and the end LBA 224 of the entry corresponding to the disk 16 and ends the processing.

[0094] Using FIG. 11 and subsequent figures, a description is made as to a flow of processing that takes place when a virtual tape library device is operated by the hosts 2, as well as a flow of backup/restore processing using a virtual tape library device.

[0095] First in FIG. 11, a flow of processing that takes place when a command arrives from one of the hosts 2 to the storage device system 0 concerning an instruction to a tape drive or a robot of the tape library device, as well as a processing to write data to the virtual tape library device, is described.

[0096] The virtual tape drive and the virtual robot operate according to SCSI Stream Commands, which are commands for SCSI sequential access type devices, or SCSI Media Changer Commands, which are commands for SCSI media changer type devices, as stipulated by ANSI that the storage device system 0 receives from the hosts 2 via the Fibre Channel interface 62. FIG. 11 shows an example of processing that takes place when a command requesting a processing to load a tape into a tape drive and a command requesting a processing to write data to a tape are issued.

[0097] First in step 1501, the block I/O receiving section 68 of the storage device system 0 receives, from one of the hosts 2, a MOVE MEDIUM command, which requests a tape to be taken out of a slot in the library device and to be loaded into a tape drive. The block I/O receiving section 68 sends the MOVE MEDIUM command received to the virtual tape library section 114.

[0098] Let us assume, for example, that the MOVE MEDIUM command is a command that instructs to move the virtual tape stored in the slot whose slot number 212 is 2 in the virtual tape management table 210 in FIG. 4, i.e., the virtual tape whose tape number 211 is 3, to the virtual tape drive whose drive number 231 is 1 of the virtual tape drives managed by the virtual tape drive table 230.

[0099] In step 1502, in order to establish a state in which the virtual tape is loaded on the virtual tape drive, the virtual tape library section 114 writes 3, which is the tape number of the virtual tape to be loaded, in the tape in 234 entry of the virtual tape drive whose drive number 231 is 1 in the virtual tape drive table 230.

[0100] In step 1503, the block I/O receiving section 68 of the storage device system 0 receives from the host 2 a write command for the tape drive whose drive number is 1. Since the write command is a command for the virtual tape drive, the block I/O receiving section 68 sends the command to the virtual tape library section 114.

[0101] In step 1504 and step 1505, in order to write data on the virtual tape currently loaded in the virtual tape drive whose drive number is 1, the virtual tape library section 114 specifies the tape number of the virtual tape loaded in the virtual tape drive, and further specifies, based on the tape number, the device number of the disk 16 that corresponds to the virtual tape and the LBA at which to begin writing. The write data is written to the virtual tape beginning at the specified LBA.

[0102] Specifically, the virtual tape library section 114 first refers to the virtual tape drive table 230, and ascertains, due to the fact that 3 is written in the tape in 234 that corresponds to the virtual tape drive whose drive number 231 is 1, that data should be written to the virtual tape whose tape number is 3. Next, the virtual tape library section 114 refers to the virtual tape management table 210 and recognizes that write data should be written to the disk 16 whose device number is 102, since the device number of the disk 16, which corresponds to the virtual tape whose tape number 211 is 3, is 102 (step 1504).

[0103] In step 1505, the virtual tape library section 114 refers to the pointer 217 of the virtual tape management table 210 and determines the LBA at which to begin writing. The virtual tape library section 114 then issues a write request to the disk system 1 to write data beginning at the LBA determined. Upon receiving the write request from the virtual tape library section 114, the disk access processing section 111 writes the write data to the storage region beginning with the LBA determined of the disk 16 whose device number 214 is 102.

[0104] When the write processing is completed, the virtual tape library section 114 in step 1506 updates the value of the pointer 217 in the virtual tape management table 210 and ends the processing. In other words, the virtual tape library section 114 shifts the pointer 217 rearward by an amount equal to the size of the write data.

[0105] Next, referring to FIGS. 12 through 16, a backup/restore processing of NAS data is described.

[0106] In those disks 16 that belong to the file system group 162, file systems are formed by the file service 67 and accessed by the NAS clients 3 on a file-by-file basis. Backups of NAS data are made by the backup service 69's following instructions from the backup server 31 to back up data onto virtual tapes. In the backup processing according to the present embodiment, commands according to NDMP (Network Data Management Protocol) between the backup server 31 and the backup service 69 are used to send and receive commands and information required for the backup/restore processing; however, the execution of the backup processing is not limited to this mode. The NDMP stipulates a method for the backup server 31 and the backup service 69 to communicate with each other via LAN in order to send and receive SCSI commands for controlling tape drives and library robots, and a command format regarding backup/restore commands.

[0107] FIGS. 12 and 13 indicate diagrams of an example of a processing executed primarily by the backup service 69 in a backup processing of NAS data. The first processing to take place in the backup processing is a virtual tape loading processing, as in the processing shown in FIG. 11. For this reason, in the backup processing shown in FIGS. 12 and 13, the block I/O receiving section 68 and the virtual tape library section 114 perform a processing similar to the processing in steps 1501 and 1502 in FIG. 11 to prepare the virtual tape.

[0108] Next, the backup service 69 receives from the backup server 31 a command instructing a backup. At the same time, the backup service 69 receives the name of the file system to be backed up and information regarding the virtual tape drive to be used in the backup through such means as command parameters or environmental variables (step 2001).

[0109] In step 2002, the backup service 69 searches, from the mounting names 206 of the disk management table 200, for the name of the file system to be backed up that was received in step 2001, and specifies the device number to be backed up.

[0110] In step 2003, the backup service 69 refers to the virtual tape drive table 230 and obtains, based on the information regarding the virtual tape drive to be used in the backup and received in step 2001, the tape number of the tape currently loaded in the virtual tape drive. The backup service 69 then refers to the virtual tape management table 210 and obtains, based on the tape number, the device number of the disk 16 that corresponds to the virtual tape. At this time, the backup service 69 sets the value of the corresponding option flag 218 to 1 in the virtual tape management table 210 as a flag indicating the virtual tape as the tape to be used in the backup of NAS data.

[0111] In step 2004 and subsequent steps, the backup service 69 instructs the disk system 1 to activate the mirror/split section 112, in order to utilize the mirror/split section 112 of the disk system 1 to execute a copy processing from the disk 16 to be backed up to the disk 16 comprising the virtual tape, which is the backup destination. The mirror/split section 112 can create copies not only of an entire disk 16, but also of specific regions of one of the disks 16. Consequently, when issuing a copy instruction, the backup service 69 designates the backup start LBA and end LBA of the backup source disk 16 (i.e., a NAS device) and the start LBA and end LBA of the backup destination disk 16 (i.e., a virtual tape) in its instruction to activate the mirror/split section 112.

[0112] In step 2004, the backup service 69 first determines whether or not the capacity of the virtual tape is larger than the capacity of the disk 16 to be backed up. If it is larger, the backup service 69 instructs the disk system 1 to copy all data stored on the backup source disk 16 to the backup destination disk 16 (step 2005).

[0113] If the capacity of the virtual tape is smaller than the capacity of the backup source disk 16, the processing proceeds to the processing beginning with step 2006, which is a copy processing of backup data spanning a plurality of virtual tapes. The processing beginning with step 2006 is described using FIG. 13.

[0114] In step 2006, the backup service 69 instructs the disk system 1 to copy data stored in a part of the storage regions of the backup source disk 16 to the backup destination disk 16 that makes up a virtual tape. The copy size is matched to the size of the virtual tape.

[0115] In step 2007, the backup service 69 sets the option flag 218 corresponding to the backup destination virtual tape in the virtual tape management table 210 to 2. The option flag 218 has the value 1 or 2 when NAS data is backed up on the corresponding virtual tape. When the backup data obtained by the backup service 69 cannot be stored on one virtual tape, the value of the option flag 218 becomes 2; when the backup data can be stored on one virtual tape, the value of the option flag 218 becomes 1.

[0116] In step 2008, the backup service 69 determines whether a virtual tape replacement processing is required. If there is data on the backup source disk 16 that has not yet been copied to a virtual tape, it is determined that the virtual tape must be replaced.

[0117] If a virtual tape replacement is required, the processing proceeds to step 2009, where the backup service 69 notifies the backup server 31 that the current virtual tape has reached its end. Upon receiving this notice, the backup server 31 issues a request for a tape replacement processing to the storage device system 0, and the backup service 69 receives the request (step 2010). This request is specifically realized by the backup server 31's issuing a MOVE MEDIUM command or an EXCHANGE MEDIUM command.

[0118] In step 2011, the virtual tape library section 114, upon receiving a command such as the MOVE MEDIUM command or the EXCHANGE MEDIUM command from the backup service 69, updates the virtual tape drive table 230. This processing is virtually identical to step 1502 in FIG. 11.

[0119] When the backup service 69 receives in step 2012 a request to resume the backup processing from the backup server 31, the backup service 69 resumes the backup processing.

[0120] In step 2013, a processing similar to the processing in step 2003 is executed, and the disk 16 that comprises a virtual tape is specified. Subsequently, the processing returns to step 2006 to repeat the processing to copy data stored on the backup source disk 16 to the disk 16 comprising the virtual tape, as well as the virtual tape replacement processing, until all data stored on the backup source disk 16 is copied onto virtual tapes.

[0121] Next, referring to FIGS. 14 and 15, a description is made as to the flow of a processing by the backup service 69 when restoring NAS data from a virtual tape to an NAS device that belongs to the file system group 162.

[0122] In the restore processing, the virtual tape loading processing is performed as in the backup processing shown in FIGS. 12 and 13. For this reason, first, the processing that takes place in steps 1501 and 1502 in FIG. 11 is performed to prepare a virtual tape. After the preparation of the virtual tape is completed, the backup service 69 receives a restore command from the backup server 31 (step 2101), which begins the restore processing by the backup service 69.

[0123] Steps 2102 and 2103 are virtually identical to steps 2002 and 2003, respectively, in FIG. 12, and serve to specify the restore destination disk 16 and the disk 16 that comprises the restore source virtual tape.

[0124] In step 2104, the backup service 69 checks the option flag 218 of the virtual tape management table 210 in order to determine whether backup data, i.e. data currently stored on virtual tape and to be restored, is stored on a plurality of virtual tapes.

[0125] If the backup data is not stored on a plurality of virtual tapes, the processing proceeds to step 2105, where the backup service 69 refers to the virtual tape management table 210 to check whether there are other virtual tapes defined on the disk 16 that comprises the virtual tape in question.

[0126] If there are no other virtual tapes defined on the disk 16 that comprises the virtual tape in question, there should only be the data to be restored on the disk 16; consequently, the restore processing can be completed by simply changing the disk 16 into an NAS device that belongs to the file system group 162. To this end, in step 2106, the backup service 69 switches the disk 16 storing the restore source data, which is currently managed by the virtual tape management table 210, with the restore destination disk 16, which is currently managed by the disk management table 200; this realizes a processing equivalent to the restore processing, and the restore processing ends. Specifically, the backup service 69 switches the device number that corresponds to the restore source virtual tape registered in the virtual tape management table 210 with the device number that corresponds to the restore destination NAS device registered in the disk management table 200, and registers in the virtual tape management table 210 the device number of the disk 16 currently managed as an NAS device and registers in the disk management table 200 the device number of the disk 16 currently managed as a virtual tape.

[0127] When the restore processing ends, the disk 16 that was used as a virtual tape before restoration becomes available for access from the NAS clients 3, while the disk 16 that was formerly available for access from the NAS clients 3 is now treated as a virtual tape.

[0128] If in step 2104 the backup data is determined to be stored spanning a plurality of virtual tapes, or if in step 2105 it is determined that other virtual tapes are defined on the disk 16 that comprises the restore source virtual tape, the processing beginning with step 2111 in FIG. 15 takes place.

[0129] Beginning with step 2111, the data copy processing from the restore source disk 16 to the restore destination disk 16 is performed using the mirror/split section 112 of the disk system 1, as in the backup processing shown in FIGS. 12 and 13. Since a plurality of disk-to-disk copy will be performed, the backup service 69 prepares and manages a disk pointer for storing copy positions.

[0130] In step 2111, the backup service 69 initializes the disk pointer value to 0. Next, in step 2112, the backup service 69 instructs the disk system 1 to activate the mirror/split section 112 to copy data stored on the restore source disk 16 to a restore destination disk 16. A copy instruction is issued by the backup service 69 to the disk system 1, assuming that at this time the copy beginning position (in other words, the position at which writing the backup data begins) on the restore destination disk 16 is an LBA indicated by the disk pointer and that the copy size is identical to the volume of the virtual tape.

[0131] In step 2113, the backup service 69 increases the value of the disk pointer by the number of blocks equivalent to the volume of the virtual tape. In step 2114, the backup service 69 determines whether the disk pointer has reached the end of the restore destination disk 16; it the disk pointer has reached the end of the disk 16, the restore processing ends.

[0132] If the disk pointer has not reached the end of the restore destination disk 16, the virtual tape must be replaced to continue the restore processing; the backup service 69 consequently notifies the backup server 31 that the tape has reached its end (step 2009), and a virtual tape replacement processing according to an instruction from the backup server 31 takes place (steps 2010 and 2011). This processing is identical to the processing that takes place from steps 2009 to 2011 in FIG. 13.

[0133] When the virtual tape replacement processing ends, the backup service 69 receives a request to resume the restore processing from the backup server 31 (step 2115), and specifies the disk 16 that comprises the restore source virtual tape based on the request received to resume restore processing (step 2013). Subsequently, the processing returns to step 2112, and the processing beginning with step 2112 is repeated until all backup data to be restored is restored.

[0134] FIG. 16 describes the flow of a processing for one of the hosts 2 to read the content of a virtual tape that is a backup of NAS data, i.e., the content of one of the disks 16 that belongs to the file system group 162. Steps 1501 and 1502 are the preparation processing, such as loading of a virtual tape, and are the same as the processing that takes place in steps 1501 and 1502 in the processing to write to a virtual tape shown in FIG. 11.

[0135] Next, in step 2303, the block I/O receiving section 68 receives a read command for a virtual tape drive from one of the hosts 2. The read command is then sent to the virtual tape library section 114; in step 2304, the virtual tape library section 114 refers to the virtual tape drive table 230 and the virtual tape management table 210 and specifies, based on the drive number designated in the read command, the device number of the disk 16 that corresponds to the virtual tape to be accessed.

[0136] In step 2305, the virtual tape library section 114 determines whether the content of the virtual tape to be read is a backup of data on one of the disks 16 that belongs to the file system group 162 (i.e., NAS data). This determination can also be made by referring to the option flag 218 of the virtual tape management table 210.

[0137] To read the backup content of NAS data, the file service 69 in step 2306 mounts the disk 16 that comprises the virtual tape and makes the disk 16 available for access as a file system. In step 2307, the file service 31 reads data from the disk 16, creates data in general backup format, such as tar format, and sequentially sends data to the virtual tape library section 114 (step 2308); and the virtual tape library section 114 sends the data to the host 2 via the block I/O receiving section 68 (step 2311).

[0138] If it is determined in step 2305 that the processing is not a processing to read backup data of NAS data, the processing proceeds to step 2310, where the virtual tape library section 114 reads the data using a normal method. In other words, in step 2310, the virtual tape library section 114 reads data from the disk 16 that comprises the virtual tape and sends the data read without any alterations to the host 2 via the block I/O receiving section 68.

[0139] According to the embodiment described, the disk system 1 and the front end server 6 realize the storage device system 0 that has the functions of a disk device, a file server and a tape library; however, the configuration is not necessarily limited to the configuration shown in FIG. 1. For example, a mode in which the disk system 1 and the front end server 6 in FIGS. 1 and 2 may be mounted on one device, or a mode in which the file service 67 and/or the backup service 69 may operate on different devices, can be applications of the present invention.

[0140] According to the storage device system described above, not only a tape device but a library device with a library mechanism can be emulated, which makes it possible to maintain and manage large capacity tape media on a storage device with magnetic disks.

[0141] Furthermore, disks can be treated either as magnetic disks or virtual tapes; since disks that are treated as magnetic disks can be changed to be treated as virtual tapes and disks that are treated as virtual tapes can conversely be changed to be treated as magnetic disks, capacities of magnetic disks and virtual tapes can be freely altered.

[0142] In addition, a disk device, a file service and a tape library device can be consolidated on a single storage device, and volume can be allocated freely among the three.

[0143] Moreover, due to the fact that a data copy function of the disk device can be utilized in the processing to make a backup on the virtual tape device and in the processing to restore data from the virtual tape device, there is no need to read data to a backup server when performing a backup processing or restore processing; this consequently makes high-speed and low-load backup processing and restore processing possible. By realizing the restore processing from a virtual tape to a magnetic disk through making changes in mappings of the virtual tape and the disk, the restore processing can be executed at high-speed and low-load.

[0144] In a storage device system with magnetic tapes in accordance with the present invention, a storage device that emulates a tape library device and that has both the functions of magnetic disks and virtual tapes can be realized. Further, a high-speed backup processing and restore processing can be realized using virtual tapes.

[0145] While the description above refers to particular embodiments of the present invention, it will be understood that many modifications may be made without departing from the spirit thereof. The accompanying claims are intended to cover such modifications as would fall within the true scope and spirit of the present invention.

[0146] The presently disclosed embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims, rather than the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.