Data replication system and data replication method

Abstract

To recover backup data after performing data verification, even when the capacity of a volume is expanded at some point in a backup cycle.SOLUTION: A controller extracts summary information related to an outline of a predetermined volume from volume mapping information related to the configuration of the predetermined volume at the time point when backup images of multiple generations are created respectively. The controller verifies whether or not a volume configuration based on the backup image of a specific generation corresponding to specific volume mapping information of the predetermined volume corresponding to a specific backup generation selected on the basis of the summary information from among the backup images of the multiple generations, and the volume configuration based on the backup image at a present time point of the predetermined volume match. When both volume configurations match, as the result of the verification, the controller verifies the backup data on the basis of the backup image of the specific generation and performs recovery.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a data replication system and a data replication method, and is suitable for application to a data replication system relating to a technique for restoring backup data after performing data verification, for example. [Background technology]

[0002] For example, Patent Document 1 discloses a technology for recovering a volume to its state before a cyber-attack. Patent Document 1 discloses a technology in which, in a storage device, multiple generations of a volume are stored as backup images in a data protection area that is not accessible from the outside, and a copy of one generation selected from the multiple generations is stored in an access volume that is accessible from the outside, thereby restoring the backup data of the selected one generation. The technology described in Patent Document 1 is based on the premise that the volume capacity will not be expanded during system operation, especially during a backup cycle. [Prior art documents] [Patent documents]

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

[0004] In the technology described in Patent Document 1, if the volume capacity is expanded during a backup cycle, it is not possible to guarantee consistency between the volume configuration of the mainframe (hereinafter referred to as "MF") at the time of backup and the volume configuration of the MF at the time of data verification, and even if data verification is performed to determine whether the two volume configurations match, the two volume configurations may not match, making it impossible to recover the backup data.

[0005] The present invention has been made in consideration of the above points, and aims to propose a data replication system and a data replication method that can recover backup data after verifying the data, even if the volume capacity is expanded during the backup cycle. [Means for solving the problem]

[0006] In order to solve this problem, the present invention comprises a first storage device that creates a backup image of a specified volume from which data is read and written by an external device; a second storage device that accumulates multiple generations of backup images of the specified volume that were created at different times in a data protection area that is inaccessible to the external device; and a control device that extracts summary information regarding an overview of the specified volume from volume mapping information regarding the configuration of the specified volume at the time each of the multiple generations of backup images was created, and obtains specific volume mapping information of the specified volume that corresponds to a specific backup generation selected from the multiple generations of backup images based on the summary information.The control device verifies whether the volume configuration based on the backup image of the specific generation that corresponds to the specific volume mapping information matches the volume configuration based on the backup image of the specified volume at the current time, and if the verification shows that the two volume configurations match, it verifies and recovers backup data based on the backup image of the specific generation.

[0007] Furthermore, the present invention includes a storing step in which a first storage device creates a backup image of a predetermined volume from which data is read and written by an external device; a storing step in which a second storage device stores multiple generations of backup images of the predetermined volume, created at different times, in a data protection area that is inaccessible to the external device; a summary information extracting step in which a control device extracts summary information regarding an overview of the predetermined volume from volume mapping information regarding the configuration of the predetermined volume at the time when each of the multiple generations of backup images was created; and an acquiring step in which the control device acquires specific volume mapping information of the predetermined volume corresponding to a specific backup generation selected from the multiple generations of backup images based on the summary information, wherein the control device verifies whether the volume configuration based on the backup image of the specific generation corresponding to the specific volume mapping information matches with the volume configuration based on the backup image of the predetermined volume at the current time, and if the verification shows that both volume configurations match, the backup data is verified and recovered based on the backup image of the specific generation. [Effects of the Invention]

[0008] According to the present invention, even if the capacity of a volume is expanded during a backup cycle, the backup data can be recovered after verifying the data. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a block diagram showing an example of an overall configuration example of a data replication system according to a first embodiment. [Figure 2] FIG. 2 is a block diagram showing an example of a hardware block configuration of a storage device or the like. [Figure 3] FIG. 10 is a diagram showing an example of volume mapping information corresponding to a volume configuration. [Figure 4]FIG. 10 is a diagram illustrating an example of a management table of a management table volume. [Figure 5] FIG. 10 is a diagram illustrating an example of data verification when the capacity of a volume is expanded. [Figure 6] 10 is a flowchart illustrating an example of a procedure for a capacity expansion process. [Figure 7] 10 is a flowchart illustrating an example of a procedure for volume mapping information saving processing. [Figure 8] 10 is a flowchart illustrating an example of a procedure for data verification and recovery processing on the open side. [Figure 9] 10 is a flowchart illustrating an example of a procedure for data verification and recovery processing on the mainframe side. [Figure 10] FIG. 10 is a diagram showing an example of a selection screen including summary information. [Figure 11] FIG. 10 is a diagram illustrating an example of a volume configuration in a data replication system according to a second embodiment. [Figure 12] 12 is a diagram showing an example of information used in the volume configuration shown in FIG. 11. FIG. [Figure 13] FIG. 13 is a diagram illustrating an example of group mapping information illustrated in FIG. [Figure 14] FIG. 13 is a diagram showing an example of the combined mapping information shown in FIG. [Figure 15] 10 is a flowchart illustrating an example of a procedure for volume mapping information storage processing according to the second embodiment. [Figure 16] 10 is a flowchart illustrating an example of a procedure for data verification and recovery processing on the open side. [Figure 17] FIG. 10 is a diagram illustrating an example of a group selection screen. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings. The examples are illustrative of the present invention, and some omissions and simplifications have been made as appropriate for clarity of explanation. The present invention can be implemented in various other forms. Unless otherwise specified, each component may be singular or plural.

[0011] In order to facilitate understanding of the invention, the position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. Therefore, the present invention is not necessarily limited to the position, size, shape, range, etc. disclosed in the drawings.

[0012] Examples of various types of information may be described using expressions such as "table," "list," and "queue," but the various types of information may also be expressed using data structures other than these. For example, various types of information such as "XX table," "XX list," and "XX queue" may also be expressed as "XX information." When describing identification information, expressions such as "identification information," "identifier," "name," "ID," and "number" are used, but these are interchangeable.

[0013] When there are multiple components with the same or similar functions, they may be described using the same reference numeral with different subscripts. When there is no need to distinguish between these multiple components, the subscripts may be omitted.

[0014] In the embodiments, processing performed by executing a program may be described. Here, a computer executes the program using a processor (e.g., a CPU or a GPU) and performs processing defined by the program using storage resources (e.g., a memory) and interface devices (e.g., a communication port). Therefore, the entity performing the processing by executing the program may be the processor. Similarly, the entity performing the processing by executing the program may be a controller, device, system, computer, or node having a processor. The entity performing the processing by executing the program may be any computing unit, and may include a dedicated circuit that performs specific processing. Here, the dedicated circuit may be, for example, an FPGA (Field Programmable Gate Array), an ASIC (Application Specific Integrated Circuit), or a CPLD (Complex Programmable Logic Device).

[0015] A program may be installed on a computer from a program source. The program source may be, for example, a program distribution server or a computer-readable storage medium. When the program source is a program distribution server, the program distribution server may include a processor and a storage resource for storing the program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. In addition, in an embodiment, two or more programs may be realized as one program, or one program may be realized as two or more programs.

