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 suitably applicable to, for example, a data replication system related to a technique of restoring backup data after performing data verification.

Background Art

[0002] For example, as a technique for recovering a volume to a state before a cyber attack, there is a technique disclosed in Patent Document 1. In Patent Document 1, in a storage device, a plurality of generations of a volume are stored in a data protection area that cannot be accessed from the outside as a backup image, and a copy of one generation selected from the plurality of generations is stored in an access volume that can be accessed from the outside, and a technique for restoring backup data of the selected one generation is disclosed. In the technique described in Patent Document 1, it is assumed that the capacity of the volume is not expanded during system operation, particularly during the backup cycle.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the technique described in Patent Document 1, if the capacity of the volume is expanded during the backup cycle, thereafter, the 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 cannot be guaranteed, and even if data verification is performed on whether the two volume configurations match, the two volume configurations do not match, so there may be a case where backup data cannot be recovered.

[0005] The present invention has been made in consideration of the above points, and proposes a data replication system and a data replication method capable of verifying data and recovering backup data even when the volume capacity is expanded during the backup cycle.

Means for Solving the Problems

[0006] In order to solve such problems, in the present invention, a first storage device that creates a backup image of a predetermined volume in which data is read and written by an external device, and a plurality of generations of backup images created at different times with respect to the predetermined volume are stored in a data protection area that cannot be accessed from the external device. A second storage device, and summary information regarding the outline of the predetermined volume is extracted from volume mapping information regarding the configuration of the predetermined volume at the time when each of the plurality of generations of backup images is created, and a specific backup selected from among the plurality of generations of backup images based on the summary information. A control device that acquires specific volume mapping information of the predetermined volume corresponding to a generation, and the control device verifies whether a volume configuration based on the backup image of the specific generation corresponding to the specific volume mapping information matches a volume configuration based on the current backup image of the predetermined volume. As a result of the verification, when both volume configurations match, the backup data is verified and recovered based on the backup image of the specific generation.

[0007] In the present invention, a storage step in which a first storage device creates a backup image of a predetermined volume where data is read and written by an external device, an accumulation step in which a second storage device accumulates multiple generations of backup images created at different times for the predetermined volume in a data protection area inaccessible to the external device, a summary information extraction step in which a control device extracts summary information regarding the outline 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 acquisition step in which the control device acquires specific volume mapping information of the predetermined volume corresponding to a specific backup generation selected based on the summary information from among the multiple generations of backup images. The control device verifies whether a volume configuration based on the backup image of the specific generation corresponding to the specific volume mapping information matches a volume configuration based on the current backup image of the predetermined volume. As a result of this verification, if both volume configurations match, the backup data is verified and recovered based on the backup image of the specific generation.

Effect of the Invention

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

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 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Mode for Carrying Out the Invention

[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings. The examples are illustrative for explaining the present invention, and are appropriately omitted and simplified for the sake of clarity of explanation. The present invention can also be implemented in various other forms. Unless otherwise specified, each component may be in a single or plural number.

[0011] In the drawings, the positions, sizes, shapes, ranges, etc. of the respective components shown may not represent the actual positions, sizes, shapes, ranges, etc. in order to facilitate the understanding of the invention. For this reason, the present invention is not necessarily limited to the positions, sizes, shapes, ranges, etc. disclosed in the drawings.

[0012] As examples of various information, it may be described in expressions such as "table", "list", "queue", etc., but the various information may be represented by data structures other than these. For example, various information such as "XX table", "XX list", "XX queue" may also be referred to as "XX information". When explaining identification information, expressions such as "identification information", "identifier", "name", "ID", "number" are used, but these are mutually replaceable.

[0013] When there are a plurality of components having the same or similar functions, they may be described with the same reference numeral and different subscripts. Also, when it is not necessary to distinguish these plurality of components, the subscripts may be omitted in the description.

[0014] In an embodiment, the processing performed by executing a program may be described. Here, a computer executes a program by a processor (e.g., a CPU or a GPU), and performs the processing defined by the program while using a storage resource (e.g., a memory) and an interface device (e.g., a communication port), etc. Therefore, the subject of the processing performed by executing the program may be the processor. Similarly, the subject of the processing performed by executing the program may be a controller, a device, a system, a computer, or a node having a processor. The subject of the processing performed by executing the program only needs to be an arithmetic unit, and may include a dedicated circuit for performing a specific processing. Here, the dedicated circuit is, for example, an FPGA (Field Programmable Gate Array), an ASIC (Application Specific Integrated Circuit), a CPLD (Complex Programmable Logic Device), or the like.

[0015] The program may be installed in a computer from a program source. The program source may be, for example, a program distribution server or a storage medium readable by a computer. When the program source is a program distribution server, the program distribution server includes 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. Also, 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] Also, in the following description, a "host computer (host)" and a "computer system" are systems including one or more physical computers. The physical computer may be a general-purpose computer or a dedicated computer. The physical computer may function as a computer (e.g., called a host computer or a server system) that issues an I / O (Input / Output) request, or may function as a computer (e.g., a storage device) that performs data I / O in response to an I / O request.

