Storage system and data replication method in storage

Abstract

In a storage system, management operations of Snapshots are enabled even for logical volumes that cannot be given a pair relationship. 【Solution means】The storage system 201 generates meta-information management information that manages the correspondence between family identification information, intra-family identification information, and destination meta-information. The storage system 201 also generates conversion information that manages the correspondence between the identification information of the source logical volume for replication and the identification information of the destination logical volume for replication, respectively, and the family identification information and the intra-family identification information. In response to an access request from a higher-level device, the storage system 201 refers to the conversion information, and acquires the corresponding family identification information and intra-family identification information from the identification information of the source logical volume for replication and the destination logical volume for replication. Then, based on the acquired information, the storage system 201 refers to the meta-information management information, acquires the destination meta-information corresponding to each of the source logical volume for replication and the destination logical volume for replication, and accesses each data.

Description

Technical Field

[0001] The present invention relates to a storage system and a data replication method in storage.

Background Art

[0002] In recent years, the need for data utilization has increased, and the opportunity for data replication has also increased. Along with this, in a storage system, the volume replication function has become increasingly important. As a volume replication function, for example, there is a technology for quickly creating a Snapshot of a logical volume (LDEV) within a local storage. In this technology, instead of copying (moving) data, a method (redirect-on-write (RoW)) of updating only the metadata indicating the storage location of the data is adopted, thereby realizing high-speed splitting (Snapshot creation) and high-speed restoration (data recovery from a Snapshot). And in RoW, a conventional technique has been proposed to prevent a decrease in I / O performance by copying meta-information during data splitting and restoration (see, for example, Patent Document 1).

[0003] In this conventional technique, by defining a relationship called a pair between the source logical volume of the Snapshot and the destination logical volume, the relevance of data is managed, and Snapshot management operations such as data splitting and restoration are executed in units of pairs.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in the above-described conventional technology, there is a problem that even for logical volumes related to Snapshots, management operations of Snapshots cannot be executed between logical volumes to which a pair relationship cannot be assigned. Logical volumes to which a pair relationship cannot be assigned include, for example, a logical volume obtained by further replicating a replication destination logical volume with respect to a replication source logical volume, and the replication source logical volume, and there are also two replication destination logical volumes with respect to the replication source logical volume. Thus, logical volumes with non-consecutive Snapshot generations cannot be assigned a pair relationship, and management operations of Snapshots cannot be executed.

[0006] The present invention has been made in view of the above problems, and an object thereof is to enable management operations of Snapshots even between logical volumes to which a pair relationship cannot be assigned in a storage system.

Means for Solving the Problems

[0007] In order to achieve the above object, in the present invention, a storage system having a storage controller that provides a plurality of logical volumes to a host device and can create a snapshot as a destination logical volume that is a copy of a source logical volume, wherein the storage controller manages a pair management information that manages a correspondence between a set of identification information of the source logical volume and identification information of the destination logical volume indicating a pair relationship of the snapshots of the source logical volume and the destination logical volume, and first reference destination meta information indicating a reference destination of data stored in the destination logical volume, manages each information of replication source management information that manages a correspondence between the identification information of the source logical volume and second reference destination meta information indicating a reference destination of data stored in the source logical volume, assigns the same family identification information that uniquely identifies the family to the source logical volume and the destination logical volume so that the source logical volume and the destination logical volume belong to the same family within a family indicating a group of the logical volumes, assigns family internal identification information that uniquely identifies the logical volume within the same family to the first reference destination meta information and the second reference destination meta information, generates meta information management information that manages a correspondence between the family identification information, the family internal identification information, the first reference destination meta information, and the second reference destination meta information, generates conversion information that manages a correspondence between each of the identification information of the source logical volume and the identification information of the destination logical volume, the family identification information to which the source logical volume and the destination logical volume belong, and the family internal identification information of the source logical volume and the destination logical volume, and in response to an access request to each of the data stored in the source logical volume and the destination logical volume from the host device, refers to the conversion information, obtains the corresponding family identification information and the family internal identification information from the identification information of the source logical volume and the identification information of the destination logical volume, respectively, and refers to the meta information management information based on the obtained family identification information and the family internal identification information,Obtaining the first reference destination meta information and the second reference destination meta information corresponding to each of the source logical volume and the destination logical volume, and accessing each of the data stored in the source logical volume and the destination logical volume based on the obtained first reference destination meta information and the second reference destination meta information.

Effect of the Invention

[0008] According to the present invention, in a storage system, even logical volumes that cannot be given a pair relationship can be managed by Snapshot.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10A

Figure 10B

Figure 10C

Figure 10D

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15A

Figure 15B

Best Mode for Carrying Out the Invention