[0016] In the following description, a "host computer (host)" or "computer system" refers to a system including one or more physical computers. The physical computers may be general-purpose computers or dedicated computers. A physical computer may function as a computer that issues I / O (Input / Output) requests (e.g., called a host computer or server system), or as a computer that performs data I / O in response to I / O requests (e.g., a storage device).

[0017] Furthermore, the computer system may be a distributed system configured with one or more (typically, a plurality of) physical node devices. A physical node device is a physical computer.

[0018] Furthermore, when a physical computer (e.g., a node device) executes predetermined software, SDx (Software Defined anything) may be constructed on the physical computer or a computer system including the physical computer. For example, SDS (Software Defined Storage) or SDDC (Software Defined Data Center) may be adopted as SDx.

[0019] For example, a storage system as an SDS may be constructed by running software having a storage function on a physical general-purpose computer.

[0020] Furthermore, at least one physical computer (e.g., a storage device) may run one or more virtual computers as a server system and a virtual computer as a storage controller of the storage system (typically, a device that inputs and outputs data to and from a PDEV unit in response to an I / O request).

[0021] In other words, such at least one physical computer may have both the functionality as at least part of a server system and the functionality as at least part of a storage system.

[0022] Furthermore, a computer system (typically a storage system) may have a redundant configuration group. The redundant configuration may be a configuration with multiple node devices, such as erasure coding, RAIN (Redundant Array of Independent Nodes), and inter-node mirroring, or may be a configuration with a single computer (for example, a node device), such as one or more RAID (Redundant Array of Independent (or Inexpensive) Disks) groups as at least a part of a PDEV unit.

[0023] Furthermore, in the following description, identification numbers are used as identification information for various objects, but other types of identification information (for example, identifiers including alphabetic characters or symbols) may also be used.

[0024] Hereinafter, the embodiments will be described in detail with reference to the drawings. 1 is a block diagram showing an example of the overall configuration of a data replication system according to the first embodiment. The data replication system includes a primary mainframe 80, a secondary mainframe 90, a production storage device 40, a backup storage device 10, a verification storage device 30, an open server 50, and an open storage device 60. In the following description, the primary mainframe 80, the secondary mainframe 90, the production storage device 40, the backup storage device 10, and the verification storage device 30 are collectively referred to as the "mainframe side," and the open server 50 and the open storage device 60 are collectively referred to as the "open side." The primary mainframe 80, the secondary mainframe 90, and the open server 50 can also be referred to as the first host, the second host, and the third host, respectively.

[0025] The primary mainframe 80 is connected to the production storage device 40 via a network 101, which is, for example, a SAN (Storage Area Network). The secondary mainframe 90, the backup storage device 10, the verification storage device 30, and the open server 50 are connected to one another via a network 102, which is, for example, a SAN (Storage Area Network). The open storage device 60 is connected to the backup storage device 10 and the verification storage device 30, respectively.

[0026] The primary mainframe 80 has control software 81 including an API (Application Programming Interface) for exchanging data with the production storage device 40 via the network 101. The primary mainframe 80 has control software 81 that controls the production storage device 40 when exchanging data with at least one host.

[0027] The secondary mainframe 90 has control software 91 including an API (Application Programming Interface) for exchanging data with the backup storage device 10, the verification storage device 30, and the open server 50 via the network 102, and volume mapping information 92. The volume mapping information 92 will be described later. The secondary mainframe 90 has control software 91 that controls the backup storage device 10 when exchanging data with at least one host.

[0028] The open server 50 is connected to the open storage device 60 via a network 103, which is, for example, a LAN (Local Area Network). The open server 50 has a definition file in which configuration information of volumes such as the export volume 12 is defined.

[0029] The first host is connected to the production storage device 40 and issues I / O requests to the production volume 41 of the production storage device 40 to store and read data in the production volume 41. The production volume 41 stores data exchanged with the host. The production storage device 40 is a storage device installed close to the first host and has the production volume 41.

[0030] The backup storage device 10 is connected to the production storage device 40 and is installed, for example, at a location remote from the production storage device 40. The backup storage device 10 has a volume 13, a data area 14, a relay volume 15, and a virtual volume (not shown). The virtual volume (not shown) is a virtual volume virtually created as a secondary volume of the production volume 41 by SI (Shadow Image).

[0031] The relay volume 15 is a volume for relaying information to be transmitted between the open side and the mainframe side. For example, volume mapping information is written in the relay volume 15. The volume 13 and data area 14 will be described later.

[0032] The backup storage device 10 is an example of a first storage device, and creates a backup image of a production volume 41, which is an example of a predetermined volume from which data is read and written by an external device, and stores the backup image in the data area 14.

[0033] In the backup storage device 10, data of a production volume 41 consisting of unit volumes subdivided into, for example, four is copied to the backup storage device 10. A backup image of the copied data is created in the data area 14 by, for example, SI (Shadow Image). A backup image is created in the data area 14 according to the time when the backup was acquired.

[0034] The data area 14 is configured as a storage area that is not provided with information for access from an external device and can only be recognized by the storage controller of the backup storage device 10. For example, if the data area 14 is configured with multiple volumes, it may be configured so that the volume IDs required to access the data are not provided to the outside.

[0035] A backup image is a backup image of the production volume 41 at a different point in time. To create a backup image, for example, a thin image saved to the data protection area 69 is used. However, other implementation methods may be used as long as they are capable of acquiring the data that constitutes the backup image. Alternatively, a backup function may be used that can store the data that constitutes the backup image in a separate volume. Hereinafter, data that is made up of backup data at a specified point in time may be referred to as a "backup image."

[0036] The open storage device 60 is an example of a second storage device, and accumulates multiple generations of backup images created at different times for the production volume 41 in a data protection area 69 that cannot be accessed from external devices. The open storage device 60 includes an export volume 12, a mapping volume 12x, a data protection area 69, a management table volume 11, a Verify-base-Volume (hereinafter referred to as a "VB volume") 61, and a Verify-access-Volume (hereinafter referred to as a "VA volume") 62. The export volume 12 stores the actual data of the backup images of each generation.

[0037] The export volume 12 is mapped to a virtual volume (not shown) using circumscribing volume mapping information, serves as a storage destination for data of the virtual volume (not shown), and stores a copy of data of the production volume 41 .

[0038] In this embodiment, for the data stored in the production volume 41, a virtual volume (not shown) that pairs with the production volume 41 is created in the backup storage device 10. Volume mapping information is registered in the management table volume 11 with this virtual volume as the external source volume and the production volume 41 of the production storage device 40 as the external destination volume.

[0039] The data is copied, for example, asynchronously, from the production volume 41 to the export volume 12 via a virtual volume (not shown). This external connection volume mapping information is used, for example, in an external connection function implemented by UVM (Universal Volume Manager) provided by Hitachi, Ltd. (registered trademark). The external connection function is a function that, for example, uses virtualization technology to integrate multiple disk arrays of different models as if they were a single disk array. By connecting an external storage device having a logical volume and mapping that logical volume, it is possible to treat multiple disk arrays of different models as if they were a single disk array.

[0040] The management table volume 11 stores management information such as backup data management information for managing the copy number assigned to each backup image, access VOL information relating to the configuration of the volume 13, linking information between the copy number and the access volume, and information on the time period during which the access volume can be backed up, as will be described later. The management table volume 11 records meta information for each backup generation. The meta information includes, for example, the backup date and time and information on the association of so-called snapshot pair information.

