STORAGE SYSTEM AND STORAGE SYSTEM MANAGEMENT METHOD

Abstract

To migrate a volume while maintaining a pair.SOLUTION: A first node configures a primary volume, a second node configures a secondary volume that forms a pair of the primary volume and a remote copy, and sets up the remote copy using identification information of the primary volume and identification information of the secondary volume, and a third node configures a destination volume to which the secondary volume is migrated. The first node forms a new pair between the primary volume and the destination volume in response to a new pair formation request specifying the identification information of the primary volume and the secondary volume and information specifying the third node, and the second node releases the pair between the secondary volume and the primary volume and replaces the identification information of the destination volume with the identification information of the secondary volume.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a storage system and a method for managing a storage system. [Background technology]

[0002] Japanese Patent Laid-Open Publication No. 2022-169249 (Patent Document 1) describes a conventional technology for managing a storage system. This publication states that "a volume to which a storage function is applied is migrated without copying data written to the volume to be migrated between computers, while maintaining the functionality of the storage function." "Multiple computers are connected so as to be able to access one or more physical storage devices. Each computer is configured to transfer ownership of the volume to be migrated to the destination computer. If the volume to be migrated from a first computer to a second computer is an owner volume to which a storage function is applied, and control data, which is metadata other than area mapping data, is required for data I / O instead of or in addition to area mapping data (metadata about the owner volume that represents the relationship between volume areas and storage areas), the first computer copies the control data of the owner volume to the second computer." [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2022-169249 Summary of the Invention [Problem to be solved by the invention]

[0004] With conventional technology, when migrating a volume that formed an asynchronous remote copy pair to another node, the pair had to be broken. For example, when removing a node, the volume on the target node had to be moved to another node. However, because the storage controller cannot transfer information between nodes for volumes that formed an asynchronous remote copy pair, the pair had to be broken first before the volume could be moved to another node. Furthermore, due to the same issue with capacity rebalancing that occurs when adding a node, the pair had to be broken in order to move an existing asynchronous remote copy pair to the additional node, resulting in high operational costs and low fault tolerance.

[0005] Therefore, an object of the present invention is to perform volume migration while maintaining the pair. [Means for solving the problem]

[0006] In order to achieve the above object, one representative storage system of the present invention comprises a plurality of nodes each having a processor, wherein a first node configures a primary volume that provides a logical storage area to a host, a second node configures a secondary volume that forms a remote copy pair with the primary volume and sets the remote copy using identification information of the primary volume and identification information of the secondary volume, a third node configures a destination volume that becomes the migration destination when migrating with the secondary volume as the source volume, the first node forms a new pair between the primary volume and the destination volume when it receives a request to form a new pair specifying the identification information of the primary volume, the identification information of the secondary volume, and information that identifies the third node, and the second node releases the pair between the secondary volume and the primary volume and replaces the identification information of the destination volume with the identification information of the secondary volume. Furthermore, one representative storage system of the present invention comprises a plurality of nodes each having a processor, wherein a first node configures a primary volume that provides a logical storage area to a host, a second node configures a secondary volume that forms a remote copy pair with the primary volume and sets the remote copy using identification information for the primary volume and identification information for the secondary volume, a third node configures a destination volume that becomes the migration destination when migrating using the primary volume as the source volume, and when the second node receives a request to form a new pair specifying the identification information for the primary volume, the identification information for the secondary volume, and information that identifies the third node, it forms a new pair between the secondary volume and the destination volume, and the first node releases the pair between the secondary volume and the primary volume and replaces the identification information of the destination volume with the identification information of the primary volume. Furthermore, one representative storage system management method of the present invention is a storage system management method comprising a plurality of nodes each having a processor, wherein a first node configures a primary volume that provides a logical storage area to a host, a second node configures a secondary volume that forms a remote copy pair with the primary volume and sets the remote copy using identification information for the primary volume and identification information for the secondary volume, a third node configures a destination volume that becomes the migration destination when migrating with the secondary volume as the source volume, and when the first node receives a request to form a new pair specifying the identification information for the primary volume, the identification information for the secondary volume, and information that identifies the third node, the first node forms a new pair between the primary volume and the destination volume, and the second node releases the pair between the secondary volume and the primary volume and replaces the identification information of the destination volume with the identification information of the secondary volume. Furthermore, one representative storage system management method of the present invention is a management method for a storage system having a plurality of nodes each having a processor, wherein a first node configures a primary volume that provides a logical storage area to a host, a second node configures a secondary volume that forms a remote copy pair with the primary volume and sets the remote copy using identification information of the primary volume and identification information of the secondary volume, a third node configures a destination volume that becomes the migration destination when migrating with the primary volume as the source volume, the second node forms a new pair between the secondary volume and the destination volume when it receives a request to form a new pair specifying the identification information of the primary volume, the identification information of the secondary volume, and information that identifies the third node, and the first node releases the pair between the secondary volume and the primary volume and replaces the identification information of the destination volume with the identification information of the primary volume. [Effects of the Invention]

[0007] According to the present invention, it is possible to migrate volumes while maintaining pairs. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief explanation of the drawings]