[0017] Also, the computer system may be a distributed system composed of one or more (typically multiple) physical node devices. The physical node device is a physical computer.

[0018] Also, by a physical computer (e.g., a node device) executing predetermined software, SDx (Software Defined anything) may be constructed in the physical computer or a computer system including the physical computer. As the SDx, for example, SDS (Software Defined Storage) or SDDC (Software Defined Data Center) may be adopted.

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

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

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

[0022] In addition, 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 a configuration with a single computer (e.g., a node device) such as one or more RAID (Redundant Array of Independent (or Inexpensive) Disks) groups as at least a part of the PDEV section.

[0023] Also, in the following description, identification numbers are used as identification information for various objects, but other types of identification information (e.g., identifiers including letters and symbols) may be adopted instead of the identification numbers.

[0024] Hereinafter, embodiments will be described in detail with reference to the drawings. FIG. 1 is a block diagram showing an example of the overall configuration example of the data replication system in 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 said to be the first host, the second host, and the third host, respectively.

[0025] The primary mainframe 80 is connected via a network 101, which is, for example, a SAN (Storage Area Network), to a production storage device 40. The secondary mainframe 90, backup storage device 10, verification storage device 30, and open server 50 are connected to each other 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 data exchange with the production storage device 40 via the network 101. The primary mainframe 80 is equipped with control software 81 for controlling 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 data exchange with the backup storage device 10, verification storage device 30, and 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 is equipped with control software 91 for controlling 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 an 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 in order to store and read data from the production volume 41. The production volume 41 stores data exchanged with the host. The production storage device 40 is storage installed in the vicinity of the first host and has a 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 separated from the production storage device 40. The backup storage device 10 has a volume 13, a data area 14, a relay volume 15, and virtual volumes (not shown). The virtual volumes (not shown) are virtual volumes virtually created as secondary volumes of the production volume 41 by SI (ShadowImage).

[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 to the relay volume 15. The volume 13 and the 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 the production volume 41 as an example of a predetermined volume where data is read and written by an external device, and stores it in the data area 14.

[0033] In the backup storage device 10, for example, data of the production volume 41 composed of unit volumes finely divided into four is copied to the backup storage device 10. The copied data has a backup image created in the data area 14 by, for example, SI (ShadowImage). In the data area 14, a backup image is created according to the time point when the backup is acquired.

[0034] The data area 14 is composed of a storage area that cannot be accessed by an external device and can only be recognized by the storage controller of the backup storage device 10. For example, when the data area 14 is composed of a plurality of volumes, the volume ID required to access the data may not be provided externally.

[0035] The backup image is a backup image at different times of the production volume 41. To create a backup image, for example, a Thin Image that is evacuated to the data protection area 69 is used. However, any other implementation method may be adopted as long as it is a function to obtain the data constituting the backup image. Also, a backup function that can store the data constituting the backup image in another volume may be used. Hereinafter, the data constituted by the backup data at a predetermined 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 a plurality of generations of backup images created at different times with respect to the production volume 41 in a data protection area 69 that cannot be accessed by an external device. 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 "VB volume") 61, and a Verify-access-Volume (hereinafter referred to as "VA volume") 62. The export volume 12 stores the actual data of each generation of backup images.