[0041] The VB volume 61 is a volume for storing backup images that are the subject of data verification. The backup images stored in the VB volume 61 are selected from among the multiple backup images stored in the data protection area 69 and are the subject of data verification.

[0042] The VA volume 62 is a volume to which backup images of the VB volume 61 are copied one by one, for example, by TI (Thin Image). Note that in this embodiment, the VA volume 62 is provided separately from the VB volume 61 in order to ensure read-only access when reading out backup images from the verification storage device 30, as will be described later, from a security standpoint.

[0043] The VA volume 62 is linked to a virtual volume in the data protection area 35 of the verification storage device 30, for example, by UVM. The VA volume 62 is a single large-capacity volume, but the virtual volume functions as, for example, four unit volumes obtained by dividing the single volume. A backup image of a specific generation stored in the VA volume 62 can be referenced as a backup image of a specific generation in the virtual volume 34.

[0044] On the other hand, the open storage device 60 includes a mapping volume 12x that stores volume mapping information corresponding to the export volume 12, a mapping volume 61x that stores volume mapping information corresponding to the VB volume 61, and a volume 62x that stores volume mapping information corresponding to the VA volume 62.

[0045] In this embodiment, the actual data that constitutes the backup image of the data area 14 exists in the export volume 12 of the open storage device 60. The export volume 12 is linked to the volume 13 of the data area 14 by, for example, UVM.

[0046] In this embodiment, for the data stored in the export volume 12, volume 13 is created in the backup storage device 10 as a virtual volume paired with the export volume 12. Volume mapping information is registered in the management table volume 11, with this volume 13 as the external source volume and the export volume 12 of the open storage device 60 as the external destination volume.

[0047] That is, in this embodiment, a backup image at a specific point in time (specific generation) is linked to the volume 13, thereby providing the backup image at a specific point in time (specific generation) to the open storage device 60 (its export volume 12). This linking is an operation in which a backup image at a specific point in time (specific generation) of the export volume 12 is associated with the volume 13, and the associated backup image is provided by the volume 13. This operation is executed, for example, when the backup storage device 10 receives a command from the second host.

[0048] It should be noted that the data that constitutes the backup image of volume 13 is stored in export volume 12 of the open storage device 60 , and therefore access to volume 13 is generally slower than access to production volume 41 .

[0049] As described above, in this embodiment, the backup storage device 10 creates a backup image of the production volume 41 from which data is read and written by an external device (host), and stores the backup image in the data area 14.

[0050] The above-mentioned export volume 12 is, for example, a large-capacity volume, is mapped to volume 13 using external volume mapping information, and is the storage destination for the actual data of volume 13. The export volume 12 uses, for example, an external function called UVM (Universal Volume Mapping) to provide the backup storage device 10 with four unit volumes obtained by finely dividing the large-capacity volume.

[0051] The data protection area 69 stores multiple generations of backup images by storing backup data created at each point in time in the export volume 12, for example, backup images of each generation acquired by acquiring a TI (Thin Image). The data protection area 69 cannot be accessed from external devices. Details of the data protection area 69 will be described later.

[0052] The mapping volume 12x stores volume mapping information corresponding to the backup images of each generation.

[0053] The open server 50 is an example of a control device, which extracts summary information regarding the overview of the production volume 41 from volume mapping information regarding the configuration of the production volume 41 at the time when each of the multiple generations of backup images was created, and obtains specific volume mapping information of the production volume 41 corresponding to a specific backup generation selected from the multiple generations of backup images based on the summary information (for example, as described below, the number of unit volumes of the production volume 41 has been reduced to two).

[0054] The open server 50 acquires, via the relay volume 15, the volume mapping information of the volume to be backed up that was written to the relay volume 15 in conjunction with the backup, and writes the volume mapping information to the mapping volume of the open storage device 60. In the open storage device 60, multiple generations of backup images exist, and multiple pieces of volume mapping information corresponding to the multiple generations of backup images are written to the mapping volume.

[0055] The open server 50 acquires summary information from the management table of the management volume of the open storage device 60 so that the backup generation can be selected, and displays information on the GUI that allows the volume configuration for each generation to be recognized, as will be described later.

[0056] In the open storage device 60, the volume mapping information corresponding to the backup image of the selected generation among the plurality of volume mapping information managed in the management volume is assigned to the volume.

[0057] The open server 50 acquires volume mapping information corresponding to the backup image of the selected generation from the open storage device 60 via the network 103 and stores it in the relay volume 15 of the backup storage device 10 via the SAN 102.

[0058] In this embodiment, the open server 50 extracts, as summary information, at least one of the number of unit volumes that make up the production volume 41 and their total capacity from the volume mapping information regarding the configuration of the production volume 41 at the time each of the multiple generations of backup images was created.

[0059] Specifically, in conjunction with the processing related to the backup image of a specific generation described above, volume mapping information corresponding to the backup image of that specific generation is generated, and summary information is extracted from the volume mapping information. Details of the processing related to the generation of this summary information will be described later. That is, each time multiple generations of backup images are created, summary information is extracted.

[0060] The open server 50 controls the entire backup process. For example, the open server 50 manages the number of generations of backup images that have been acquired. The open server 50 includes file conversion software 51 as software.

[0061] The file conversion software 51 has a function for transmitting information to be transmitted between the secondary mainframe 90 and the open server 50 and open storage device 60, and a function for converting file formats.

[0062] Examples of the information to be transmitted include, in addition to the backup schedule such as the start / end of backup, volume mapping information relating to the current and previous configurations of each volume.

[0063] The file conversion software 51 creates summary information from the volume mapping information corresponding to each backup image and stores it in the open storage device 60 via the network 103 .

[0064] The storage management software 53 controls the open side, i.e., the open server 50 and the open storage device 60. The storage management software 53 controls backup and data verification (and restoration), for example, controlling the start of backup. The backup schedule is set in advance. The storage management software 53 stores information about the acquired backup in the management table of the management table volume 11.

[0065] On the other hand, the open server 50 is an example of a control device, which verifies whether the volume configuration based on the backup image of a specific generation corresponding to specific volume mapping information matches the volume configuration based on the current backup image of the production volume 41, and if the result of the verification shows that the two volume configurations match, it verifies and recovers the backup data based on the backup image of the specific generation. A specific description will be given below.

[0066] The verification storage device 30 has a data protection area 35 that cannot be accessed from external devices. The data protection area 35 has a virtual volume 32, which will be described later. The actual data stored in a VA volume 62, which will be described later, is copied to the virtual volume 32, for example, by UVM. This data is the data that is the target of data verification, which will be described later.

[0067] In this embodiment, for the data stored in the VA volume 62, a virtual volume 32 that pairs with the VA volume 62 is created in the verification storage device 30. Volume mapping information is registered in the management table volume 11, with this virtual volume 32 as the external source volume and the VA volume 62 of the open storage device 60 as the external destination volume.

[0068] The open server 50 verifies whether a backup image of a specific generation of a virtual volume (not shown) has the same volume configuration as the backup image that is the target of data verification. The actual data of the backup image that is the target of data verification is stored in the VA volume 62.

[0069] If the volume configuration is the same, the open server 50 copies the backup image of a specific generation of the virtual volume, for example, using the above-mentioned SI (Shadow Image), and restores it as backup data, but if the volume configuration is not the same, it determines that the data authentication is an error and, for example, does not restore the backup data or notifies the user of this fact.

