JP2004178337A - Storage device system, storage device, computer and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve problems in a disk array device that time required for recognizing thousands of volumes by a computer is extremely long, many memories are occupied and volume recognition/separation processing can not be easily performed. <P>SOLUTION: In one embodiment, a storage device comprises a control part for transmitting a response signal to a computer so as to recognize a virtual drive capable of dealing a non-transport type storage area as a storage medium allowed to be transported and a storage part for storing volume management information indicating correspondence relation between the virtual drive and the storage area. The computer comprises an interface for receiving the response signal and a control part for recognizing the virtual drive capable of dealing the non-transport type storage area as the storage medium allowed to be transported. The control part of the storage device specifies a storage area to be accessed on the basis of an access request from the computer to the virtual drive and the volume management information. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a method for managing and controlling a storage area in a storage device. In particular, in a large-scale storage device represented by a disk array device, the present invention relates to a volume management and control method when the storage device holds a huge number of storage areas (volumes).
[0002]
[Prior art]
In recent years, a disk array device is often used as a storage device for storing program data used by a computer.
[0003]
A disk array device is a storage device that combines a plurality of magnetic disk devices and achieves high performance and high reliability. The disk array device can treat a plurality of magnetic disk devices as one logical storage area (volume) when viewed from the host computer. Furthermore, the volume can be divided into volumes of an arbitrary size, or several volumes can be combined and treated as a larger volume. With the increase in the capacity of magnetic disk devices, a single disk array device can handle thousands of volumes. For example, Non-Patent Document 1 discloses a method of recognizing a volume in the OS.
[0004]
[Non-patent document 1]
(Art Baker), The Windows NT Device Driver Book
[0005]
[Problems to be solved by the invention]
Even if a disk array device can handle thousands of volumes, there is a problem in handling thousands of volumes by connecting them to one computer. Generally, an OS on a computer performs recognition processing of all volumes connected to the computer when the OS is started. In the volume recognition processing, first, an interface board (a Fiber Channel board or a SCSI board is generally used) connected to the computer is detected, and then an identification number (in the case of SCSI, a target While incrementing the number and the logical unit number), the type of the connected volume and the name of the vendor are confirmed by issuing the “INQUIRY command”, and the volume capacity is confirmed by the “READ CAPACITY command”. This volume detection processing is performed for all interface boards connected to the computer. When an appropriate response is received from the volume, the OS creates information for the volume and stores the information in a memory on the computer. The information created here is referred to for accessing the volume thereafter.
[0006]
When thousands of volumes are connected to a single computer, not only does it take time to detect thousands of volumes when the computer starts up, but also information for managing thousands of volumes occupies memory. Will be.
[0007]
Further, a system form called a storage area network (SAN: Storage Area Network) in which storage and computers are connected by a network has come to be used. In the SAN, a plurality of storage devices and a plurality of computers are connected by a fiber channel or Ethernet network ("Ethernet" is a registered trademark of Fuji Xerox Co., Ltd .; the same applies hereinafter). Particularly in the SAN, it is desirable that the correspondence between the computer and the volume can be easily changed in accordance with the processing.
[0008]
An object of the present invention has been conceived in view of the above-described problems. In a storage device system having a storage device and a computer, a configuration in which a storage device (or a storage device group in a SAN) has thousands of volumes has , A program and a method.
[0009]
[Means for Solving the Problems]
In order to achieve the object of the present invention, a storage device system according to an embodiment of the present invention includes a computer, a storage device having a plurality of storage areas for storing data accessed by the computer, and a computer and a storage device. And a management computer for management. The storage device includes a control unit that performs emulation for causing the computer to recognize a virtual drive that can handle the non-transportable storage area as a transportable storage medium, and a correspondence relationship between the virtual drive and the storage area. And a storage unit for storing volume management information indicating the above. The computer also has an interface for receiving the response signal, and a control unit that recognizes a virtual drive that handles the non-transportable storage area as a transportable storage medium based on the response signal. Further, the control unit of the storage device specifies the storage area to be accessed based on the access request to the virtual drive from the computer and the volume management information.
[0010]
It is preferable that the control unit of the computer according to the above-described embodiment further recognizes the storage area connected to the virtual drive as an actual non-transport storage area.
[0011]
It is preferable that the control unit of the storage device of the above-described embodiment receives a switching request for switching the correspondence between the virtual drive and the storage area from the computer, and rewrites the volume management information based on the switching request.
It is preferable that the control unit of the computer according to the above-described embodiment transmits the file system type information of the virtual drive recognized based on the response signal to the management computer.
[0012]
It is preferable that the control unit of the storage device of the above-described embodiment transmits the file system type information of the virtual drive recognized based on the response signal to the management computer.
[0013]
The storage unit of the storage device according to the above-described embodiment further stores, as volume management information, replica information for copying information stored in the first storage region of the storage region to the second storage region, Of the storage area, based on the replica information, duplicates the information stored in the first storage area in the storage area to the second storage area, and issues a request from the computer to retrieve the first storage area from the virtual drive. In this case, it is preferable to stop copying the information stored in the first storage area to the second storage area. Thereby, the first storage area can be handled as copy information at the timing when the first storage area is separated from the virtual drive.
[0014]
BEST MODE FOR CARRYING OUT THE INVENTION
·System configuration
FIG. 1 shows a system configuration according to an embodiment of the present invention.
[0015]
In the system configuration of FIG. 1, the computers 10, 11 and the disk array device 100 are connected via a fiber channel switch 50 (hereinafter, FC switch 50). The FC switch 50 and each device are connected using a fiber channel. In the present embodiment, the computer and the disk array device are connected using Fiber Channel, but may be connected using LAN, for example, Ethernet.
[0016]
The disk array device 100 is provided with FC ports 101 and 102 as connection ports for connecting to the FC switch 50. The virtual removable drives 110 to 113 are virtually provided by being managed in a volume management table 400 described later for each computer. The virtual removable drives 110 and 111 are connected to the computer 10 via the FC port 101, and 112 and 113 are connected to the computer 11 via the FC port 102.
[0017]
The connection switching unit 150 switches the correspondence between the volumes 131 to 135 and the virtual removable drives 110 to 113 according to the contents of a volume management table 400 described later.
[0018]
In this embodiment, the number of FC ports, virtual removable drives, volumes, and disk array devices is not limited as long as it is one or more.
[0019]
The operation management computer 19 is connected to the computers 10 and 11 and the disk array device 100 via a LAN such as Ethernet.
[0020]
The operation management computer 19 communicates with the agent program 360 on the computers 10 and 11. The operation management computer 19 communicates with the control module 190 of the disk array device 100.
[0021]
It is assumed that the administrator monitors the state of the computer system via the operation management computer 19 and performs necessary operations.
[0022]
・ Disk array device
FIG. 2 shows a physical configuration diagram of the disk array device 100.
[0023]
The disk array device 100 is a storage device including FC ports 101 and 102, which are connection ports connected to the FC switch 50, a disk device 290, and a control unit 250.
The disk array device 100 includes a control unit 250 that sends a response signal for causing the computers 10 and 11 to recognize a virtual removable drive that can handle the storage area of the non-transportable disk device 290 as a transportable disk. Have. The control unit 250 receives an access request to the virtual removable drive from the computers 10 and 11, and specifies the storage area of the disk device 290 to be accessed based on the access request and the volume management table 400, and It manages access to data stored in the plurality of storage areas 61 of the device 100.
[0024]
In the case of the present embodiment, 25 disk devices 290 are connected via the disk controller module 220.
[0025]
The control unit 250 includes an FC interface module 200 which is an interface connected to the computers 10 and 11 via the FC ports 101 and 102, and a storage for temporarily storing data and commands received from the computer and data read from the disk device 290. A cache controller 210 for connecting the disk device 290, an array controller 230 for controlling the FC interface module 200, the cache memory 210, and the disk controller module 220, and controlling the array. A control module 190 that communicates with the management computer 19.
[0026]
The array controller 230 manages the correspondence between the disk device 290 and the logical volumes 131 to 135. In the present embodiment, the 25 connected disk devices 290 constitute five logical volumes by combining the five disk devices 290.
[0027]
The cache memory 210 stores a volume management table 400 indicating the correspondence between the virtual removable drive and the storage area of the disk device 290.
[0028]
The disk device 290 is a storage area for storing data accessed by the computers 10 and 11, and is a non-transportable storage area that cannot transport a disk to a driver. The storage area of the disk device 290 is treated as a logical unit volume by the array controller. The disk device 290 may have a plurality of storage areas.
[0029]
The virtual removable drives 110 to 113, the connection switching unit 150, the duplication unit 155, and the virtual changer devices 118 and 119 are realized as a control program executed by the array controller 230.
[0030]
・ Configuration of computer and operation management computer
FIG. 11 is a diagram showing the configurations of the computers 10 and 11 and the operation management computer 19. The computers 10 and 11 and the operation management computer 19 include a CPU (control unit) 1001, a memory 1003 for storing programs to be executed by the CPU 1001 and data necessary for execution, and data between the CPU 1001, the memory 1003 and the bus 1005. It is composed of a chipset 1002 that mediates exchange of data, an FC interface module 1008 connected to the bus 1005, and an Ethernet module 1009. As shown in FIG. 1, the computers 10 and 11 connect to the disk array device 100 from the FC interface module 1008 via the FC switch 50. The agent program 360 on the computers 10 and 11 connects to the operation management computer via the Ethernet module 1009.
[0031]
・ Computer software module configuration
FIG. 3 is a diagram illustrating software modules of the computers 10 and 11.
[0032]
These software modules 300, 310, 320, 331, 332, 333, 339, 360, and 399 are programs stored in the memory 103 of the computers 10 and 11 and executed by the CPU 1001.
[0033]
・ Volume management
FIG. 4 shows the contents of a volume management table 400 indicating the relationship between a virtual removable drive and a volume.
[0034]
The volume management table 400 indicates each volume number, the capacity of each volume, the number of a virtual removable drive that virtually loads each volume (a plurality of virtual removable drives may correspond to one volume), and It has a flag for prohibiting writing to the volume, information indicating the type of the file system of each volume, a number of a secondary volume as a replica volume to be described later, and information indicating the date and time when the secondary volume was detached. . It should be noted that the volume numbers are assigned so as not to be duplicated in the disk array device. Here, for simplicity, the numbers in FIG. 1 will be described as they are as the volume numbers 131 to 135. Also, the numbers of the virtual removable drives are assigned so as not to be duplicated in the disk array device. Similarly, the numbers in FIG. 1 will be described as the virtual removable drive numbers 110 to 113 as they are.
[0035]
Immediately after the disk array device 100 is started, the column of “virtual removable drive number” in the volume management table 400 is set to blank (NULL) as an initial value. This means that a virtual removable drive is not virtually loaded on the volume.
[0036]
FIG. 5 shows display contents of the setting screen 410 on display means (display or the like / not shown) on the operation management computer 19.
[0037]
The operation management computer 19 collects information of the volume management table 400 in the array controller 230 via the control module 190, and displays the contents of the volume management table 400 on the setting screen 410.
[0038]
The administrator can input and operate the contents of the volume management table 400 by using a GUI such as a mouse through the setting screen 410.
[0039]
The display example in FIG. 5 is an image in which a virtual removable drive to load the volume 132 using the mouse cursor 411 is being selected. The number of the virtual removable drive displayed on the pull-down menu 412 can be selected on the mouse cursor 411.
[0040]
The operation management computer 19 instructs the array controller 230 to set / change the contents of the volume management table 400 based on information input by a GUI such as a mouse.
[0041]
The array controller 230 changes the settings of the volume management table 400 based on an instruction from the operation management computer 19.
[0042]
-Disk array device recognition processing
The operation when the computer is started will be described. As shown in FIG. 1, it is assumed that the computer is connected to the already activated disk array device.
[0043]
When the computer is started, the computer searches for devices connected to the computer and recognizes the disk array device 100.
[0044]
The computer issues a confirmation command (for example, an INQUIRY command) to the recognized disk array device 100 to confirm what kind of storage device is connected to the computers 10 and 11.
[0045]
In response to the confirmation command, the disk array device 100 returns the type of the device (whether the device is a magnetic disk device / optical disk device or the disk is removable / fixed), the device name, the vendor name, and the like to the computers 10 and 11. I do.
[0046]
If the disk device connected internally is the disk device 290, the conventional disk array device returns information indicating "magnetic disk device / fixed disk" as the device type. For example, in a disk array device using an FC channel, since a SCSI command is used in many cases, the first byte "00H (1 byte in hexadecimal)" of the data string returned in response to the INQUIRY command corresponds to this.
[0047]
In the disk array device 100 of this embodiment, when the array controller 230 receives a confirmation command from the host computer via the FC interface module 200, it returns "magnetic disk device / removable disk" as the device type. For example, in this case, the first byte of the reply data string for the INQUIRY command is “80H (1 hexadecimal byte)”.
[0048]
The computers 10 and 11 load the device driver 310 corresponding to the device type based on the reply information from the disk array device 100.
[0049]
Usually, a dispatcher 320 for switching a file system is provided on the device driver 310, and a plurality of file systems 331 to 333 are loaded. Thus, a plurality of different file systems can be used for each computer. In the present embodiment, a description will be given on the assumption that the computer 10 can use the file system A 331 and the file system B 332, and the computer 11 can use the file system A 331 and the file system C 333.
[0050]
The file system API 339 is an interface for using an appropriate file system 331 to 333 when the application 399 accesses the disk device 290. This allows the application 399 to access the storage device by a fixed procedure irrespective of the file system.
[0051]
Therefore, the disk array device instructs the host to recognize the fixed disk device as a drive that treats the disk as a removable drive, so that the host loads a driver that treats the fixed disk device as a removable disk. be able to. Thus, the host can recognize the storage area of the non-transport type (fixed type) disk device 290 as a virtual removable drive that can handle the storage area as a transportable disk. Therefore, particularly when the number of volumes is extremely large, the host can recognize the device in units of drives, and thus the resources associated with the device recognition processing can be suppressed.
[0052]
Further, in the embodiment of the present invention, the fixed disk emulation module 350 is provided between the file system API 339 and the application 399. If this module is not provided, the disk array device 100 is recognized as a removable drive by the application 399 using the storage device via the file system API 339. There are databases and the like as applications that use the disk array device. Usually, these applications are prohibited from being constructed on a removable drive.
[0053]
Therefore, when a request for device type identification is issued, the fixed disk emulation module 350 returns “magnetic disk / fixed disk” to the file system. Therefore, the application 399 can recognize the volume connected to the virtual removable drive of the disk array device 100 as the actual type of “magnetic disk / fixed disk”, thereby virtualizing the drive to the application 399. Unreasonable usage restrictions that can occur due to the above can be avoided.
The fixed disk emulation module 350 is not automatically loaded by the OS. This is because the array controller 230 returns “80H” with the INQUIRY command in response to the type confirmation from the computer, and it is possible to determine whether or not the device is a virtual removable storage device from only this information. It is not possible. Generally, an administrator who manages the computers 10 and 11 loads the fixed disk emulation module 350 in accordance with the execution of the application so that the use restriction is not imposed on the application. In order to automate the loading process, the device name and the vendor name are obtained from the information string returned by the INQUIRY command, and if the specific device name and the vendor name are included, the fixed disk emulation module 350 is loaded. It is constituted so that. This can be realized by modifying the OS, or by providing the function to an application or an agent program.
[0054]
・ Description of processing
Now, each process in the present invention will be described. Here, a description will be given assuming that the volume 131 is initialized in the file system A format, the volume 132 is initialized in the file system B format, and the volume 133 is initialized in the file system C format. The volumes 134 and 135 are not used.
[0055]
・ Load processing
FIG. 6 is a flowchart of the volume loading process.
[0056]
The operation management computer 19 receives an instruction to load the volume 132 into the virtual removable drive via the setting screen 410, and instructs the disk array device 100 to execute the received load (601).
[0057]
Upon receiving the volume load instruction, the array controller 230 of the disk array device 100 sets and updates the volume management table 400 via the control module 190 according to the instruction (603). That is, the disk array device 100 sets the volume 132 of the volume management table 400 to the virtual removable drive “110” or “111” loaded on the computer 10 according to the volume load instruction. Here, it is assumed that “110” is set. Next, the operation management computer 19 notifies the application 399 that the volume 132 has been loaded to the virtual removable drive “110” via the host agent 360 on the computer 10 (605).
[0058]
Thereby, the array controller 230 can access the volume 132 of the virtual removable drive 110 based on the access (read / write processing or the like) request by executing the application 399 and the volume management table 400. Here, since the volume 132 is initialized in the format of the file system B, the volume 132 is accessed using the file system B 332.
[0059]
Eject processing (volume disconnection)
FIG. 7 is a flowchart of a volume ejection process (volume disconnection).
[0060]
The operation management computer 19 receives an instruction to eject the volume 132 from the setting screen 410. That is, the operation management computer 19 receives an instruction to invalidate the relationship between the volume 132 and the virtual removable drive via the setting screen 410 (701).
[0061]
The operation management computer 19 instructs the agent program 360 on the computer 10 to disconnect the volume 132 from the virtual removable drive (703).
[0062]
The agent program 360 notifies the application 399 of the disconnection of the volume (705).
[0063]
When the application 399 rejects the request, the agent program 360 notifies the operation management computer 19 of the rejection, and the disconnection fails (709).
[0064]
When the application 399 permits the disconnection, the agent program 360 instructs the file system via the file system API 399 to eject the volume 132 (711).
[0065]
Upon receiving the eject request, the file system flushes out all the data in the buffers and caches of the file system or the like (713), and sends an eject command (START in SCSI) to the disk array device 100 via the removable device driver 310. A STOP UNIT command is issued (sets a bit for ejection) (715).
[0066]
Upon receiving the eject command via the FC interface module 200, the array controller 230 of the disk array device 100 clears (for example, inputs NULL) the virtual removable volume in the volume management table 400 corresponding to the volume 132 (717). As a result, there is no correspondence between the volume 132 and the virtual removable drive 110 in the volume management table 400.
[0067]
When clearing the virtual removable volume in the volume management table 400, the array controller 230 reports the completion of the ejection to the removable device driver 310 of the computer 10 (719).
[0068]
Upon receiving the completion of the ejection, the removable device driver 310 reports the completion of the ejection to the file system (721).
[0069]
Upon receiving the completion of the ejection, the file system reports the completion of the ejection to the agent program 360 as a reply of the file system API 399 (723).
[0070]
The agent program 360 notifies the operation management computer 19 of the completion of disconnection (725).
[0071]
Upon receiving the disconnection completion notification, the operation management computer 19 reads the volume management table 400 via the control module 190 and confirms that the volume 132 has been disconnected (727).
[0072]
As described above, in the embodiment of the present invention, a volume can be easily ejected only by rewriting the volume management table 400 of the disk array device 190. As a result, the application 399 cannot access the volume 132 of the virtual removable drive 110.
[0073]
Therefore, the array controller of the disk array device provides a volume management table indicating the correspondence between drives and volumes, and the array controller determines the volume to be accessed based on the access request from the host to the drive and the volume management table. Can be identified. Therefore, it is possible to easily change the volume of the fixed disk device from the computer 10 to the computer 11 only by rewriting the volume management table 400 of the disk array device 190.
[0074]
Further, for example, when the volume 133 is loaded on the virtual removal drive 110 loaded on the computer 10, the volume 133 is ejected from the virtual removal 110 of the computer 10 in the management table 400, and the virtual removal 112 of the computer 11 is deleted. , 113 by loading the volume 133, the volume 133 that could be used by the computer 10 can be used by the computer 11, and the volume can be easily replaced.
[0075]
・ Registration of file system type in volume management table 400
The operation management computer 19 receives a file system type detection request through the GUI.
[0076]
Upon receiving the file system type detection request, the agent program 360 acquires the file system information of the currently loaded volume via the file system API 339.
[0077]
Next, the agent program 360 calls a removable device driver, and issues a confirmation command (for example, an INQUIRY command) for each type of the currently loaded volume to the disk array device 100.
[0078]
The disk array device 100 returns the volume number of each volume based on the confirmation command.
[0079]
As a result, the agent program 360 can acquire the volume number of each currently loaded volume.
[0080]
Therefore, the agent program 360 can return the file system type information and the volume number of each currently loaded volume to the operation management computer 19.
[0081]
The operation management computer 19 sets and registers file system type information for each volume in the volume management table 400 based on the received information.
[0082]
・ Use of file system type information
The agent program 360, upon receiving a notification request of the available file system type from the operation management computer 19, returns the type information of the available file system.
[0083]
Thereby, the operation management computer 19 acquires, from the agent program 360, the type information of the file system that can be used in the computers 10 and 11. In this embodiment, the computer 10 reports that the file system is the file system A and the file system B, and the computer 11 reports that the file system is the file system A and the file system C.
[0084]
A computer that can be used for each volume can be specified based on the type information information of the available file system for each computer and the information of the volume management table 400. Specifically, the computers that can use the volume 131 are the computers 10 and 11, the computers that can use the volume 132 are only the computer 10, and the computers that can use the volume 133 are the computers. It can easily be specified that there is only 11.
[0085]
Therefore, on the setting screen 410, if the volume format does not match the file system available on the computer, and the computer cannot be used even if a specific volume is loaded into the volume management table 400, the volume management table 400 A process for suppressing the load process for a specific volume may be provided.
[0086]
・ Double load
Since the volume 131 has the format of the file system A, it can be used by the computers 10 and 11.
[0087]
When the volume is already used by the computer 10, even if the operation management computer 19 instructs to load the volume 131 into the virtual removable drive 112, the load request fails because the volume is already being used.
[0088]
However, if the operation management computer 19 sets a write inhibit flag for the volume 131 in advance, the computers 10 and 11 may be allowed to use the volume 131 at the same time. This is because if no data is written to the volume 131, it is used by a plurality of computers and there is no problem.
[0089]
When the volume 131 is loaded on two computers, the write prohibition flag cannot be cleared from the setting screen 410.
・ Replica volume
A replica volume (replica volume) refers to a volume that records exactly the same data string on two different volumes. Here, description will be made assuming that the volumes 134 and 135 are replica volumes. The replica volume has a primary / secondary relationship, and in this embodiment, the volume 134 is treated as primary and the volume 135 is treated as secondary.
[0090]
The operation management computer 19 receives the specification of the volume number and its replica volume number by using the GUI, and instructs the array controller 230 to make the specification. For example, assume that “135” is designated as the replica volume number of the volume 134.
[0091]
The array controller 230 sets “135” as the replica volume number of the volume 134 in the volume management table 400 according to the instruction.
[0092]
As a result, the duplication unit 155 connects the volume 134 and the volume 135, and the writing of data generated in the volume 134 is performed in synchronization with the volume 135.
[0093]
-Loading of uninitialized volumes
The loading process for the volumes 134 and 135 that have not been initialized by the computer 10 or 11 will be described.
[0094]
The operation management computer 19 receives an instruction to load the volume 134 into the virtual removable drive via the GUI.
[0095]
Upon receiving the load instruction, the disk array device 100 sets and updates the volume management table 400 via the control module 190 according to the instruction. Here, the disk array device 100 sets and changes the volume 134 to the virtual removable drive “110” or “111” in the volume management table 400. Here, it is assumed that the value is set and changed to “110”.
[0096]
Here, since the volume 134 is in an uninitialized state, the operation management computer 19 accepts the designation of a desired file system type via the GUI. Here, it is assumed that "File system A" is specified.
[0097]
The operation management computer 19 instructs to set and update the volume management table 400 via the control module 190 according to the received specification of the file system type.
[0098]
The array controller 230 of the disk array device 100 sets and updates the volume management table 400 according to the instruction.
[0099]
On the other hand, the operation management computer 19 instructs the host agent 360 to initialize the volume 134 in the format of the file system A.
[0100]
The host agent 360 initializes the volume 134 in the format of the file system A via the file system API 399.
[0101]
The host agent 360 reports the completion of the file system format to the operation management computer 19.
[0102]
When receiving the format completion report, the operation management computer 19 notifies the application 399 that the volume 134 has been loaded via the host agent 360 on the computer 10.
[0103]
As a result, the array controller 230 can access the initialized volume 134 of the virtual removable drive 110 based on the access request of the application 399 and the volume management table 400. Since the volume 134 is initialized in the format of the file system A, the volume 134 is accessed using the file system A 331. In addition, since the writing of the same data string as that of the volume 134 has occurred in the volume 135 set as a sub-volume of the volume 134, the volume 135 is also initialized in the file system A format.
[0104]
-Purpose and issues of replica volume
Next, processing for separating the primary and secondary relations of the replica volume will be described.
[0105]
For example, if the primary volume 134 and the secondary volume 135 are separated at a certain time T, the secondary volume is a copy of the volume 134 at the time T and can be used as a backup at the time T. In the processing at the time of disconnection, it is an essential condition that the state of the volume is completed as a file system. That is, if data that has not yet been written to the volume remains in the buffer or cache of the file system or the like, it cannot be used as a backup at time T.
・ Separation of positive and secondary
FIGS. 8 and 9 are flowcharts for explaining the primary / secondary disconnection processing of the replica volume.
[0106]
First, the operation management computer 19 receives a request for primary / secondary disconnection of a replica volume from the GUI and instructs the array controller 230. For example,
It is assumed that the primary volume 134 and the secondary volume 135 are separated at a certain time T.
[0107]
Upon receiving the instruction, the array controller 230 clears the replica volume number “135” of the volume 134 in the volume management table 400 (801).
[0108]
Next, the operation management computer 19 instructs the agent program 360 on the computer 10 to disconnect the volume 134 from the virtual removable drive (803).
[0109]
The agent program 360 notifies the application 399 that the volume 134 is to be disconnected (805).
[0110]
When the application 399 rejects the request, the application 399 notifies the operation management computer 19 of the rejection, and the disconnection fails (809).
[0111]
When the application 399 permits the disconnection, the agent program 360 instructs the file system to eject the volume 134 (811).
[0112]
Upon receiving the eject request, the file system flushes all data in the buffer or cache of the file system or the like (813). Next, the removable device driver 310 sends an eject command (START in SCSI) to the array controller 230. A STOP UNIT command is issued (setting a bit for ejection) (815).
[0113]
Upon receiving the eject command, the array controller 230 refers to the volume management table 400, confirms that the request is to disconnect the volume 135 (replica volume number “135” is cleared in the volume management table 400), and copies the data. The connection between the volumes 134 and 135 is released by the means 155 (817).
[0114]
Further, the array controller 230 holds the time at which the volume was disconnected in the volume management table 400 (818).
[0115]
The array controller 230 reports the completion of the ejection to the removable device driver 310 of the computer 10 (819), but the volume 134 remains loaded on the virtual removable drive 110 (the virtual removable drive number is “134”). as it is).
[0116]
The removable device driver 310 reports the completion of the ejection to the file system (821), and the file system reports the completion of the ejection to the agent program 360 (823).
[0117]
The agent program 360 notifies the application 399 that the volume 134 has been loaded again (824).
[0118]
Upon receiving the disconnection completion notification from the agent program 360 (825), the operation management computer 19 reads the volume management table 400 via the control module 190 and confirms that the volume 135 has been disconnected (827).
[0119]
The array disk device 100 updates the setting screen 410 based on the volume management table 400 (829). On the setting screen, the time when the disconnection is performed is displayed.
[0120]
Further, a write prohibition flag may be set as necessary.
[0121]
As described above, the primary and secondary separation of the replica volume can be more easily performed between the volume 134 and the volume 135, and the problem that the separated volume is incomplete and cannot be used can be eliminated. Further, the secondary volume 134 can also be used as a backup at the time when the raw volume 135 is disconnected.
[0122]
Since the volume 135 is in the format of the file system A, it can be used from the computer 11. As described above, by adding the type information of the copied file system to the duplicate volume, it is possible to determine which computer can use the duplicate volume. If the write prohibition flag is set, the computers 10 and 11 can use the computers simultaneously.
[0123]
・ Variation of file system type detection
In the above-described embodiment, the file system type is detected by the agent program 360 provided on the host computer. However, the file system type may be detected by the file system identification unit 151 provided in the array controller 230 of the disk array device 100. good.
[0124]
The file system identification means 151 periodically searches the contents of the volume in the disk array device, searches a data string set in advance via the control module, and identifies the type of the file system based on the search result. .
[0125]
In this case, by using the file system identification means provided in the disk array device, it is not necessary to develop software for identifying the file system corresponding to various OSs.
・ Variation of load processing for control module
In the above-described embodiment, which volume is loaded into the virtual removable drive has been described using the volume management table 400. As another method, a MOVE command defined by a SCSI command via the FC interface module may be used. In the MOVE command, an application, a GUI of the operation management computer 19, and the like can be used to specify which drive is loaded with which media as an element number. As the element number, the virtual removable drive number or volume number shown in the above embodiment can be used.
[0126]
To use the MOVE command, the operation management computer 19 is connected to the FC switch 50 as shown in FIG.
[0127]
In the disk array device 100, virtual changer devices 118 and 119 are provided for FC ports 101 and 102, respectively.
[0128]
The virtual changer devices 118 and 119 are realized as a control program executed inside the array controller 230.
[0129]
Upon receiving the MOVE command, the array controller 230 updates the volume management table 400 based on the element number specified in the command.
[0130]
Thus, by allocating identifiers (element numbers) to the volume and the virtual removable drive and performing volume connection switching, it is possible to perform volume connection switching using the SCSI MOVE command.
[0131]
In the embodiment of the present invention described above, the volume is managed according to the volume management table 400 indicating the relationship between the volume and the drive to be virtually loaded, so that even a computer using a disk array device having thousands of volumes Never mount on volumes. Therefore, the amount of occupied memory required for mounting the volume can be reduced, and the boot time of the computer can be reduced.
[0132]
In the connection device (for example, FC switch 50) that controls the correspondence between the computers 10 and 11 and the storage device 100, a configuration that realizes the function realized by the control unit 250 of the disk array device 100 described above is adopted. May be.
[0133]
【The invention's effect】
According to the present invention, in a storage system having a storage device and a computer, it is possible to provide a configuration, a program, and a method including thousands of volumes of a storage device (or a storage device group in a SAN).
[Brief description of the drawings]
FIG. 1 is a diagram of a computer system showing an embodiment of the present invention.
FIG. 2 is a diagram showing a hardware configuration of the disk array device.
FIG. 3 is a diagram showing a software configuration on a computer.
FIG. 4 is a diagram showing a configuration of a volume management table.
FIG. 5 is a diagram showing a configuration of a setting screen.
FIG. 6 is a diagram showing a flowchart of a loading process.
FIG. 7 is a diagram showing a flowchart of a disconnection process.
FIG. 8 is a diagram showing a flowchart of a detaching process of a replica volume.
FIG. 9 is a diagram showing a flowchart of a detaching process of a replica volume.
FIG. 10 is a diagram of a computer system illustrating an embodiment of the present invention using a virtual changer device.
FIG. 11 is a configuration diagram of a computer and an operation management computer.
[Explanation of symbols]
10-11 computer, 19 operation management computer, 50 FC switch, 100 disk array device, 101 FC port, 102 FC port, 110-113 virtual removable drive, 118-119 virtual changer device, 131 -135: volume, 150: connection switching means, 151: file system identification means, 155: copying means, 190: control module, 200: FC interface module, 210: cache memory, 220: disk controller module, 230: array controller, 290: magnetic disk device, 300: OS, 310: removable device driver, 320: dispatcher, 331: file system A, 332: file system B, 333: file system C, 39 ... file system API, 350 ... fixed disk emulation module, 360 ... agent program 400 ... volume management table, 410 ... setting screen, 411 ... mouse car sole, 412 ... pull-down menu