[0008] [Figure 1] An explanatory diagram of migration in the first embodiment [Figure 2] Storage system hardware configuration [Figure 3] Remote copy illustration [Figure 4] Input / output processing diagram [Figure 5] Memory information list [Figure 6] Specific example of a system configuration management table [Figure 7] Example of a pair management table [Figure 8] Example of a journal management table [Figure 9] Specific example of migration configuration management table [Figure 10] Path creation process diagram [Figure 11] Illustration of remote copy processing (asynchronous transfer) [Figure 12] FIG. 1 is an explanatory diagram of the migration process of the first embodiment. [Figure 13] FIG. 2 is an explanatory diagram of the migration process of the first embodiment. [Figure 14] An explanatory diagram of migration in the second embodiment [Figure 15] FIG. 1 is an explanatory diagram of the migration process of the second embodiment. [Figure 16] FIG. 2 is an explanatory diagram of the migration process of the second embodiment. [Figure 17] FIG. 1 is an explanatory diagram of the migration process of the third embodiment. [Figure 18] FIG. 2 is an explanatory diagram of the migration process of the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, an embodiment will be described with reference to the drawings. [Example]

[0010] FIG. 1 is an explanatory diagram of migration in Example 1. The storage system in Example 1 has a primary site 201a and a secondary site 201b. The primary site 201a and the secondary site 201b each have a plurality of nodes. The plurality of nodes have a storage control system (SCS) 501. As an example, each node is provided with a plurality of SCSs 501 for redundancy.

[0011] One of the nodes in the primary site 201a has a primary volume (PVOL) 102x. One of the nodes in the secondary site 201b has a secondary volume (SVOL) 102y. The primary volume 102x and the secondary volume 102y form a volume pair 103a. The configuration of the storage system of the secondary site 201 b is managed as configuration information 105 .

[0012] The process when the user terminal 100 receives an operation from the user and moves the secondary volume 102y to another node in the secondary site 201b will be described. (1) The user terminal 100 selects a secondary volume 102y to be the migration target. The selected secondary volume 102y is called the source volume, source secondary volume, or SVOL (source). The node that has the source volume is called the source node. (2) The user terminal 100 sets a path for remote copying. This process includes (2-a) and (2-b). (2-a) A node having a secondary volume 102z that is the destination of the migration is selected. The secondary volume 102z that is the destination of the migration is called the migration destination volume, migration destination secondary volume, or SVOL(dest.). The node having the migration destination volume is called the migration destination node. (2-b) A path is set from the node having the primary volume 102x to the node having the destination secondary volume 102z. (3) A new volume pair 103b is formed between the primary volume 102x and the migration destination secondary volume 102z, and the data is synchronized. (4) The volume pair 103a between the primary volume 102x and the source secondary volume 102y is released.

[0013] 2 shows the hardware configuration of a storage system. Multiple sites 201 are connected via a network 202. Each site 201 includes multiple nodes 210. The multiple nodes 210 are connected within the site 201 via a network 220 so that they can communicate with each other.

[0014] Each node 210 has a configuration in which a control device 211, a plurality of drives 214 as storage devices, and ports 215 are connected by a bus 216. Port 215 communicates with other nodes over network 220 . The plurality of drives 14 comprises a physical storage area. The control device 211 has a processor 213 and a memory 212. The processor 213 operates as a storage control system (SCS) by loading and executing a predetermined program in the memory 212. The storage control system (SCS) configures volumes, which are logical storage areas, from the physical storage areas of the drives 214, and processes input and output to and from the volumes.

[0015] Fig. 3 is an explanatory diagram of remote copying. In Fig. 3, the primary site 201a includes a node 210a, a node 210b, and a node 210c. The secondary site 201b includes a node 210d, a node 210e, and a node 210f.

[0016] The node 210a has a primary volume 102a, a primary volume 102b, and a journal volume 102c. The node 210d has a journal volume 102h, a secondary volume 102i, and a secondary volume 102j.

[0017] The primary volume 102a, the primary volume 102b, the journal volume 102c, the journal volume 102h, the secondary volume 102i, and the secondary volume 102j belong to group 1, in which consistency is managed. Writes to primary volume 102a and primary volume 102b are accumulated in journal volume 102c. The contents of journal volume 102c are transferred to journal volume 102h, and then chronologically reflected in secondary volumes 102i and 102j, thereby achieving asynchronous remote copying of group 1.

[0018] Furthermore, the node 210b has a primary volume 102d and a journal volume 102e, and the node 210c has a primary volume 102f and a journal volume 102g. The node 210e has a journal volume 102k and a secondary volume 102l, and the node 210f has a journal volume 102m and a secondary volume 102n.

[0019] Primary volume 102d, journal volume 102e, primary volume 102f, journal volume 102g, journal volume 102k, secondary volume 102l, journal volume 102m, and secondary volume 102n belong to group 2, in which consistency is managed. Writes to primary volume 102d are accumulated in journal volume 102e. Writes to primary volume 102f are accumulated in journal volume 102g. The contents of journal volumes 102e and 102g are transferred up to the write data at the same time. Data in journal volume 102e is transferred to journal volume 102k and then reflected in secondary volume 102l. Data in journal volume 102g is transferred to journal volume 102m and then reflected in secondary volume 102n. As a result, asynchronous remote copying of group 2 is achieved.