[0037] The export volume 12 is mapped with a virtual volume (not shown) and external volume mapping information, serves as a storage destination for the data of the virtual volume (not shown), and stores a copy of the 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 forms a pair with the production volume 41 is created in the backup storage device 10. This virtual volume is used as an external source volume, and the production volume 41 of the production storage device 40 is used as an external destination volume, and the volume mapping information is registered in the management table volume 11.

[0039] A copy of the data is executed, for example, asynchronously from the production volume 41 to the export volume 12 via a virtual volume (not shown). This external volume mapping information is used, for example, in an external function realized by UVM (Universal Volume Manager) provided by Hitachi, Ltd. (registered trademark). The external function is, for example, a function that integrates a plurality of disk arrays of different models as if they were a single disk array by virtualization technology, connects an external storage device having a logical volume, and maps the logical volume, so that a plurality of disk arrays of different models can be treated 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 numbers attached to each backup image as described later, VOL information for access related to the configuration of the volume 13, association information between the copy number and the access volume, and access volume backup available time zone information. The management table volume 11 records meta information for each backup generation. The meta information includes, for example, information regarding the backup date and time and the association of so-called Snapshot pair information.

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

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

[0043] The VA volume 62 is associated with the virtual volume of the data protection area 35 of the verification storage device 30, for example, by UVM. Although the VA volume 62 is a single large-capacity volume, the virtual volume functions as, for example, four unit volumes obtained by dividing the single volume. The backup images of a specific generation stored in the VA volume 62 can be referred to as the backup images of a specific generation of 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] Here, in this embodiment, the physical data constituting the backup images of the data area 14 exists in the export volume 12 of the open storage device 60. The export volume 12 is associated with the volume 13 of the data area 14, for example, by UVM.

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

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

[0048] Note that since the data constituting the backup image of the volume 13 is stored in the export volume 12 of the open storage device 60, it is generally slower compared to access to the production volume 41.

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

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

[0051] In the data protection area 69, backup data created at each time point in the export volume 12 is obtained one by one, and backup images of multiple generations are accumulated by accumulating backup images of each generation obtained, for example, by acquiring TI (Thin Image). The data protection area 69 cannot be accessed from an external device. Details of the data protection area 69 will be described later.

[0052] In the mapping volume 12x, volume mapping information corresponding to each generation of backup images is stored.

[0053] The open server 50 is an example of a control device. It extracts summary information regarding the outline of the production volume 41 from the volume mapping information regarding the configuration of the production volume 41 at the time when multiple generations of backup images are each created, and also obtains specific volume mapping information (for example, as will be described later, the number of unit volumes of the production volume 41 has decreased to 2) of the production volume 41 corresponding to a specific backup generation selected based on the summary information from among the multiple generations of backup images.

[0054] The open server 50 acquires the volume mapping information of the volume to be backed up written to the relay volume 15 along with the backup, via the relay volume 15, and writes the volume mapping information to the mapping volume of the open storage device 60. In the open storage device 60, there are multiple generations of backup images, and a plurality of volume mapping information corresponding to each of the multiple generations of backup images is 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 as to be able to select a backup generation, and displays information that enables awareness of the volume configuration for each generation on the GUI, as will be described later.

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

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

[0058] In the present embodiment, as summary information, the open server 50 extracts at least one of the number of unit volumes constituting the production volume 41 and its total capacity from the 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.

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

[0060] The open server 50 controls the entire backup. The open server 50 manages, for example, which generations of backup images are being acquired. The open server 50 includes file conversion software 51 as software.

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