[0070] In this embodiment, if the open storage device 60 finds that the volume configurations of both volumes do not match as a result of data verification, it may, for example, notify the copy number of the unit volume whose volume configuration does not match, and allow the user to select only some of the unit volumes whose volume configuration matches.

[0071] <Hardware configuration> 2 is a block diagram showing an example of a hardware block configuration of a storage device, etc. The storage device, etc. includes the backup storage device 10, verification storage device 30, production storage device 40, and open storage device 60 shown in FIG.

[0072] 2, the backup storage device 10 will be described as an example, but the other storage devices have a similar configuration. The backup storage device 10 has a PDEV 171 which is a plurality of (or one) physical storage devices, and a storage controller 161 connected to the PDEV 171.

[0073] The storage controller 161 has an I / F 11a, an I / F 11b, an I / F 163, a memory 162, and a processor 161a connected thereto. The I / F 11a, the I / F 11b, and the I / F 163 are examples of an interface unit. The memory 162 is an example of a storage unit. The processor 161a is an example of a processor unit.

[0074] The I / F 11a is a communication interface device that mediates data exchange between the first host or an external storage device and the storage controller 161. The first host or an external storage device is connected to the I / F 11a via an FC (Fibre Channel) network.

[0075] A first host or an external storage device sends an I / O request (write request or read request) to the storage controller 161 specifying an I / O destination (for example, a logical volume number such as a LUN (Logical Unit Number) or a logical address such as an LBA (Logical Block Address)).

[0076] The I / F 11b is a communication interface device that mediates data exchange between the second host and the storage controller 161. The second host is connected to the I / F 11b via an IP (Internet Protocol) network.

[0077] The FC network and the IP network may be the same communication network. The second host manages the backup storage device 10.

[0078] The I / F 163 is a communication interface device that mediates the exchange of data between a plurality of PDEVs 171 and the storage controller 161. A plurality of PDEVs 171 are connected to the I / F 163.

[0079] The memory 162 stores programs executed by the processor 161a and data used by the processor 161a. The processor 161a executes the programs stored in the memory 162. For example, a set of the memory 162 and the processor 161a is duplicated.

[0080] 3 is a diagram showing an example of volume mapping information corresponding to a volume configuration. In the illustrated example, the volume mapping information is information for managing the correspondence between, for example, the export volume 12 of the open storage device 60 and the volume 13 of the backup storage device 10.

[0081] The volume mapping information includes the backup acquisition date and time, an open storage volume ID (IDentifier), and a mainframe storage volume ID (IDentifier). The open storage volume ID indicates the volume ID of the export volume 12 in the open storage device 60. The mainframe storage ID indicates the volume ID of the volume 13 in the backup storage device 10.

[0082] For example, a backup acquired at 9:00:00 on Jan. 1, 2022 has volume mapping information as shown in the example below. Specifically, the volume ID "101" of the export volume 12 in the open storage device 60 corresponds to the volume IDs "1001," "1002," "1003," and "1004" of the volume 13 in the backup storage device 10.

[0083] 4 is a diagram showing an example of the management table of the management table volume 11. The management table includes storage ID, volume ID, . . ., backup acquisition date and time, . . ., the number of volumes on the mainframe side, and their total capacity.

[0084] A storage ID is an ID used to identify multiple storage devices, etc. from one another. A volume ID is an ID used to distinguish between volumes. The number of volumes on the mainframe side indicates the number of volumes on the mainframe side ("mainframe volumes" in the figure), and the total capacity indicates the sum of the capacities of all volumes on the mainframe side.

[0085] For example, the volume ID "101" of the open storage device 60 with a storage ID of "800000020000" is associated with the backup acquisition dates and times "January 1, 2022, 9:00:00," "January 3, 2022, 9:00:00," and "January 5, 2022, 9:00:00." The backups acquired at these backup acquisition dates and times indicate, for example, that the number of volumes on the mainframe side is 2,000, 4,000, and 6,000, respectively, with total capacities of 2 TB, 4 TB, and 6 TB.

[0086] In this embodiment, the following correspondences exist: That is, the volume ID "101" of the export volume 12 (12a) of the open storage device 60 corresponds to the volume IDs "1001," "1002," "1003," and "1004" of the volume 13 (13a) of the backup storage device 10; the volume ID "102" of the export volume 12 (12b) of the open storage device 60 corresponds to the volume IDs "2001," "2002," "2003," and "2004" of the volume 13 (13b) of the backup storage device 10; and the volume ID "103" of the export volume 12 (12a) of the open storage device 60 corresponds to the volume IDs "3001," "3002," "3003," and "3004" of the volume 13 (13c) of the backup storage device 10.

[0087] 5 is a diagram showing an example of data verification when the capacity of a volume is expanded during system operation. The illustrated example shows an example in which the capacity of a production volume 41, which was made up of two unit volumes, is expanded to four unit volumes in the middle of a backup cycle during system operation.

[0088] Backup images acquired at various times are stored in the export volume 12 of the open storage device 60. In the open storage device 60, backup images acquired at different times are continuously stored in the data protection area 69. For example, multiple generations of backup images 14a to 14d are stored in the data protection area 69. In the illustrated example, four generations of backup images 14a to 14d are stored, from newest to oldest, from left to right.

[0089] Each backup image 14a to 14d is assigned a copy number as follows: backup image 14a is assigned copy number #1, backup image 14b is assigned copy number #2, backup image 14c is assigned copy number #3, and backup image 14d is assigned copy number #4.

[0090] For example, when creating backup images 14a, 14b, 14c, and 14d, the storage controller of the backup storage device 10, in accordance with instructions from the host, for example, assigns a copy number indicating the backup generation described above to each of the backup images 14a, 14b, 14c, and 14d, and manages them in the backup data management information of the management table volume 11. Since each of the backup images 14a, 14b, 14c, and 14d is a backup image at a different point in time specified by the export volume 12, in this embodiment they are collectively referred to as a "backup generation" or simply as a "generation."