[0020] Figure 4 is an explanatory diagram of input / output processing. The following describes a case where a host 401 at the primary site 201a performs a write. An application 402 at the host 401 writes data "A" and "B" to the primary volume 102a. The node 210a that owns the primary volume 102a accumulates a history of writes to the primary volume 102a in a journal volume 102c.

[0021] The data "A" and "B" stored in journal volume 102c are transferred to secondary site 201b. In the example of FIG. 4, data 403a, which is the write history of data "A," is sent directly to node 210d and stored in journal volume 102h. Data 403b, which is the write history of data "B," is sent to node 210d via node 210e and stored in journal volume 102h. The writing of data "A" and the writing of data "B" are then reflected in secondary volume 102i. As a result, the contents of secondary volume 102i match the contents of primary volume 102a. The host at the secondary site 201b is capable of reading from the secondary volume 102i.

[0022] 5 is a list of memory information. The information stored in the memory 212 includes a control information table 610 and a storage program 620. The control information table 610 includes a system configuration management table 611 , a pair configuration management table 612 , a journal management table 613 , and a migration configuration management table 614 . The storage program 620 includes a path creation processing program 621, a node failure recovery processing program 622, a data transfer processing program 623, a path change processing program 624, an I / O processing program 625, and a migration processing program 626. By executing the various programs included in this storage program 620, the processor 213 realizes the function of a storage control system (SCS). This memory information can be backed up in the storage area of ​​the drive 214.

[0023] 6 is a specific example of the system configuration management table 611. The system configuration management table 611 includes a node configuration management table 710, a drive configuration management table 720, and a port configuration management table 730. The node configuration management table 710 includes the following items: a node ID 711, a node status 712, a drive ID list 713 indicating drives that the node has, and a port ID list 714 indicating ports that the node has. The drive configuration management table 720 has the following items: drive ID 721 , drive status 722 , and drive size 723 . The port configuration management table 730 includes the following items: port ID 731 , port status 732 , and port address 733 .

[0024] 7 is a specific example of the pair configuration management table 612. The pair configuration management table 612 includes a volume management table 810, a pair management table 820, and a path management table 830. The volume management table 810 includes the following items: volume ID, owner node ID 812, retreat node ID 813, size 814, attribute 815, and internal identifier 816. The attribute 815 takes values ​​such as normal VOL, PVOL, SVOL, and JNVOL (journal volume).

[0025] The pair management table 820 has the following items: pair ID 821 , primary journal group ID 822 , primary volume ID 823 , secondary journal group ID 824 , secondary volume ID 825 , path ID 826 , and status 827 . The path management table 830 has the following fields: path ID 831 , protocol information 832 , destination address 833 , access policy 834 , and preferred path 835 .

[0026] 8 is a specific example of the journal management table 613. The journal management table 613 includes a journal group ID and the volume ID of the volume managed by the journal group.

[0027] 9 is a specific example of the migration configuration management table 614. The migration configuration management table 614 includes a volume management table 1010 and a volume migration management table 1020. The volume management table 1010 includes the following items: volume ID, owner node ID, retreat destination node ID, and status. The volume migration management table 1020 includes the following items: migration process ID 921 , migration source volume ID 922 , migration destination volume ID 923 , and status 924 .

[0028] 10 is an explanatory diagram of the path creation process. In the path creation process, first, the user terminal 100 instructs the SCS 501A of the primary site to create a path (step S901). The SCS 501A receives the instruction to create a path (step S902) and transmits a login request to the specified node (step S903).

[0029] The SCS 501B of the secondary site receives the login request (step S904), and then notifies the SCS 501A that the login has been completed (step S905).

[0030] When the SCS 501A receives the login completion notification (step S906), it compares the login response information with the input information (step S907). If the login response information matches the input information, the SCS 501A validates the path (step S908) and notifies the user terminal 100 of the completion of the operation (step S909). When the user terminal 100 receives a notification that the operation is complete (step S910), the path creation process ends.

[0031] FIG. 11 is an explanatory diagram of the remote copy process (asynchronous transfer). The SCS 501A, which is the owner node of the primary volume, writes write data from the host to the primary volume (step S1101), and then writes the write data to the primary volume together with metadata to the journal volume of the primary volume (step S1102).

[0032] The SCS 501B of the source node (SVOL source node) having the source secondary volume sends a journal read request to the SCS 501A (step S1103). The SCS 501A receives the journal read request (step S1104) and transfers the update differential data metadata of the journal volume (step S1105). The SCS 501B receives the update differential data and metadata (step S1106) and writes the received data and metadata to the journal volume of the secondary volume (step S1107).Then, the SCS 501B writes data from the journal volume of the secondary volume to the secondary volume (step S1108).