[0062] Examples of the above-mentioned information to be transmitted include, in addition to backup schedules such as the start / end of backup, volume mapping information regarding the configuration of each current and previous volume.

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

[0064] The storage management software 53 controls the open side, that is, the open server 50 and the open storage device 60. The storage management software 53 controls backup and data verification (and restore), and controls, for example, the start of backup. The backup schedule is set in advance. The storage management software 53 stores the acquired information related to the 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, and verifies whether the volume configuration based on a 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. As a result of the verification, if both volume configurations match, the backup data is verified and recovered based on the backup image of the specific generation. This will be specifically described below.

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

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

[0068] The open server 50 verifies the data 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. Note that the physical data of the backup image that is the target of data verification is stored in the VA volume 62.

[0069] When the open server 50 has the same volume configuration, it copies the backup image of a specific generation of the virtual volume by, for example, the SI (ShadowImage) described above and restores it as backup data. On the other hand, when the volume configurations are not the same, it determines that the data authentication is an error and, for example, does not perform the restoration of the backup data or notifies to that effect.

[0070] Note that in this embodiment, in the open storage device 60, as a result of data verification, when the two volume configurations do not match, for example, it notifies the copy numbers of the unit volumes where the volume configurations do not match, and it may also be configured to allow selection of only some unit volumes where the volume configurations match.

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

[0072] In FIG. 2, the backup storage device 10 is described as an example, but other storage devices have the same configuration. The backup storage device 10 includes a plurality (or one) of physical storage devices PDEV171 and a storage controller 161 connected to the PDEV171.

[0073] The storage controller 161 includes an I / F11a, an I / F11b, an I / F163, a memory 162, and a processor 161a connected thereto. The I / F11a, the I / F11b, and the I / F163 are an example 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] I / F11a is a communication interface device that mediates data exchange between the first host or an external storage device and the storage controller 161. To I / F11a, the first host or an external storage device etc. are connected via an FC (Fibre Channel) network.

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

[0076] I / F11b is a communication interface device that mediates data exchange between the second host and the storage controller 161. To I / F11b, the second host is connected 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] I / F163 is a communication interface device that mediates data exchange between a plurality of PDEV171 and the storage controller 161. A plurality of PDEV171 are connected to I / F163.

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

[0080] FIG. 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 a 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, in the case of a backup whose backup acquisition date and time was acquired at 9:00:00 on January 1, 2022, the volume mapping information is as shown in the following example. Specifically, for the volume ID "101" of the export volume 12 of the open storage device 60, the volume IDs "1001", "1002", "1003", and "1004" of the volume 13 of the backup storage device 10 correspond.

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

[0084] The storage ID is an ID for identifying multiple storage devices from each other. The volume ID is an ID for distinguishing between volumes. The number of volumes on the mainframe side indicates the number of volumes on the mainframe side (the "mainframe volume" shown in the figure), and the total capacity indicates the total value of the capacities of all the volumes on the mainframe side.

[0085] For example, for the volume ID "101" with the storage ID of the open storage device 60 being "800000020000", the backup acquisition dates and times are "January 1, 2022, 9:00:00", "January 3, 2022, 9:00:00", and "January 5, 2022, 9:00:00". In the backups acquired at these backup acquisition dates and times, for example, the number of volumes on the mainframe side is 2000, 4000, and 6000 respectively, and the total capacity is shown to be 2 [TB], 4 [TB], and 6 [TB].

[0086] In the present embodiment, the following correspondence relationship exists. That is, for the volume ID "101" of the export volume 12(12a) of the open storage device 60, the volume IDs "1001", "1002", "1003", and "1004" of the volume 13(13a) in the backup storage device 10 correspond. For the volume ID "102" of the export volume 12(12b) of the open storage device 60, the volume IDs "2001", "2002", "2003", and "2004" of the volume 13(13b) in the backup storage device 10 correspond. For the volume ID "103" of the export volume 12(12a) of the open storage device 60, the volume IDs "3001", "3002", "3003", and "3004" of the volume 13(13c) in the backup storage device 10 correspond.

