Source: http://www.google.com/patents/US20040250021?dq=5,583,822
Timestamp: 2016-06-26 17:41:22
Document Index: 451463517

Matched Legal Cases: ['art 22', 'art 25', 'art 20', 'art 20', 'art 22', 'art 20', 'art 22', 'art 20', 'art 22', 'art 22', 'art 20', 'art 20', 'art 20', 'art 20', 'art 22', 'art 20', 'arts 7', 'art 20', 'art 7', 'art 81', 'art 82', 'art 7', 'art 73', 'art 72', 'art 7', 'art 7', 'art 72', 'art 20', 'art 20', 'art 53', 'art 82', 'art 7', 'art 7', 'art 7', 'art 7', 'art 7', 'art 7', 'art 7', 'art 7', 'art 7', 'art 7', 'art 7', 'art 7', 'art 7', 'art 7', 'art 7', 'art 7', 'art 7', 'art 7', 'art 7', 'art 20', 'art 20', 'art 20']

Patent US20040250021 - Virtualization controller and data transfer control method - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsEmbodiments of the present invention are directed to systems and methods of controlling data transfer between a host system and a plurality of storage devices. One embodiment is directed to a virtualization controller for controlling data transfer between a host system and a plurality of storage devices....http://www.google.com/patents/US20040250021?utm_source=gb-gplus-sharePatent US20040250021 - Virtualization controller and data transfer control methodAdvanced Patent SearchPublication numberUS20040250021 A1Publication typeApplicationApplication numberUS 10/882,797Publication dateDec 9, 2004Filing dateJun 30, 2004Priority dateNov 25, 2002Also published asUS7263593, US7366853, US7694104, US7877568, US8190852, US8572352, US20040103261, US20060195676, US20070162721, US20070192558, US20120297159Publication number10882797, 882797, US 2004/0250021 A1, US 2004/250021 A1, US 20040250021 A1, US 20040250021A1, US 2004250021 A1, US 2004250021A1, US-A1-20040250021, US-A1-2004250021, US2004/0250021A1, US2004/250021A1, US20040250021 A1, US20040250021A1, US2004250021 A1, US2004250021A1InventorsKiyoshi Honda, Naoko Iwami, Kazuyoshi SerizawaOriginal AssigneeHitachi, Ltd.Export CitationBiBTeX, EndNote, RefManPatent Citations (99), Referenced by (66), Classifications (23), Legal Events (2) External Links: USPTO, USPTO Assignment, EspacenetVirtualization controller and data transfer control method
US 20040250021 A1Abstract
Embodiments of the present invention are directed to systems and methods of controlling data transfer between a host system and a plurality of storage devices. One embodiment is directed to a virtualization controller for controlling data transfer between a host system and a plurality of storage devices. The virtualization controller comprises a plurality of first ports for connection with the plurality of storage devices each having a storage area to store data; a second port for connection with the host system; a processor; and a memory configured to store volume mapping information which correlates first identification information used by the host system to access a first storage area in one of the storage devices, with second identification information for identifying the first storage area, the correlation being used by the processor to access the first storage area. When data stored in the first storage area is transferred to a second storage area in one of the storage devices, the processor correlates the first identification information with a third identification information for identifying the second storage area and registers the first identification information and the third identification information in the volume mapping information. Images(24) Claims(36)
BRIEF DESCRIPTION OF THE DRAWINGS [0013] [0013]FIG. 1 shows an example of a computer system according to the present invention. [0014] [0014]FIG. 2 shows programs and information which are stored in the recording medium of the managing unit, as an example. [0015] [0015]FIG. 3 shows programs and information which are stored in the recording medium of the virtualization controller, as an example. [0016] [0016]FIG. 4 shows an example of volume mapping information which is managed by the virtualization controller according to the first embodiment of the present invention. [0017] [0017]FIG. 5 shows an example of storage device state management information which is managed by the virtualization controller according to the first embodiment. [0018] [0018]FIG. 6 outlines how a request for access to a virtual storage device from the host compute is processed according to the first embodiment of the present invention. [0019] [0019]FIG. 7 outlines the process of data transfer between storage devices according to the first embodiment. [0020] [0020]FIG. 8 shows another example of volume mapping information which is managed by the virtualization controller according to the first embodiment. [0021] [0021]FIG. 9 shows an example of the process which is performed by the routing processor of the virtualization controller according to the first embodiment. [0022] [0022]FIG. 10 shows an example of the process which is performed by the data transfer processor of the virtualization controller according to the first embodiment. [0023] [0023]FIG. 11 shows an example of the process which is performed by the storage device monitor of the virtualization controller according to the first embodiment. [0024] [0024]FIG. 12 shows an example of volume mapping information which is managed by the virtualization controller according to the second embodiment. [0025] [0025]FIG. 13 outlines how the host computer accesses a virtual storage device according to the second embodiment. [0026] [0026]FIG. 14 shows an example of the process of data transfer between storage devices according to the second embodiment. [0027] [0027]FIG. 15 shows an example of volume mapping information which is managed by the virtualization controller according to the third embodiment. [0028] [0028]FIG. 16 shows how a virtual volume is configured according to the third embodiment, as an example. [0029] [0029]FIG. 17 shows an example of the process which is performed to introduce a virtualization controller in a computer system according to the second embodiment. [0030] [0030]FIG. 18 shows an example of volume management information which is managed by the host computer according to the second embodiment. [0031] [0031]FIG. 19 shows an example of a computer system according to the fourth embodiment. [0032] [0032]FIG. 20 shows an example of programs and information which are stored in the storage medium of the virtualization controller according to the fourth embodiment. [0033] [0033]FIG. 21 shows different access paths between a host computer and a storage according to the fourth embodiment. [0034] [0034]FIG. 22 shows an example of volume mapping information which is managed by the virtualization controller according to the fourth embodiment. [0035] [0035]FIG. 23 shows an example of routing control information which is managed by the virtualization controller according to the fourth embodiment. [0036] [0036]FIG. 24 shows an example of the frame data routing process according to the fourth embodiment. [0037] [0037]FIG. 25 shows an example of volume mapping information which is managed by a port section (In Port) according to the fourth embodiment. [0038] [0038]FIG. 26 shows an example of volume mapping information which is managed by a storage control part according to the fourth embodiment. [0039] [0039]FIG. 27 shows an example of volume mapping information which is managed by a port section (Out Port) according to the fourth embodiment. [0040] [0040]FIG. 28 shows an example of volume mapping information which is managed by a port section (In Port) according to the fourth embodiment. [0041] [0041]FIG. 29 shows an example of volume mapping information which is managed by a storage control part according to the fourth embodiment. [0042] [0042]FIG. 30 shows an example of volume mapping information which is managed by a port section (Out Port) according to the fourth embodiment.
DETAILED DESCRIPTION OF THE INVENTION Embodiment 1 [0043] A first embodiment of the present invention will be explained referring to FIGS. 1 to 12. [0044] [0044]FIG. 1 shows one example of a computer system according to the present invention. The computer system has a plurality of host computers 1, a plurality of storage devices 3, a virtualization controller 2 which is connected with the host computers 1 and storage devices 3, and a managing unit 4. The host computers 1 and storage devices 3 are connected with the virtualization controller 2 via a network 5, while the managing unit 4 is connected with the virtualization controller 2 via a network 6. The networks 5 and 6 may use the same network protocol or different network protocols. It is also possible that in the network 5, the protocol for connection between the storage devices and the virtualization controller is different from that for connection between the host computers and the virtualization controller. Also, a different network protocol may be used to connect each storage device or each host computer with the virtualization controller 2. [0045] Each of the host computers 1 has a CPU 10 for execution of an application program, a memory 11 for storage of the application program, a recording medium 12 and a port 13 which is connected to the network 5 to receive or send data. [0046] The managing unit 4 has a CPU 40 which executes a management program for management of the virtualization controller 2, a memory 41 for storage of the management program, a port 43 which is connected to the network 6 to receive or send data, and a recording medium 42. [0047] Each of the storage devices 3 has the following components: a port 33 which is connected to the network 5 to receive or send data; a disk device group 34 which includes a plurality disk devices 35; a disk interface controller 32 (HDD I/F in FIG. 1) which processes data transmission with each disk device 35; a CPU 30 which controls each access to a disk device 35 in response to an access request from a host computer 1; and a buffer 31 which stores data to be transmitted between a host computer 1 and a disk device 35. [0048] The virtualization controller 2 is a switch which transmits frames between the host computers 1 and storage devices 3. The virtualization controller 2 has the following components: a plurality of ports 23 for data transmission with the host computers 1 or storage devices 3; a path control part 22 which controls path selection for the plurality of ports 23; a managing part 25 which handles data transmission to or from the managing unit 4; and a main control part 20 which controls the virtualization controller according to data transmitted with the managing unit 4. The main control part 20 has a memory 51 and a recording medium 52 which store a program (discussed hereinbelow) and information, and a CPU 50 which executes the program using this information. FIG. 1 shows a situation in which the path control part 22 is connected with the CPU 50, memory 51 and recording medium 52 in the main control part 20 via a bus. However, it may also be possible that the path control part 22 and the main control part 20 are connected by means of a bridge. [0049] Although FIG. 1 shows a situation in which that the host computer 1, storage devices 3 and managing unit 4 each have one port, the number of ports is not limited thereto and they may have more than one port. Furthermore, the ports 23 of the virtualization controller are compatible with different network protocols so the ports 23 may be used as managing ports. [0050] Each of the storage devices 3 may at least have a port 33 which is connected to the network 5 to receive or send data, and an area for storage of data to be accessed from a host computer 1; therefore it may be a separate disk device or the like. [0051] [0051]FIG. 2 shows, as an example, programs which are stored in the recording medium 42 of the managing unit 4 and read into the memory 41 and executed by the CPU 40, and management information which is stored in the recording medium 42 of the managing unit 4. [0052] A volume management program 414 is a program which is executed to read volume mapping information 515 (discussed hereinbelow) from the virtualization controller 2 and send it to an output device to inform an administrator of the volume mapping information 515 or receive, from the administrator through an input device, information to be newly registered in the volume mapping information 515 or updating information for the volume mapping information, and send it to the virtualization controller 2 and set the information received from the administrator in the volume mapping information 515. Volume mapping management information 411 includes volume mapping information 515 read from the virtualization controller 2 and registration or updating information received from the administrator. A volume manager 401 is implemented in that the CPU 40 of the managing unit 4 executes the volume management program 414 using the volume mapping management information 411. [0053] Here, a volume refers to a storage area which is managed by each storage device (including a virtual storage device); it is possible for one storage device to manage more than one volume. Hereinafter, volumes which are managed by the storage devices 3 are called “real volumes” and volumes which are managed by the virtualization controller 2 are called “virtual volumes.”
[0054] A storage device management program 415 is a program which is executed to read storage device state management information 512 (discussed hereinbelow) from the virtualization controller 2 and send it to an output device to inform the administrator of the state of a storage device or receive, from the administrator through an input device, information to be registered in the storage device state management information 512 or updating information, and set the information on the virtualization controller 2. Storage device management information 412 includes storage device state management information 512 received from the virtualization controller 2 and registration or updating information received from the administrator. A storage device manager 402 is implemented in that the CPU 40 of the managing unit 4 executes the storage device management program 415 using the storage device management information 412. [0055] A data transfer management program 416 is a program which is executed to generate data transfer control information 413 to transfer data between volumes under the control of the virtualization controller 2, issue a data transfer request containing data transfer control information 413 to the virtualization controller 2, receive the result of processing for data transfer from the virtualization controller 2 and inform the administrator of the result. A data transfer manager 403 is implemented in that the CPU 40 of the managing unit 4 executes the data transfer management program 416. [0056] [0056]FIG. 3 shows, as an example, programs which are stored in the recording medium 52 of the virtualization controller 2 and read into the memory 51 and executed by the CPU 50, and management information which is stored in the recording medium 52 of the virtualization controller 2. [0057] A routing processor 501 performs the following two routing tasks for frame data which is transmitted between a host computer 1 and a storage device 3. [0058] Here, frame data includes all information such as access request information sent from the host computer 1 to the storage device 3, status information sent from the storage device 3 to the host computer 1, and data which is transmitted between the host computer 1 and the storage device 3 according to access request information. [0059] A real routing processor 504 controls routing of frame data transmitted directly between the host computer 1 and the storage device 3 according to routing information 514 as information on interconnection of devices connected to the network 5. In other words, the real routing processor 504 instructs the path control part 22 on which path to be used for frame data transmission. As instructed by the real routing processor 504, the path control part 22 transmits frame data. The real routing processor 504 is implemented in that the CPU 50 of the virtualization controller 2 executes a routing program 516 read in the memory 51 according to routing information 514. [0060] Then, according to volume mapping information 515 (discussed hereinbelow), a virtualization routing processor 505 (hereinafter called the virtualization processor) processes the frame data received from the host computer 1 as explained later and sends it to the storage device 3 or processes the frame data received from the storage device 3 as explained later and sends it to the host computer 1. The virtualization processor 505 is implemented in that the CPU 50 of the virtualization controller 2 executes a virtualization routing program 517 read in the memory 51 according to the volume mapping information 515. [0061] [0061]FIG. 1 and FIG. 2 show an embodiment in which the virtualization controller 2 has one main control part 20 and the main control part 20 carries out a routing process including a virtualization process. However, the present invention is not limited thereto. An alternative approach may be that each of the ports 23 has a processor which performs the routing process. This will enable parallel routing operation at each port, thereby improving the performance of the virtualization controller 2. It is also possible that the routing processor consists of hardware only. [0062] A storage device monitor 502 in FIG. 3 monitors the state of each storage device 3 which is an object of virtualization control by the virtualization controller 2, holds the result of monitoring as storage device state management information 512, in the event of detection of a change in the state of a storage device 3, informs the managing unit 4 of the change in the state, and updates the storage device state management information 512 held by itself according to the storage device management information 412 received from the managing unit 4. The storage device monitor 502 is implemented in that the CPU 50 of the virtualization controller 2 executes a storage device monitoring program 518. [0063] A data transfer processor 503 stores data transfer control information 413 which is included in the data transfer request received from the managing unit 4, in the memory 51 or recording medium 52 of the virtualization controller 2 as data transfer control information 513, and performs the process of data transfer between volumes under the control of the virtualization controller 2 according to the data transfer control information 513. The data transfer processor 503 is implemented in that the CPU 50 of the virtualization controller 2 executes a data transfer program 519. Details of the data transfer process will be given later. [0064] [0064]FIG. 4 shows an example of volume mapping information 515 which is managed by the virtualization controller 2. The volume mapping information 515 is control information which shows mapping (correlation) between virtual volumes and real volumes. The virtual volume management information 520 includes virtual volume identification information and information representing a virtual volume state. Virtual volume identification information includes Port ID, unique in the network, Port Name, unique to each port, and LUN (Logical Unit Number), unique in the device. Information representing a virtual volume state includes Size, which indicates the capacity of a virtual volume, and virtual volume Status information. The real volume management information 521 includes information for identifying the real volume corresponding to a virtual volume and information representing a real volume state. Real volume identification information includes Port ID, unique in the network, Port Name, unique to each port, and LUN, unique in the device. Information which represents a real volume state includes Size, which indicates the capacity of a real volume, and real volume Status information. [0065] Here, Port ID and Port Name as virtual volume identification information are identifiers assigned to a virtual port (hereinafter a “virtual port”) of a storage device virtually shown to the host computer 1 (hereinafter “virtual storage device”). For instance, when the host computer specifies Port ID of a virtual port and LUN of a virtual volume and sends frame data, the virtualization processor 505 of the virtualization controller 2 controls the process in a way that according to volume mapping information 515, the frame data is sent to the storage device having the real volume corresponding to the virtual volume identified by Port ID and LUN. However, it appears to the host computer as if it were accessing the storage device having a port identified by Port ID specified by it. [0066] [0066]FIG. 4 shows a case that the virtual volume identified by LUN=0 which is accessed through the virtual port identified by Port ID=V_Pid_1, Port Name=V_Pname_1 is mapped to (correlated with) the real volume identified by LUN=0 which is accessed through the real port identified by Port ID=P_Pid_1, Port Name=P_Pname_1. [0067] A virtual port may have a plurality of virtual volumes. In the case shown in FIG. 4, the virtual port identified by Port ID=V_Pid_2, Port Name=V_Pname_2 has two virtual volumes, LUN=0 (5 GB), LUN=1 (5 GB), which are mapped to real volumes identified by Port ID=V_Pid_2, Port Name=V_Pname_2, LUN=0 (5 GB) and Port ID=V_Pid_1, Port Name=V_Pname_1, LUN=1 (5 GB), respectively. [0068] An example of control which uses status information will be described later. [0069] [0069]FIG. 5 shows an example of storage device state management information 512 which is managed by the virtualization controller 2. The storage device state management information 512 has identification information for a storage device detected by the storage device monitor 502 and the real volume managed by this storage device. In this example, the storage device state management information 512 includes identification information such as Port ID which is assigned to a storage device port and unique in the network, Port Name, unique to each port, Node Name, unique to each storage device, and LUN which is assigned to each real volume in the storage device and unique in the device, as well as real volume state information such as Size. Although FIG. 5 shows a case that Port ID, Port Name, Node Name, LUN and Size information are shown as the storage device state management information 512, the storage device state management information 512 is not limited thereto. For example, it is possible to register information on ports of the virtualization controller 2 connected with real volumes as the storage device state management information 512. [0070] [0070]FIG. 5 shows a case that the port identified by Port ID=P_Pid_1, Port Name=P_Pname_1, Node Name=P_Nname_1 has the real volumes identified by LUN=0 (10 GB), LUN=1 (5 GB) and the port identified by Port ID=P_Pid_2, Port Name=P_Pname_2, Node Name=P_Name_2 has the real volume identified by LUN=0 (5 GB), and the port identified by Port ID=P_Pid_3, Port Name=P_Pname_3, Node Name=P_Nname_3 has the real volume identified by LUN=1 (10 GB). [0071] Here, real volume identification information (LUN) or identification information for ports having real volumes (Port ID, Port Name, Node Name) can be used as an entry for real volume management information 521 of the volume mapping information 515 or as an entry for routing information 514. It is desirable that the storage device state management information 512 can be set by the managing unit 4. In the present invention, as described above, when the CPU 40 of the managing unit 4 executes the storage device management program 415, the managing unit 4 can set storage device state management information 512. [0072] Furthermore, when a new storage device is connected to the virtualization controller 2, the CPU 50 of the virtualization controller 2 executes the storage device monitoring program 518 to obtain Port ID, Port Name, Node Name, LUN, and Size information from the newly connected storage device and register it in the storage device state management information 512 and inform the managing unit 4 of detection of the new device. Preferably the virtualization controller 2 should not execute the process of routing to the new device (should not make a registration into an entry for the routing information 514) until the managing unit executes the volume management program 414 and sets status information of the virtual volume management information 520 of the volume mapping information 515. [0073] On the other hand, when a storage device already connected with the virtualization controller 2 is disconnected, or when the virtualization controller 2 detects a problem that a storage device does not respond or a similar problem, the virtualization controller 2 updates the information registered in the storage device state management information 512 and informs the managing unit 4 of the change in the state of the storage device. At this time the virtualization controller 2 refers to the virtual volume management information 520 of the volume mapping information 515. It is desirable that only when the status information satisfies a certain condition (for example, only when there is a change in the state of a device whose status information is set as “Active”) should it inform the managing unit 4 of the change in the state. It is also possible that one storage device has more than one port, though such a case is not shown in FIG. 5. [0074] [0074]FIG. 6 outlines how an access request is processed when the host computer 1 accesses a storage device virtualized by the virtualization controller 2 (virtual storage device). As shown in FIG. 6, the host computer 1 issues a request for access to the virtual volume LUN=0 (10 GB) of the virtual volume identified by Port ID=V_Pid_1, Port Name=V_Pname_1, among the virtual volume group 60 which includes a plurality of virtual volumes virtualized by the virtualization controller 2. [0075] The routing processor 501 detects that the access request issued from the host computer 1 to the virtual volume is a request for access to a virtual storage device. In this embodiment, when the routing processor 501 detects that Port ID in the access request is included in the virtual volume management information of the volume mapping information 515, the request is found to be a request for access to a virtual storage device. Then, the virtualization processor 505 refers to Port ID and LUN which are included in the access request; and the access request is converted into a request for access to the real volume registered in the volume mapping information 515 which corresponds to the Port ID and LUN. Then the converted access request is issued to the storage device 3. The virtualization processor 505 carries out the abovementioned conversion of the access request by converting the Port ID and LUN included in the access request issued from the host computer 1 into Port ID and LUN of the corresponding real volume registered in the volume mapping information 515. [0076] After this, a series of operations, including data reception/transmission between the host computer 1 and the storage device 3 and transmission of status information, are carried out through the virtualization controller 2. In data reception/transmission, transmission of status information, etc., frame data which is transmitted between the host computer 1 and the storage device 3 is also converted by the virtualization processor 505. Here, conversion does not mean conversion of data itself but conversion of information added to data such as destination (receiver) identification information (D_ID), source (sender) identification information (S_ID), error detection code CRC (Cyclic Redundancy Check) and the like. For example, if the virtualization controller 2 receives an access request with D_ID=V_Pid_1 from the host computer 1, the routing processor 501 converts its D_ID into P_Pid_1 using volume mapping information, newly generates CRC, adds it to the frame data and sends the converted frame data to the storage device 3. On the other hand, if the virtualization controller 2 receives frame data with S_ID=P_Pid_1 from the storage device 3, the routing processor 501 converts its S_ID into V_Pid_1, replaces the CRC in the frame data by the newly generated CRC and sends the frame data to the host computer 1. [0077] [0077]FIG. 7 outlines how the real volume of a storage device 3 correlated with a virtual volume which the virtualization controller 2 provides to the host computer, is changed to the real volume of another storage device and the mapping (correlation) between the virtual and real volumes is revised. In this case, data transfer is made from the former real volume so far correlated with the virtual volume to the real volume to be newly correlated with the virtual volume. [0078] [0078]FIG. 7 shows a case that a request for storing (transferring) data stored in the real volume identified by Port ID=P_Pid_1, Port Name=P_Pname_1, LUN=0 into the real volume identified by Port ID=P_Pid_3, Port Name=P_Pname_3, LUN=1 arises under a certain condition and the administrator issues a data transfer request through the managing unit 4 to the virtualization controller 2. The data transfer request issued from the managing unit contains data transfer control information 413 including information for identifying the source and destination real volumes for data transfer (Port ID, Port Name, LUN, etc.). [0079] In the virtualization controller 2 which has received the data transfer request, the data transfer processor 503 of the main control part 20 analyzes data transfer control information and performs processing for data transfer according to the result of the analysis. In other words, as in the case shown in FIG. 7, under the control of the data transfer processor 503, the virtualization controller 2 issues a data transfer (copy) request to the storage device 3 having the real volume identified by Port ID=P_Pid_1, Port Name=P_Pname_1, LUN=0. This data transfer request contains information for identifying the destination real volume for data transfer (Port ID=P_Pid_3, Port Name=P_Pname_3, LUN=1 in the case shown in FIG. 7). The storage device having the port identified by P_Pid_1 which has received the data transfer request, sends the data stored in the real volume identified by LUN=0 to the real volume identified by Port ID=P_Pid_3, Port Name=P_Pname_3, LUN=1. The storage device having the port identified by P_Pid_3 stores the frame data received from the storage device having the port identified by P_Pid_1, in the real volume identified by LUN=1. Data transfer is thus performed by copying the data from the storage device with the port identified by P_Pid_1 to the storage device with the port identified by P_Pid_3. [0080] After completion of the data transfer process, the data transfer processor 503 enters the destination real volume ID in the volume mapping information 515 and also updates the status information in the virtual volume management information 520 and enters the updated information. One example of volume mapping information 515 which has undergone such updating and entry is shown in FIG. 8. [0081] [0081]FIG. 8 shows an example of volume mapping information 515 revised as a result of the data transfer process shown in FIG. 7, where the real volume mapped to (correlated with) the virtual volume identified by Port ID=V_Pid_1, Port Name=V_Pname_1, LUN=0 is changed from the real volume identified by Port ID=P_Pid_1, Port Name=P_Pname_1, LUN=0 (source real volume) to the real volume identified by Port ID=P_Pid_3, Port Name=P_Pname_3, LUN=1 (destination real volume). [0082] [0082]FIG. 8 shows that the real volume identified by Port ID=P_Pid_1, Port Name=P_Pname_1, LUN=0 (source real volume) and the real volume identified by Port ID=P_Pid_3, Port Name=P_Pname_3, LUN=1 (destination real volume) are registered as the real volumes which are mapped to (correlated with) the virtual volume identified by Port ID=V_Pid_1, Port Name=V_Pname_1, LUN=0. Furthermore, the status information of the virtual volume management information 520 is “Active” for the real volume identified by Port ID=P_Pid_3, Port Name=P_Pname_3, LUN=1 and Inactive for the real volume identified by Port ID=P_Pid_1, Port Name=P_Pname_1, LUN=0. An access request to a virtual volume is executed on a real volume whose status information is “Active”. For example, if the routing processor transmits an access request or frame data according to the volume mapping information 515 shown in FIG. 8, the request for access to the virtual volume identified by Port ID=V_Pid_1, Port Name=V_Pname_1, LUN=0 or data transmission according to this request is executed on the real volume identified by Port ID=P_Pid_3, Port Name=P_Pname_3, LUN=1, depending on the status information of the virtual volume management information 520. [0083] In this embodiment, as mentioned above, when data in a real volume owned by a storage device is transferred to a real volume owned by another storage device, mapping (correlation) between the virtual and real volumes is revised by the data transfer processor 503. However, the identification information which the host computer uses to access a volume is information for identifying a virtual volume (Port ID, Port Name of the virtual port and LUN of the virtual volume) which does not change even when data transfer is made. Let's look at the case of data transfer shown in FIG. 7. When the host computer issues an access request to the virtual volume identified by Port ID=V_Pid_1, Port Name=V_Pname_1, LUN=0, before data transfer the virtualization processor 505 sends the access request to the real volume identified by Port ID=P_Pid_1, Port Name=P_Pname_1, LUN=0 according to the volume mapping information 515 shown in FIG. 4. After data transfer, the virtualization processor 505 sends the access request to the real volume identified by Port ID=P_Pid_3, Port Name=P_Pname_3, LUN=1 according to the volume mapping information 515 shown in FIG. 8. Therefore, according to this embodiment, it is possible to transfer data between storage devices without revising the identification information which the host computer uses to identify the volume to be accessed. [0084] The volume mapping information 515 shown in FIG. 8 contains information for identifying an uncompleted command issued to a real volume. In the case shown in FIG. 8, uncompleted commands C_id_0, C_id_1, C_id_2 are registered in the source real volume identified by P_Pid_1, P_Pname_1, LUN=0 and uncompleted commands C_id_3, C_id_4 (commands to the virtual volume for data transfer which the virtualization controller 2 receives from the host computer after the data transfer processor 503 sends the data transfer request to the source real volume) are registered in the destination real volume identified by Port ID=P_Pid_3, Port Name=P_Pname_3, LUN=1. A command is registered in the volume mapping information by the virtualization controller 2 when the virtualization controller 2 receives it from the host computer, and deleted when the virtualization controller 2 receives, from a storage device, status information or the like which notifies of completion of a process that depends on the command. However, when the virtualization controller 2 sends the data transfer request to the source real volume, it registers a command to the virtual volume for data transfer which it receives from the host computer 1, in an entry for the destination real volume. If the virtualization controller 2 receives status information on completion of a data write command from the source storage device 3 after it sends the data transfer request to the source real volume, it only sets information on completion of the command in the volume mapping information 515 without deleting the registered uncompleted command. The volume mapping information 515 may contain not only information for identifying uncompleted commands but also command information, though omitted in FIG. 8. [0085] In the case shown in FIGS. 7 and 8, data is transferred volume by volume. However, the present invention is not limited thereto. It is also possible to transfer data on a block address basis as far as the volume mapping information 515 holds start/end address information of the source storage device and the start/end address information of the destination storage device. [0086] Also, in the case shown in FIGS. 7 and 8, the data transfer processor 503 issues a data transfer request to one storage device to perform data transfer. However, the present invention is not limited thereto. It is also possible to transfer data, for example, by the data transfer processor 503 issuing a read request to the source storage device and a write request to the destination storage device. [0087] It is desirable that status information of the virtual volume management information 520 can be set or updated by the volume manager 401 of the managing unit 4. [0088] [0088]FIG. 9 shows an example of a frame data transfer process which is performed by the routing processor 501 of the virtualization controller 2. This process starts when the virtualization controller 2 receives frame data from a host computer 1 or storage device 3 (100). The routing processor 501 decides whether virtualization is needed or not, using information for identifying the frame data source/destination included in the frame data (source Port ID, destination Port ID, etc.), and if necessary, the frame data type information included in the frame data and various information (destination LUN, etc.) in the frame payload (101). In this example, if the destination Port ID or LUN is registered in the virtual volume management information 520 of the volume mapping information 515, then the frame data is decided to need virtualization. [0089] If virtualization is needed, the virtualization processor 505 performs the virtualization process (102) explained below. [0090] 1. When the received frame data is frame data from the host computer which is addressed to a virtual storage device: [0091] The virtualization processor 505 detects the storage device which corresponds to the virtual storage device identified by the destination identification information in the frame data according to the volume mapping information 515. In order to convert the frame data received from the host computer into frame data addressed to this storage device, it converts the destination identification information (D_ID) included in the frame data into Port ID of the storage device. It also converts the CRC in the received frame data into CRC which is based on the new destination identification information. The converted frame data is sent to the storage device 3 through a port 23. [0092] 2. When the received frame data is frame data from the storage device mapped to (correlated with) the virtual storage device, which is addressed to the host computer: [0093] The virtualization processor 505 detects the virtual storage device which corresponds to the frame data source storage device according to the volume mapping information 515. In order to convert the frame data received from the storage device into frame data from this virtual storage device, it replaces the source identification information (S_ID) in the frame data by Port ID of the virtual storage device. It also replaces the CRC in the frame data by CRC which is based on the new source identification information. The frame data whose source identification information and CRC have been replaced is sent to the host computer 1 through a port 23. [0094] At the step of making a decision on the need for virtualization as shown in FIG. 9 (101), if the routing processor 501 decides that virtualization is not needed, the real routing processor 504 performs routing of the received frame data according to the routing information 514 (103). [0095] [0095]FIG. 10 shows an example of a data transfer process which is performed by the data transfer processor 503 of the virtualization controller 2. [0096] The data transfer process starts when the virtualization controller 2 receives a data transfer request from the managing unit 4 (110). The data transfer processor 503, which has received the data transfer request, generates data transfer control information 513 according to information which indicates the data transfer source and destination real volumes. The data transfer control information at least has information for identifying the data transfer source and destination real volumes (Port ID, LUN, etc.). The data transfer processor 503 issues an access request (request for data transfer) to the storage device 3 having the source real volume according to the data transfer control information 513 (111). [0097] After issuance of the data transfer request, the data transfer processor 503 waits for notification of completion from each storage device 3 issuing an access request (112). The data transfer processor 503 confirms whether or not the notifications of completion from the storage devices 3 issuing data transfer requests are all notifications of normal completion (113). If the data transfer processor 503 receives a notification of abnormal completion, it is desirable for the data transfer processor 503 to repeat the steps from issuance of an access request (data transfer request) (111) to confirmation of notification of normal completion (113) for the storage device issuing the notification of abnormal completion. [0098] If the data transfer processor 503 receives notifications of normal completion from all the storage devices 3 issuing data transfer requests, then the data transfer processor 503 registers the data transfer destination real volume in the virtual volume management information 520, updates the status information of the virtual volume management information (114) and notifies the managing unit 4 of completion of the data transfer process (115). [0099] In the data transfer process shown in FIG. 10, when the source storage device 3 which receives the data transfer request from the virtualization controller 2 has the following functions, it is guaranteed that the access requests to the source real volume have all been completed when the status information of the virtual volume management information 520 is updated. [0100] If the source storage device 3 receives a write command from the host computer 1 during the data transfer process, it writes data in the recording medium 35 according to the write command and stores the written data in a temporary storage area (escape volume). The escape volume is a storage area in the recording medium of the storage device 3. As part of the data transfer process, the source storage device 3 sends the data stored in the escape volume to the destination storage device 3. Therefore, when the source storage device 3 notifies the data transfer processor 503 of the virtualization controller 2 of completion, there is no uncompleted command for the source real volume and the data revised by writing during the data transfer process has already been sent to the destination storage device. Hence, it is guaranteed that when the data transfer processor 503 updates the virtual volume management information 520, the access requests to the source real volume have all been processed. In this way, data coherence is ensured when data is transferred between real volumes and the real volume mapped to the virtual volume is changed from the source real volume to the destination real volume. [0101] With the abovementioned data transfer process, the virtualization controller 2, which controls data transfer between storage devices, reduces the processing load required of data transfer, by utilizing the functions of the individual storage devices. [0102] Another approach to ensuring data coherence is to use the following method. An entry for registration of a received command is provided for each real volume in the volume mapping information 515 of the virtualization controller 2. Each time the routing processor 501 of the virtualization controller 2 receives a command addressed to the storage device 3 from the host computer, it registers the content of the command in the entry for the real volume to which this command is addressed. When the virtualization controller 2 receives, from the storage device, notification of completion of a process depending on the command, the routing processor 501 deletes the command registered in the volume mapping information 515. On condition that the volume mapping information 515 thus enables the virtualization controller 2 to know the existence of an uncompleted command if any, the data transfer processor 503 of the virtualization controller 2 sends a data transfer request to the storage device 3, then the routing processor 501 of the virtualization controller 2, which has received a command to the virtual volume as the object of data transfer from the host computer 1, temporarily stores this command in the recording medium 52 of the virtualization controller 2. Then, when the virtualization controller 2 receives notification of completion of data transfer from the source storage device 3, the routing processor 501 of the virtualization controller 2 forwards the command stored in the recording medium 52 to the destination real volume. This approach reduces the time required from when the virtualization controller 2 sends a data transfer request to the source storage device 3 until it receives notification of completion of data transfer from this storage device 3. [0103] As stated earlier, after the data transfer processor 503 updates the status information of the virtual volume management information 520, an access request to a virtual volume or data transmission according to an access request is executed on a real volume whose status information in the virtual volume management information 520 is “Active.”
[0104] As discussed so far, for data transfer between storage devices under virtualization control, the virtualization controller 2 updates the volume mapping information 515 so that, without the need for revising the information for identifying the virtual volume which the host computer 1 recognizes as the object of access, the real volume mapped to the virtual volume can be dynamically changed. Therefore, the host computer 1 continues processing for access to the virtual volume without knowing that data transfer between the storage devices (real volumes) has taken place. [0105] In the above embodiment, data coherence is ensured by using the function of the storage device 3 (source) which has received the data transfer request from the virtualization controller 2 (data coherence here implies that when the virtual volume management information 520 is updated, all access requests to the former real volume have been completed). However, the present invention is not limited thereto. [0106] Next, an explanation will be given below of a method which only uses the function of the virtualization controller 2 to detect that all access requests to the former real volume have been completed, as a variation of the above data transfer process. [0107] In this method, an entry for registration of a received command is provided for each real volume. Each time the virtualization controller 2 receives a command addressed to a virtual volume or real volume 3 from the host computer, it registers the content of the command in the entry for the real volume to which this command is to be forwarded. When the virtualization controller 2 receives, from a storage device, status information on completion of a process depending on the command, it deletes the command registered in the volume mapping information 515. The command itself registered in the entry is held in the recording medium 52 of the virtualization controller 2. [0108] When the virtualization controller 2 sends a data transfer request to the storage device 3, it registers the command for the virtual volume as the object of data transfer, in the entry for the destination real volume. After sending the data transfer request, if the virtualization controller 2 detects status information on completion of a data write command from the source storage device 3, it does not delete the command registered in the volume mapping information but registers only information on completion of the process for the command in the volume mapping information. [0109] On condition that there is no uncompleted command for the source real volume (on condition that information on completion of processing is registered for all commands registered in the volume mapping information 515 which concerns the source real volume), the virtualization controller 2 updates the data between the source real volume and the destination real volume according to the data write command held temporarily by the virtualization controller 2 (undeleted command for which information on completion has been registered in the volume mapping information 515). [0110] In other words, for data updating done in the source real volume according to the write command after sending the data transfer request to be reflected in the destination real volume, the virtualization controller 2 controls the source and destination storage devices in a way to write the data updated in the source real volume into the destination real volume. [0111] Furthermore, when updating of data between the source and destination real volumes is completed, the virtualization controller 2 sends the destination real volume the command for the virtual volume (registered in the volume mapping information 515) which it has received after sending the data transfer request. [0112] In the data transfer process, it is also acceptable that the virtualization controller 2 monitors the data write command which is being processed. For example, if writing operation according to a write command issued to the source real volume before issuance of a data transfer request is not performed yet even after start of the data transfer process (transfer of write data between the source storage device and the virtualization controller 2 according to the write command is not started), the virtualization controller 2 aborts the writing operation for the source real volume. Namely, the virtualization controller 2 issues a request for canceling the write command issued to the source real volume, to that real volume and the same write command as the cancelled write command is issued to the destination real volume after completion of data transfer. This permits data transfer with reduced overhead. [0113] Even when the real volume mapped to the virtual volume is changed, the abovementioned method ensures data coherence between the former real volume and the new real volume. [0114] [0114]FIG. 11 shows an example of the process of monitoring the storage device connection state by the storage device monitor 502 of the virtualization controller 2. The storage device monitor 502 of the virtualization controller 2 monitors the connection state of a storage device connected with a port 23. When it detects a change in the connection state, it starts the process shown in FIG. 11 (120). [0115] Each of the storage devices 3 connected with the virtualization controller 2 stores software for notifying the virtualization controller 2 of its status, in its own memory. As this software is executed by the CPU 30 of the storage device, the storage device sends the storage device monitor 502 of the virtualization controller 2 management information such as Node Name, Port Name, Port ID, LUN and Size of the real volume of the storage device. Therefore, the storage device monitor 502 can detect the connection state from the management information received from the storage device. When the storage device is connected with a port 23, the virtualization controller 2 can detect it; and when the storage device is disconnected from the port 23, the virtualization controller 2 can also detect it. In this way, the storage device monitor 502 detects the state of connection between the port and storage device on its own and can detect a change in the state of connection. [0116] Once the storage device monitor 502 has detected a change in the state of connection, it decides whether the change in the state of connection is caused by the addition of a new storage device or other reason (for example, disconnection between the port 23 and storage device) (121). [0117] If a new storage device has been added, the storage device monitor 502 obtains from this storage device the following information for identifying the port of the storage device: Node Name (unique to each device), Port ID (unique in the network), Port Name (unique to each port), LUN (Logical Unit Number, unique in the storage device) as management information for a real volume which is managed by the storage device, and so on. The storage device monitor 502 decides whether Node Name, unique to each storage device, and Port Name, an identifier unique to each storage device port, have already been registered in the storage device state management information 512 (122) and carries out the following steps according to the result of the decision. [0118] If the obtained Node Name and Port Name have already been registered in the storage device state management information 512, the storage device monitor 502 notifies the managing unit 4 that the storage device whose ID has been registered is connected (123) and concludes the series of steps for storage device monitoring. If Port ID (unique in the network) correlated with the Node Name and Port Name obtained from the storage device has already been registered in the storage device state management information 512 by the managing unit 4, it is desirable for the virtualization controller 2 to set this registered Port ID on the storage device. On the other hand, if such Port ID has not been registered, it is desirable for the virtualization controller 2 to assign and set Port ID to the storage device and register the Port ID set on the storage device, in the storage device state management information 512 and notify the managing unit 4 of this Port ID. If the real volume management information which the storage device monitor 502 has obtained from the storage device is different from the management information registered in the storage device state management information 512, the storage device monitor 502 updates the storage device state management information 512 using the obtained management information and notifies the managing unit 4 of the updating. [0119] If the Node Name and Port Name which the storage device monitor 520 has obtained from the storage device have not been registered in the storage device state management information 512, the storage device monitor 502 registers the obtained information in the storage device state management information 512 (124) and notifies the managing unit 4 (123) and concludes the series of steps for storage device monitoring. [0120] If the storage device monitor 502 decides that the change in the connection state is caused by a reason other than addition of a new storage device (for example, deletion of a storage device) at step 121, the storage device monitor 502 decides whether the storage device whose connection state has changed is an object of virtualization control or not (125), and carries out the following steps according to the result of the decision. [0121] If the storage device is to be under virtualization control, the storage device monitor 502 notifies the managing unit 4 of the detected change in the connection state (123) and concludes the series of steps for storage device monitoring. If it is not to be under virtualization control, the storage device monitor 502 carries out a prescribed process according to the network protocol (for example, RSCN (Registered State Change Notification) in Fibre Channel)) (126) and concludes the series of steps for storage device monitoring. [0122] With the abovementioned steps, the virtualization controller 2 monitors the connection state of each storage device 3 connected with the virtualization controller 2, and notifies the managing unit of a change in the connection state, if any. In addition, it can control notification of connection state change according as whether each storage device 3 connected with the virtualization controller 2 is to be under virtualization control or not. Embodiment 2 (Identification of a Storage Device Based on Personal Information) [0123] In the first embodiment, Port ID and Port Name are used as information for identifying the port 33 of a storage device 3. However, the present invention is not limited thereto. Other information may be used for the same purpose as far as it identifies the port 33 of the storage device 3. In the first embodiment, Node Name is used for identifying the storage device 3. Again other information may be used for the same purpose as far as it identifies the storage device 3. For example, it is possible to use, as information for identifying the storage device 3, an identifier used in the device identification page (83h) of vital product data as prescribed by SCSI (Small Computer System Interface). Also, a vendor-specific identifier (hereinafter called “personal information”) may be used as information for identifying a volume. [0124] Next, referring to FIGS. 12 to 14, an explanation will be given below of the data transfer process which is carried out when personal information is used to identify the real volume of the storage device 3 or the virtual volume provided to the host computer by the virtualization controller 2. [0125] [0125]FIG. 12 shows an example of volume mapping information 515 which has entries for registration of personal information. As shown in FIG. 12, the real volumes identified by P_Pid_1 (LUN=0 or 1), P_Pid_2 (LUN=0) and P_Pid_3 (LUN=0) have personal information and the corresponding virtual volumes have personal information in the same way as the real volumes. [0126] Here, the personal information assigned to a virtual volume need not coincide with the personal information of the corresponding real volume (for example, while the virtual volume identified by V_Pid_2 (LUN=0) has personal information “DDD_01,” the corresponding real volume has personal information “BBB_01.”) The personal information assigned to virtual volumes may be generated by the virtualization controller 2 and registered in the volume mapping information 515 as information for identifying the virtual volumes. Even if the real volumes do not have personal information, the virtualization controller 2 can generate personal information for the virtual volumes and register it in the volume mapping information 515. As in the case that the personal information (“AAA_00”) of the virtual volume identified by V_Pid_2 (LUN=1) is the same as that of the corresponding real volume (“AAA_00”), a virtual volume may have the same personal information as the corresponding real volume. [0127] In addition, personal information assigned to a virtual volume need not be revised even if the real volume corresponding to the virtual volume is changed and data transfer is performed. For example, personal information “AAA_01,” assigned to V_Pid_1 (LUN=0, Active) does not coincide with the personal information of the corresponding real volume, “CCC_01,” but coincides with the personal information of the real volume before data transfer, “AAA_1.”. This is because the virtual volume identified by V_Pid_1 (LUN=0, Active) had the same personal information as the corresponding real volume before data transfer and, even after data transfer, inherits the same personal information as that of the source real volume. [0128] [0128]FIG. 13 shows a case that the host computer 1 which uses personal information to identify volumes accesses a volume through the virtualization controller 2. [0129] In the second embodiment, the host computer 1 has a storage device identification processor 15 in addition to the same components as those of the first embodiment. The storage device identification processor 15 is implemented in that the CPU 10 executes a program stored in the memory 11 of the host computer 1. It identifies the volume and storage device to be accessed by the host computer, using personal information. In other words, when accessing a storage device, the storage device identification processor 15 requests the storage devices connected through a network to the host computer to send personal information for identifying the real volumes in the storage devices, and receives the personal information from the storage devices. The storage device identification processor 15 checks the personal information received from the storage devices, against the personal information of the real volume to be accessed which is stored in the memory 11 of the host computer 1. The storage device identification processor 15 decides the storage device which has sent the same personal information as that of the real volume to be accessed, to be the storage device to be accessed. Once the storage device to be accessed is identified with the above-mentioned storage device identifying process, the host computer 1 issues an access request to the identified storage device. [0130] [0130]FIG. 13 shows a case that the host computer 1 accesses the real volume identified by personal information “AAA_01.”
[0131] First, let's assume that the host computer 1 is connected to a storage device with no intermediation of the virtualization controller 2. As shown in FIG. 13, the real volume having personal information “AAA_01” can be accessed through the port of the storage device 3 identified by Port ID=P_Pid_1, Port Name=P_Pname_1. The storage device identification processor 14 receives the personal information “AAA_01” from the storage device 3 which has this port, and thus identifies this storage device 3 as the device to be accessed. Then the host computer 1 issues ail access request to the storage device 3 to be accessed, using the source address information (Port ID=P_Pid_1) and real volume identification information (LUN=0) included in the frame of the received personal information (“AAA_01”). After this, data transmission from the host computer 1 to the storage device 3 according to the access request is made using the frame containing identification information Port ID=P_Pid_1, LUN=0. [0132] Next, let's assume that, as shown in FIG. 13, the host computer 1 is connected to a storage device 3 through the virtualization controller 2 and the storage device is to be under virtualization control. The virtualization processor 505 of the virtualization controller 2 assigns a virtual volume to the real volume of the storage device 3 (registers information for identifying a virtual volume correlated with the real volume, in the volume mapping information 515) and, for the virtual volume, sets the same personal information as the personal information “AAA_01” of the real volume, in the volume mapping information 515. [0133] As a result of the abovementioned operation of the virtualization processor 505, the storage device identification processor 15 of the host computer 1 requests the device connected through the network to send its personal information, and the virtualization controller 2 sends the personal information “AAA_01” to the host computer 1. Therefore, when the storage device identification processor 15 of the host computer 1 receives the personal information “AAA_01” from the virtualization controller 2, it decides that the volume to be accessed is the virtual volume of the virtual storage device identified by the source (sender) address information (Port ID=V_Pid_1) and virtual volume identification information (LUN=0) included in the received frame. Then the host computer sends an access request and data to the virtual volume to be accessed by sending a frame containing identification information Port ID=V_Pid_1, LUN=0. The frame containing identification information Port ID=V_Pid_1, LUN=0 is converted by the virtualization routing processor 505 of the virtualization controller 2 into a frame addressed to the real volume identified by Port ID=P_Pid_1, LUN=0, which is then sent to the storage device 3 having the port identified by Port ID=P_Pid_1. The steps which are taken after the host computer 1 detects (decides) the storage device to be accessed are the same as those in the first embodiment, so a detailed description of these steps is omitted. [0134] As described above, the storage device identification processor 15 of the host computer 1 can detect the storage device or volume to be accessed, using the personal information “AAA_01” set on the virtual volume for the virtual post identified by Port. ID=V_Pid_1, Port Name=V_Pname_1, even when the storage device is under virtualization control of the virtualization controller 2. [0135] In connection with FIG. 13, even if there is a switch dedicated to routing (a switch which does not have the virtualization routing processor 505) between the host computer 1 and the storage device 3, the host computer 1 can recognize a virtual volume as the volume to be accessed, by the same procedure as mentioned above, and the virtualization controller 2 can forward the frame data from the host computer 1 to the real volume corresponding to the virtual volume. [0136] Also, FIG. 13 shows that Port ID (P_Pid_1) for the real volume is different from Port ID (V_Pid_1) for the virtual volume. However, the present invention is not limited thereto. Since Port ID can be assigned to the virtual port by the virtualization controller 2, Port ID for a virtual volume may also be the same (namely Port ID=P_Pid_1) as Port ID of the real port used to access the real volume corresponding to this virtual volume. [0137] [0137]FIG. 14 shows an example of control of personal information in data transfer between storage devices under virtualization control. [0138] The figure concerns a case that the data stored in the real volume identified by Port ID=P_Pid_1 and the personal information “AAA_01” is transferred to the real volume identified by Port ID=P_Pid_3 and the personal information “CCC_01.” In the case shown in FIG. 14, as personal information of the virtual volume, the same information (AAA_01) as the personal information of the real volume correlated with the virtual volume is used. After data transfer, even when the real volume correlated with the virtual volume is changed by the data transfer, the virtualization processor 505 of the virtualization controller 2 inherits the personal information “AAA_01” of the source real volume as the personal information of the virtual volume without any revision. [0139] When the personal information set on the virtual volume before data transfer is inherited after data transfer as explained above, even if the host computer 1 identifies the volume using the personal information, the process of data transfer between the storage devices can be hidden from the host computer 1. Thus, after data transfer, the host computer 1 can identify the volume to be accessed, using the information for identifying the volume to be accessed, which the host computer 1 used before data transfer. As a consequence, even when data transfer between storage devices takes place, the host computer 1 need not stop a process which it is performing and can continue the process. The steps other than the process of inheriting the personal information set on the virtual volume are the same as those in the first embodiment and their description is omitted here. [0140] If the personal information set on the virtual volume is inherited from one virtualization controller to another, the host computer 1 can identify the volume using the personal information while replacement of the virtualization controller is hidden from the host computer 1. As a consequence, the host computer 1 need not stop a process which it is performing and can continue the process. The routing processor 501 of the virtualization controller 2 notifies the volume manager 401 of the managing unit 4 of the personal information of the virtual volume as part of the volume mapping information 515 and stores it in the managing unit 4 as volume mapping management information 411. Hence, when the virtualization controller is replaced, the volume manager 401 of the managing unit 4 notifies the new virtualization controller 2 of the volume mapping management information 411 for the old virtualization controller 2 and sets it in the volume mapping information 515 for the new virtualization controller 2. By doing so, the personal information can be inherited from one virtualization controller 2 to another. [0141] When the virtualization controller is replaced, it is desirable that the virtual port identifier which is managed by the old virtualization controller be also inherited by the new virtualization controller. It is also desirable for the administrator to be able to specify, for the new virtualization controller 2 through the managing unit 4, whether, after data transfer, it inherits the old personal information (or uses the source personal information) without revising the personal information set on the virtual volume or new personal information is set, and so on. [0142] In the second embodiment, it is assumed that the storage devices 3 and the virtualization controller 2 have personal information for each volume (namely personal information is assigned to each volume). However, the present invention is not limited thereto. For example, the storage devices 3 and the virtualization controller 2 may have personal information on a device-by-device basis. Furthermore, although a port is identified by Port ID, Port Name and personal information according to the second embodiment, the invention is not limited thereto. Any method of identifying a port uniquely is acceptable and any combination of various identification information may be used to identify a port. [0143] [0143]FIG. 17 shows the configuration of a computer system in which a host computer and a storage device each have more than one port. The host computer 1 shown in FIG. 17 is different from the one shown in FIG. 13 in that it has a plurality of ports 13 (Hid_1, Hid_2). The storage device 3 shown in FIG. 17 is different from the one shown in FIG. 13 in that it has more than one port 33 (P_Pid1, P_Pid2). [0144] Since the storage device has more than one port, when the storage device identification processor 15 of the host computer 1 requests the storage device 3 to send personal information, the same personal information is sent from the ports. The storage device identification processor 15 stores the plurality of ports which have sent the same personal information, in the memory 11 as volume management information. [0145] [0145]FIG. 18 shows an example of volume management information stored in the memory 11 of the host computer 1. Volume management information is generated by the storage device identification processor 15 as the host computer 1 receives personal information from the storage devices. Volume management information is generated for each storage device and contains the volume number of the real volume owned by the storage device, the personal information of the real volume, the path used for access from the host computer 1 to the real volume, and the status information of the real volume. Here the path information concerns a primary path and a secondary path. The host computer usually uses the primary path to access the real volume; however, if the primary path is in trouble or disconnected, the host computer can use the secondary path to access the real volume. [0146] Referring to FIG. 17, an explanation will be given below of the process of modifying a computer system in which a host computer is connected with a storage device with no intermediation of a virtualization controller, in a way that a virtualization controller is connected between the host computer and storage device without stopping operation of the host computer and the real volume of the storage device is virtualized by the virtualization controller 2 and the virtual volume is provided to the host computer. [0147] First, let's assume that port Hid_1 of the host computer 1 is connected via path 5-a to port P_Pid_1 of the storage device 3 and port Hid_2 of the host computer 1 is connected via path 5-b to port P_Pid_2 of the storage device 3. The volume management information as shown in FIG. 18 is stored in the memory 11 of the host computer 1, and according to this volume management information, the host computer 1 uses the primary path 5-a passing through ports Hid_1 and P_Pid_1 to access the real volume identified by personal information AAA_01, and uses the primary path 5-b passing-through ports Hid_2 and P_Pid_2 to access the real volume identified by personal information AAA_02. [0148] Next are the steps which are taken when the path 5-b is disconnected and a virtualization controller 2 is introduced in the abovementioned computer system. [0149] 1. Since the path 5-b is disconnected, the host computer 1 must change the path for access to the real volume identified by AAA_02 from the path 5-b to the path 5-a. So, in order to temporarily stop access to the real volume identified by AAA_02, the storage device identification processor 15 registers the status information of this real volume in the volume management information as “Inactive.” Under the control of the CPU 10 of the host computer, the path for access to the real volume identified by AAA_02 is switched to the path 5-a which is registered as a secondary path in the volume management information. After switching of the paths, the storage device identification processor 15 returns the status information of the real volume identified by AAA_02 in the volume management information to “Active.” The abovementioned process is performed by the CPU 10 according to an instruction which the user of the host computer gives via an input device such as a keyboard. Alternatively, arrangements may be made that the storage device identification processor 15 automatically performs the process. In other words, it is also possible that the storage device identification processor 15 refers to the volume management information and automatically switches from the primary path to the secondary path. [0150] 2. Next, the path 5-b is disconnected and a virtualization controller 2 is connected between the host computer 1 and the storage device 3. In this case, port Hid_2 of the host computer 1 is connected via path 5-c to port 23 of the virtualization controller 2 and port P_Pid_2 of the storage device 3 is connected via path 5-d to port 23 of the virtualization controller 2. [0151] 3. Once the virtualization controller 2 is connected with the computer system, the volume mapping information 515 for the virtualization controller 2 must be set. In this embodiment, in order to specify the virtual volume to be correlated with the real volume identified by AAA_02 in the storage device 3, the virtualization processor 505 of the virtualization controller 2 registers virtual Port ID (Port ID=V_Pid_01) and virtual Port Name (Pname=V_Pname_1) in the volume mapping information 515 in relation to this real volume. The virtualization processor 505 assigns to this virtual volume the same personal information as the personal information AAA_02 of the corresponding real volume, which is registered in the volume mapping information 515. The volume mapping information is set according to input information which the managing unit 4 receives from the user. In other words, the information which the managing unit 4 receives from the user is sent to the virtualization processor 505 of the virtualization controller 2 under the control of the volume manager 401 and the virtualization processor 505 sets volume mapping information according to that information. [0152] 4. After the volume mapping information 515 has been set, the host computer 1 receives an instruction from the user and requests other devices connected with it to send their personal information. The virtualization controller 2, which has received this request, sends personal information AAA_02 to the host computer. [0153] 5. The host computer 1, which has received the personal information AAA_02 from the virtualization controller 2, knows from the sender address (Port ID=V_Pid_01, etc.) included in the received frame that it has received personal information from a new device. Then, again the storage device identification processor 15 changes the status information of the real volume identified by AAA_02 to “Inactive.” And it changes the primary path for access to the real volume identified by AAA_02 as registered in the volume management information from the path passing through port Hid_2 and port P_Pid_2 to the path passing through port Hid_2 and port V_Pid_01 (virtual port), according to the sender address included in the received frame. Under the control of the CPU 10 of the host computer, this new primary path is now used to access the real volume identified by AAA_02. After switching of the paths, the storage device identification processor 15 returns the status information of the real volume identified by AAA_02 to “Active.”
[0154] Though the volume management information including status information for each volume is shown above, the volume management information can include different types of status information. For example, status information for each access pass (i.e., status information for a primary pass and status information for a secondary pass), which indicates whether or not a real volume can be accessed via each access pass, can be included in the volume management information. Then storage device identification processor 15 can decide which access pass can be used to access the real volume according to the status information. If the host computer has a storage device manager similar to the one which the managing unit 4 has, the host computer can maintain such status information in the volume management information. Once the abovementioned steps have been taken, even after the host computer 1 is connected with the virtualization controller 2, it can identify the real volume of the storage device using the same personal information (AAA_02) as before connection of the virtualization controller 2. Therefore, even when the virtualization controller 2 is newly introduced in the computer system and the host computer issues an access request to the virtual volume, there is no need to set new personal information on the host computer. For this reason, the host computer need not stop a process which it is performing. Embodiment 3 Plurality of Storage Devices Constitute One Virtual Volume [0155] In the first and second embodiments, one real volume constitutes one virtual volume. However, the present invention is not limited thereto and also applicable to a case that plurality of real volumes constitute one virtual volume. [0156] Referring to FIGS. 15 and 16, an explanation will be given below of the case that a plurality of real volumes constitute one virtual volume. [0157] [0157]FIG. 15 shows an example of volume mapping information 515 where the real volume identified by Port ID=P_Pid_1, Port Name=P_Pname_1, LUN=3 (5 GB) and the real volume identified by Port ID=P_Pid_2, Port Name=P_Pname_2, LUN=1 (5 GB) constitute one virtual volume identified by Port ID=P_Pid_3, Port Name=P_Pname_3, LUN=0 (10 GB). The volume management table (FIG. 15) is the same as the one shown in FIG. 12 except that two real volumes are assigned to one virtual volume and address information for the real volumes is added as an entry to the virtual volume management information 520. In the case shown in FIG. 15, the personal information of the real volume identified by Port ID=P_Pid_1, Port Name=P_Name_1, LUN=3 is used as the personal information of the virtual volume identified by Port ID=V_Pid_3, Port Name=V_Pname_3, LUN=0. [0158] [0158]FIG. 16 shows an example of a computer system in which two real volumes constitute one virtual volume. In the computer system shown in FIG. 16, the virtualization controller 2 takes the same steps to deal with data transfer and storage device monitoring as in the first and second embodiments, so only the routing process is explained below. [0159] The routing process begins when the virtualization controller 2 receives frame data from the host computer 1 or storage device 3. The routing processor 501, which has received the frame data, decides whether virtualization is needed or not, using source (sender)/destination (receiver) identification information in the frame data, and if necessary, frame data type and various information (LUN, etc.) as payload in the frame. In a specific example, if the source/destination identification information (Port ID, etc.) and information in the frame payload (LUN) are registered in the virtual volume management information 520 of the volume mapping information 515, the routing processor 501 decides that virtualization is needed. [0160] If the routing processor 501 decides that virtualization is needed, the virtualization processor 505 carries out the following steps for virtualization. [0161] 1. When the received frame data is frame data addressed to a storage device from the host computer: [0162] The virtualization processor 505 decides whether the received frame data is a read/write access request or not. If the frame data is a read/write access request, the virtualization processor 505 identifies the storage device corresponding to the virtual storage device to which the frame data is addressed, according to the volume mapping information 515 and address and data length information in the access request information (payload in the received frame in particular). Then, in order to convert the received frame into a frame for the identified storage device, the destination identification information (D_ID) in the frame data and CRC are replaced by destination identification information indicating the port of the identified storage device, and CRC which is based on the new destination identification information. Furthermore, if necessary, new address information and data length information are generated as access request information. The new frame as a result of conversion is sent to the storage device 3 through a port 23 of the virtualization controller 2. If the access request is to be sent to two storage devices (request for access across address 989680h), the virtualization processor 505 generates an access request for each of the storage devices and sends the request to each storage device. [0163] If the frame data received by the virtualization controller 2 is data (write data) other than a read/write access request, the virtualization processor 505 identifies the storage device corresponding to the virtual storage device to which the frame data is addressed, according to the volume mapping information 515 and, if necessary, address and data length information as the write access request information which the virtualization controller 2 received before reception of the write data, and write data offset information. Then, in order to convert the received frame into a frame for the identified storage device, the virtualization processor 505 replaces the destination identification information (DID) in the frame data and CRC by identification information for the identified storage device, and new CRC which is based on this identification information. The virtualization controller 2 sends the frame to the identified storage device 3 through a port 23. [0164] 2. When the received frame data is frame data addressed to the host computer from a storage device mapped to a virtual storage device: [0165] The virtualization processor 505 decides whether the received frame data is a read data or not, and takes steps depending on the type of frame data. For example, if the frame data is read data, the virtualization processor 505 identifies the virtual storage device corresponding to the storage device which has sent the frame data. Then, in order to convert the received frame into a frame from the identified virtual storage device, the virtualization processor 505 replaces the source (sender) identification information (S_ID) in the frame data and CRC by identification information for the virtual storage device, and CRC which is based on the new destination identification information. The virtualization controller 2 sends the frame to the host computer 1 through a port 23. [0166] When two storage devices send read data according to one read access request simultaneously, it is desirable that until forwarding of the data received from one storage device to the host computer is completed, the virtualization controller 2 suspend forwarding of the read data received from the other storage device. For example, if the virtualization controller 2 receives read data from the storage device with the real volume identified by P_Pid_1, P_Pname_1, LUN=3 (5 GB) and the storage device with the real volume identified by P_Pid_2, P_Pname_2, LUN=1 (5 GB), the virtualization controller 2 temporarily stores the read data from the storage device with the real volume identified by P_Pid_2, P_Pname_2, LUN=1 (5 GB) to suspend forwarding of the read data. Moreover, when two storage devices send response data according to one read access request, the virtualization controller 2 generates one response data based on the two response data received from the two storage devices, and sends the generated response data to the host computer. [0167] In the abovementioned computer system in which more than one real volume constitute one virtual volume, data can be transferred between storage devices under virtualization control without revising the identification information for the volume which the host computer recognizes as the volume to be accessed, as in the first and second embodiments. More specifically, like the first and second embodiments, as data transfer is done between storage devices, the virtualization controller 2 updates the volume mapping information 515 and changes the real volume correlated with the virtual volume from the data transfer source real volume to the data transfer destination real volume, so the real volume mapped to the virtual volume is dynamically changed without revising the identification information for the volume which the host computer 1 recognizes as the volume to be accessed. Thus, the host computer 1 can continue its operation without knowing the data transfer which takes place between storage devices (real volumes). Embodiment 4 Intelligent Ports Provide Virtualization Control and Storage Functions [0168] In the above embodiments, the main control part 20 of the virtualization controller 20 which functions as a switch executes all processes according to the present invention. However, the present invention is not limited thereto. Alternatively, it is possible that each of the ports 23 has a processor which performs the routing task. [0169] Furthermore, the virtualization controller 2 is not limited to one which only incorporates ports 23, a path control part 22 and a main control part 20. For example, like a disk array controller in a disk array system, it is possible to control the system in a way that a host computer recognizes plural physical disk devices as a single logical storage. Another approach is that the virtualization controller 2 has a storage control function as follows: parity data as redundant data is added to the data being accessed by a host computer and the data is stored on a disk and the virtualization controller 2 has a storage control part to perform parity control and other related tasks to enable data transfer with the host computer using the parity data even if a disk device fails. It is also possible that the virtualization controller 2 has the function as a storage (storage function) by incorporating a storage control part and a storage group composed of plural storages such as disk devices. [0170] Next, referring to FIGS. 19 to 22, an explanation will be given concerning a case that the virtualization controller has a storage control part and a storage group to provide a storage function and its constituent parts or components process their respective tasks. [0171] [0171]FIG. 19 shows an example of a computer system according to the present invention. The components other than the virtualization controller 2 are the same as those shown in FIG. 1. In the virtualization controller 2, one or more port sections 8, and one or more storage control parts 7-1, 7-2, and the main control part 20 are connected through a backplane 9, and the storage control part 7-1 is connected with plural disk devices 35. Each port section 8 incorporates: an interface control part 81 (SN I/F in the figure) which controls a network 5 connected with host computers 1 or storage devices 3; an interface control part 82 (BP I/F) which controls the backplane 9 for connection with other components inside the virtualization controller 2; a memory 85 which stores programs and information (discussed hereinbelow); and a CPU 84 which executes the program using such information. The storage control part 7-1 incorporates: an interface control part 73 (hereinafter called BP I/F) which controls the backplane 9; an interface control part 72 for data transfer with plural disk devices 35 (hereinafter called “HDD I/F); a cache 71 which stores data to be transferred from/to the disk devices 35 or storage devices 3; and a CPU 70 which performs relevant tasks and executes the programs (discussed hereinbelow). The storage control part 7-2 is structurally the same as the storage control part 7-1 except that it does not have an interface control part 72 for data transfer with disk devices 35. The main control part 20 is the same as the main control part 20 shown in FIG. 1 except that it includes a management port 25 and has an interface control part 53 for control of the backplane 9. The program to be executed by the CPU 50 will be discussed hereinbelow. [0172] Although FIG. 19 shows a case in which host computers 1, storage devices 3, a management server (managing unit) 4, and port sections 8 in the virtualization controller 2 each have one port, the invention is not limited thereto. Each of them may have more than one port. Likewise, the components which constitute the virtualization controller 2 may each have more than one interface control part 82 (BP I/F) for control of the backplane 9 and in that case, it is desirable that the components should be interconnected through plural backplanes. Since the port sections 8 of the virtualization controller 2 are compatible with different network protocols, they may be used as management ports. [0173] [0173]FIG. 20 shows programs to be executed by the CPU in a component of the virtualization controller 2 and an example of management information. The programs and management information shown here are the same as those in FIG. 3 except for the following three points. Firstly, the virtualization processor 505 newly has virtualization routing control information 530. Secondly, the virtualization routing program 517 has a program for transfer of command frames (command transfer program) 531, a program for transfer of response frames (response transfer program) 532, and a program for transfer of other frame data (other transfer program) 533. Thirdly, the virtualization controller 2 newly has an internal storage access processor 506 which holds internal storage configuration management information 508 as information on the configuration of storage devices 35 in the virtualization controller 2, and an internal storage access control program 507 for actually transferring frame data. [0174] It is desirable that the internal storage access processor 506 should control the system in a way that a host computer recognizes plural physical disk devices as a single logical storage device, and also by adding parity data as redundant data to the data being accessed by the host computer and storing it on a disk, the internal storage access processor 506 can perform parity control and other related tasks to enable data transfer with the host computer using the parity data even if a disk device fails. However, this is not directly related to the present invention and a detailed explanation thereof is omitted here. Details of the virtualization routing control information 530, command transfer program 531, response transfer program 532 and other transfer program 533 will be given later. [0175] In FIG. 3 and FIG. 20, a program or the like for initialization of the virtualization controller 2 is not shown. The virtualization controller 2 may have at least an initialization program to initialize various management information upon turning on the power or a group of programs which initialize the system or carry out diagnosis according to an instruction from the managing unit (management server) 4 or the like. [0176] [0176]FIG. 21 shows three major types of access path between a host computer and a storage device. In connection with the figure, a storage group 34 as a component of the virtualization controller 2 is referred to as an internal storage, and storage devices 3 which are connected through the network 5 with the virtualization controller 2 as external storages; and the port section 8 connected with the host computer 1 is called In Port and the port section 8 connected with external storage devices 3 is called Out Port. The first type of access path is a route which connects the host computer 1 with the internal storage 34 through the port section 8 (In Port) and the storage control part 7-1. The second type of access path is a route which connects the host computer 1 with an external storage 3 through the port section 8 (In Port), the storage control part 7-2 and the port section 8 (Out Port). The third type of access path is a route which connects the host computer 1 with an external storage 3 through the port section 8 (In Port) and the port section 8 (Out Port). [0177] [0177]FIG. 22 is a table showing an example of volume mapping information 515 which is used in this embodiment. The difference from the table in FIG. 4 is that this table newly includes virtualization module management information 523 which manages information for identifying the component performing the virtualization process (discussed hereinbelow), and external volume connection module management information 254 which, when a real volume exists in an external storage 3, manages the identifier for the port for connection with the external storage 3. In FIG. 22, “Storage Control part #1” refers to the identification for the storage control part 7-1 in FIG. 19, and “Storage Control part #2” refers to the identification for the storage control part 7-2 in FIG. 19. In FIG. 22, Size (volume state information) and Status information are omitted here, but it is desirable to manage such information. In addition, since the internal storage configuration management information 507 contains detailed real volume management information concerning the internal storage 34, an explanation thereof is omitted here. In this embodiment, it is not necessary for each component of the virtualization controller 2 to hold and manage all information as elements of volume mapping information 515; rather, it is desirable for each component to hold and manage only information that it needs to carry out the task assigned to it. [0178] [0178]FIG. 23 is a table showing an example of virtualization routing control information 530 which is managed by each component of the virtualization controller 2. The virtualization routing control information 530 is generated, referenced or updated when each component of the virtualization controller 2 performs the frame data transfer process as mentioned later. It has source management information 534 (which includes source identification and source-specified command identification) and destination management information 535 (which includes destination identification and self-specified command identification). The command identification is information which is added to individual frame data in order to identify which command is relevant to the frame data being transferred between the source and destination. Although a detailed explanation of the composition of frame data is not given here, frame data at least contains information for identifying the source (sender)/destination (receiver) of the frame data (source/destination identification), frame data type information, and header information including command identification, and payload information including access request information or status information or data. FIG. 23 suggests, as an example of virtualization routing control information 530 which is held and managed by the port section 8 (In Port) connected with the host computer 1, that the port section 8 has received three commands identified by Host_Tag_1, Host_Tag_2, and Host_Tag_3 from the host computer identified by Host_Pid_1 and respectively has added command identifiers InPort_Tag_1, InPort_Tag 2, and InPort_Tag_3 (which it has specified) to the commands and respectively has sent them to the storage control part 7-1 (SC#1 in FIG. 23), storage control part 7-2 (SC#2 in FIG. 23) and port section 8 (Out Port in FIG. 23). [0179] [0179]FIG. 24 shows an example of the frame data transfer process which is performed by a component of the virtualization controller 2. This means that the process can be performed by a port section 8, the storage control part 7-1, or the storage control part 7-2. This process begins when frame data is received from the host computer 1 or internal storage 34 or external storage device 3, or when a component of the virtualization controller 2 receives frame data from another component. Next, the frame data transfer process according to this embodiment will be explained as an example, referring to FIG. 24. When a component of the virtualization controller 2 receives frame data, first of all it decides whether virtualization is needed or not (130) (discussed hereinbelow). The following is a concrete example of conditions of frame data which should be decided as needing virtualization. [0180] (1) The destination identification in the frame data is registered in the virtual volume management information 520 of the volume mapping information 515. [0181] (2) The source identification in the frame data is registered in the real volume management information 521 of the volume mapping information 515. [0182] (3) The command identification in the frame data is registered in the source management information 534 or destination management information 535 of the virtualization routing control information 530. [0183] The above conditions for decision on the necessity for virtualization are mere examples and do not limit the invention. The real routing process (131) which is to be performed if it is decided that virtualization is not needed is the same as the process shown in FIG. 9 and an explanation thereof is omitted here. Next, if it is decided that virtualization is needed, the component concerned detects the type of frame data using frame data type information included in the frame data. [0184] Command Frame [0185] If the received frame data is found to be a command frame (132), the command transfer program 531 takes the following steps for transfer of the command frame. [0186] 1. Decision on Necessity for Command Conversion (133) [0187] Using the frame data destination identification included in the received frame data, and if necessary, various information included in the payload of the received frame data (destination LUN, etc.) and volume mapping information 515, the command transfer program 531 decides whether it should perform the after-mentioned command conversion process or not. For example, if the destination Port ID or LUN is registered in the virtual volume management information 520 of the volume mapping information 515, and the information for identifying it is registered in the virtualization module management information 523, then the program decides that the command needs conversion by it. [0188] 2. Command Conversion (134) [0189] If the command transfer program 531 decides that command conversion by it is needed, it performs the command conversion process as follows: using the virtual volume management information 520 and real volume management information 521 of the volume mapping information 515, it replaces the destination identification included in the received frame data by identification corresponding to a real volume, and the source identification by its identification, and access request (command) information (LUN, etc) by access request information (LUN, etc) corresponding to a real volume. If it is decided at step 133 that command conversion is not needed, the step of command conversion (134) is not taken and the sequence proceeds to step 135. [0190] 3. Detection of Command Frame Destination (135) [0191] If it is decided that command conversion is not needed, or after the above command conversion process is performed, the command transfer program 531 detects the destination to which the command frame is to be transferred, using the virtualization module management information 523 (for In Port), or the external volume connection module management information 524 (for the storage controller), or the real volume management information 521 (for Out Port) in the volume mapping information 515. [0192] 4. Registration of Virtualization Routing Control Information (136) [0193] Next, the command transfer program 531 registers the source identification and command identification included in the received command frame, the destination identification for identifying the command frame destination, and the command identification generated by it, as the source management information 534 and destination management information 535 of the virtualization routing control information 530. [0194] 5. Command Transfer (137) [0195] The command transfer program 531 replaces the command identification included in the received command frame by the command identification which it has generated and sends the latter to the above detected command frame destination (137). This concludes the whole command frame transfer process. [0196] Response Frame [0197] If the received frame data is found at step 132 to be not a command frame but a response frame (138), the response transfer program 532 takes the following steps for transfer of the response frame. [0198] 1. Decision on Necessity for Response Generation (139) [0199] Using the command identification included in the received response frame and volume mapping information 515, the response transfer program 532 decides whether it should perform the response generation process or not. For example, if the source identification included in the received response frame is registered in the real volume management information 521 of the volume mapping information 515, and its identification is registered in the virtualization module management information 523, then it decides that the response frame is frame data which needs response generation by it. [0200] 2. Response Generation (140) [0201] If the response transfer program 532 decides that response generation is needed, it performs the response generation process as follows: using the virtual volume management information 520 of the volume mapping information 515, it replaces the source identification included in the received response frame by identification corresponding to a virtual volume, and the destination identification by identification for the corresponding host computer, and if necessary, generates new status information according to the status information included in the received response frame and replaces the old status information by the new one. [0202] 3. Detection of Response Frame Destination (141) [0203] Then, the response transfer program 532 detects the destination to which the response frame is to be transferred, using the command identification included in the received frame data and the virtualization routing control information 530. For example, it detects the command management information in the destination management information 535 of the virtualization routing control information 530 which agrees with the command identification included in the received frame data and recognizes the source identification in the source management information 534 corresponding to the command management information, as representing the destination for the response frame. [0204] 4. Response Transfer (142) [0205] Next, the response transfer program 532 replaces the command identification included in the received response frame by the corresponding source command identification in the source management information 534 of the virtualization routing control information 530, and sends it to the response frame destination detected at step 141. [0206] 5. Updating the Virtualization Routing Control Information (143) [0207] Then, the response transfer program 532 deletes the corresponding entry (destination/source management information) in the virtualization routing control information 530 according to the command identification included in the received response frame and concludes the whole response frame transfer process. [0208] Other Frame [0209] If the received frame data is found to be a frame (e.g., data) other than a command frame and a response frame, the other transfer program 533 takes the following steps for transfer of the frame data. [0210] 1. Decision on Necessity for Virtualization (144) [0211] Using the frame data destination/source identification and command identification included in the received frame data, volume mapping information 515 and virtualization routing control information 530, the other transfer program 533 decides whether it should perform the virtualization process or not. For example, if the destination or source identification is registered in the real volume management information 521 or virtual volume management information 520 of the volume mapping information 515, and its identification is registered in the virtualization module management information 523, then the other transfer program 533 decides that it is frame data which needs virtualization by it. [0212] 2. Virtualization (Source/Destination Identification Conversion) (145) [0213] If the other transfer program 533 decides that virtualization by it (source/destination identification conversion) is needed, it performs the virtualization process as follows: using the virtual volume management information 520 and real volume management information 521 of the volume mapping information 515, it replaces the source or destination identification included in the received frame data by virtual or real volume identification information. For example, if the destination identification included in the received frame data agrees with virtual volume identification information (from a host computer to the virtualization controller), the other transfer program 533 replaces the destination identification by real volume identification information; or if the source identification included in the received frame data agrees with real volume identification information (from the virtualization controller to a host computer), it replaces the source identification by virtual volume identification information. [0214] 3. Detection of Other Frame Data Destination (146) [0215] Then, the other transfer program 533 detects the destination to which the frame data is to be transferred, using the command identification included in the received frame data and the virtualization routing control information 530. For example, the other transfer program 533 detects the command management information in the source management information 534 of the virtualization routing control information 530 which agrees with the command identification included in the received frame data and recognizes the destination identification in the destination management information 535 corresponding to the command management information, as representing the destination for the frame data. [0216] 4. Transfer of Frame Data (147) [0217] Next, the other transfer program 533 replaces the command identification included in the received frame data by the corresponding source command identification in the source management information 534 of the virtualization routing control information 530, and sends it to the frame data destination detected at step 156. [0218] For simplification, the above explanation assumes that the external port identification (which is used with a host computer or storage device) is the same as the internal one (which is used with another internal component of the virtualization controller). However, the present invention is not limited thereto. When the internal and external port identifications are different, it may be sufficient for the virtualization controller 2 to have information which defines the relation between them. [0219] Next, an explanation will be given of the data transfer process in this embodiment where different access paths between a host computer and a storage device offering a real volume are available. In this embodiment, a port section 8 or the storage control part 7-1 or storage control part 7-2 performs the data transfer process and, upon completion of data transfer, updates the volume mapping information 515. Which component is to perform this process is determined according to the virtualization module management information 523 of the volume mapping information 515. In other words, the component registered as a virtualization module in the virtualization module management information 523 performs the data transfer process for the corresponding virtual volume and updates the volume mapping information 515. For example, if the volume mapping information 515 is as shown in FIG. 22, the storage control part 7-2 performs the data transfer process for the virtual volume identified by Port ID=V_Pid_2, Port Name=V_Pname_2, LUN=0 and updates the volume mapping table. The sequences for data transfer and volume mapping table updating are the same as in the first embodiment. [0220] In this embodiment, the virtualization module may be changed. Next is an explanation of a data transfer process involving change of the virtualization module. A data transfer process involving change of the virtualization module is classified into two cases: in one case, the access path type (first, second or third access path) is changed; and in the other case, the access path is constant but the virtualization module is changed. The following is an explanation of a case that the access path is changed from the second access path type to the third one. [0221] [0221]FIG. 25 shows an example of volume mapping information 515 which is held by the port section 8 (In Port) of the virtualization controller 2 before the data transfer process; FIG. 26 shows an example of volume mapping information 515 which is held by the storage control part 7-2 before the data transfer process; and FIG. 27 shows an example of real volume mapping information 515 which is held by the port section 8 (Out Port) of the virtualization controller 2 before the data transfer process. [0222] As shown in FIG. 25, V_Pid_1, V_Pid_2, and V_Pid_3 are registered as virtual volume management information managed by the port section 8 (In Port). This indicates that the port section 8 (In Port) constitutes an access path for three virtual volumes (V_Pid_1, V_Pid_2, and V_Pid_3) which the virtualization controller 2 offers to the host computer. Likewise, FIG. 26 indicates that the storage control part 7-2 constitutes an access path for the virtual volume V_Pid_2; and FIG. 27 indicates that the port section 8 (Out Port) constitutes an access path for two virtual volumes (V_Pid_2 and V_Pid_3). In addition, the virtualization module management information in FIGS. 25, 26 and 27 indicates that the storage control part 7-1 (SC#1), storage control part 7-2 (SC#2), and Out Port perform virtualization of the virtual volumes identified by V_Pid_1, V_Pid_2, and V_Pid_3, respectively. [0223] Therefore, the access path between the virtual volume V_Pid_1 and the host is of the first type, namely a path which leads from In Port through the backplane 9 to the storage control part 7-1 in which virtualization is performed. The access path between the virtual volume V_Pid_2 and the host is of the second type, namely a path which leads from In Port through the backplane 9 to the storage control part 7-2 in which virtualization is performed, and then (after virtualization) leads through Out Port and reaches an external storage. The access path between the virtual volume V_Pid_3 and the host is of the third type, namely a path which leads from In Port through the backplane 9 to Out Port 7-1 in which virtualization is performed, skipping the storage control parts. [0224] FIGS. 28 to 30 show examples of volume mapping information 515 which are respectively held by the port section 8 (In Port), storage control part 7-2, and port section 8 (Out Port) after the access path to the virtual volume (V_Pid_2) shown in FIGS. 25 to 27 has been changed from the second type to the third type and data transfer between external storages 3 (data transfer from the real volume identified by P_Pid_2 and LUN 0 to the real volume identified by P_Pid_3 and LUN 1) has been made. [0225] [0225]FIG. 28 and FIG. 30 respectively show volume mapping information which is held by the port section 8 (In Port) and the port section 8 (Out Port) respectively. As indicated by FIG. 28 and FIG. 30, the identification for the real volume corresponding to the virtual volume identified by V_Pid_2 is replaced by P_Pid_3, P_Pname_3, LUN 1, which is destination real volume identification, and the virtualization module management information is replaced by “Out Port” which represents the port section to perform virtualization in the new access path (third type access path). FIG. 29 shows volume mapping information which is held by the storage control part 7-2. In the third type access path, the storage control part does not constitute an access path which is used to offer a virtual volume to the host computer. Therefore, the entry for the virtual volume identified by V_Pid_2 is deleted here. [0226] A detailed explanation of the data transfer process according to this embodiment is omitted because the process is achieved when an adequate component of the virtualization controller 2 (for example, a component which performs virtualization before data transfer) follows the abovementioned data transfer process according to the above (first to third) embodiments., [0227] It is desirable that volume mapping information 515 should be updated by the components of the virtualization controller 2 synchronously. Therefore, it is desirable that as in the above embodiments, its updating should be made through the main control part 20 of the virtualization controller 2 upon completion of data transfer between storages. In other words, it is desirable that a component which performs the process for data transfer between storages should notify the main control part 20 of completion of data transfer and the main control part 20 thus notified should update the relevant volume mapping information 515. The same applies to the procedure for updating volume mapping information 515 in a case that only the access path is changed and data transfer between storages is not made. [0228] The above explanation assumes that the port section (In Port) connected with the host computer 1 and the port section (Out Port) connected with an external storage 3 are different port sections. However, the present invention is not limited thereto. It is also possible, for example, that a port section 8 is connected with a host computer 1 and an external storage 3 at the same time. Furthermore, the above explanation assumes that Port ID and Port Name as information for identifying a virtual volume are identifiers assigned to a virtual port offered to the host computer 1 by the virtualization controller 2. However, the invention is not limited thereto. According to this embodiment in particular, the actual identifiers assigned to port sections 8 of the virtualization controller 2 may be used as virtual volume management information. [0229] According to the present invention, data can be transferred between storage devices without revising the identification information which a host computer uses to identify the volume to be accessed. As a consequence, data transfer takes place without stopping operation of the host computer. [0230] Furthermore, according to the present invention, even when a virtualization controller is newly introduced or replaced in a computer system, a host computer can access data without revising the information for identifying the volume to be accessed. As a consequence, it is possible to introduce or replace a virtualization controller in the computer system without stopping operation of the host computer. [0231] It is to be understood that the above description is intended to be illustrative and not restrictive. Many embodiments will be apparent to those of skill in the art upon reviewing the above description. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the appended claims along with their full scope of equivalents. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS79018 *Jun 16, 1868 smithUS79019 *Jun 16, 1868 Improved oonneotiefg-eod adjustmentUS93541 *Aug 10, 1869 Improvement in can-openersUS4025904 *Sep 8, 1975May 24, 1977Texas Instruments IncorporatedProgrammed allocation of computer memory workspaceUS5408465 *Jun 21, 1993Apr 18, 1995Hewlett-Packard CompanyFlexible scheme for admission control of multimedia streams on integrated networksUS5504882 *Jun 20, 1994Apr 2, 1996International Business Machines CorporationFault tolerant data storage subsystem employing hierarchically arranged controllersUS5504982 *Jun 27, 1994Apr 9, 1996Sharp; Jason W.Embedded arrowhead removing toolUS5548712 *Jan 19, 1995Aug 20, 1996Hewlett-Packard CompanyData storage system and method for managing asynchronous attachment and detachment of storage disksUS5758118 *Dec 8, 1995May 26, 1998International Business Machines CorporationMethods and data storage devices for RAID expansion by on-line addition of new DASDsUS5870537 *Mar 13, 1996Feb 9, 1999International Business Machines CorporationConcurrent switch to shadowed device for storage controller and device errorsUS5895485 *Feb 24, 1997Apr 20, 1999Eccs, Inc.Method and device using a redundant cache for preventing the loss of dirty dataUS5895495 *Mar 13, 1997Apr 20, 1999International Business Machines CorporationDemand-based larx-reserve protocol for SMP system busesUS5917723 *May 22, 1995Jun 29, 1999Lsi Logic CorporationMethod and apparatus for transferring data between two devices with reduced microprocessor overheadUS6012123 *Jun 10, 1997Jan 4, 2000Adaptec IncExternal I/O controller system for an independent access parity disk arrayUS6044444 *Mar 17, 1997Mar 28, 2000Emc CorporationRemote data mirroring having preselection of automatic recovery or intervention required when a disruption is detectedUS6098129 *Apr 1, 1998Aug 1, 2000Hitachi, Ltd.Communications system/method from host having variable-length format to variable-length format first I/O subsystem or fixed-length format second I/O subsystem using table for subsystem determinationUS6101497 *Apr 25, 1997Aug 8, 2000Emc CorporationMethod and apparatus for independent and simultaneous access to a common data setUS6106748 *Jun 10, 1998Aug 22, 2000Carter Wallace, Inc.Method for removing prophylactic devices from mandrelsUS6173374 *Feb 11, 1998Jan 9, 2001Lsi Logic CorporationSystem and method for peer-to-peer accelerated I/O shipping between host bus adapters in clustered computer networkUS6195730 *Jul 24, 1998Feb 27, 2001Storage Technology CorporationComputer system with storage device mapping input/output processorUS6209002 *Feb 17, 1999Mar 27, 2001Emc CorporationMethod and apparatus for cascading data through redundant data storage unitsUS6219753 *Jun 4, 1999Apr 17, 2001International Business Machines CorporationFiber channel topological structure and method including structure and method for raid devices and controllersUS6230239 *Dec 11, 1997May 8, 2001Hitachi, Ltd.Method of data migrationUS6240486 *Jul 29, 1999May 29, 2001Emc CorporationSystem and method for on-line, real time, data migrationUS6240494 *Dec 16, 1998May 29, 2001Hitachi, Ltd.Subsystem replacement methodUS6247099 *Jun 3, 1999Jun 12, 2001International Business Machines CorporationSystem and method for maintaining cache coherency and data synchronization in a computer system having multiple active controllersUS6247103 *Jan 6, 1998Jun 12, 2001International Business Machines CorporationHost storage management control of outboard data movement using push-pull operationsUS6341329 *Feb 9, 2000Jan 22, 2002Emc CorporationVirtual tape systemUS6356977 *Dec 12, 2000Mar 12, 2002Emc CorporationSystem and method for on-line, real time, data migrationUS6363462 *Jan 15, 1999Mar 26, 2002Lsi Logic CorporationStorage controller providing automatic retention and deletion of synchronous back-up dataUS6523096 *Mar 13, 2001Feb 18, 2003Hitachi, Ltd.Apparatus for and method of accessing a storage region across a networkUS6529976 *Jun 15, 2000Mar 4, 2003Hitachi, Ltd.Heterogeneous computer system, heterogeneous input output system and data back-up method for the systemsUS6553408 *Jul 2, 1999Apr 22, 2003Dell Products L.P.Virtual device architecture having memory for storing lists of driver modulesUS6560673 *Jan 31, 2001May 6, 2003Hewlett Packard Development Company, L.P.Fibre channel upgrade pathUS6587935 *Aug 27, 2002Jul 1, 2003Emc CorporationMethod and apparatus for mirroring data in a remote data storage systemUS6598134 *Aug 30, 2001Jul 22, 2003Emc CorporationSystem and method for on-line, real time, data migrationUS6675258 *Jun 30, 2000Jan 6, 2004Lsi Logic CorporationMethods and apparatus for seamless firmware update and propagation in a dual raid controller systemUS6675268 *Dec 11, 2000Jan 6, 2004Lsi Logic CorporationMethod and apparatus for handling transfers of data volumes between controllers in a storage environment having multiple paths to the data volumesUS6681303 *Aug 19, 1999Jan 20, 2004Hitachi, Ltd.Storage systemUS6681339 *Jan 16, 2001Jan 20, 2004International Business Machines CorporationSystem and method for efficient failover/failback techniques for fault-tolerant data storage systemUS6684310 *Jan 12, 2001Jan 27, 2004Fujitsu LimitedAccess control method and storage device using sameUS6697367 *Jun 12, 2000Feb 24, 2004Emc CorporationMultihop system callsUS6708232 *Feb 12, 2001Mar 16, 2004Hitachi, Ltd.Data migration method, protocol converter and switching apparatus using itUS6718404 *Jun 1, 2001Apr 6, 2004Hewlett-Packard Development Company, L.P.Data migration using parallel, distributed table driven I/O mappingUS6745281 *Jun 28, 2000Jun 1, 2004Nec CorporationFiber channel connection magnetic disk device and fiber channel connection magnetic disk controllerUS6851020 *Mar 30, 2001Feb 1, 2005Hitachi, Ltd.Storage subsystem that connects fiber channel and supports online backupUS6857057 *Oct 3, 2002Feb 15, 2005Hewlett-Packard Development Company, L.P.Virtual storage systems and virtual storage system operational methodsUS6876556 *Apr 8, 2002Apr 5, 2005Virginia Tech Intellectual Properties, Inc.Accelerated commutation for passive clamp isolated boost convertersUS6883064 *Feb 19, 2002Apr 19, 2005Hitachi, Ltd.Disk array controller comprising a plurality of disk array controlling unitsUS6922761 *Mar 25, 2002Jul 26, 2005Emc CorporationMethod and system for migrating dataUS20020003022 *May 15, 2001Jan 10, 2002Csida Jason GenePresentation and bonding of garment side panelsUS20020004857 *Apr 12, 2001Jan 10, 2002Hiroshi ArakawaComputer systemUS20020004890 *Aug 30, 2001Jan 10, 2002Yuval OfekSystem and method for on-line, real time, data migrationUS20020019908 *Jun 1, 2001Feb 14, 2002Reuter James M.System and method for managing virtual storageUS20020019920 *Jun 1, 2001Feb 14, 2002Reuter James M.Process for fast, space-efficient disk copies using parallel distributed table driven I/O mappingUS20020019922 *Jun 1, 2001Feb 14, 2002Reuter James M.Data migration using parallel, distributed table driven I/O mappingUS20020019923 *Jun 1, 2001Feb 14, 2002Reuter James M.Distributed fine-grained enhancements for distributed table driven I/O mappingUS20020026558 *Jun 1, 2001Feb 28, 2002Reuter James M.Architecture for parallel distributed table driven I/O mappingUS20020029326 *Jun 1, 2001Mar 7, 2002Reuter James M.Centralized fine-grained enhancements for distributed table driven I/O mappingUS20020065864 *Jun 12, 2001May 30, 2002Hartsell Neal D.Systems and method for resource tracking in information management environmentsUS20020087544 *Dec 29, 2000Jul 4, 2002Selkirk Stephen S.Dynamically changeable virtual mapping schemeUS20020087751 *Jan 2, 2002Jul 4, 2002Advanced Micro Devices, Inc.Switch based scalable preformance storage architectureUS20020103889 *Jun 19, 2001Aug 1, 2002Thomas MarksonVirtual storage layer approach for dynamically associating computer storage with processing hostsUS20020112113 *Jan 11, 2002Aug 15, 2002Yotta Yotta, Inc.Storage virtualization system and methodsUS20030037071 *Aug 3, 2001Feb 20, 2003International Business Machines CorporationQuiesce system storage device and method in a dual active controller with cache coherency using stripe locks for implied storage volume reservationsUS20030051109 *Jun 28, 2001Mar 13, 2003Cochran Robert A.Method and system for providing logically consistent logical unit backup snapshots within one or more data storage devicesUS20030056038 *Jun 28, 2001Mar 20, 2003Cochran Robert A.Method and system for providing advanced warning to a data stage device in order to decrease the time for a mirror split operation without starving host I/O request processsingUS20030093567 *Jan 18, 2002May 15, 2003Lolayekar Santosh C.Serverless storage servicesUS20030097607 *Nov 21, 2001May 22, 2003Bessire Michael L.System and method for ensuring the availability of a storage systemUS20030101228 *Nov 2, 2001May 29, 2003Busser Richard W.Data mirroring between controllers in an active-active controller pairUS20030105931 *Nov 30, 2001Jun 5, 2003Weber Bret S.Architecture for transparent mirroringUS20030115218 *Dec 19, 2001Jun 19, 2003Bobbitt Jared E.Virtual file systemUS20030115432 *Dec 14, 2001Jun 19, 2003Biessener Gaston R.Data backup and restoration using dynamic virtual storageUS20030126327 *Dec 28, 2001Jul 3, 2003Pesola Troy RaymondVolume translation apparatus and methodUS20030126388 *Dec 27, 2001Jul 3, 2003Hitachi, Ltd.Method and apparatus for managing storage based replicationUS20030145168 *Feb 11, 2003Jul 31, 2003Lecrone Douglas E.Method and apparatus for maintaining data coherencyUS20030145169 *Mar 7, 2003Jul 31, 2003Teruo NagasawaSubsystem replacement methodUS20030158999 *Feb 21, 2002Aug 21, 2003International Business Machines CorporationMethod and apparatus for maintaining cache coherency in a storage systemUS20040003022 *Jun 27, 2002Jan 1, 2004International Business Machines CorporationMethod and system for using modulo arithmetic to distribute processing over multiple processorsUS20040028043 *Jul 31, 2002Feb 12, 2004Brocade Communications Systems, Inc.Method and apparatus for virtualizing storage devices inside a storage area network fabricUS20040049553 *Mar 6, 2003Mar 11, 2004Takashige IwamuraInformation processing system having data migration deviceUS20040054850 *Sep 18, 2002Mar 18, 2004Fisk David C.Context sensitive storage managementUS20040054866 *Sep 5, 2003Mar 18, 2004Blumenau Steven M.Mapping of hosts to logical storage units and data storage ports in a data processing systemUS20040068637 *Oct 3, 2002Apr 8, 2004Nelson Lee L.Virtual storage systems and virtual storage system operational methodsUS20040073831 *Dec 27, 2002Apr 15, 2004Moshe YanaiRemote data mirroringUS20040084610 *Nov 1, 2002May 6, 2004Leong Ak WingOptical navigation sensor with integrated lensUS20040084641 *Apr 22, 2003May 6, 2004Finisar CorporationMethod for in situ measurement of the optical offset of an optical componentUS20040098547 *Jun 30, 2003May 20, 2004Yuval OfekApparatus and methods for transferring, backing up, and restoring data in a computer systemUS20040111485 *Feb 26, 2003Jun 10, 2004Yasuyuki MimatsuConnecting device of storage device and computer system including the same connecting deviceUS20040123180 *Aug 29, 2003Jun 24, 2004Kenichi SoejimaMethod and apparatus for adjusting performance of logical volume copy destinationUS20040139237 *Oct 28, 2003Jul 15, 2004Venkat RanganApparatus and method for data migration in a storage processing deviceUS20040143832 *Aug 8, 2003Jul 22, 2004Yasutomo YamamotoStorage unit, installation method thereof and installation program thereforUS20040148443 *Aug 7, 2003Jul 29, 2004Hitachi, Ltd.Method for controlling information processing system and information processing systemUS20050010734 *Nov 3, 2003Jan 13, 2005Kenichi SoejimaData processing method with restricted data arrangement, storage area management method, and data processing systemUS20050010743 *Apr 6, 2004Jan 13, 2005Sun Microsystems, Inc.Multiple-thread processor for threaded software applicationsUS20050033878 *Oct 28, 2003Feb 10, 2005Gururaj PangalApparatus and method for data virtualization in a storage processing deviceUS20050055501 *Sep 8, 2004Mar 10, 2005Copan Systems, Inc.High-density storage systems using hierarchical interconnectUS20050081009 *Oct 8, 2003Apr 14, 2005Williams James A.Access controller for storage devicesUS20050138184 *Dec 17, 2004Jun 23, 2005Sanrad Ltd.Efficient method for sharing data between independent clusters of virtualization switches* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7058731Aug 3, 2004Jun 6, 2006Hitachi, Ltd.Failover and data migration using data replicationUS7073025 *May 20, 2004Jul 4, 2006Hitachi, Ltd.Disk array apparatus and control method for the sameUS7089386Jul 12, 2005Aug 8, 2006Hitachi, Ltd.Method for controlling storage device controller, storage device controller, and programUS7093087Oct 10, 2003Aug 15, 2006Hitachi, Ltd.Method for controlling storage device controller, storage device controller, and programUS7197519Aug 6, 2003Mar 27, 2007Hitachi, Ltd.Database system including center server and local serversUS7243116Sep 22, 2004Jul 10, 2007Hitachi, Ltd.Storage systemUS7334097Mar 27, 2006Feb 19, 2008Hitachi, Ltd.Method for controlling storage device controller, storage device controller, and programUS7418563Oct 12, 2006Aug 26, 2008Hitachi, Ltd.Method for controlling storage device controller, storage device controller, and programUS7523148May 23, 2005Apr 21, 2009Hitachi, Ltd.Storage systemUS7596637 *Feb 28, 2006Sep 29, 2009Hitachi, Ltd.Storage apparatus and control method for the same, and computer program productUS7673107 *Jul 3, 2007Mar 2, 2010Hitachi, Ltd.Storage system and storage control deviceUS7693879Feb 15, 2007Apr 6, 2010Hitachi, Ltd.Database system including center server and local serversUS7770059 *Aug 3, 2010Emc CorporationFailure protection in an environment including virtualization of networked storage resourcesUS7809906May 28, 2004Oct 5, 2010Hitachi, Ltd.Device for performance tuning in a systemUS7885283 *Oct 19, 2006Feb 8, 2011Fujitsu LimitedApparatus and method for connecting storage devicesUS7904681 *Mar 8, 2011Emc CorporationMethods and systems for migrating data with minimal disruptionUS7930496Jun 29, 2006Apr 19, 2011International Business Machines CorporationProcessing a read request to a logical volume while relocating a logical volume from a first storage location to a second storage location using a copy relationshipUS7962712Jul 22, 2008Jun 14, 2011Hitachi, Ltd.Method for controlling storage device controller, storage device controller, and programUS8046554Oct 25, 2011Hitachi, Ltd.Storage subsystem and performance tuning methodUS8072987Dec 6, 2011Emc CorporationFull array non-disruptive data migrationUS8107467 *Dec 27, 2005Jan 31, 2012Emc CorporationFull array non-disruptive failoverUS8140785Jun 29, 2006Mar 20, 2012International Business Machines CorporationUpdating metadata in a logical volume associated with a storage controller for data units indicated in a data structureUS8166314Apr 24, 2012Emc CorporationSelective I/O to logical unit when encrypted, but key is not available or when encryption status is unknownUS8180842 *May 15, 2012Fujitsu LimitedCommunication device management programUS8261068Sep 4, 2012Emc CorporationSystems and methods for selective encryption of operating system metadata for host-based encryption of data at rest on a logical unitUS8281098Sep 20, 2011Oct 2, 2012Hitachi, Ltd.Storage subsystem and performance tuning methodUS8285933Oct 9, 2012Hitachi, Ltd.Avoiding use of an inter-unit network in a storage system having multiple storage control unitsUS8321608 *Nov 27, 2012Hitachi, Ltd.Pool I/O device operation confirmation method and computer systemUS8347063 *Aug 19, 2005Jan 1, 2013Intel CorporationMethod and system for device address translation for virtualizationUS8385359 *Oct 27, 2010Feb 26, 2013Fujitsu LimitedInformation communication system, connection setting apparatus and non-transitory computer-readable storage medium storing connection setting programUS8416954Apr 9, 2013Emc CorporationSystems and methods for accessing storage or network based replicas of encrypted volumes with no additional key managementUS8443160 *Aug 6, 2010May 14, 2013Hitachi, Ltd.Computer system and data migration methodUS8463980Sep 30, 2010Jun 11, 2013Microsoft CorporationShared memory between child and parent partitionsUS8589504Jun 29, 2006Nov 19, 2013Emc CorporationFull array non-disruptive management data migrationUS8892840May 13, 2013Nov 18, 2014Hitachi, Ltd.Computer system and data migration methodUS9063895Jun 29, 2007Jun 23, 2015Emc CorporationSystem and method of non-disruptive data migration between heterogeneous storage arraysUS9098211Jun 29, 2007Aug 4, 2015Emc CorporationSystem and method of non-disruptive data migration between a full storage array and one or more virtual arraysUS9098455Sep 25, 2014Aug 4, 2015Inmage Systems, Inc.Systems and methods of event driven recovery managementUS9209989 *Dec 26, 2008Dec 8, 2015Inmage Systems, Inc.Causation of a data read operation against a first storage system by a server associated with a second storage system according to a host generated instructionUS20050141444 *Dec 16, 2004Jun 30, 2005Fujitsu LimitedCommunication device management programUS20050193168 *Jan 11, 2005Sep 1, 2005Yoshiaki EguchiStorage subsystem and performance tuning methodUS20050198553 *May 20, 2004Sep 8, 2005Takeki OkamotoDisk array apparatus and control method for the sameUS20050251636 *Jul 12, 2005Nov 10, 2005Hitachi, Ltd.Method for controlling storage device controller, storage device controller, and programUS20060020754 *May 23, 2005Jan 26, 2006Susumu SuzukiStorage systemUS20060031594 *Aug 3, 2004Feb 9, 2006Hitachi, Ltd.Failover and data migration using data replicationUS20060117159 *May 27, 2005Jun 1, 2006Fujitsu LimitedData storage system and data storage control deviceUS20060168412 *Mar 27, 2006Jul 27, 2006Hitachi, Ltd.Method for controlling storage device controller, storage device controller, and programUS20070028066 *Oct 12, 2006Feb 1, 2007Hitachi, Ltd.Method for controlling storage device controller, storage device controller, and programUS20070043928 *Aug 19, 2005Feb 22, 2007Kiran PanesarMethod and system for device address translation for virtualizationUS20070143362 *Feb 15, 2007Jun 21, 2007Norifumi NishikawaDatabase system including center server and local serversUS20070168470 *Feb 28, 2006Jul 19, 2007Hitachi, Ltd.Storage apparatus and control method for the same, and computer program productUS20070242617 *Oct 19, 2006Oct 18, 2007Fujitsu LimitedNetwork device connecting apparatus and network device connecting methodUS20080005146 *Jun 29, 2006Jan 3, 2008International Business Machines CorporationUpdating metadata in a logical volume associated with a storage controllerUS20080052478 *Jun 29, 2006Feb 28, 2008International Business Machines CorporationRelocating a logical volume from a first storage location to a second storage location using a copy relationshipUS20080215771 *Jan 31, 2008Sep 4, 2008Hiroyuki OsakiPool i/o device operation confirmation method and computer systemUS20080288733 *Jul 22, 2008Nov 20, 2008Susumu SuzukiMethod for controlling storage device controller, storage device controller, and programUS20100169452 *Dec 26, 2008Jul 1, 2010Rajeev AtluriCausation of a data read operation against a first storage system by a server associated with a second storage system according to a host generated instructionUS20100318579 *Aug 18, 2010Dec 16, 2010Hitachi, Ltd.Control Device for Storage System Capable of Acting as a Constituent Element of Virtualization Storage SystemUS20110055477 *Mar 3, 2011Hitachi, Ltd.Avoiding use of an inter-unit network in a storage system having multiple storage control unitsUS20110134796 *Jun 9, 2011Fujitsu LimitedInformation communication system, connection setting apparatus and non-transitory computer-readable storage medium storing connection setting programUS20120036330 *Aug 6, 2010Feb 9, 2012Hitachi, Ltd.Computer system and data migration methodUS20140223097 *Apr 9, 2014Aug 7, 2014Fujitsu LimitedData storage system and data storage control deviceEP2073115A2May 19, 2008Jun 24, 2009Hitachi Ltd.Avoiding use of an inter-unit network in a storage system having multiple storage control unitsWO2012050724A2 *Sep 14, 2011Apr 19, 2012Microsoft CorporationShared memory between child and parent partitionsWO2012050724A3 *Sep 14, 2011Jul 5, 2012Microsoft CorporationShared memory between child and parent partitionsWO2013095520A1 *Dec 22, 2011Jun 27, 2013Intel CorporationObject-aware storage* Cited by examinerClassifications U.S. Classification711/114, 711/202, 711/165International ClassificationG06F3/06, G06F12/08Cooperative ClassificationG06F3/0689, G06F3/0649, G06F3/067, G06F3/0605, G06F3/061, G06F3/0617, G06F3/0613, G06F3/0665, G06F3/0647European ClassificationG06F3/06A6L4R, G06F3/06A2P4, G06F3/06A4V4, G06F3/06A4H2L, G06F3/06A2R4, G06F3/06A4H2, G06F3/06A2P, G06F3/06A2A2, G06F3/06A6DLegal EventsDateCodeEventDescriptionSep 14, 2011FPAYFee paymentYear of fee payment: 4Oct 14, 2015FPAYFee paymentYear of fee payment: 8RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services