[0033] 12 and 13 are explanatory diagrams of the migration process of the embodiment 1. This migration process involves the user terminal 100, SCS 501A, SCS 501B, SCS 501C, and SCS 501D.

[0034] The SCS 501A is the SCS of the owner node of the primary volume. The SCS 501B is the SCS of the source node (SVOL source node) that has the source secondary volume. The SCS 501C is the SCS of the destination node (SVOL destination node) that has the secondary volume of the destination. The SCS 501D is a discovery node SCS that centrally manages the configuration of secondary sites.

[0035] First, the user terminal 100 determines a destination node and instructs the creation of a volume (step S1201). The SCS of the node that receives this instruction is the SCS 501C. The SCS 501C creates a secondary volume at the destination (step S1202). The identification information for this volume is Vol1. Furthermore, the user terminal 100 instructs the SCS 501C to create a journal volume (step S1203). In response to this instruction, the SCS 501C creates a journal volume (step S1204). This volume identification information is designated as JNLVol3.

[0036] Next, the user terminal 100 performs migration registration by specifying VOL0, which is the migration target, as the source volume ID and the created Vol1 as the destination volume ID (step S1205). Migration registration is performed by registering the VolID pair information in the volume migration management table 1020 (step S1206). Furthermore, since this migration process is a migration that maintains the remote copy pair, it is managed by assigning a status of "Remote Copying" to distinguish it from other migrations.

[0037] The user terminal 100 queries the SCS 501D for the identifier of the node that has the primary volume paired with the source secondary volume (step S1207). The SCS 501D acquires information from the shared database between the nodes (step S1208), and returns the node information to the user terminal 100 (step S1209).

[0038] The user terminal 100 receives the node information as a response (step S1210) and performs a path creation process (step S1211). This path creation process is a process for creating a path from the owner node of the primary volume to the destination node.

[0039] Thereafter, the system performs pair formation processing (step S1212). Specifically, first, the user terminal 100 instructs the SCS 501A to form a pair using the primary volume, Vol0, and JNLVol3 (step S1213). Here, Vol0 is the identification information of the migration source secondary volume. When the SCS 501A receives the instruction (step S1214), it requests the representative node 501D to form a pair with Vol0 (step S1215).

[0040] When the representative node 501D receives the instruction (step S1216), it identifies the owner node of JNLVol3 (i.e., the destination node) from the database shared between the nodes (step S1217). Then, it identifies Vol0 and Vol1 (i.e., the destination secondary volume) that is being migrated within the target node using the volume migration management table 1020 (step S1218). That is, it searches the source volume ID 922 column using Vol0 as a key, and sets the destination volume ID 923 corresponding to the matching row as the VolID of the volume being migrated. Next, the VolID being migrated is compared with the owner node of JNLVO1, and if they do not match, an error is returned as an operational error. The node of the VolID being migrated is identified by referencing the volume management table 1010. The owner node of JNLVO1 identifies the volume ID from the journal management table 613, and then identifies the owner node ID of that volume ID by referencing the volume management table 1010. If the two match, the process continues.

[0041] The SCS 501C of the identified destination node forms a pair between Vol1, which is the destination secondary volume, and the primary volume (step S1219). The SCS 501C starts the copy process from the primary volume to Vol1 (step S1220) and completes the copy (step S1221). After SCS501C starts copying, SCS501D sends a response to SCS501A indicating that pair creation is complete (step S1222). Upon receiving the response indicating that pair creation is complete (step S1223), SCS501A notifies the user terminal 100 that the operation is complete (step S1224). The user terminal 100 receives the notification and completes the operation (step S1225).

[0042] Thus, in the pair creation process of this embodiment, the user terminal 100 instructs the creation of a new pair by specifying the identification information (Vol0) of the source secondary volume and the identification information (JNLVol3) of the journal volume corresponding to the destination secondary volume. SCS501A of the node having the primary volume (PVol) does not directly create a pair using the identification information (Vol0) of the specified secondary volume, but rather identifies the node by making an inquiry to SCS501D of the representative node based on JNLVol3, and designates Vol1, which is being migrated to Vol0 within that node, as the destination. In this way, a pair is created with the destination secondary volume by replacing Vol0 with Vol1.

[0043] After the pair creation process shown in Fig. 12, the user terminal 100 waits for the copy of SCS 501B to be completed (step S1301), as shown in Fig. 13. After the copy is completed, the user terminal 100 instructs SCS 501B of the source node to put input / output to the source secondary volume on hold (step S1302). The SCS 501B receives an instruction from the user terminal 100 (step S1303) and puts input / output to the source secondary volume on hold (step S1304).

[0044] Thereafter, the user terminal 100 instructs the SCS 501A to release the pair (old pair) between the primary volume and the migration source secondary volume (step S1305). The SCS 501A receives the instruction from the user terminal 100 (step S1306) and releases the pair (step S1307). The SCS 501B updates the pair status upon receiving the pair release (step S1308). After canceling the pair, the SCS 501A transmits a completion response to the user terminal 100 (step S1309), and the user terminal 100 completes the operation (step S1310). Thereafter, post-migration processing is performed (step S1311).