[0087] FIG. 5 is a diagram showing an example of data verification when the capacity of a volume is expanded during system operation. In the illustrated example, it shows an example when the capacity of the production volume 41, which was composed of 2 unit volumes, was expanded to 4 unit volumes during the backup cycle during system operation.

[0088] In the export volume 12 of the open storage device 60, backup images acquired at each point in time are stored. In the open storage device 60, backup images acquired at different points in time continue to be stored in the data protection area 69. In the data protection area 69, for example, backup images 14a to 14d of multiple generations are stored. In the illustrated example, as an example, four generations of backup images 14a to 14d are stored so that they become the latest to the oldest from left to right.

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

[0090] For example, when creating the backup images 14a, 14b, 14c, and 14d, the storage controller of the backup storage device 10 assigns a copy number representing the above-described backup generation to each of the backup images 14a, 14b, 14c, and 14d according to an instruction from a host, for example, and manages it 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 the present embodiment, it is collectively referred to as a "backup generation" or simply a "generation".

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

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

[0093] The data replication method includes a storage 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 where data is read and written by an external device, an accumulation step in which an open storage device 60 as an example of a second storage device accumulates multiple generations of backup images created at different times with respect to the production volume 41 in a data protection area 69 that cannot be accessed from an external device, a summary information extraction step in which an open server 50 as an example of a control device 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, 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 based on the summary information from among the multiple generations of backup images, and a data verification and recovery step in which an open server 50 as an example of a control device verifies whether the volume configuration based on a specific generation of backup image corresponding to the specific volume mapping information matches the volume configuration based on the current backup image of the volume 13 that reflects the current production volume 41, and if the verification result shows that both volume configurations match, verifies and recovers the backup data based on the specific generation of backup image. The following will be described specifically.

[0094] FIG. 6 is a flowchart showing an example of the procedure for capacity expansion processing. On the mainframe side, when the capacity of a volume is expanded, the volume configuration is updated using the external function described above. On the open side, the capacity of the volume is expanded and the definition file regarding the volume is updated.

[0095] In step S1, in the production storage device 40, for example, during the backup cycle, for the production volume 41 composed of two unit volumes, for example, two additional unit volumes are added. In step S2, the backup storage device 10 sets the SI (Shadow Image) pair of the volume. As a result, in the backup storage device 10, the data of 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 of the management table volume 11 according to the change in the above-described volume configuration.

[0097] In step S4, two unit volumes are added. When unit volumes are added, the following step S5 is executed, while when unit volumes are not added, the execution of step S5 is omitted.

[0098] In step S5, the open storage device 60 sets the TI (Thin Image) pair of the volume. 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] FIG. 7 is a flowchart showing an example of the procedure of the volume mapping information storage process. The volume mapping information storage process is a process of acquiring volume configuration information regarding each volume, and is executed, for example, periodically. As the execution timing, for example, the time of backup is assumed.

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

[0101] In step S11, the secondary main frame 90 checks the volume mapping information. In step S12, the secondary main frame 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 secondary main frame 90 delivers the volume mapping information to the open server 50, the secondary main frame 90 automatically creates the hash value, while when the open server 50 delivers the volume mapping information to the secondary main frame 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 main frame 90 to that effect and ends abnormally (step S15).

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

[0105] If the definition file and the volume mapping information are not consistent 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 are consistent 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 it in the management table of the management table volume 11 (hereinafter also referred to as "ledger"). Here, the volume mapping information actually includes many types of configuration information, and it may not be necessary to refer to all types of configuration information during data verification. Therefore, in this embodiment, summary information such as the number (and total capacity) of volumes 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 the 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, for example, a copy of the mapping volume 12x in the data protection area 69 of the verification storage device 30.

[0107] FIG. 8 is a flowchart showing an example of the procedure of data verification and recovery processing on the open side. The data verification and recovery processing enables verification work on the mainframe side by allocating the data to be verified to a volume using verification content on the open side.