[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the embodiments described below do not limit the invention according to the claims, and not all of the elements and combinations thereof described in the embodiments are essential for the solution means of the invention. Also, for configurations that are essential for the configuration of the invention but are well-known, illustration and description may be omitted.

[0011] In the following description, expressions such as "xxx table" may be used to describe information from which output is obtained for input, but this information may be data of any structure. Therefore, "xxx table" can be referred to as "xxx information".

[0012] In the following description, the configuration of each table is an example, and one table may be divided into two or more tables, or all or part of two or more tables may be combined into one table.

[0013] In the following description, the "program" may be used as the subject to describe the processing. The program, when executed by the processor unit, performs the defined processing while appropriately using the storage unit and / or the network interface, etc. Therefore, the subject of the processing may be the processor unit (or a device such as a controller having the processor unit).

[0014] The program may be installed in a device such as a computer, or may be, for example, in a program distribution server or a computer-readable (e.g., non-transitory) recording medium. In the following description, two or more programs may be realized as one program, or one program may be realized as two or more programs.

[0015] Also, the "processor unit" is one or more processors. A processor is typically a microprocessor such as a CPU (Central Processing Unit), but may also be another type of processor such as a GPU (Graphics Processing Unit). Also, the processor may be single-core or multi-core. Also, the processor may be a processor in a broad sense such as a hardware circuit (e.g., FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit)) that performs part or all of the processing.

[0016] In the following description, an identification number is used as identification information for various objects, but other types of identification information (e.g., an identifier including letters or symbols) may be adopted. In the following description, "#" represents a number, for example, "xxx#" represents xxx identified by the number.

[0017] In the following description, when describing elements of the same type without distinction, reference signs (or common signs among the reference signs) are used, and when describing elements of the same type separately, identification numbers (or reference signs) of the elements may be used. Also, the number of each element shown in each figure is an example and is not limited to the illustration.

[0018] (Functional overview of the storage system 201 according to the embodiment) FIG. 1 is an explanatory diagram of the functional overview of the storage system 201 according to the embodiment. The storage system 201 has a function of creating a Snapshot, which is a replicated logical volume of a logical volume (hereinafter referred to as "LDEV"). The storage system 201 also has a function of creating a vClone. A vClone is a replicated destination logical volume that replicates the replicated source logical volume created in the same manner as a Snapshot. However, a vClone does not have a pair relationship between the replicated source logical volume and the replicated destination logical volume, and shares metadata management resources between the replicated source logical volume and the replicated destination logical volume.

[0019] In the storage system 201, upon acquisition or Write of a Snapshot, RoW (Redirect-on-Write) is adopted, in which only metadata indicating the storage location of data is updated without copying the data. In RoW, an append area for storing data of an LDEV or a Snapshot, and a meta information area for storing meta information of the data appended to the append area are provided in a physical drive (PDEV 220 described later). The meta information includes a pair management table 321, a PVOL management table 322, a Family meta information management table 323, and an LDEV⇒Family conversion table 324 described later.

[0020] As shown in FIG. 1, the storage system 201 has each state before and after vClone support.

[0021] Before vClone support, the pair relationship between the source logical volume (PVOL), LDEV#A, which is the replication source of the Snapshot using RoW, and the destination logical volume (SVOL), LDEV#B, is maintained in the pair management table 321. When accessing LDEV#B, the meta information of the data to be accessed is identified from the "reference destination meta#" in the pair management table 321. When accessing LDEV#A, the meta information of the data to be accessed is identified from the "reference destination meta#" in the PVOL management table 322.

[0022] On the other hand, after vClone support, there are two states: before vClone (with pair relationship) and after vClone (without pair relationship), and the two states can transition to each other. In the case of before vClone (with pair relationship), the relationship between the source and destination LDEVs is maintained. On the other hand, in the case of after vClone (without pair relationship), splitting and restoring are possible between any LDEVs.

[0023] There are two methods for creating a vClone. That is, the first one is "Method 1: Converting an existing Snapshot with a pair relationship into a vClone", and the second one is "Method 2: Creating a vClone with an LDEV in the SMPL state (without a destination logical volume in a pair relationship) as the destination".

[0024] After vClone support, the Family meta information management table 323 and the LDEV ⇒ Family conversion table 324 are added. The data reference destination of the LDEV is managed in units of "Family". "Family" is a group of LDEVs that had a pair relationship between PVOL and SVOL before vClone, and after vClone, it is the Parent and vClone that had a pair relationship between PVOL and SVOL before vClone. The Parent is the PVOL that had a pair relationship between PVOL and SVOL with the corresponding vClone as the SVOL before vClone.

[0025] The LDEV⇒Family conversion table 324 manages the Family# of the Family to which the LDEV belongs and the in-Family ID indicating the data reference destination of the corresponding LDEV. The Family meta-information management table 323 manages the meta-information of the reference destination for each in-Family ID. The Family meta-information management table 323 and the LDEV⇒Family conversion table 324 are generated based on the information stored in the pair management table 321 and the PVOL management table 322.

[0026] Before vClone after vClone support, when accessing LDEV#A and #B, the in-Family ID is obtained from the LDEV⇒Family conversion table 324. Then, based on the obtained in-Family ID, the meta-information management table 323 of the Family is referred to identify the meta-information of the data to be accessed. Before vClone, the reference destination meta# of the pair management table 321 and the PVOL management table 322 is invalidated. However, since the pair relationship #AA between PVOL and SVOL in the pair management table 321 is maintained, it has the same function as the Snapshot before vClone support.

[0027] After vClone after vClone support, the access method to LDEV#A and #B is the same as before vClone. On the other hand, LDEV#A becomes "Parent" and LDEV#B becomes "vClone", and the pair relationship #AA between PVOL and SVOL in the pair management table 321 is invalidated. Therefore, management operations can be performed even for Snapshots with non-consecutive generations, such as LDEV#X3 and LDEV#X1 which are the replicas of the replication destination LDEV#X2 from the replication source LDEV#X1, and LDEV#Y1 and #Y2 which are two replication destinations from the replication source LDEV#Y.

