Data management system and data management method

A data management system for backing up data in a first environment to a second environment includes: backup management information in which source data, backup data, a backup method, and data backed up using the backup method are associated; and a secondary usage data copy unit serving as a secondary usage processing unit that receives a usage request for the backup data stored in the second environment, wherein the secondary usage processing unit refers to the backup management information, specifies the backup data required for processing the usage request, specifies the backup method for the backup data, restores the backup data on the basis of the specified backup method, and enables processing of the usage request.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a data management system and a data management method.

2. Description of the Related Art

In recent years, hybrid cloud and multi-cloud data management, which combine on-premises with private cloud or public cloud data management and the like, have become widespread. For example, U.S. Pat. No. 10,127,117 B2 discloses a technology for backing up a volume stored in on-premises block storage to low-cost public cloud object storage.

In addition, there are cases where there is a desire to analyze data, which has been generated on premises, on a public cloud computing infrastructure. As described above, using data which has been generated in a certain environment and backed up in another environment, at the backup destination, is referred to as the secondary usage of data. In a case where data has been backed up to the cloud by using technology like that in U.S. Pat. No. 10,127,117 B2, by duplicating the data from the cloud backup to the computing infrastructure, it is considered possible to quickly utilize the data without network communication occurring between on-premises and the cloud.

In order to secondarily use the data generated by the system across a plurality of sites as described above, it is necessary to ascertain at which site the data is generated, as well as where, and by what method the data is managed. JP 2022-108398 A discloses a technology for quickly ascertaining the data usage status of a storage device in a hybrid cloud configuration.

SUMMARY OF THE INVENTION

In the technology disclosed in JP 2022-108398 A, the relationship between the storage volume and the site where the backup of the storage volume is stored can be tracked, but the details of the method of acquiring the backup are not known. When the backup method is different, the processing to restore a backup to a cloud analysis infrastructure is also different, and thus, in JP 2022-108398 A, the processing to restore the backup to the cloud analysis infrastructure cannot be specified. Therefore, in a configuration in which on-premises data is backed up to the cloud by using a plurality of backup methods, data secondary usage cannot be realized.

In order to solve the above problems, one representative example of a data management system of the present invention is a data management system for backing up data in a first environment to a second environment, the data management system including: backup management information in which source data, backup data, and a backup method are associated; and a secondary usage processing unit that receives a usage request for the backup data stored in the second environment, wherein the secondary usage processing unit refers to the backup management information, specifies backup data required for processing the usage request, specifies a backup method for the backup data, restores the backup data on the basis of the specified backup method, and enables processing of the usage request.

In addition, one representative data management method of the present invention is characterized by including steps in which a data management system for backing up data in a first environment to a second environment: generates backup management information by associating source data, backup data, and a backup method; receives a usage request for the backup data stored in the second environment; and specifies backup data required for processing the usage request by referring to the backup management information, specifies a backup method for the backup data, restores the backup data on the basis of the specified backup method, and enables processing of the usage request.

With the present invention, secondary usage of data in which backups are utilized effectively can be realized.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

First Embodiment

FIG.1is a diagram illustrating an outline of a configuration and processing of a computer system100according to a first embodiment. The computer system100illustrated inFIG.1includes a cloud-based management server110, an on-premises environment120(first site), and a cloud environment130(second site). The cloud-based management server110, the on-premises environment120, and the cloud environment130are communicably connected by, for example, a network N1.

The cloud-based management server110includes backup management information111, table-volume mapping information112, a backup execution unit113, and a secondary usage data copy unit114. Note that the cloud-based management server110also includes constituent elements other than the foregoing, and all of the constituent elements will be described below with referenceFIG.4.