Claims (13)

A storage system comprising a computer and a storage device having a plurality of storage areas for storing data accessed by the computer,
The storage device,
A control unit that transmits a response signal to the computer so as to recognize a virtual drive that can be treated as a non-transportable storage area as a transportable storage medium,
A storage unit for storing volume management information indicating the correspondence between the virtual drive and the storage area,
The calculator is:
An interface for receiving the response signal;
A control unit that recognizes the virtual drive based on the response signal,
A storage device system, wherein the control unit of the storage device specifies the storage area to be accessed based on an access request to the virtual drive from the computer and the volume management information. The storage device system according to claim 1, wherein:
The control unit of the computer,
Furthermore, the storage system is characterized in that the storage area associated with the virtual drive is recognized as an actual non-transport type storage area. The storage device system according to claim 1, wherein:
The control unit of the storage device,
A storage system, wherein a switching request for switching a correspondence between the virtual drive and the storage area is received from the computer, and the volume management information is rewritten based on the switching request. The storage device system according to claim 1, wherein:
The control unit of the computer,
A storage system, wherein the type information of the file system of the virtual drive recognized based on the response signal is transmitted to the management computer. The storage device system according to claim 1, wherein
The control unit of the storage device,
A storage system, wherein the type information of the file system of the virtual drive recognized based on the response signal is transmitted to the management computer. The storage device system according to claim 1, wherein
The storage unit of the storage device,
Replica information for copying information stored in a first storage area of the storage area to a second storage area as the volume management information,
The control unit of the storage device,
Based on the replica information, a request is issued from the computer to copy information stored in a first storage area to a second storage area, and to retrieve the first storage area from a virtual drive from the computer. In this case, the copying of the information stored in the first storage area to the second storage area is stopped, so that the first storage area is treated as copy information at a timing when the first storage area is separated from the virtual drive. A storage device system, characterized in that: A storage device having a plurality of storage areas for storing data accessed by a computer,
A control unit that transmits a response signal to the computer so as to recognize a virtual drive that can be treated as a non-transportable storage area as a transportable storage medium,
A storage unit for storing volume management information indicating the correspondence between the virtual drive and the storage area,
The storage device, wherein the control unit specifies the storage area to be accessed based on an access request to the virtual drive from the computer and the volume management information. A computer that accesses data stored in a plurality of storage areas of a storage device,
From the storage device, an interface for receiving a response signal for recognizing a virtual drive capable of treating the non-transportable storage area as a transportable storage medium,
A control unit that recognizes the virtual drive based on the response signal. A connection device for controlling a correspondence between a computer and a storage device having a plurality of storage areas for storing data accessed by the computer,
A control unit that sends a response signal for causing the computer to recognize a virtual drive that can handle the non-transportable storage area as a transportable storage medium,
A storage unit for storing volume management information indicating the correspondence between the virtual drive and the storage area,
The connection device, wherein the control unit specifies the storage area to be accessed based on an access request to the virtual drive from the computer and the volume management information. A program for managing access to data stored in a plurality of storage areas of the storage device,
A function of receiving a response signal from the storage device for recognizing a virtual drive that can handle the non-transportable storage area as a transportable storage medium;
A program for causing a computer to implement, based on the response signal, a function of recognizing a virtual drive connected to the non-transportable storage area as a transportable storage medium. A program for managing access to data stored in a plurality of storage areas of the storage device,
A function of giving a response signal to the computer to recognize a virtual drive that can handle the non-transportable storage area as a transportable storage medium;
A function of storing volume management information indicating a correspondence relationship between the virtual drive and the storage area,
A program for causing a computer to realize a function of specifying the storage area to be accessed based on an access request to the virtual drive from the computer and the volume management information. A method for managing access to data stored in a plurality of storage areas of a storage device,
Receiving a response signal from the storage device for recognizing a virtual drive that can handle the non-transportable storage area as a transportable storage medium;
Recognizing a virtual drive that connects the non-transportable storage area as a transportable storage medium based on the response signal. A method for managing access to data stored in a plurality of storage areas of a storage device,
A step of giving a response signal to the computer to recognize a virtual drive that can handle the non-transportable storage area as a transportable storage medium;
Storing volume management information indicating the correspondence between the virtual drive and the storage area;
Specifying the storage area to be accessed based on the access request to the virtual drive from the computer and the volume management information.

Images