[0045] In post-migration processing, the user terminal 100 sends a volume swap instruction to the SCS 501B (step S1312). Upon receiving the instruction (step S1313), the SCS 501B updates the volume ID in the volume management table by replacing the value of the ID of the destination secondary volume (Vol1 in this example) with the ID of the source secondary volume (Vol0 in this example). The secondary volume ID in the pair management table is also updated by rewriting the value of the destination secondary volume ID (Vol1 in this example) to the ID of the source secondary volume (Vol0 in this example) (step S1314). After that, the entry relating to the migration process registered in this process is deleted from the volume migration management table. Thereafter, the pending input / output is released (step S1315), a path change is notified (step S1316), and a completion response is sent to the user terminal 100 (step S1317). The user terminal 100 receives the completion response, completes the operation (step S1318), and instructs the SCS 501B to delete the migration source secondary volume (step S1319). The SCS 501B receives the instruction from the user terminal 100 and deletes the source secondary volume (step S1320), and ends post-migration processing.

[0046] In this way, when forming a pair with a migration destination volume, the identification information of the migration destination journal volume is used for rereading, and after forming a pair with the migration destination secondary volume, the identification information of the migration source secondary volume is rewritten to the identification information of the migration destination secondary volume. As a result, the primary volume can perform secondary volume migration while remaining paired with the same secondary volume identification information.

[0047] In the above explanation, the user terminal 100 receives an operation from the user and executes a series of processes, but the SCS 501 may execute the processes instead of the user terminal. [Example]

[0048] In this second embodiment, a configuration in which data is copied from a source secondary volume to a destination secondary volume will be described. Fig. 14 is an explanatory diagram of migration in Example 2. The storage system in Example 2 has a primary site 201a and a secondary site 201b. The primary site 201a and the secondary site 201b each have a plurality of nodes. The plurality of nodes have a storage control system (SCS) 501. As an example, each node is provided with a plurality of SCSs 501 for redundancy.

[0049] One of the nodes in the primary site 201a has a primary volume (PVOL) 102x. One of the nodes in the secondary site 201b has a secondary volume (SVOL) 102y. The primary volume 102x and the secondary volume 102y form a volume pair 103a. The configuration of the storage system of the secondary site 201 b is managed as configuration information 105 .

[0050] The process when the user terminal 100 receives an operation from the user and moves the secondary volume 102y to another node in the secondary site 201b will be described. (1) The user terminal 100 selects a secondary volume 102y to be the migration target. The selected secondary volume 102y is called the source volume, source secondary volume, or SVOL (source). The node that has the source volume is called the source node. (2) The user terminal 100 sets a path for remote copying. This process includes (2-a) and (2-b). (2-a) A node having a secondary volume 102z that is the destination of the migration is selected. The secondary volume 102z that is the destination of the migration is called the migration destination volume, migration destination secondary volume, or SVOL(dest.). The node having the migration destination volume is called the migration destination node. (2-b) A path is set from the node having the primary volume 102x to the destination node having the destination secondary volume 102z, and a path is also set from the source node to the destination node. (3) A new volume pair is formed between the source secondary volume 102y and the destination secondary volume 102z, and the data is synchronized. (4) A new volume pair 103b is formed from the primary volume 102x and the destination secondary volume 102z, but the data is not copied and is held. (5) Activate the delta volume paths of the primary volume 102x, the source secondary volume 102y, and the destination secondary volume 102z. (6) The volume pair 103a between the primary volume 102x and the source secondary volume 102y is released, and the source secondary volume is deleted.

[0051] 15 and 16 are explanatory diagrams of the migration process of the embodiment 2. This migration process involves the user terminal 100, SCS 501A, SCS 501F, SCS 501G, and SCS 501D.

[0052] The SCS 501A is the SCS of the owner node of the primary volume. The SCS 501F is the SCS of the source node (SVOL source node) that has the source secondary volume. The SCS 501G is the SCS of the destination node (SVOL destination node) that has the secondary volume of the destination. The SCS 501D is a discovery node SCS that centrally manages the configuration of secondary sites.

[0053] First, the user terminal 100 determines the destination node and instructs the creation of a volume (step S1501). The SCS of the node that receives this instruction is the SCS 501G. The SCS 501G creates a secondary volume at the destination (step S1502). The identification information for this volume is Vol1. Furthermore, the user terminal 100 instructs the SCS 501G to create a journal volume (step S1503). In response to this instruction, the SCS 501G creates a journal volume (step S1504). This volume identification information is designated as JNLVol3.

[0054] The user terminal 100 queries the SCS 501D for the identifier of the node that has the primary volume paired with the migration source secondary volume (step S1505). The SCS 501D acquires information from the shared database between the nodes (step S1506), and returns the node information to the user terminal 100 (step S1507).

[0055] The user terminal 100 receives the node information as a response (step S1508) and performs a path creation process to create a path from the source node to the destination node (step S1509).After that, a pair is formed between the source secondary volume (Vol0) and the destination secondary volume (Vol1) using JNLVol3 (step S1510).