The on-premises environment120includes a data management server121, a backup server122, a DB server123, and block storage124. The data management server121, the backup server122, the DB server123, and the block storage124are communicably connected to each other via a network such as a LAN (Local Area Network N2in the on-premises environment120, for example. The DB server123stores the data of a DB123ain a block volume124aprovided by the block storage124, for example.

The cloud environment130includes a backup server131, a DB server132, and block storage133. The backup server131, the DB server132, and the block storage133are communicably connected to each other via a network such as a LAN N3in the cloud environment130, for example. The DB132aof the DB server132is, for example, connected to a block volume133aprovided by the block storage133, and the data is made available.

FIG.1illustrates steps S1and S2as a processing procedure outlining the overall processing according to the first embodiment.

In step S1, the backup execution unit113transfers a backup of data of the on-premises environment120to the cloud environment130according to user input information. When the backup processing is complete, the backup execution unit stores the backup information in the backup management information111. In step S1, for example, the volume124ais stored as a plurality of backups (a backup b1, a backup b2, and a backup b3) in the cloud environment130by using a plurality of backup methods. For example, the backup server122is capable of acquiring the backup b1to the object storage of the cloud environment130for the data of the DB123aand the volume124a.Furthermore, by using the backup function, the block storage124is capable of acquiring a backup of a snapshot124bof the volume124aas the backup b2to the object storage in the cloud environment130. In addition, by using the remote copy function, the block storage124is capable of acquiring the backup b3by copying the snapshot124bof the volume124ato the block volume of the block storage133in the cloud environment130.

In step S2, the secondary usage data copy unit114restores a backup (one backup from among the backup b1, the backup b2, and the backup b3) of the cloud environment130to the DB132aor the volume133aaccording to user input information.

FIG.2is a diagram illustrating a hardware configuration example of the computer system100according to the first embodiment.

The on-premises environment120comprises a switch200for connecting a network N2within the on-premises environment120to the network N1outside the on-premises environment120. Note that the switch200is not necessarily required, and the network N2in the on-premises environment120and the network N1outside the on-premises environment120may be the same network. In addition, these networks N1and N2may have a redundant configuration. Furthermore, these networks N1and N2may be any communication means such as Ethernet (registered trademark), InfiniBand, or wireless communication. In addition, inFIG.2, there is a fixed number of the data management server121, the backup server122, the DB server123, and the block storage124. However, in the first embodiment, the number of the data management server121, the backup server122, the DB server123, and the block storage124is not necessarily fixed, and may be one or more.

The data management server121includes a CPU202, which serves as an example of a processor, a memory203serving as a main storage device, a disk device204serving as a secondary storage device, and one or more of an NW/IF205. The CPU202, the memory203, the disk device204, and the NW/IF205are connected via a bus201.

The CPU202executes various processing by reading programs stored on the disk device204into the memory203and executing the programs. The CPU202transmits and receives data to and from other devices (the backup server122, DB server123, and block storage124) connected by the network N2via the bus201and the NW/IF205.

The backup server122includes the CPU202, the memory203, the disk device204, and the NW/IF205. The CPU202, the memory203, the disk device204, and the NW/IF205are connected via a bus201.

The DB server123includes the CPU202, the memory203, the disk device204, and the NW/IF205. The CPU202, the memory203, the disk device204, and the NW/IF205are connected via a bus201.

The block storage124includes the CPU202, the memory203, the disk device204, and the NW/IF205. The CPU202, the memory203, the disk device204, and the NW/IF205are connected via a bus201.

FIG.3is a logical configuration diagram of the computer system100according to the first embodiment.

The data management server121stores a data management program300. When executed by the CPU202of the data management server121, the data management program300receives and manages the catalog information of the DB server.

The backup server122stores a backup utility301. When executed by the CPU202of the backup server122, the backup utility301backs up, for example, the DB123aof the DB server123and the block volume124aof the block storage124in which the data of the DB123ais stored, to the object storage of the cloud environment130. In the following description, the backup server122and the backup utility301are of one type, but there may be two or more different types of backup servers and backup utilities. In this case, the corresponding backup server and the backup utility also need to be prepared in the cloud environment130.

The DB server123stores an RDBMS (Relational Database Management System)302. When the RDBMS302is executed by the CPU202of the DB server123, for example, an IO of data is issued to the DB123a,and as a result, an IO operation is performed on the block volume124aconnected to the DB123a,and the data is stored. In the following description, the program stored in the DB server123is referred to as the RDBMS302, but is not necessarily an RDBMS, and may be software for another database such as a NoSQL database.

The block storage124stores a backup processing program303. When executed by the CPU202of the block storage124, the backup processing program303performs a backup by, for example, acquiring the snapshot124bof the block volume124a,and copying the snapshot124bto the block volume133aof the block storage133in the cloud environment130. After the snapshot124bof the block volume124ais acquired, the snapshot124bmay be converted into an object by using a function of the backup processing program303, and the object may be backed up to the object storage of the cloud environment130. In the following description, the backup methods by using the storage function are the aforementioned two methods, but other backup methods may also be used as long as the methods are methods of backing up to the cloud environment130.

The backup server131in the cloud environment130stores a backup utility304. When executed by the backup server131, the backup utility304executes, for example, processing to restore the backup b1of the cloud environment130backed up by the backup server122of the on-premises environment120.

The DB server132in the cloud environment130stores an RDBMS (Relational Database Management System)305. When executed by the DB server132, the RDBMS305issues, for example, an IO of data to the DB132a,and performs an IO operation on the block volume133aconnected to the DB132a.

The block storage133in the cloud environment130stores a backup processing program306. When executed by the block storage133, the backup processing program306acquires, for example, a snapshot of the backup b3which is a block volume backed up by the block storage124of the on-premises environment120. It is also possible to execute restore processing to the block volume from the object stored in the backup b2backed up by the block storage124of the on-premises environment120.

FIG.4is a diagram illustrating information and programs held on the cloud-based management server110. The cloud-based management server110stores backup management information111, table-volume mapping information112, volume management information115, a backup execution unit113, a secondary usage data copy unit114, and a secondary usage catalog creation unit116.

The backup management information111is a table that manages information relating to backups of the configuration block storage124and133and the DB servers123and132in the on-premises environment120and the cloud environment130. Details of the backup management information111will be described below with reference toFIG.7illustrating a specific example.

The table-volume mapping information112is a table that manages, for example, a relationship between a DB table included in the DB123aon the DB server123of the on-premises environment120and the volume124ain the block storage124in which information of the DB123ais stored. Details of the table-volume mapping information112will be described below with reference toFIG.5in which a specific example is shown.

The volume management information115is a table that manages information relating to block volumes stored in the block storage124and133configured in the on-premises environment120and the cloud environment130. Details of the volume management information115will be described below with reference toFIG.6in which a specific example is shown.

The backup execution unit113is a program that communicates with the block storage124of the on-premises environment120, the backup server122, and the block storage133in the cloud environment130, instructs the block storage124to perform backups, instructs the backup server122to perform backups, and stores information relating to the backups in the backup management information111as a result of processing.

The secondary usage catalog creation unit116is a program that communicates with the data management server121of the on-premises environment120and that creates a secondary usage data catalog by using the DB table-volume mapping information112, the volume management information115, and the backup management information111. The secondary usage data catalog indicates target candidates for secondary usage requests. By presenting this secondary usage data catalog, the user is able to select which data is for secondary usage and make usage requests. That is, the secondary usage catalog creation unit116functions as a candidate presentation unit that presents data that is a target candidate for a usage request. Details of the secondary usage data catalog creation processing will be described below inFIG.8with reference to a specific example of a flowchart.

The secondary usage data copy unit114is a program for restoring backup data to the DB server132and the block storage133in the cloud environment130according to items of a secondary usage catalog1000which are selected by the user. That is, the secondary usage data copy unit114functions as a secondary usage processing unit that receives and processes a usage request for the backup data.

FIG.5is a diagram illustrating an example of the DB table-volume mapping information112. As illustrated inFIG.5, the DB table-volume mapping information112manages a DB table501, which is a value for identifying a DB table included in the DB server123of the on-premises environment120, a DB ID502, which is a value for identifying a DB in which the DB table is stored, a volume ID503, which is a value for identifying a storage volume in which the DB table is stored, and a storage ID504, which is a value for identifying storage in which the storage volume is stored. The request for secondary usage is made by designating a table. By referring to the DB table-volume mapping information112, in a case where a table is designated, it is possible to determine which volume in which storage is to be copied.

FIG.6is a diagram illustrating an example of the volume management information115. As illustrated inFIG.6, the volume management information115manages a volume ID601, which is a value for identifying a volume stored in the block storage124of the on-premises environment120, a backup ID602, which is a value for identifying a backup stored to the cloud environment130as a backup of a volume stored in the block storage124of the on-premises environment120, a volume size603, which is a value for identifying the capacity of a volume stored in the block storage124of the on-premises environment120, and a storage ID604, which is a value for identifying storage in which the volume is stored. By referring to the volume management information115, it is possible to check whether a backup of the volume to be copied exists.

FIG.7is a diagram illustrating an example of the backup management information111. As illustrated inFIG.7, the backup management information111manages a backup ID701, which is a value for identifying a backup stored in the cloud environment130, a backup method702, which is a value for identifying the method with which the backup stored in the cloud environment130was acquired, a source volume ID703, which is a value for identifying a volume from which the backup was acquired, a source storage ID704, which is a value for identifying storage in which the volume from which the backup was acquired is stored, and a last update date and time705, which is a value for identifying the last time the backup was acquired. Here, the backup method702need not be limited to the method inFIG.7(backup to object storage using storage function, backup using backup software, copy to block volume using storage function), and may hold information on another backup method. By referring to the backup management information111, the backup method can be specified in a case where a backup of the volume to be copied exists.

FIG.8is a diagram illustrating a flowchart of secondary usage catalog creation processing800according to the first embodiment.

According toFIG.8, first, the secondary usage catalog creation unit116refers to the catalog information of the DB stored in the data management server121of the on-premises environment120and acquires a list of DB table information (step S801).

Next, the secondary usage catalog creation unit116presents DB catalog information including a list of DB tables to the user, and receives a request to create a catalog for the secondary usage of data from the user (step S802).

Next, the secondary usage catalog creation unit116refers to the DB table-volume mapping information112, and checks whether or not a DB table selected by the user already exists in the DB table-volume mapping information112(step S803). Here, in a case where the DB table selected by the user already exists in the DB table-volume mapping information112, the processing advances to step S807(step S804). On the other hand, in a case where the DB table selected by the user does not exist in the DB table-volume mapping information112, in order to acquire information relating to the DB table selected by the user and the volume in which the DB table is stored and register the information in the DB table-volume mapping information112, the processing advances to step S805(step S804).

In step S805, the secondary usage catalog creation unit116executes DB table-volume mapping processing to acquire information relating to the DB table selected by the user and the storage volume in which the DB table is stored. Details of the DB table-volume mapping processing will be described below with reference toFIG.9.

In step S806, the secondary usage catalog creation unit116updates the DB table-volume mapping information112by registering the information relating to the DB table and the volume obtained as a result of step S805in the DB table-volume mapping information112.

In step S807, the secondary usage catalog creation unit116refers to the volume management information115to check whether there is a backup in the storage volume in which the DB table is stored. In a case where a backup exists in the storage volume in which the DB table is stored, the processing advances to step S809(step S808). On the other hand, when there is no backup in the storage volume in which the DB table is stored, the processing advances to step S810(step S808).

In step S809, the secondary usage catalog creation unit116refers to the backup management information111to acquire, for the backup checked in step S807, information on each backup generation (the last update date and time705) and the backup method702.

In step S810, the secondary usage catalog creation unit116presents the secondary usage catalog to the user by using the information on the storage volume in which the DB table is stored and the storage volume backup. A specific example of the secondary usage catalog will be described below with reference toFIG.10.

FIG.9is a diagram illustrating a flowchart of DB table-volume mapping processing900.

In step S901, the secondary usage catalog creation unit116executes processing to specify a path corresponding to the DB table.

In step S902, the secondary usage catalog creation unit116executes processing to specify an FS (file system) corresponding to the path. In step S903, the secondary usage catalog creation unit116executes processing to specify a logical volume corresponding to the FS.

In step S904, the secondary usage catalog creation unit116executes processing to specify a volume group corresponding to the logical volume.

In step S905, the secondary usage catalog creation unit116executes processing to specify a physical volume corresponding to the volume group.

In step S906, the secondary usage catalog creation unit116executes processing to specify correspondence of a block volume corresponding to the physical volume.

FIG.10is a diagram illustrating an example of a secondary usage catalog selection screen.

The secondary usage catalog1000is a selection screen that is created by the cloud-based management server110on the basis of the DB table-volume mapping information112, the backup management information111, and the volume management information115and that is displayed on the cloud-based management server. The secondary usage catalog1000includes an input field1001for inputting a search condition and an input field1002for selecting data for secondary usage.

A search condition can be arbitrarily inputted to the input field1001.

The input field1002for selecting data for secondary usage displays a table name1003, which is information for identifying a DB table name of a secondary usage target acquired in the secondary usage catalog creation processing800, a DB name1004for identifying a DB in which the DB table is stored, a storage ID1005for identifying a storage device in which data of the DB is stored, a data location1006for identifying information on a site in which the storage in which the data of the DB is stored exists, and a last update date1007for identifying the generation of the data.

The user is able to select, from the input field1002, and display at least one piece of data.

A confirm button1008is a button for receiving an instruction to transmit the information inputted to the input field1002to the secondary usage data copy unit114. When the confirm button1008is pressed, the secondary usage data copy unit114of the cloud-based management server110starts copy processing based on the information of1003to1007. Details of the copy processing will be described below inFIG.11with reference to a specific example.

FIG.11is a diagram illustrating a flowchart of secondary usage service execution processing1100.

According toFIG.11, the secondary usage data copy unit114first receives a data copy request which the user inputs upon referring to the secondary usage catalog1000(step S1101). Here, the secondary usage catalog1000is information created by the secondary usage catalog creation processing800.

Next, in step S1102, the secondary usage data copy unit114refers to the selected information of the secondary usage catalog1000and checks whether the secondary usage target is the latest on-premises data. For example, in the secondary usage catalog1000, in a case where the value of the location1006of the data of the row inputted to the input field1002is onpremimse.siteX, it is possible to determine that the data copy source is the on-premises environment120, and hence it can be determined that the data is the latest data and therefore the processing advances to step S1104. On the other hand, for example, in the secondary usage catalog1000, in a case where the value of the data location1006of the row inputted to the input field1002is cloud.y, bucket://Z, it is possible to determine that the data copy source is the cloud environment130, and hence it can be determined that the data copy source is the backup data and therefore the processing advances to step S1103.

In step S1104, the secondary usage data copy unit114performs processing to construct an environment in which remote access from the cloud environment130is performed on the data of the on-premises environment120. Details of the processing to construct an environment in which remote access is performed from the cloud environment130on the data in the on-premises environment120will be described below with reference toFIG.12.

In step S1103, the secondary usage data copy unit114refers to the selected information of the secondary usage catalog1000and the backup management information111, checks the information on the backup method with which the backup of the secondary usage target was acquired, and determines the next step on the basis of the result. For example, in a case where the data storage location1006of the selected row for which there is an input to the input field1002in the secondary usage catalog1000is bucket://Z, it is possible to check that the data has been backed up to the object storage in the cloud environment130by using the storage function by searching the backup management information111for the row in which the backup ID is bucket://Z and referring to the information of the backup method702of the corresponding row, and an advance to step S1105can be confirmed. Similarly, in a case where the data storage location1006of the selected row for which there is an input to the input field1002in the secondary usage catalog1000is cloud.y Volume #4 and the storage ID1005is Storage_1, by searching the backup management information111for the row in which the backup ID701is volume #4 and the source storage ID704is Storage_1 and checking the value of the backup method702, it can be determined that the volume is being copied to the block storage133in the cloud environment130by using the storage function, and an advance to step S1106can be confirmed. Similarly, in a case where the data storage location1006of the selected row for which there is an input to the input field1002in the secondary usage catalog1000is bucket://y, by searching the backup management information111for the row in which the backup ID701is bucket://y and checking the backup method702, it can be determined that the data has been backed up to the object storage in the cloud environment130by using the function of the backup software, and an advance to step S1107can be determined.

In step S1105, restore processing, to the block storage133, of the data backed up to the object storage in the cloud environment130by using the storage function is performed. Details of the restore processing, to the block storage133, of the data backed up to the object storage in the cloud environment130by using the storage function will be described below with reference toFIG.13.

In step S1106, restore processing, to the block volume133a, of data backed up to a block volume b3of the block storage133in the cloud environment130by using the storage function is performed. Details of the restore processing, to the block volume133a,of the data backed up to the block volume b3of the block storage133in the cloud environment130by using the storage function will be described below with reference toFIG.14.

In step S1107, the restore processing of the data backed up to the object storage in the cloud environment130to the cloud environment130is performed by the backup software. This processing is processing to restore the backup b1, which was backed up in the object storage of the cloud environment130by the backup server123in the on-premises environment120, to the cloud environment130. The backup b1is backed up to the cloud environment by the backup utility301included in the backup server122which is on premises. Therefore, in order to restore the backup b1to the cloud environment130, the backup server131, which has the backup utility304with the function to restore backups by using the backup utility301, is required in the cloud environment130. Here, the DB server and the block volume are restored from the backup in the cloud environment130by using the function of the backup server131in the cloud environment130.

FIG.12is a diagram illustrating a flowchart of processing1200to construct an environment in which remote access is performed from the cloud environment130on data in the on-premises environment120.

In step S1201, the secondary usage data copy unit114instructs the RDBMS302of the DB server123in the on-premises environment120to switch to a backup mode.

In step S1202, the secondary usage data copy unit114issues a request to the block storage124in the on-premises environment120to perform copy processing of the volume124aconstituting the secondary usage target. Here, the copy processing instruction to the block storage124of the on-premises environment120refers to steps S1203and S1204.

In step S1203, the block storage124of the on-premises environment120takes the snapshot124bof the copy target volume124a.

In step S1204, the block storage124of the on-premises environment120splits the snapshot124bfrom the target volume124a.Here, the splitting of the snapshot124bfrom the target volume124asignifies split processing to prevent a write operation to the snapshot124bfrom overwriting the data of the volume124awhen the splitting is complete.

In step S1205, the secondary usage data copy unit114issues an instruction to the on-premises RDBMS302to terminate the backup mode.

In step1206, the secondary usage data copy unit114issues a request to the block storage133in the cloud environment130to perform remote access processing with respect to a block volume124bof the on-premises environment120. Here, the remote access processing refers to steps S1207, S1208, and S1209.

In step S1207, the block storage133in the cloud environment130creates a volume having the same capacity as the volume capacity of the volume124bof the on-premises environment120in order to construct an environment for realizing remote access. Here, information on the volume capacity is included in the remote access processing request in step S1206, and the secondary usage data copy unit114refers to the volume management information115and uses the value disclosed under volume size603in the row in which the volume is assigned the volume ID601.

In step1208, the block storage133in the cloud environment130constructs a remote access environment by using an external volume connection function to connect, as an external volume, the volume124bof the on-premises environment to the volume created in step1207.

In step S1209, the volume in the block storage133created in step S1207is mounted from the DB server132in the cloud environment130so as to make the data available for secondary usage.

As described above, in a case where data targeted for secondary usage is not backed up in the cloud environment130, a snapshot of the data in the on-premises environment120is created, and an environment enabling remote access is constructed. In this case, network communication between the on-premises environment and cloud environment is limited to a relatively low load. This is because a portion of the volume is selectively transmitted. Note that the snapshot created in step S1203can be deleted after use.

FIG.13is a diagram illustrating a flowchart1300in which the storage function is used to perform restore processing on a backup stored in the object storage of the cloud environment130to a volume of the block storage133in the cloud environment130.

In step S1301, the secondary usage data copy unit114issues a request to the block storage133in the cloud environment130to restore the backup b2.

In step S1302, the block storage133in the cloud environment130creates a volume having the same capacity as the volume capacity of the volume124bof the on-premises environment120as a restore destination of the data of the backup b1. Here, information on the volume capacity is included in the request for the volume restore processing in step S1301, and the secondary usage data copy unit114refers to the volume management information115and uses the value described under the volume size603in the row in which the volume is assigned the volume ID601.

In step S1303, the block storage133uses the backup processing program306to perform a restore from the backup b2of the object storage to the volume created in step S1302.

In step S1304, the volume in the block storage133to which the data has been copied by the restore processing in step S1303is mounted from the DB server132in the cloud environment130so as to make the data available for secondary usage.

FIG.14is a diagram illustrating a flowchart1400for performing restore processing from another volume in the block storage133with respect to a backup copied to the block storage133in the cloud environment130by using the storage function.

In step S1401, the secondary usage data copy unit114issues a request to the block storage133in the cloud environment130to restore the backup b3.

In step S1402, the block storage133in the cloud environment130acquires a snapshot from the backup b3, which is a volume for performing a backup, to the cloud environment130, of the block volume124aof the block storage124in the on-premises environment120.

In step S1403, the snapshot obtained in step S1402is split from the backup b3.

In step S1404, the snapshot acquired in step S1403is mounted from the DB server132in the cloud environment130so as to make the data available for secondary usage.

As described above, the disclosed data management system is a data management system for backing up data in a first environment to a second environment, the data management system including:

backup management information111in which source data, backup data, and a backup method are associated; and a secondary usage data copy unit114serving as a secondary usage processing unit that receives a usage request for the backup data stored in the second environment, wherein the secondary usage processing unit refers to the backup management information, specifies the backup data required for processing the usage request, specifies the backup method for the backup data, restores the backup data on the basis of the specified backup method, and enables processing of the usage request.

As an example, the first environment is an on-premises environment, the second environment is a cloud environment, and the first environment stores the data in block storage.

With this configuration, data backed up by various methods can be easily and effectively used in a hybrid cloud environment.

The disclosed data management system further includes a secondary usage catalog creation unit116serving as a candidate presentation unit that presents data constituting target candidates for the usage request, wherein the secondary usage processing unit receives a user selection from among the target candidates, and in a case where backup data of the selected data exists in the second environment, restores the backup data in the second environment and processes the usage request.

The disclosed data management system further includes a secondary usage catalog creation unit116serving as a candidate presentation unit that presents data constituting target candidates for the usage request, wherein the secondary usage processing unit receives a user selection from among the target candidates, and in a case where backup data of the selected data does not exist in the second environment, performs remote access processing on the data of the first environment.

At this time, the secondary usage processing unit constructs a remote access environment by generating a snapshot of data in the first environment and mapping the generated snapshot to a volume in the second environment.

As described above, with the disclosed system, if there is backup data in the second environment, the backup data is restored and undergoes secondary usage, and if there is no backup data in the second environment, a snapshot of data in the first environment is generated and remote access is performed. Therefore, data usage from the second environment is possible regardless of whether a backup has been made.

Note that the present invention is not limited to or by the above-described embodiments, and includes various modifications. For example, the above-described embodiments have been described in detail to facilitate understanding of the present invention, and the present invention is not necessarily limited to or by embodiments having all the configurations described. In addition, modifications are not limited to those from which such configurations have been removed, rather, configurations can also be replaced or added.

For example, in the foregoing embodiments, a case was illustrated in which data in an on-premises environment is backed up to a cloud environment, but a configuration in which the data in the on-premises environment is backed up to another on-premises environment is also conceivable.