[0091] In the verification storage device 30, if the volume configuration of the backup image to be verified (in the illustrated example, for example, backup image 14c with copy number #3) matches the current volume configuration of the production volume 41, the backup data is restored based on the backup image to be verified.

[0092] The data replication system has the above configuration, and an example of its operation will now be described. First, an outline of the data replication method used by the data replication system will be described.

[0093] The data replication method includes a storing step in which a backup storage device 10, which is an example of a first storage device, creates a backup image of a production volume 41, which is an example of a predetermined volume to which data is read and written by an external device; a storing step in which an open storage device 60, which is an example of a second storage device, stores multiple generations of backup images of the production volume 41, which have been created at different times, in a data protection area 69 that cannot be accessed from external devices; and a step in which an open server 50, which is an example of a control device, extracts summary information relating to an overview of the production volume 41 from volume mapping information relating to the configuration of the production volume 41 at the times when each of the multiple generations of backup images was created. The method includes a summary information extraction step in which the open server 50 acquires specific volume mapping information of the production volume 41 corresponding to a specific backup generation selected from multiple generations of backup images based on the summary information, and a data verification and recovery step in which the open server 50, as an example of a control device, verifies whether or not the volume configuration based on the backup image of the specific generation corresponding to the specific volume mapping information matches the volume configuration based on the current backup image of volume 13 that reflects the current state of the production volume 41, and if the result of the verification shows that the two volume configurations match, verifies and recovers the backup data based on the backup image of the specific generation. A specific description will be given below.

[0094] 6 is a flowchart showing an example of the procedure for capacity expansion processing. When the capacity of a volume is expanded, the mainframe updates the volume configuration using the external connection function described above. On the open system, the capacity of the volume is expanded and the definition file related to the volume is updated.

[0095] In step S1, for example, in the middle of a backup cycle, two more unit volumes are added to a production volume 41 that is made up of two unit volumes in the production storage apparatus 40. In step S2, the backup storage apparatus 10 sets an SI (Shadow Image) pair of the volumes. As a result, in the backup storage apparatus 10, data in the production volume 41 is copied to a virtual volume (not shown).

[0096] In step S3, for example, the secondary mainframe 90 updates the volume mapping information in the management table volume 11 in response to the change in the volume configuration described above.

[0097] In step S4, two unit volumes are added. If unit volumes are added, the following step S5 is executed, whereas if no unit volumes are added, step S5 is omitted.

[0098] In step S5, the open storage device 60 sets a TI (Thin Image) pair of the volumes. As a result, in the backup storage device 10, the data of the export volume 12 is acquired in the data protection area 69. In step S6, the open storage device 60 updates the definition file related to the volume.

[0099] 7 is a flowchart showing an example of the procedure for volume mapping information saving processing. The volume mapping information saving processing is a process for acquiring volume configuration information for each volume, and is executed, for example, periodically. An example of the execution timing is assumed to be during backup.

[0100] The volume mapping information save process is executed under the control of the secondary mainframe 90. In this volume mapping information save process, the secondary mainframe 90 writes the acquired volume mapping information to the relay volume 15, and further, the open server 50 saves the volume mapping information in the mapping volume 12x of the open storage device 60 via the relay volume 15. This will be explained in detail below.

[0101] In step S11, the secondary mainframe 90 checks the volume mapping information, and in step S12, the secondary mainframe 90 writes the volume mapping information to the relay volume 15.

[0102] In step S13, the open server 50 reads the volume mapping information from the relay volume 15. In step S14, the open server 50 determines whether the hash value is normal. Here, the hash value is, for example, a value calculated from the data stored in the relay volume 15. When the volume mapping information is handed over from the secondary mainframe 90 to the open server 50, the secondary mainframe 90 automatically creates the hash value, whereas when the volume mapping information is handed over from the open server 50 to the secondary mainframe 90, the open storage device 60 automatically creates the hash value.

[0103] If the hash value is not normal in step S14, the open server 50 notifies the secondary mainframe 90 of this fact and terminates the process abnormally (step S15).

[0104] If the hash value is normal in step S14, the open server 50 determines whether the definition file that defines the configuration information of the export volume 12 is consistent with the volume mapping information of the export volume 12 (step S16). Specifically, since both the volume mapping information received from the secondary mainframe 90 (mainframe side) and the definition file of the open server 50 (open side) contain the configuration information of the export volume 12, their consistency is confirmed.

[0105] If the definition file and the volume mapping information do not match in step S16, the open server 50 executes step S14 described above. On the other hand, if the definition file and the volume mapping information match in step S16, the open server 50 executes step S17. In step S17, the open server 50 extracts summary information from the volume mapping information as an overview of the information required for data verification, and records the information in the management table (hereinafter also referred to as the "ledger") of the management table volume 11. Here, the volume mapping information actually includes many types of configuration information, and there are cases where it is not necessary to refer to all types of configuration information during data verification. Therefore, in this embodiment, summary information such as the number of volumes (and total capacity) is extracted from the volume mapping information. The summary information is used, for example, during data verification on the open side (open server 50).

[0106] In step S18, the open server 50 stores volume mapping information corresponding to the backup image in the mapping volume 12x of the open storage device 60. In step S19, the open storage device 60 creates a copy of the mapping volume 12x in the data protection area 69 of the verification storage device 30, for example.

[0107] 8 is a flowchart showing an example of the procedure for data verification and recovery processing on the open side. The data verification and recovery processing uses verification content on the open side and assigns the data to be verified to a volume, making it possible to perform verification work on the mainframe side as well.

[0108] In step S21, for example, a user starts up verification content on the open server 50. The verification content is, for example, the storage management software 53 of the open server 50 described above. The reason for using the verification content in this manner is that by using the verification content on the open side and allocating data to be verified to a volume, data verification can also be performed on the mainframe side.

[0109] In step S22, the open server 50 acquires meta information (including summary information) for each backup generation from the management table (ledger) of the management table volume 11, and displays an operation screen (not shown) (hereinafter referred to as the "backup generation selection screen") related to backup generations that can be subject to data verification based on the meta information for each backup generation. On the backup generation selection screen, the user selects the backup generation (backup acquisition date and time) that should be subject to data verification. The management table volume 11 can be directly accessed from the open server 50 via the network 103. Since the management table volume 11 and the open server 50 are isolated from the production storage device 40 on the mainframe side, there is no risk of virus infection via the production storage device 40.

[0110] More specifically, in step S22, the storage management software 53, which is an example of verification content, displays a tabular selection screen 200 including summary information such as that shown in Fig. 10 on the backup generation selection screen described above. Specifically, the open server 50 displays backup images of multiple generations, and also displays the selection screen 200 for selecting one of the backup images of multiple generations in front of and over the backup images.

[0111] That is, the open server 50 displays summary information when a backup image of a specific generation is selected from backup images of multiple generations as follows.

[0112] In step S23, the user refers to the backup generation selection screen on the open server 50 and selects the backup generation to be the target of data verification. The backup acquisition date and time is associated with the backup generation.

[0113] In step S24, the open server 50 assigns the backup generation of the mapping volume 12x corresponding to the backup generation to be verified to the volume 62x as the access volume. The volume to be verified is identified based on the volume mapping information from the mainframe. In this embodiment, the backup generation to be verified is known when the user selects the backup generation.

[0114] In step S25, the open server 50 mounts the volume 62x on the open server 50.

[0115] In step S26, the open server 50 acquires the volume mapping information of volume 62x and writes the volume mapping information to the relay volume 15. Specifically, the open server 50 writes the volume mapping information of the volume that is the target of data verification selected on the open side to the relay volume 15. This volume mapping information is used when performing data verification and recovery on the mainframe side.

[0116] 9 is a flowchart showing an example of the procedure for data verification and recovery processing on the mainframe side. In step S31, the secondary mainframe 90 acquires volume mapping information from the relay volume 15 as configuration information related to the backup generation that is the target of data verification.

[0117] In step S32, the secondary mainframe 90 compares the acquired configuration information with the configuration information of the target volume. If the data verification in step S32 shows that the two pieces of configuration information match, the secondary mainframe 90 executes step S34, whereas if the two pieces of configuration information do not match, the secondary mainframe 90 executes step S36. In step S34, the secondary mainframe 90 verifies the target volume (also referred to as "data verification"). In step S35, the secondary mainframe 90 recovers the target volume using the verification storage device 30. Meanwhile, in step S36, the secondary mainframe 90 executes a mismatch process. In this mismatch process, for example, an external notification is sent to the effect that the two pieces of configuration information do not match.

[0118] In this mismatch process, if the configurations of both volumes do not match, the verification storage device 30 (or secondary mainframe 90) displays the mismatched configurations on a display unit (not shown).

[0119] The data replication system according to this embodiment includes a backup storage device 10 (an example of a first storage device) that creates a backup image of a production volume 41 (an example of a predetermined volume to which data is read and written by an external device) and stores the backup image in a data area 14; an open storage device 60 (an example of a second storage device) that stores multiple generations of backup images of the production volume 41, created at different times, in a data protection area 69 that is inaccessible to external devices; and an open server 50 (an example of a control device) that extracts summary information about the predetermined volume from volume mapping information about the configuration of the production volume 41 at the time each of the multiple generations of backup images was created, and acquires specific volume mapping information for the production volume 41 corresponding to a specific backup generation selected from the multiple generations of backup images based on the summary information. The open server 50 verifies whether the volume configuration based on the specific generation of backup image corresponding to the specific volume mapping information matches the volume configuration based on the current backup image of the production volume 41. If the volume configurations match, the open server 50 verifies and recovers backup data based on the specific generation of backup image. The open server 50 may also include some of the functions of a secondary mainframe 90.

[0120] The data replication method of the data replication system according to this embodiment includes a storing step in which a backup storage device 10 as an example of a first storage device creates a backup image of a production volume 41 as an example of a predetermined volume to which data is read and written by an external device, and stores the backup image in a data area 14; a storing step in which an open storage device 60 as an example of a second storage device stores multiple generations of backup images of the production volume 41 created at different times in a data protection area 69 that cannot be accessed from external devices; and a storing step in which an open server 50 as an example of a control device stores multiple generations of backup images of the production volume 41 based on volume mapping information relating to the configuration of the production volume 41 at the time when each of the multiple generations of backup images was created. The method includes a summary information extraction step of extracting summary information regarding an overview of the production volume 41; an acquisition step in which the open server 50 acquires specific volume mapping information of the production volume 41 corresponding to a specific backup generation selected from multiple generations of backup images based on the summary information; and a data verification and recovery step in which the open server 50 verifies whether or not the volume configuration based on the backup image of the specific generation corresponding to the specific volume mapping information matches the volume configuration based on the current backup image of the production volume 41, and if the verification shows that the two volume configurations match, verifies and recovers backup data based on the backup image of the specific generation.

[0121] In this way, even if the capacity of the production volume 41 is expanded during the backup cycle, the backup data can be recovered after verifying the data. Therefore, it becomes possible to expand the capacity of the production volume 41 while the system is in operation, improving flexibility when building a system. For example, a user can calculate the total capacity of backup data in accordance with the requirements when installing the system, start operation with a minimum volume configuration, and then expand the total capacity of the production volume 41 while the system is in operation.

[0122] In this embodiment, the open server 50 extracts, as the summary information described above, at least one of the number of unit volumes constituting the production volume 41 and their total capacity from the volume mapping information relating to the configuration of the production volume 41 at the time each of the multiple generations of backup images was created. In this way, the user can easily select a specific generation of backup image from among the multiple generations of backup images by referring to summary information that can be easily grasped, such as the number of unit volumes.

[0123] In this embodiment, the open server 50 displays backup images of multiple generations and also displays a selection screen for selecting one of the backup images of multiple generations, making it easier for the user to select a backup image of a specific generation from the backup images of multiple generations.

[0124] In this embodiment, when a backup image of a specific generation is selected from backup images of multiple generations, the open server 50 displays summary information, for example, superimposed on the selection screen described above. In this way, the user can easily select a backup image of a specific generation from backup images of multiple generations by referring to the summary information.

[0125] The data replication system according to this embodiment is provided with a display unit (not shown) that displays the mismatched configurations when the two volume configurations do not match during the mismatch processing described above. This allows the user to reselect a backup image generation taking into account the mismatched configurations.

[0126] (2) Second embodiment The data replication system according to the second embodiment has almost the same configuration and operation as the data replication system according to the first embodiment, so a description of the same configuration and operation will be omitted and the following description will focus on the differences. Unlike the first embodiment, the second embodiment employs the concept of grouping volumes.

[0127] 11 is a diagram showing an example of a volume configuration in a data replication system according to the second embodiment. The backup storage device 10 holds volume mapping information that associates volumes on the mainframe side with volumes on the open side as configuration information of the UVM described above.

[0128] In the illustrated example, the open storage device 60 has export volumes 12a to 12c and a first VA volume 62a to a third VA volume 62c that are acquired at different times. The export volumes 12a to 12c correspond to the above-mentioned export volume 12, and the first VA volume 62a to the third VA volume 62c correspond to the above-mentioned VA volume 62. The illustrated example shows a case where the three export volumes 12a to 12c are set in one policy group.

[0129] The export volume 12a with volume ID "101" in the open storage device 60 corresponds to volume 13a in the backup storage device 10, which includes unit volumes with volume IDs "1001", "1002", "1003" and "1004", through the external connection function described above.

[0130] The export volume 12b with volume ID "102" in the open storage device 60 corresponds to volume 13b in the backup storage device 10, which includes unit volumes with volume IDs "2001", "2002", "2003" and "2004", through the external connection function described above.

[0131] The export volume 12c with volume ID "103" in the open storage device 60 corresponds to the volume 13c including the unit volumes with volume IDs "1001," "1002," "1003," and "1004" in the backup storage device 10 through the external connection function described above. The volumes 13a to 13c correspond to the volume 13 described above.

[0132] The first VA volume 62a with volume ID "301" in the open storage device 60 corresponds to the virtual volume 32a including unit volumes with volume IDs "1001", "1002", "1003" and "1004" in the verification storage device 30 through the external connection function described above.

[0133] The second VA volume 62b with volume ID "302" in the open storage device 60 corresponds to the virtual volume 32b including unit volumes with volume IDs "2001", "2002", "2003" and "2004" in the verification storage device 30 through the external connection function described above.

[0134] The third VA volume 62c with volume ID "303" in the open storage device 60 corresponds to the virtual volume 32c including the unit volumes with volume IDs "1001," "1002," "1003," and "1004" in the verification storage device 30, through the external connection function described above. The virtual volumes 32a to 32c correspond to the virtual volume 32 described above.

[0135] Fig. 12 is a diagram showing an example of information used in the volume configuration shown in Fig. 11. In the first embodiment, volume mapping information was used, whereas in the second embodiment, in order to perform the above-mentioned grouping, combined mapping information is used, which is created by combining the volume mapping information with group mapping information such as the following:

[0136] In the second embodiment, the secondary mainframe 90 combines the following group mapping information with the volume mapping information (see the lower left side of Fig. 12). The illustrated group mapping information indicates that, for example, as shown in the upper left side of Fig. 12, group A includes unit volumes with volume IDs "1001", "1002", and "2001", group B includes unit volumes with volume IDs "1003", "1004", "2002", "2003", "2004", and "3004", and group C includes unit volumes with volume IDs "3001", "3002", and "3003".

[0137] The open server 50 (or both the mainframe and the open server 50) combines the group mapping information with the volume mapping information described above to create the following combined mapping information: That is, the combined mapping information indicates, for each group, which unit volumes of the volumes 13 and which export volumes 12 are included.

[0138] More specifically, as shown in the lower right side of Figure 12, the combined mapping information indicates that group A includes unit volumes of volumes 13 with volume IDs "1001," "1002," and "2001," and also includes export volumes 12 with volume IDs "101" and "102," group B includes unit volumes of volumes 13 with volume IDs "1003," "1004," "2002," "2003," "2004," and "3004," and also includes export volumes 12 with volume IDs "101," "102," and "103," and group C includes unit volumes of volumes 13 with volume IDs "3001," "3002," and "3003," and also includes export volume 12 with volume ID "103."

[0139] Fig. 13 is a diagram showing an example of the group mapping information shown in Fig. 12. The group mapping information includes a group label and a mainframe storage ID for each backup acquisition date and time. The mainframe storage ID indicates the volume ID of the volume 13 in the backup storage device 10 on the mainframe side.

[0140] In the example shown, at the backup acquisition date and time of "January 1, 2022, 9:00:00," as described above, it is defined that group A contains unit volumes with volume IDs "1001," "1002," and "2001," group B contains unit volumes with volume IDs "1003," "1004," "2002," "2003," "2004," and "3004," and group C contains unit volumes with volume IDs "3001," "3002," and "3003."

[0141] Fig. 14 is a diagram showing an example of the merged mapping information shown in Fig. 12. The merged mapping information includes a group label, a mainframe storage ID, and an open storage volume ID for each backup acquisition date and time. The mainframe storage ID indicates the volume ID of the volume 13 in the backup storage device 10 on the mainframe side. The open storage volume ID indicates the volume ID of the export volume 12 in the open storage device 60.

[0142] In the example shown, as described above, at the backup acquisition date and time "January 1, 2022, 9:00:00," group A includes unit volumes of volumes 13 with volume IDs "1001," "1002," and "2001," and also includes export volumes 12 with volume IDs "101" and "102," group B includes unit volumes of volumes 13 with volume IDs "1003," "1004," "2002," "2003," "2004," and "3004," and also includes export volumes 12 with volume IDs "101," "102," and "103," and group C includes unit volumes of volumes 13 with volume IDs "3001," "3002," and "3003," and also includes export volume 12 with volume ID "103."

[0143] In this embodiment, the production volume 41 is made up of multiple volumes. The open server 50 manages the multiple volumes by dividing them into at least one group. The open server 50 extracts summary information relating to an overview of at least one volume included in the group, acquires specific volume mapping information for the production volume 41 corresponding to a specific backup generation selected from multiple generations of backup images based on the summary information, and displays the summary information as described below when a backup image of a specific generation is selected from the multiple generations of backup images.

[0144] Fig. 15 is a flowchart showing an example of the procedure for volume mapping information storage processing according to the second embodiment. The illustrated flowchart corresponds to the flowchart shown in Fig. 7 of the first embodiment. The flowchart shown in Fig. 15 differs from the flowchart shown in Fig. 7 of the first embodiment mainly in the processing content of step S11.

[0145] In step S11, the secondary mainframe 90 on the mainframe side checks the volume mapping information. Specifically, the secondary mainframe 90 checks whether the volume mapping information matches the mainframe-side volume ID included in the group mapping information.

[0146] Steps S12 to S19 are almost the same as those in the first embodiment, but in step S17, the open server 50 extracts summary information relating to an overview of at least one volume included in the group from the volume mapping information and registers it in the management table of the management table volume 11. Also, in step S18, the open server 50 does not combine the volume mapping information and the group mapping information at this stage, but stores them in the mapping volume 12x in their respective formats. The combination of the volume mapping and the group mapping is performed on the open side (open server 50) when verifying the data.

[0147] Fig. 16 is a flowchart showing an example of the procedure for data verification and recovery processing on the open side. The flowchart shown in Fig. 16 corresponds to the flowchart shown in Fig. 8 in the first embodiment. Note that steps S21, S22, S23, S24, S25, and S26 are the same as those in the first embodiment, and therefore will not be described unless there is a particular need to mention them.

[0148] Steps S21 and S22 are the same as in the first embodiment. As a result, a backup generation selection screen (not shown) is displayed, as in the first embodiment. On the backup generation selection screen, the user selects the backup generation (backup acquisition date and time) to be subject to data verification.

[0149] In step S22A, the open server 50 (or both the mainframe side and the open server 50) combines the volumes to be verified on a group basis based on the volume mapping information. Specifically, the secondary mainframe 90 combines the group mapping information with the volume mapping information to generate combined mapping information required for data verification on the open side.

[0150] As described above, when the user selects a specific backup generation on the backup generation selection screen, the open server 50 displays a group selection screen 201 shown in Fig. 17 based on the selected specific backup generation. The group selection screen 201 displays information about the volumes included in the group corresponding to the specific backup generation.

[0151] Specifically, the group selection screen 201 displays group information including a check box 201a, a group label 201b of the group corresponding to the particular backup generation, a detailed description of the group 201c, the number of export volumes 201d, the number of volumes on the mainframe side 201e, and their total capacity 201f.

[0152] In step S23A, the user selects a group for data verification on the open server 50. Specifically, the user selects the desired group by checking the check box 201a corresponding to the desired group on the group selection screen 201. At this time, the group selection screen 201 displays summary information acquired from the management table (ledger), such as at least one of the number of volumes 201e on the mainframe side and their total capacity 201f. The user determines which group to select, particularly based on the summary information.

[0153] When the selection of the group information is completed, the open server 50 executes steps S24 to S26 in the same manner as in the first embodiment. In the second embodiment, in step S24, the open server 50 assigns the backup generation of the mapping volume 12x that is the target of data verification and corresponds to the group information to the volume 62x.

[0154] In this embodiment, the production volume 41 is made up of multiple volumes. The open server 50 manages the multiple volumes by dividing them into at least one group. The open server 50 extracts summary information regarding an overview of at least one volume included in the group, acquires specific volume mapping information for the production volume 41 corresponding to a specific backup generation selected from multiple generations of backup images based on the summary information, and displays the summary information as described below when a backup image of a specific generation is selected from the multiple generations of backup images. In this way, by dividing related volumes among the multiple volumes that make up the production volume 41 into groups, the user can recover backup data from a backup image of a specific generation while referring to the summary information of the related volumes.

[0155] The present invention is not limited to the above-described embodiments, and includes various modifications and equivalent configurations within the spirit and scope of the appended claims. 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, the elements described in parallel in the present embodiment may be configured such that at least one of the elements is connected in series to the other elements. [Industrial Applicability]

[0156] The present invention can be applied to, for example, a data replication system relating to a technique for restoring backup data after performing data verification. [Explanation of symbols]

[0157] 10: Backup storage device, 30: Verification storage device, 5: Open server, 60: Open storage device, 90: Secondary mainframe

Claims

1. a first storage device that creates a backup image of a predetermined volume from which data is read and written by an external device and stores the backup image in a data area; a second storage device that accumulates backup images of multiple generations created at different times for the predetermined volume in a data protection area that cannot be accessed from the external device; a control device that extracts summary information relating to an overview of the predetermined volume from volume mapping information relating to the configuration of the predetermined volume at the time when each of the multiple generations of backup images was created, and acquires specific volume mapping information of the predetermined volume corresponding to a specific backup generation selected from the multiple generations of backup images based on the summary information; the volume mapping information is information that indicates a correspondence relationship between the specified volume in the first storage device and a backup image volume in the second storage device at the time when each of the multiple generations of backup images was created, and The control device Verify whether or not the volume configuration based on the backup image of the specific backup generation corresponding to the specific volume mapping information matches the volume configuration based on the current backup image of the specified volume, and if the result of the verification shows that both volume configurations match, verify and recover the backup data based on the backup image of the specific backup generation. A data replication system comprising:

2. A first storage device that creates a backup image of a specified volume from which data is read and written by an external device and stores the backup image in a data area; a second storage device that accumulates backup images of multiple generations created at different times for the predetermined volume in a data protection area that cannot be accessed from the external device; a control device that extracts summary information relating to an overview of the predetermined volume from volume mapping information relating to the configuration of the predetermined volume at the time when each of the multiple generations of backup images was created, and acquires specific volume mapping information of the predetermined volume corresponding to a specific backup generation selected from the multiple generations of backup images based on the summary information; The control device verifying whether or not a volume configuration based on the backup image of the specific backup generation corresponding to the specific volume mapping information matches a volume configuration based on the current backup image of the specified volume, and if the result of the verification shows that both volume configurations match, verifying and recovering backup data based on the backup image of the specific backup generation; displaying the backup images of the plurality of generations and displaying a selection screen for selecting one of the backup images of the plurality of generations; When the backup image of the specific backup generation is selected from the backup images of the multiple generations, the summary information is displayed. A data replication system comprising:

3. A first storage device that creates a backup image of a specified volume from which data is read and written by an external device and stores the backup image in a data area; a second storage device that accumulates backup images of multiple generations created at different times for the predetermined volume in a data protection area that cannot be accessed from the external device; a control device that extracts summary information relating to an overview of the predetermined volume from volume mapping information relating to the configuration of the predetermined volume at the time when each of the multiple generations of backup images was created, and acquires specific volume mapping information of the predetermined volume corresponding to a specific backup generation selected from the multiple generations of backup images based on the summary information; The control device verifying whether or not a volume configuration based on the backup image of the specific backup generation corresponding to the specific volume mapping information matches a volume configuration based on the current backup image of the specified volume, and if the result of the verification shows that both volume configurations match, verifying and recovering backup data based on the backup image of the specific backup generation; If the volume configurations do not match, a display unit is provided to display the mismatched configurations. A data replication system comprising:

4. A first storage device that creates a backup image of a predetermined volume from which data is read and written by an external device and stores the backup image in a data area; a second storage device that accumulates backup images of multiple generations created at different times for the predetermined volume in a data protection area that cannot be accessed from the external device; a control device that extracts summary information relating to an overview of the predetermined volume from volume mapping information relating to the configuration of the predetermined volume at the time when each of the multiple generations of backup images was created, and acquires specific volume mapping information of the predetermined volume corresponding to a specific backup generation selected from the multiple generations of backup images based on the summary information; The control device verifying whether or not a volume configuration based on the backup image of the specific backup generation corresponding to the specific volume mapping information matches a volume configuration based on the current backup image of the specified volume, and if the result of the verification shows that both volume configurations match, verifying and recovering backup data based on the backup image of the specific backup generation; The predetermined volume is made up of multiple volumes, The control device The plurality of volumes are managed by dividing them into at least one group, and the summary information relating to an overview of at least one of the volumes included in the group is extracted, When the backup image of the specific backup generation is selected from the backup images of the multiple generations, the summary information is displayed. A data replication system comprising:

5. a summary information extraction step in which the control device extracts summary information relating to an overview of a predetermined volume from volume mapping information relating to the configuration of the predetermined volume at the time when each of the multiple generations of backup images was created; an acquisition step in which the control device acquires specific volume mapping information of the predetermined volume corresponding to a specific backup generation selected from backup images of multiple generations based on the summary information; a verification / recovery step in which the control device verifies whether or not a volume configuration based on the backup image of the specific backup generation corresponding to the specific volume mapping information matches a volume configuration based on the current backup image of the specified volume, and if the result of the verification shows that both volume configurations match, verifies and recovers backup data based on the backup image of the specific backup generation; and the first storage device is configured to create a backup image of the predetermined volume from which data is read and written by an external device; the second storage device accumulates backup images of multiple generations created at different times for the predetermined volume in a data protection area that cannot be accessed from the external device; With respect to the specified volume, the volume mapping information is information that indicates a correspondence relationship between the specified volume in the first storage device and a backup image volume in the second storage device at the time when each of the multiple generations of backup images was created. A data replication method comprising:

6. A summary information extraction step in which the control device extracts summary information regarding an overview of a specified volume from volume mapping information regarding the configuration of the specified volume at the time when each of multiple generations of backup images was created; an acquisition step in which the control device acquires specific volume mapping information of the predetermined volume corresponding to a specific backup generation selected from backup images of multiple generations based on the summary information; a verification / recovery step in which the control device verifies whether or not a volume configuration based on the backup image of the specific backup generation corresponding to the specific volume mapping information matches a volume configuration based on the current backup image of the specified volume, and if the result of the verification shows that both volume configurations match, verifies and recovers backup data based on the backup image of the specific backup generation; a selection screen display step in which the control device displays the backup images of the multiple generations and displays a selection screen for selecting one of the backup images of the multiple generations; a summary information display step in which the control device displays the summary information when the backup image of the specific backup generation is selected from the backup images of the multiple generations; and the first storage device is configured to create a backup image of the predetermined volume from which data is read and written by an external device; the second storage device accumulates backup images of multiple generations created at different times for the predetermined volume in a data protection area that cannot be accessed from the external device; A data replication method comprising:

7. A summary information extraction step in which the control device extracts summary information regarding an overview of a specified volume from volume mapping information regarding the configuration of the specified volume at the time when each of multiple generations of backup images was created; an acquisition step in which the control device acquires specific volume mapping information of the predetermined volume corresponding to a specific backup generation selected from backup images of multiple generations based on the summary information; a verification / recovery step in which the control device verifies whether or not a volume configuration based on the backup image of the specific backup generation corresponding to the specific volume mapping information matches a volume configuration based on the current backup image of the specified volume, and if the result of the verification shows that both volume configurations match, verifies and recovers backup data based on the backup image of the specific backup generation; a mismatched configuration display step in which a display unit displays the mismatched configuration when the configurations of both volumes do not match; and the first storage device is configured to create a backup image of the predetermined volume from which data is read and written by an external device; the second storage device accumulates backup images of multiple generations created at different times for the predetermined volume in a data protection area that cannot be accessed from the external device; A data replication method comprising:

8. A summary information extraction step in which the control device extracts summary information regarding an overview of a specified volume that is composed of multiple volumes from volume mapping information regarding the configuration of the specified volume at the time when each of multiple generations of backup images was created; an acquisition step in which the control device acquires specific volume mapping information of the predetermined volume corresponding to a specific backup generation selected from backup images of multiple generations based on the summary information; a verification / recovery step in which the control device verifies whether or not a volume configuration based on the backup image of the specific backup generation corresponding to the specific volume mapping information matches a volume configuration based on the current backup image of the specified volume, and if the result of the verification shows that both volume configurations match, verifies and recovers backup data based on the backup image of the specific backup generation; a summary information display step in which the control device displays the summary information when the backup image of the specific backup generation is selected from the backup images of the multiple generations; and the control device, which manages the plurality of volumes by dividing them into at least one group, extracts the summary information relating to an overview of at least one of the volumes included in the group in the summary information extraction step; the first storage device is configured to create a backup image of the predetermined volume from which data is read and written by an external device; the second storage device accumulates backup images of multiple generations created at different times for the predetermined volume in a data protection area that cannot be accessed from the external device; A data replication method comprising:

Images