[0056] Pair formation using JNLVol3 is a process in which the creation of a new pair is instructed by specifying the identification information of the source secondary volume (Vol0) and the identification information of the journal volume corresponding to the destination secondary volume (JNLVol3), and then Vol0 is reinterpreted as Vol1 by querying the representative node SCS501D based on JNLVol3, thereby forming a pair with the destination secondary volume.

[0057] After forming a pair between the source secondary volume (Vol0) and the destination secondary volume (Vol1), a path creation process is performed to create a path from the owner node of the primary volume to the destination node (step S1511). Then, a pair is formed between the primary volume and the destination secondary volume (Vol1) using JNLVol3 (step S1512). As a result, a delta pair is formed between the primary volume, source secondary volume (Vol0), and destination secondary volume (Vol1). Note that data is not copied from the primary volume to the destination secondary volume (Vol1) and the state is put into hold.

[0058] After the delta pair shown in Fig. 15 is formed, the user terminal 100 waits for the completion of copying data from the source secondary volume (Vol0) to the destination secondary volume (Vol1) (step S1601), as shown in Fig. 16. After the copying is complete, the user terminal 100 instructs the SCS 501A to release the pair (old pair) between the primary volume and the source secondary volume (step S1602). The SCS 501A receives the instruction from the user terminal 100 (step S1603) and releases the pair (step S1604). The SCS 501F updates the pair status upon receiving the pair release (step S1605). After canceling the pair, the SCS 501A transmits a completion response to the user terminal 100 (step S1606), and the user terminal 100 completes the operation (step S1607).

[0059] The user terminal 100 instructs the SCS 501F of the source node to put input / output to the source secondary volume on hold (step S1608). The SCS 501F receives an instruction from the user terminal 100 (step S1609), puts input / output to the source secondary volume on hold (step S1610), and the user terminal 100 completes the operation (step S1611). The user terminal 100 instructs the SCS 501A to validate the delta pair (step S1612). The SCS 501A receives the instruction from the user terminal 100 (step S1613) and changes the state of the delta pair to copy (step S1614). The SCS 501F updates the pair status (step S1615). After canceling the pair, the SCS 501A transmits a completion response to the user terminal 100 (step S1616), and the user terminal 100 completes the operation (step S1617).

[0060] Thereafter, post-migration processing is performed (step S1618). The post-migration processing is the same as in the first embodiment and so a detailed explanation will be omitted, but it includes switching the identification information of the source secondary volume and the destination secondary volume.

[0061] In this way, when forming a pair with a migration destination volume, the identification information of the migration destination journal volume is used for rereading, and after forming a pair with the migration destination secondary volume, the identification information of the migration source secondary volume is rewritten to the identification information of the migration destination secondary volume. As a result, the primary volume can perform secondary volume migration while remaining paired with the same secondary volume identification information. Furthermore, because data is copied from the source secondary volume to the destination secondary volume, the data copy is completed within the secondary site, reducing the amount of communication between the primary site and the secondary site. [Example]

[0062] In this third embodiment, a process for moving the primary volume to another node within the main site will be described.

[0063] 17 and 18 are explanatory diagrams of the migration process of the embodiment 3. This migration process involves the user terminal 100, SCS 501A, SCS 501B, SCS 501H, and SCS 501J.

[0064] The SCS 501A is the SCS of the source node that has the source primary volume PVol(source). The SCS 501B is the SCS of the owner node of the secondary volume (SVOL). The SCS 501H is the SCS of the destination node that has the destination primary volume PVol(dest.). The SCS501J is a discovery node SCS that centrally manages the configuration of the primary site.

[0065] First, the user terminal 100 determines the destination node and instructs the creation of a volume (step S1701). The SCS of the node that receives this instruction is the SCS501H. The SCS501H creates a destination primary volume PVol(dest.) (step S1702). The identification information for this volume is Vol1. Furthermore, the user terminal 100 instructs the SCS 501H to create a journal volume (step S1703). In response to this instruction, the SCS 501H creates a journal volume (step S1704). This volume identification information is designated as JNLVol3.

[0066] The user terminal 100 queries the SCS 501J for the identifier of the node that has the secondary volume paired with the source primary volume (step S1705). The SCS 501J acquires information from the shared database between the nodes (step S1706), and returns the node information to the user terminal 100 (step S1707).

[0067] The user terminal 100 receives the node information as a response (step S1708) and performs a path creation process to create a path from the source node to the destination node (step S1709).After that, a pair is formed between the source primary volume PVol(source) (Vol0) and the destination primary volume PVol(dest.) (Vol1) using JNLVol3 (step S1710).

[0068] Pair formation using JNLVol3 is a process in which the identification information of the source primary volume (Vol0) and the identification information of the journal volume corresponding to the destination primary volume (JNLVol3) are specified to instruct the formation of a new pair, and Vol0 is reinterpreted as Vol1 by querying the representative node SCS501J based on JNLVol3, thereby forming a pair with the destination primary volume.