[0108] In step S21, on the open server 50, for example, a user activates the verification content. The verification content is, for example, the storage management software 53 of the open server 50 described above. Using the verification content in this way enables data verification work on the mainframe side by allocating the data to be verified to a volume using the verification content on the open 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 based on the meta information for each backup generation, displays an operation screen (hereinafter referred to as the "backup generation selection screen") for the backup generation that can be the target of data verification. The user selects the backup generation (backup acquisition date and time) to be the target of data verification on the backup generation selection screen. 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 as an example of the verification content displays a tabular selection screen 200 including summary information as shown in FIG. 10 on the backup generation selection screen described above. Specifically, the open server 50 displays backup images of multiple generations, and on top of that, a selection screen 200 for selecting any one of the backup images of multiple generations is displayed in front.

[0111] That is, when a backup image of a specific generation is selected from among the backup images of multiple generations by the open server 50, summary information is being displayed.

[0112] In step S23, on the open server 50, the user refers to the backup generation selection screen 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 allocates the backup generation of the mapping volume 12x corresponding to the backup generation to be the target of data verification to the volume 62x as the access volume. The volume to be the target of data verification is specified based on the volume mapping information from the mainframe side. In this embodiment, at the stage when the user selects a backup generation, the backup generation to be the target of data verification is known.

[0114] In step S25, the open server 50 mounts the volume 62x to 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 selected as the data verification target 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] Figure 9 is a flowchart showing an example of the procedure of data verification and recovery processing on the mainframe side. In step S31, the secondary mainframe 90 acquires the volume mapping information from the relay volume 15 as the configuration information regarding the backup generation to be verified.

[0117] In step S32, the secondary mainframe 90 collates the acquired configuration information with the configuration information of the target volume. As a result of the data verification in step S32, when both configuration information match, the secondary mainframe 90 executes step S34, while when both 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 by the verification storage device 30. On the other hand, in step S36, the secondary mainframe 90 executes the processing at the time of mismatch. In this processing at the time of mismatch, for example, it notifies the outside that both configuration information do not match.

[0118] In this processing at the time of mismatch, the verification storage device 30 (or the secondary mainframe 90) displays the non-matching configuration on a display unit (not shown) when both volume configurations do not match.

[0119] The data replication system according to this embodiment creates a backup image of a production volume 41 as an example of a predetermined volume where data is read and written by an external device, and stores it in a backup storage device 10 as an example of a first storage device. The backup storage device 10 stores the backup image in a data area 14. The system also includes an open storage device 60 as an example of a second storage device that accumulates multiple generations of backup images created at different times with respect to the production volume 41 in a data protection area 69 that cannot be accessed from an external device. An open server 50, as an example of a control device, extracts summary information regarding the outline of a predetermined volume 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 acquires specific volume mapping information of the production volume 41 corresponding to a specific backup generation selected based on the summary information from among the multiple generations of backup images. The open server 50 verifies whether the volume configuration based on the backup image of a specific generation corresponding to the specific volume mapping information matches the volume configuration based on the current backup image of the production volume 41. As a result of this verification, if both volume configurations match, the backup data is verified and recovered based on the backup image of the specific generation. Note that the open server 50 may include some functions of the secondary mainframe 90.

[0120] The data replication method of the data replication system according to this embodiment includes: a storage 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 where data is read and written by an external device and stores it in a data area 14; an accumulation step in which an open storage device 60 as an example of a second storage device accumulates multiple generations of backup images created at different times with respect to the production volume 41 in a data protection area 69 that cannot be accessed by an external device; a summary information extraction step in which an open server 50 as an example of a control device 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; 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 based on the summary information from among the multiple generations of backup images; and a data verification and recovery step in which the open server 50 verifies whether the volume configuration based on the backup image of a 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 two volume configurations match as a result of the verification, verifies and recovers the 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 verified and recovered after verification. Therefore, it becomes possible to expand the capacity of the production volume 41 during system operation, improving the flexibility during system construction. For example, the user can calculate the total capacity of the backup data in accordance with the requirements at the time of system introduction, start operation with a minimum volume configuration, and expand the total capacity of the production volume 41 during system 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 its total capacity from the volume mapping information regarding the configuration of the production volume 41 at the time when backup images of multiple generations are created respectively. By doing so, it becomes easier for the user to select a backup image of a specific generation from among the backup images of multiple generations with reference to summary information such as the number of unit volumes that can be easily grasped.

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