[0028] (Configuration of the computer system 100 according to the embodiment) FIG. 2 is a configuration diagram of a computer system 100 according to an embodiment. The computer system 100 includes a storage system 201, a server system 202, and a management system 203. The storage system 201 and the server system 202 are connected via an FC (Fiber Channel) network 204. The storage system 201 and the management system 203 are connected via an IP (Internet Protocol) network 205. Note that the FC network 204 and the IP network 205 may be the same communication network.

[0029] The storage system 201 includes a plurality of storage controllers 210 and a plurality of PDEV220. The PDEV220 is connected to the storage controller 210.

[0030] The storage controller 210 has one or more processors 211, one or more memories 212, a P-I / F 213, an S-I / F 214, and an M-I / F 215.

[0031] The processor 211 may include a hardware circuit. In this embodiment, the processor 211 performs control related to Snapshot creation, restoration, vClone support processing, vClone creation processing, and input / output screens D1a, D1b, D1c (FIGS. 15A and 15B) described later.

[0032] The memory 212 is an example of a storage unit. The memory 212 stores programs executed by the processor 211, data used by the processor 211, and the like. The processor 211 executes programs stored in the memory 212. Note that in this embodiment, for example, the memory is duplicated by a combination of the memory 212 and the processor 211.

[0033] The P-I / F 213, the S-I / F 214, and the M-I / F 215 are examples of interface units.

[0034] P-I / F213 is a communication interface device that mediates data exchange between PDEV220 and storage controller 210. A plurality of PDEV220 are connected to P-I / F213.

[0035] S-I / F214 is a communication interface device that mediates data exchange between server system 202 and storage controller 210. Server system 202 is connected to S-I / F214 via FC network 204.

[0036] M-I / F215 is a communication interface device that mediates data exchange between management system 203 and storage controller 210. Management system 203 is connected to M-I / F215 via IP network 205.

[0037] Server system 202 is configured to include one or more host devices (upper devices). Server system 202 transmits an I / O request (write request, read request, or access request) specifying an I / O destination to storage controller 210. The I / O destination is, for example, a logical volume number such as a LUN (Logical Unit Number), a logical address such as an LBA (Logical Block Address), etc.

[0038] Management system 203 is configured to include one or more management devices. Management system 203 manages storage system 201.

[0039] (Configuration of Memory 212 of Storage System 201 According to Embodiment) FIG. 3 is a configuration diagram of the memory 212 of the storage system 201 according to the embodiment. The memory 212 includes memory areas such as a local memory 301, a cache memory 302, and a shared memory 303. At least one of these memory areas may be an independent memory. The local memory 301 is used by a processor 211 belonging to the same set as the memory 212 including this local memory 301.

[0040] Stored in the local memory 301 are a Family management program 311 and a pair management program 312 as programs related to this embodiment. Also stored in the local memory 301 are a volume creation program, a Snapshot creation program, a read program, a front-end write program, a back-end write program, a restore program, and the like. These programs are provided for each of the plurality of storage controllers 210 and cooperate with each other to perform target processing. The Family management program 311 and the pair management program 312 will be described later.

[0041] The cache memory 302 temporarily stores a data set that is written to or read from the PDEV 220.

[0042] The shared memory 303 is used by both the processor 211 belonging to the same set as the memory 212 including this shared memory 303 and the processor 211 belonging to a different set. Stored in the shared memory 303 are a pair management table 321, a PVOL management table 322, a Family meta-information management table 323, and an LDEV⇒Family conversion table 324. These tables will be described later with reference to the figures. Also stored in the shared memory 303 are a volume management table, a directory area management table, a mapping area management table, a directory area allocation table, a mapping area allocation table, and a Snapshot generation management table, and the like.