[0069] After forming a pair between the source primary volume PVol(source) (Vol0) and the destination primary volume PVol(dest.), a path creation process is performed to create a path from the destination node to the owner node of the secondary volume (step S1711). Then, a pair is formed between the destination primary volume PVol(dest.) and the secondary volume using JNLVol3 (step S1712). As a result, a delta pair is formed between the source primary volume (Vol0), secondary volume, and destination primary volume (Vol1). Note that data is not copied from the secondary volume to the destination primary volume (Vol1) and the state is put into hold.

[0070] After the delta pair shown in FIG. 17 is formed, the user terminal 100 instructs the release of the pair (old pair) between the source primary volume PVol(source) (Vol0) and the secondary volume, as shown in FIG. 18 (step S1801). The SCS 501A receives the instruction from the user terminal 100 and releases the pair (step S1802). The SCS 501B updates the pair status upon receiving the pair release (step S1804). After canceling the pair, the SCS 501A transmits a completion response to the user terminal 100 (step S1805), and the user terminal 100 completes the operation (step S1806).

[0071] The user terminal 100 also issues an instruction to release the pair between the source primary volume PVol(source) (Vol0) and the destination primary volume PVol(dest.) (Vol1) (step S1807). The SCS 501A receives the instruction from the user terminal 100 (step S1808) and releases the pair (step S1809). The SCS 501H updates the pair status upon receiving the pair release (step S1810). After canceling the pair, the SCS 501A transmits a completion response to the user terminal 100 (step S1811), and the user terminal 100 completes the operation (step S1812).

[0072] The user terminal 100 instructs the SCS 501A of the source node to put input / output to the source primary volume PVol(source) on hold (step S1813). The SCS 501A receives an instruction from the user terminal 100 (step S1814), puts input / output to the source primary volume PVol (source) on hold (step S1815), and the user terminal 100 completes the operation (step S1816). The user terminal 100 instructs the SCS 501H to validate the delta pair (step S1817). The SCS 501H receives the instruction from the user terminal 100 (step S1818) and changes the state of the delta pair to copy (step S1819). The SCS 501B updates the pair status (step S1820). The SCS 501H transmits a completion response to the user terminal 100 (step S1821), and the user terminal 100 completes the operation (step S1822).

[0073] Thereafter, post-migration processing is performed (step S1823). The post-migration processing is the same as in the first embodiment and so a detailed explanation will be omitted, but it includes switching the identification information of the source primary volume and the destination primary volume.

[0074] In this way, when forming a pair with a migration destination volume, the identification information of the migration destination journal volume is used for rereading, and after forming a pair with the migration destination primary volume, the identification information of the migration source primary volume is rewritten to the identification information of the migration destination primary volume. As a result, the secondary volume can perform migration of the primary volume while remaining paired with the identification information of the same primary volume.

[0075] As described above, the disclosed system comprises a plurality of nodes 210 each having a processor 213, a first node configuring a primary volume that provides a logical storage area to a host 401, a second node configuring a secondary volume that forms a remote copy pair with the primary volume and sets the remote copy using identification information for the primary volume and identification information for the secondary volume, a third node configuring a destination volume that becomes the migration destination when migration is performed using the secondary volume as the source volume, when the first node receives a request to create a new pair specifying the identification information for the primary volume, the identification information for the secondary volume, and information that identifies the third node, it forms a new pair between the primary volume and the destination volume, and the second node releases the pair between the secondary volume and the primary volume and replaces the identification information of the destination volume with the identification information of the secondary volume. This allows migration of the secondary volume while maintaining the pair.

[0076] As an example, after the second node puts input / output to the secondary volume on hold, it releases the pair between the secondary volume and the primary volume, replaces the identification information of the destination volume with the identification information of the secondary volume, and releases the pending state. Therefore, migration is possible without changing the volume identification information related to the remote copy settings and without affecting the contents of the volume.

[0077] As another example, the first node further configures a first journal volume that accumulates a history of writes to the primary volume, and the third node further configures a third journal volume that corresponds to the first journal volume after migration, and uses identification information of the third journal volume as information to identify the third node. In this way, by using the identification information of the journal volume, it is possible to form a pair with the migration destination volume without changing the identification information of the volume related to the remote copy settings.

[0078] As another example, after forming the new pair, the third node obtains the contents of the primary volume from the first node and copies them to the destination volume, and after the copying is completed, the second node releases the pair between the secondary volume and the primary volume and replaces the identification information of the destination volume with the identification information of the secondary volume. With this configuration and operation, migration of the secondary volume can be performed with simple processing.

[0079] As another example, after forming the new pair, the third node obtains the contents of the secondary volume from the second node and copies them to the destination volume, and after the copying is completed, the second node releases the pair between the secondary volume and the primary volume and replaces the identification information of the destination volume with the identification information of the secondary volume. This configuration and operation allows migration of the secondary volume while maintaining the pair, while suppressing communication between the primary site and secondary site.