[0124] In this embodiment, when a backup image of a specific generation is selected from among the backup images of multiple generations, the open server 50 displays summary information, for example, overlaid on the above-described selection screen. By doing so, it becomes easier for the user to select a backup image of a specific generation from among the backup images of multiple generations with reference to the summary information.

[0125] The data replication system according to this embodiment includes a display unit (not shown) that displays the inconsistent configuration when the two volume configurations do not match in the above-described inconsistency processing. By doing so, the user can reselect the backup image generation in consideration of the inconsistent configuration.

[0126] (2) Second Embodiment The data replication system according to the second embodiment has substantially the same configuration and operation as the data replication system according to the first embodiment. Therefore, the description of the same configuration and operation is omitted, and the following description will focus on the differences. In the second embodiment, different from the first embodiment, the concept of grouping is adopted for volumes.

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

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

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

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

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

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

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

[0134] In the open storage device 60, the third VA volume 62c with the volume ID "303" corresponds to the virtual volume 32c in the verification storage device 30 that includes the unit volumes with the volume IDs "1001", "1002", "1003", and "1004" by the external function described above. Note that 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, combined mapping information created by combining the following group mapping information with the volume mapping information is used to perform the grouping described above.

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

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

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

[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 main frame storage ID for each backup acquisition date and time. The main frame storage ID indicates the volume ID of volume 13 of the backup storage device 10 on the main frame side.

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

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

[0142] In the illustrated example, at the backup acquisition date and time "January 1, 2022, 09:00:00", as described above, in Group A, the unit volumes of Volume 13 with volume IDs "1001", "1002", and "2001" are included, and the export volumes 12 with volume IDs "101" and "102" are included. In Group B, the unit volumes of Volume 13 with volume IDs "1003", "1004", "2002", "2003", "2004", and "3004" are included, and the export volumes 12 with volume IDs "101", "102", and "103" are included. In Group C, the unit volumes of Volume 13 with volume IDs "3001", "3002", and "3003" are included, and the export volume 12 with volume ID "103" is included.

[0143] In the present embodiment, the production volume 41 is composed of a plurality of volumes. The open server 50 manages the plurality of volumes by dividing them into at least one group. The open server 50 extracts summary information regarding the outline of at least one volume included in the group, and acquires specific volume mapping information of the production volume 41 corresponding to a specific backup generation selected based on the summary information from among a plurality of generations of backup images. When a backup image of a specific generation is selected from among the plurality of generations of backup images, the summary information is displayed as described later.

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

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

[0146] Steps S12 to S19 are substantially the same as those in the first embodiment. However, in step S17, the open server 50 extracts summary information regarding the outline 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 stores the volume mapping information and the group mapping information in the mapping volume 12x in their respective formats without combining them at this stage. The combination of the volume mapping and the group mapping is performed on the open side (at the open server 50) during data verification.

[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. Since steps S21, S22, S23, S24, S25, and S26 are the same as those in the first embodiment, the description will be omitted unless particularly mentioned.

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

[0149] In step S22A, the open server 50 (or both the mainframe side and the open server 50) combines the volumes to be data-verified in group units based on the volume mapping information. Specifically, the secondary mainframe 90 combines the group mapping information and the volume mapping information to generate the 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 the 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 checkbox 201a, a group label 201b of the group corresponding to the specific backup generation, a detailed description 201c about the group, the number 201d of export volumes, the number 201e of volumes on the mainframe side, and its total capacity 201f.

[0152] In step S23A, on the open server 50, the user selects the group to be data-verified. Specifically, the user inputs a check mark in the checkbox 201a corresponding to the desired group on the group selection screen 201 to select the desired group. At this time, on the group selection screen 201, at least one of, for example, the number 201e of volumes on the mainframe side and its total capacity 201f is displayed as summary information obtained from the management table (ledger). In particular, the user determines which group to select 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 composed of a plurality of volumes. The open server 50 manages the plurality of volumes by dividing them into at least one group. The open server 50 extracts summary information regarding the outline of at least one volume included in the group, and acquires specific volume mapping information of the production volume 41 corresponding to a specific backup generation selected based on the summary information from among a plurality of generations of backup images, and displays the summary information as will be described later when a backup image of a specific generation is selected from among the plurality of generations of backup images. By doing so, by dividing the relevant volumes among the plurality of volumes constituting the production volume 41 into groups, the user can recover the backup data from the backup image of the specific generation while referring to the summary information of the relevant volumes.

[0155] Note that the present invention is not limited to the above-described embodiments, and includes various modifications and equivalent configurations within the scope of the appended claims. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and the present invention is not necessarily limited to those having all the configurations described. Also, each element described in parallel in this embodiment may be in a mode in which at least one of the elements is connected in series to another element.

Industrial Applicability

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

Explanation of Signs

[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 in which data is read and written by an external device and stores it in a data area; A second storage device that accumulates multiple generations of backup images created at different times with respect to the predetermined volume in a data protection area that cannot be accessed by the external device; A control device that extracts summary information regarding the outline 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 acquires specific volume mapping information of the predetermined volume corresponding to a specific backup generation selected based on the summary information from among the multiple generations of backup images; and The control device is configured to: Verify whether 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 predetermined volume. As a result of the verification, if both volume configurations match, verify and recover the backup data based on the backup image of the specific generation A data replication system characterized by the above.

2. The control device, as the summary information, Extracts at least one of the number of unit volumes constituting the predetermined volume and the total capacity of the predetermined volume from the volume mapping information regarding the configuration of the predetermined volume at the time when each of the multiple generations of backup images was created The data replication system according to claim 1, characterized by the above.

3. The control device is configured to: Display the multiple generations of backup images and display a selection screen for selecting any one of the multiple generations of backup images The data replication system according to claim 1, characterized by the above.

4. The control device is configured to: Display the summary information when the backup image of the specific generation is selected from among the multiple generations of backup images The data replication system according to claim 3, characterized by the above.

5. When the two volume configurations do not match, it includes a display unit that displays the non-matching configuration The data replication system according to claim 1, characterized by the above.

6. The predetermined volume is composed of a plurality of volumes, The control device, manages by dividing at least one group from the plurality of volumes, extracts the summary information regarding the outline of at least one of the volumes included in the group, and acquires the specific volume mapping information of the predetermined volume corresponding to a specific backup generation selected based on the summary information from among the backup images of multiple generations, when the backup image of the specific generation is selected from among the backup images of the multiple generations, displays the summary information The data replication system according to claim 1, characterized in that.

7. A storage step in which a first storage device creates a backup image of a predetermined volume in which data is read and written by an external device, An accumulation step in which a second storage device accumulates backup images of multiple generations created at different times with respect to the predetermined volume in a data protection area that cannot be accessed from the external device, A summary information extraction step in which a control device extracts summary information regarding the outline of the predetermined volume from the volume mapping information regarding the configuration of the predetermined volume at the time when each of the backup images of multiple generations is created, An acquisition step in which the control device acquires the specific volume mapping information of the predetermined volume corresponding to a specific backup generation selected based on the summary information from among the backup images of multiple generations, The 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 the predetermined volume. As a result of the verification, if both volume configurations match, the backup data is verified and recovered based on the backup image of the specific generation The data replication method characterized by the above.

Images