[0043] (Configuration of the pair management table 321 according to the embodiment) FIG. 4 is a configuration diagram of the pair management table 321 according to the embodiment. In the pair management table 321, for each pair of the PVOL which is the source LDEV for replication and the SVOL which is the destination LDEV for replication, the specific information of the meta information of the reference destination (reference destination meta #) and are managed. The pair management table 321 is an example of pair management information. The reference destination meta # managed by the pair management table 321 is an example of the first reference destination meta information.

[0044] (Configuration of the PVOL management table 322 according to the embodiment) FIG. 5 is a configuration diagram of the PVOL management table 322 according to the embodiment. In the PVOL management table 322, the specific information of the meta information of the reference destination (reference destination information, etc.) of the PVOL which is the source LDEV for replication and are managed. The PVOL management table 322 is an example of source management information. The reference destination meta # managed by the PVOL management table 322 is an example of the second reference destination meta information.

[0045] (Configuration of the Family meta information management table 323) FIG. 6 is a configuration diagram of the Family meta information management table 323 according to the embodiment. In the Family meta information management table 323, for each Family #, the Family internal ID that identifies the LDEV of the Family and the reference destination information of the meta information of the reference destination of the LDEV of the corresponding Family internal ID are managed. The Family meta information management table 323 is an example of meta information management information. The Family # is an example of family identification information. The Family internal ID is the identification information within the family.

[0046] (Configuration of the LDEV ⇒ Family conversion table 324 according to the embodiment) FIG. 7 is a configuration diagram of the LDEV ⇒ Family conversion table 324 according to the embodiment. In the LDEV ⇒ Family conversion table 324, for each LDEV, the Family # and the Family internal ID of the Family to which it belongs are managed. The LDEV ⇒ Family conversion table 324 is an example of conversion information.

[0047] (vClone Support Before SS ⇒ vClone Support After SS Conversion Process According to the Embodiment) FIG. 8 is a sequence diagram showing the vClone support before SS ⇒ vClone support after SS conversion process according to the embodiment. FIG. 9 is a flowchart showing the vClone support before SS ⇒ vClone support after SS conversion process according to the embodiment. The vClone support before SS ⇒ vClone support after SS conversion process is a process of converting the state from the SS (Snapshot) before vClone support shown in FIG. 1 to the SS after vClone support. The same step numbers in FIGS. 8 and 9 represent the same process.

[0048] First, referring to FIG. 8. In step S11, the management system 203 receives a conversion operation from the SS before support to the SS after support specified by the user via a terminal (not shown) and outputs it to the Family management program 311.

[0049] Next, the Family management program 311 executes the processes in steps S12 to S19 in response to the input of the conversion operation from the SS before support to the SS after support from the management system 203. Next, the Pair management program 312 executes the processes in steps S20 to S21 upon receiving the end of the process in step S19. Next, in step S22, the Pair management program 312 notifies the Family management program 311 of the completion of the process. Next, in step S23, the Family management program 311 notifies the management system 203 of the completion of the process.

[0050] Next, referring to FIG. 9. In step S12, the Family management program 311 updates the Family meta information management table 323 by associating the in-Family ID of the PVOL with the reference destination meta #. Next, in step S13, the Family management program 311 updates the Family meta information management table 323 by associating the in-Family ID of the SVOL with the reference destination meta #.

[0051] Next, in step S14, the Family management program 311 sets the Family # and the ID within the Family of the PVOL and updates the LDEV ⇒ Family conversion table 324. Next, in step S15, the Family management program 311 sets the Family # and the ID within the Family of the SVOL and updates the LDEV ⇒ Family conversion table 324.

[0052] Next, in step S16, the Family management program 311 searches for an available ID within the Family of the PVOL. If an available ID is found, the process proceeds to step S17. If no available ID is found, the flowchart in FIG. 9 ends.

[0053] In step S17, the Family management program 311 moves the reference destination meta # of the SVOL to the PVOL's table and updates the Family meta information management table 323. Next, in step S18, the Family management program 311 sets the Family # and the ID within the Family of the SVOL and updates the LDEV ⇒ Family conversion table 324. Next, in step S19, the Family management program 311 deletes the reference destination meta # from the SVOL's table and updates the Family meta information management table 323.

[0054] Next, in step S20, the pair management program 312 invalidates the reference destination meta # and updates the PVOL management table 322. Next, in step S21, the pair management program 312 invalidates the reference destination meta # and updates the pair management table 321. When step S21 ends, the flowchart in FIG. 9 ends.

[0055] (Overview of the pre-vClone support SS ⇒ post-vClone support SS conversion process according to the embodiment) With reference to FIGS. 10A to 10D, the overview of the pre-vClone support SS ⇒ post-vClone support SS conversion process described in FIGS. 8 to 9 will be described. FIGS. 10A to 10D are overview diagrams of the pre-vClone support SS ⇒ post-vClone support SS conversion process according to the embodiment.

[0056] First, refer to FIG. 10A. State 1001 in FIG. 10A shows the state before the execution of step S11 in FIG. 8. In state 1001, LDEV#A of PVOL and LDEV#B of SVOL are in a paired relationship. LDEV#A of PVOL refers to the destination meta#α of PDEV220 based on the PVOL management table 322. LDEV#B of SVOL refers to the destination meta#β of PDEV220 based on the pair management table 321.

[0057] State 1002 in FIG. 10A shows the state during the execution of steps S12 and S13 in FIG. 8. In state 1002, the paired relationship between LDEV#A of PVOL and LDEV#B of SVOL is still maintained. Operation 323a corresponds to step S12 in FIG. 8, and in the Family meta information management table 323, the destination meta#α is associated with the in-Family ID "X" of Family#1. Operation 323b corresponds to step S13 in FIG. 8, and in the Family meta information management table 323, the destination meta#β is associated with the in-Family ID "K" of Family#2.

[0058] Next, refer to FIG. 10B. State 1003 in FIG. 10B shows the state during the execution of steps S14 and S15 in FIG. 8. In state 1003, the paired relationship between LDEV#A of PVOL and LDEV#B of SVOL is still maintained. Operation 324a corresponds to step S14 in FIG. 8, and in the LDEV⇒Family conversion table 324, Family# "1" and the in-Family ID "X" are associated with LDEV#A. Operation 324b corresponds to step S14 in FIG. 8, and in the LDEV⇒Family conversion table 324, Family# "2" and the in-Family ID "K" are associated with LDEV#B.

[0059] The state 1004 in FIG. 10C shows the states during the execution of steps S17, S18, and S19 when there is an empty space in the Family internal ID of PVOL in step S16 of FIG. 8. In state 1004, the paired relationship between LDEV#A of PVOL and LDEV#B of SVOL is still maintained. Operation 323c corresponds to step S17 of FIG. 8. Operation 323c moves in the Family meta information management table 323 to associate the reference destination meta# "β" of the Family internal ID "K" of Family#2 with the reference destination meta# of the Family internal ID "Y" of Family#1. Operation 324c corresponds to step S18 of FIG. 8 and updates the LDEV⇒Family conversion table 324 to associate LDEV#B with Family# "1" and the Family internal ID "Y". Operation 323d corresponds to step S19 of FIG. 8 and deletes the reference destination meta# associated with the Family internal ID "K" of Family#2 in the Family meta information management table 323 to make it "empty".

[0060] Next, refer to FIG. 10D. The state 1005 in FIG. 10D shows the states during the execution of steps S20 and S21 of FIG. 8. In state 1005, the paired relationship between LDEV#A of PVOL and LDEV#B of SVOL is still maintained. Operation 321a corresponds to step S20 of FIG. 8 and invalidates the reference destination meta# corresponding to pair#AA in the pair management table 321. Operation 321b corresponds to step S21 of FIG. 8 and invalidates the reference destination meta# corresponding to PVOL#A in the PVOL management table 322. State 1005 indicates that LDEV#A and LDEV#B represent a Snapshot with vClone supported, and it is possible to transition to vClone at any time.

[0061] (SS⇒vClone conversion process after vClone support according to the embodiment) FIG. 11 is a sequence diagram showing the SS⇒vClone conversion process after vClone support according to the embodiment. The SS⇒vClone conversion process after vClone support is a process of converting the state from the SS before vClone to vClone after vClone support shown in FIG. 1.

[0062] First, in step S31, the management system 203 receives a conversion operation from SS⇒vClone after vClone support specified by the user via a terminal (not shown) and outputs it to the Family management program 311.

[0063] Next, in step S32, the Family management program 311 outputs the SS⇒vClone conversion operation received from the management system 203 to the Pair management program 312. In step S33, the Pair management program 312 invalidates the PVOL and SVOL in the Pair management table 321 according to the SS⇒vClone conversion operation. Next, in step S34, the Pair management program 312 notifies the Family management program 311 of the completion of the process. Next, in step S35, the Family management program 311 notifies the management system 203 of the completion of the process.

[0064] (Overview of the SS⇒vClone conversion process after vClone support according to the embodiment) Referring to FIG. 12, the overview of the SS⇒vClone conversion process described in FIG. 11 will be described. FIG. 12 is an overview diagram of the SS⇒vClone conversion process after vClone support according to the embodiment.

[0065] The state immediately before state 1201 in FIG. 12 is the state before the execution of step S31 in FIG. 11, which is state 1005 in FIG. 10D.

[0066] State 1201 in FIG. 12 shows the state at the time of execution of step S33 in FIG. 11. Operation 321c corresponds to step S33 in FIG. 11, and the PVOL and SVOL in the pair management table 321 are set to invalid values. Therefore, in state 1201, the pair relationship between LDEV#A of PVOL and LDEV#B of SVOL is dissolved.

[0067] The vClone conversion method shown in FIG. 12 via FIGS. 10A to 10D corresponds to the above-mentioned “(Method 1) Method of converting a Snapshot having an existing pair relationship into a vClone”. Also, setting the respective set values in the pair management table 321, PVOL management table 322, Family meta information management table 323, and LDEV⇒Family conversion table 324 from the beginning as shown in FIG. 12 corresponds to the above-mentioned (Method 2).

[0068] (vClone⇒vClone Support Post-SS Conversion Process According to the Embodiment) FIG. 13 is a sequence diagram showing the vClone⇒vClone support post-SS conversion process according to the embodiment. The vClone⇒vClone support post-SS conversion process is a process of converting the state from vClone to the SS before vCloneization after vClone support shown in FIG. 1.

[0069] First, in step S41, the management system 203 receives a conversion operation from vClone to SS after vClone support specified by the user via a terminal (not shown) and outputs it to the Family management program 311.

[0070] Next, in step S42, the Family management program 311 outputs the vClone⇒vClone support after SS conversion operation received from the management system 203 to the pair management program 312. In step S43, the pair management program 312 sets the PVOL and SVOL of the pair management table 321 according to the vClone⇒vClone support after SS conversion operation. Next, in step S44, the pair management program 312 notifies the Family management program 311 of the completion of the process. Next, in step S45, the Family management program 311 notifies the management system 203 of the completion of the process.

[0071] (Overview of vClone⇒vClone support after SS conversion process according to the embodiment) Referring to FIG. 14, the overview of the vClone⇒vClone support after SS conversion process described in FIG. 13 will be described. FIG. 14 is an overview diagram of the vClone⇒vClone support after SS conversion process according to the embodiment.

[0072] The state immediately before the state 1401 in FIG. 14 is the state before the execution of step S41 in FIG. 13, which is the state 1201 in FIG. 12.

[0073] The state 1401 in FIG. 14 shows the state at the time of execution of step S43 in FIG. 13. The operation 321d corresponds to step S43 in FIG. 13, and values are set in the PVOL and SVOL of the pair management table 321 respectively. The values to be set are at the discretion of the user. Note that the values to be set are not limited to the discretion of the user, and the LDEV# "A" set in the PVOL of the pair management table 321 may be obtained from the PVOL management table 322. Similarly, the LDEV# "B" set in the SVOL of the pair management table 321 may be obtained from the LDEV#B that has the same Family# as LDEV#A by referring to the LDEV⇒Family conversion table 324. As a result, in the state 1401, the pair relationship between the LDEV#A of the PVOL and the LDEV#B of the SVOL is restored.

[0074] (Input / output screens D1a, D1b, D1c according to the embodiment) Referring to FIGS. 15A and 15B, input / output screens D1a, D1b, and D1c according to an embodiment displayed on a display device (not shown) of the management system 203 and the like will be described. The input / output screens D1a, D1b, and D1c are based on the premise that the vClone support before SS ⇒ vClone support after SS conversion process (FIGS. 8 to 9) has been executed and the Family management of LDEV has been introduced.

[0075] The user can input an execution instruction for the vClone support after SS ⇒ vClone conversion process and the vClone ⇒ vClone support after SS conversion process to the storage system 201 by operating the input / output screens D1a to D1c with an input device such as a keyboard or a mouse.

[0076] FIG. 15A is a diagram showing the input / output screens D1a and D1b of the vClone support after SS ⇒ vClone conversion according to the embodiment. FIG. 15B is a diagram showing the input / output screens D1b and D1c of the vClone ⇒ vClone support after SS conversion according to the embodiment. The input / output screen D1b in FIGS. 15A and 15B is the same.

[0077] First, referring to FIG. 15A. As shown in the input / output screen D1a, in Family #1, there is a pair of Snapshots of LDEV #1P-1 and LDEV #1S-1 displayed in the Snapshot area D11. Also, in Family #2, there is a pair of Snapshots of LDEV #2P-1 and LDEV #2S-1 displayed in the Snapshot area D12. Similarly, in Family #2, there are a pair of Snapshots of LDEV #2S-1 and LDEV #2S-2, and a pair of Snapshots of LDEV #2S-1 and LDEV #2S-3 displayed in the Snapshot area D12. The Snapshot area D11 is an example of the first area.

[0078] For example, consider the case of vCloning LDEV#1S-1 of Family#1. Drag LDEV#1S-1 to the vClone area D13 on the input / output screen D1a. Then, in the storage system 201, the SS⇒vClone conversion process (Figure 11) is executed after vClone support. And as shown on the input / output screen D1b, the Snapshot pair of LDEV#1P-1 and LDEV#1S-1 of Family#1 is resolved. And it becomes a combination of Parent-vClone of LDEV#1V-1 and LDEV#1V-2 displayed in the vClone area D13. The vClone area D13 is an example of the second area.

[0079] Also, for example, consider the case of vCloning LDEV#2S-3 of Family#2. Drag LDEV#2S-3 to the vClone area D14 on the input / output screen D1a. Then, in the storage system 201, the SS⇒vClone conversion process (Figure 11) is executed after vClone support. And as shown on the input / output screen D1b, the Snapshot pair of LDEV#2S-1 and LDEV#2S-3 of Family#2 is resolved, and it becomes the vClone of LDEV#2V-1 displayed in the vClone area D14.

[0080] However, although LDEV#2S-1, which was in a Snapshot pair relationship with LDEV#2S-3, has its Snapshot relationship with LDEV#2S-3 resolved, it still has a Snapshot relationship with LDEV#2P-1 and LDEV#2S-2. Therefore, it remains in the Snapshot area D12. The Snapshot area D12 is an example of the first area. The vClone area D14 is an example of the second area.

[0081] Next, refer to FIG. 15B. For example, consider the case of snapshotting LDEV#1V-1 and LDEV#1V-2 of Family#1. On the input / output screen D1b, connect LDEV#1V-1 and LDEV#1V-2 with an arrow line pointing from LDEV#1V-1 to LDEV#1V-2. Then, in the storage system 201, the vClone⇒SS conversion process after vClone support (FIG. 13) is executed. And, as displayed on the input / output screen D1c, a snapshot pair is configured with LDEV#1V-1 of Family#1 as PVOL and LDEV#1V-2 as SVOL. And it becomes a snapshot pair of LDEV#1P-1 and LDEV#1S-2 displayed in the snapshot area D11. When a snapshot pair of LDEV#1P-1 and LDEV#1S-2 is configured and the restore button (not shown) on the input / output screen D1c is pressed in the state where this pair is selected, LDEV#1P-1 is restored from LDEV#1S-2.

[0082] Also, for example, consider the case of snapshotting LDEV#2V-1 of Family#2 so that it forms a pair with LDEV#2P-1. On the input / output screen D1b, connect LDEV#2P-1 and LDEV#2V-1 with an arrow line pointing from LDEV#2P-1 to LDEV#2V-1. Then, in the storage system 201, the vClone⇒SS conversion process after vClone support (FIG. 13) is executed. And, as displayed on the input / output screen D1c, a snapshot pair is configured with LDEV#2P-1 of Family#2 as PVOL and LDEV#2V-1 as SVOL. And it becomes a snapshot pair of LDEV#2P-1 and LDEV#2S-3 displayed in the snapshot area D12. When a snapshot pair of LDEV#2P-1 and LDEV#2S-3 is configured and the restore button (not shown) on the input / output screen D1c is pressed in the state where this pair is selected, LDEV#2P-1 is restored from LDEV#2S-3.

[0083] When taking a snapshot of the LDEV of vClone, there is a restriction that there is only one PVOL for the SVOL. Therefore, in the example of the input / output screen D1b, when taking a snapshot of LDEV#2V-1, in addition to using LDEV#2P-1 as the PVOL and LDEV#2V-1 as the SVOL, there are cases where LDEV#2S-1 is used as the PVOL and LDEV#2V-1 as the SVOL, and cases where LDEV#2S-2 is used as the PVOL and LDEV#2V-1 as the SVOL. However, other cases do not meet the above-mentioned restrictions and cannot be snapshotted.

[0084] (Effect of the Embodiment) In the above-described embodiment, a conversion process from before vClone support to after vClone support is performed, and data access that does not depend on the pair management table 321 and the PVOL management table 322 is realized while maintaining the pair relationship between the source LDEV and the destination LDEV. Therefore, the pair relationship can be resolved by a simple process as needed, and the destination LDEV can be vCloned.

[0085] Also, in the above-described embodiment, after vClone support, it is possible to restore from the destination LDEV to the source LDEV in the same manner as before vClone support.

[0086] Also, in the above-described embodiment, a conversion process from before vClone (with pair relationship) to after vClone (without pair relationship) after vClone support is performed. By this vClone, it becomes possible to establish a cooperation with other remote copies or local copies that were impossible as the SVOL. Also, since vClone shares resources with the source LDEV, high-speed pair splitting and restore operations by metadata copying are possible between LDEVs that share the same source resources.

[0087] Also, in the above-described embodiment, a conversion process from after vClone (without pair relationship) to before vClone (with pair relationship) is performed. By this snapshotting, the snapshot configuration of the source LDEV and the destination LDEV can be constructed with a high degree of freedom.

[0088] Also, in the above-described embodiment, by using the GUI (input / output screens D1a, D1b, D1c) shown in FIGS. 15A and 15B, it is possible to receive an execution instruction for processing by an intuitive operation of the user. The processing here is the conversion processing from before vClone (with pair relationship) to after vClone (without pair relationship) after vClone support, and the conversion processing from after vClone (without pair relationship) to before vClone (with pair relationship) after vClone support.

[0089] Also, in the above-described embodiment, when generating the Family meta-information management table 323 and the LDEV ⇒ Family conversion table 324, different Family#s are once assigned to two LEDVs and then the same Family# is re-assigned. For example, by reserving the once-assigned Family#, the reserved Family# can be reused during the subsequent reconfiguration of the Family, so the degree of freedom in reconfiguring the family after vClone is improved.

[0090] Note that the present invention is not limited to the above-described embodiment, and various modification examples are included. Also, the above-described embodiment has been described in detail for easy understanding of the present invention, and is not necessarily limited to having all the configurations described. In addition, not only deletion of such a configuration is possible, but also replacement and addition of the configuration are possible. Also, forms in which some or all of the above-described embodiments are appropriately combined in a consistent manner are also included in the embodiments of the present invention.

[0091] Also, each of the above configurations, functions, processing units, processing means, etc. may be realized in hardware by designing some or all of them, for example, by using an integrated circuit. Also, the present invention can also be realized by a program code of software that realizes the functions of the embodiment. In this case, a recording medium storing the program code is provided to a computer, and a processor included in the computer reads out the program code stored in the recording medium.

[0092] In this case, the program code itself read from the recording medium realizes the functions of the above-described embodiments, and the program code itself and the recording medium storing the same constitute the present invention. As a recording medium for supplying such a program code, for example, a flexible disk, CD-ROM, DVD-ROM, hard disk, SSD (Solid State Drive), optical disk, magneto-optical disk, CD-R, magnetic tape, non-volatile memory card, ROM, etc. are used.

[0093] Also, the program code for realizing the functions described in this embodiment can be implemented in a wide range of programs or script languages such as assembler, C / C++, perl, Shell, PHP, Java (registered trademark), etc.

[0094] In the above-described embodiments, the control lines and information lines show those considered necessary for explanation, and not necessarily all the control lines and information lines are shown on the product. All the components may be interconnected.

Explanation of Signs

[0095] 100: Computer system, 201: Storage system, 202: Server system, 203: Management system, 210: Storage controller, 321: Pair management table, 322: PVOL management table, 323: Meta information management table, 324: LDEV⇒Family conversion table, D11, D12, D13, D14: Areas.

Claims

1. A storage system having a storage controller that provides a plurality of logical volumes to an upper device and can create a snapshot as a replicated destination logical volume that is a replication of a replicated source logical volume, wherein the storage controller, manages a correspondence between a pair of identification information of the replicated source logical volume and the replicated destination logical volume indicating a pair relationship of the snapshot of the replicated source logical volume and the replicated destination logical volume, and first reference destination meta information indicating a reference destination of data stored in the replicated destination logical volume, as pair management information, manages a correspondence between the identification information of the replicated source logical volume and second reference destination meta information indicating a reference destination of data stored in the replicated source logical volume, as replicated source management information, manages each of the information, assigns the same family identification information that uniquely identifies the family to the replicated source logical volume and the replicated destination logical volume so that the replicated source logical volume and the replicated destination logical volume belong to the same family within a family indicating a group of the logical volumes, assigns in-family identification information that uniquely identifies the logical volume within the same family to the first reference destination meta information and the second reference destination meta information, generates meta information management information that manages a correspondence between the family identification information, the in-family identification information, the first reference destination meta information, and the second reference destination meta information, generates conversion information that manages a correspondence between each of the identification information of the replicated source logical volume and the replicated destination logical volume, the family identification information to which the replicated source logical volume and the replicated destination logical volume belong, and the in-family identification information of the replicated source logical volume and the replicated destination logical volume, in response to an access request from the upper device to each of the data stored in the replicated source logical volume and the replicated destination logical volume, refers to the conversion information, and acquires the corresponding family identification information and in-family identification information from the identification information of the replicated source logical volume and the replicated destination logical volume, respectively, Based on the obtained family identification information and the in-family identification information, refer to the meta information management information to obtain the first reference destination meta information and the second reference destination meta information corresponding to each of the source logical volume and the destination logical volume, Based on the obtained first reference destination meta information and the second reference destination meta information, access each of the data stored in the source logical volume and the destination logical volume A storage system characterized by the above.

2. The storage system according to claim 1, wherein the storage controller, when receiving an instruction to restore the source logical volume, restores the source logical volume from the destination logical volume A storage system characterized by the above.

3. The storage system according to claim 1, wherein the storage controller, in the pair management information, invalidates the identification information of the source logical volume and the identification information of the destination logical volume, and invalidates the pair relationship between the source logical volume and the destination logical volume A storage system characterized by the above.

4. The storage system according to claim 3, wherein the storage controller, in the pair management information, sets the identification information of any logical volume for the identification information of the source logical volume and the identification information of the destination logical volume to activate the pair relationship between the any logical volumes A storage system characterized by the above.

5. The storage system according to claim 4, wherein the storage controller, displays, for each group, the pair of the source logical volume and the destination logical volume for which the pair relationship is activated in the first area of the input / output screen, receives a selection of the destination logical volume among the source logical volume and the destination logical volume on the input / output screen, in the pair management information, sets invalid values for the identification information of the selected destination logical volume and the identification information of the source logical volume for which the pair relationship is activated with the destination logical volume to invalidate the pair relationship, moves and displays the pair of the source logical volume and the destination logical volume for which the pair relationship is invalidated in the second area of the input / output screen A storage system characterized by the above.

6. The storage system according to claim 5, wherein the storage controller, on the input / output screen, accepts selection of any two of the logical volumes, in the pair management information, sets the identification information of the any two logical volumes in the identification information of the source logical volume for replication and the identification information of the destination logical volume for replication, activates the pair relationship between the any two logical volumes, moves and displays the logical volumes with the activated pair relationship in the first area A storage system characterized by the above.

7. The storage system according to claim 1, wherein the storage controller, assigns different family identification information to the source logical volume for replication and the destination logical volume for replication, allocates the different family identification information to the first reference destination meta information and the second reference destination meta information respectively to generate the meta information management information and the conversion information, re - allocates any one of the same family identification information among the different family identification information to the first reference destination meta information and the second reference destination meta information in the same way, in response to the re - allocation of the same family identification information, in the meta information management information, manages the correspondence between the same family identification information, the in - family identification information that uniquely identifies the source logical volume for replication and the destination logical volume for replication within the family corresponding to the same family identification information, the first reference destination meta information, and the second reference destination meta information, and updates the meta information management information accordingly A storage system characterized by the above.

8. A data replication method in a storage system executed by a storage system having a storage controller that provides a plurality of logical volumes to a host device and can create a snapshot as a destination logical volume for replication of a source logical volume for replication. wherein the storage controller, pair management information that manages the correspondence between a set of the identification information of the source logical volume for replication and the identification information of the destination logical volume for replication indicating the pair relationship of the snapshots of the source logical volume for replication and the destination logical volume for replication, and the first reference destination meta information indicating the reference destination of the data stored in the destination logical volume for replication Replication source management information that manages the correspondence between the identification information of the replication source logical volume and second reference destination meta-information indicating the reference destination of the data stored in the replication source logical volume Manage each piece of information Assign the same family identification information that uniquely identifies the family to the replication source logical volume and the replication destination logical volume so that the replication source logical volume and the replication destination logical volume belong to the same family within the family indicating the group of logical volumes Assign in-family identification information that uniquely identifies the logical volume within the same family to the first reference destination meta-information and the second reference destination meta-information Generate meta-information management information that manages the correspondence between the family identification information, the in-family identification information, the first reference destination meta-information, and the second reference destination meta-information Generate conversion information that manages the correspondence between each of the identification information of the replication source logical volume and the identification information of the replication destination logical volume, the family identification information to which the replication source logical volume and the replication destination logical volume belong, and the in-family identification information of the replication source logical volume and the replication destination logical volume In response to an access request to each of the data stored in the replication source logical volume and the replication destination logical volume from the upper device, refer to the conversion information and obtain the corresponding family identification information and in-family identification information from the identification information of the replication source logical volume and the identification information of the replication destination logical volume respectively With reference to the meta-information management information based on the obtained family identification information and in-family identification information, obtain the first reference destination meta-information and the second reference destination meta-information corresponding to each of the replication source logical volume and the replication destination logical volume Access each of the data stored in the replication source logical volume and the replication destination logical volume based on the obtained first reference destination meta-information and second reference destination meta-information A data replication method in a storage system, characterized by having each of the above processes

Images