[0080] As another example, a system includes a plurality of nodes each having a processor, wherein a first node configures a primary volume that provides a logical storage area to a host, a second node configures a secondary volume that forms a remote copy pair with the primary volume and sets the remote copy using identification information of the primary volume and identification information of the secondary volume, a third node configures a destination volume that becomes the migration destination when migrating using the primary volume as the source volume, and when the second node receives a request to form a new pair specifying the identification information of the primary volume, the identification information of the secondary volume, and information that identifies the third node, it forms a new pair between the secondary volume and the destination volume, and the first node releases the pair between the secondary volume and the primary volume and replaces the identification information of the destination volume with the identification information of the primary volume. This configuration and operation allows migration of the primary volume while maintaining the pair.

[0081] The present invention is not limited to the above-described embodiments, but includes various modifications. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the described configurations. Furthermore, not only can the configurations be deleted, but also replacements and additions of configurations are possible. [Explanation of symbols]

[0082] 100: User terminal, 102: Volume, 103: Volume pair, 105: Configuration information, 201: Site, 202: Network, 210: Node, 211: Control device, 212: Memory, 213: Processor, 214: Drive, 215: Port, 216: Bus, 220: Network, 401: Host, 402: Application, 403: Data, 610: Control information table, 611: System configuration management table, 612: Pair configuration management table, 613: Journal management table, 614: Migration configuration management table, 620: Storage program, 621: Path creation processing program, 622: Node failure recovery processing program, 623: Data transfer processing program, 624: Path change processing program, 625: I / O processing program, 626: Migration processing program

Claims

1. a plurality of nodes each having a processor; The first node configures a primary volume that provides a logical storage area to the host; a second node configures a secondary volume that forms a remote copy pair with the primary volume, and sets the remote copy using identification information of the primary volume and identification information of the secondary volume; the third node configures a migration destination volume that is a migration destination when migrating the secondary volume as the migration source volume; when the first node receives a request for forming a new pair that specifies the identification information of the primary volume, the identification information of the secondary volume, and information that specifies the third node, the first node forms a new pair between the primary volume and the destination volume; The second node releases the pair between the secondary volume and the primary volume, and replaces the identification information of the destination volume with the identification information of the secondary volume. A storage system comprising:

2. 2. The storage system according to claim 1, A storage system characterized in that the second node, after pending input / output to the secondary volume, releases the pair between the secondary volume and the primary volume, replaces the identification information of the destination volume with the identification information of the secondary volume, and releases the pending state.

3. 2. The storage system according to claim 1, the first node further configures a first journal volume that accumulates a history of writes to the primary volume; the third node further configures a third journal volume corresponding to the first journal volume after migration; A storage system using identification information of the third journal volume as information for specifying the third node.

4. 2. The storage system according to claim 1, After the new pair is formed, the third node acquires the contents of the primary volume from the first node and copies them to the destination volume; a second node that, after the copy is completed, releases the pair between the secondary volume and the primary volume and replaces the identification information of the destination volume with the identification information of the secondary volume;

5. 2. The storage system according to claim 1, After the new pair is formed, the third node acquires the content of the secondary volume from the second node and copies it to the destination volume; a second node that, after the copy is completed, releases the pair between the secondary volume and the primary volume and replaces the identification information of the destination volume with the identification information of the secondary volume;

6. a plurality of nodes each having a processor; The first node configures a primary volume that provides a logical storage area to the host; a second node configures a secondary volume that forms a remote copy pair with the primary volume, and sets the remote copy using identification information of the primary volume and identification information of the secondary volume; the third node configures a migration destination volume that becomes a migration destination when migration is performed using the primary volume as the migration source volume; when the second node receives a request for forming a new pair that specifies the identification information of the primary volume, the identification information of the secondary volume, and information that specifies the third node, it forms a new pair between the secondary volume and the migration destination volume; The first node releases the pair between the secondary volume and the primary volume, and replaces the identification information of the destination volume with the identification information of the primary volume. A storage system comprising:

7. A method for managing a storage system having a plurality of nodes each having a processor, comprising: The first node configures a primary volume that provides a logical storage area to the host; a second node configures a secondary volume that forms a remote copy pair with the primary volume, and sets the remote copy using identification information of the primary volume and identification information of the secondary volume; the third node configures a migration destination volume that is a migration destination when migrating the secondary volume as the migration source volume; when the first node receives a request for forming a new pair that specifies the identification information of the primary volume, the identification information of the secondary volume, and information that specifies the third node, the first node forms a new pair between the primary volume and the destination volume; The second node releases the pair between the secondary volume and the primary volume, and replaces the identification information of the destination volume with the identification information of the secondary volume. A storage system management method comprising:

8. A method for managing a storage system having a plurality of nodes each having a processor, comprising: The first node configures a primary volume that provides a logical storage area to the host; a second node configures a secondary volume that forms a remote copy pair with the primary volume, and sets the remote copy using identification information of the primary volume and identification information of the secondary volume; the third node configures a migration destination volume that becomes a migration destination when migration is performed using the primary volume as the migration source volume; when the second node receives a request for forming a new pair that specifies the identification information of the primary volume, the identification information of the secondary volume, and information that specifies the third node, it forms a new pair between the secondary volume and the migration destination volume; The first node releases the pair between the secondary volume and the primary volume, and replaces the identification information of the destination volume with the identification information of the primary volume. A storage system management method comprising:

Images