Storage system management device

Abstract

To streamline volume restoration. [Solution] The device for managing the storage system includes a processor and a storage device for storing a backup management model, the backup management model includes information on the snapshot generation of a volume stored in the restore destination storage system and information on the snapshot generation of the volume stored in the cloud storage system, and the processor refers to the backup management model and selects the restore source for each snapshot generation to be used for restoring a specified generation in the restore destination storage system from the restore destination storage system and the cloud storage system.

Description

Technical Field

[0001] The present invention relates to the management of storage systems.

Background Art

[0002] As the background art of the present invention, there is Japanese Patent Laid-Open No. 2023-179097. Japanese Patent Laid-Open No. 2023-179097 discloses a technique for reducing the data transfer amount when performing a restore from the cloud. The technique includes generating catalog information for each snapshot that includes at least the storage location of the actual data of the snapshot and the reference destination that identifies other snapshots having a parent-child relationship with the snapshot, and storing the actual data of the snapshot in a physical storage device and / or a cloud service. When performing a restore by designating any one of a plurality of snapshots, the storage location of the actual data is identified by referring to the catalog information, the actual data stored in the physical storage device is acquired, and the actual data not stored in the physical storage device is acquired from the cloud service (see, for example, the summary).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] For example, in a hybrid cloud system including an on-premises storage system and a cloud storage system, a technique that can efficiently perform a restore of a volume to an arbitrary site is desired.

Means for Solving the Problems

[0005] One aspect of the present invention is a device for managing a storage system, comprising a processor and a storage device for storing a backup management model, wherein the backup management model includes information on snapshot generations of a volume stored in a restore destination storage system and information on snapshot generations of the volume stored in a cloud storage system, and the processor, by referring to the backup management model, selects from the restore destination storage system and the cloud storage system the restore source for each snapshot generation to be used for restoring a specified generation in the restore destination storage system. [Effects of the Invention]

[0006] According to one aspect of the present invention, volume restoration can be made more efficient. [Brief explanation of the drawing]

[0007] [Figure 1] A schematic example of the configuration of a computer system according to one embodiment of this specification is shown below. [Figure 2] This shows an example configuration for a hybrid cloud management system. [Figure 3] This shows an example configuration for a hybrid cloud management model. [Figure 4] This shows the directory structure of data stored in the cloud storage system. [Figure 5] An example of a backup catalog for volume A is shown. [Figure 6] An example flowchart for the backup process is shown. [Figure 7] An example flowchart of one aspect of the restore process is shown. [Figure 8] An example flowchart of one aspect of the restore process is shown. [Figure 9] An example flowchart of one aspect of the restore process is shown. [Figure 10] An example flowchart for the process of determining the source of the restore is shown. [Modes for carrying out the invention]

[0008] The embodiments of the present invention will be described below with reference to the drawings. However, the present invention is not to be construed as being limited to the embodiments described below. It will be readily apparent to those skilled in the art that the specific configuration can be modified without departing from the spirit or intent of the present invention.

[0009] In this specification, the designations "First," "Second," "Third," etc., are used to identify components and do not necessarily limit their number or order. In the configuration of the invention described below, identical or similar components or functions are denoted by the same reference numerals, and redundant descriptions are omitted.

[0010] Furthermore, in the following explanation, when describing similar elements without distinction, the common code (or reference code) in the reference code may be used, and when describing similar elements with distinction, the reference code (or element ID) may be used.

[0011] The program is executed by a processor (e.g., a CPU (Central Processing Unit)) included in the storage controller within the storage device, performing defined processing using storage resources (e.g., memory) and / or communication interface devices (e.g., a host I / F) as appropriate. Therefore, the subject of the processing may be the storage device or the processor. The storage controller may also include hardware circuits that perform some or all of the processing. The computer program may be installed from the program source. The program source may be, for example, a program distribution server or a computer-readable storage medium.

[0012] FIG. 1 schematically shows a configuration example of a computer system according to an embodiment of this specification. The computer system includes devices arranged at different locations. Specifically, at each of different locations A(20-1) and location B(20-2), one or more host devices 220 and one or more storage systems 210 are installed. The storage system 210 is a so-called on-premises storage system.

[0013] FIG. 1 shows one host device 220 and one storage system 210 at each location, but the number thereof is arbitrary. At each location, the host device 220 accesses the storage system 210 to write and read host data.

[0014] The computer system further includes a cloud system 30 installed at a location different from location A(20-1) and location B(20-2). The cloud system 30 includes a cloud storage system 310 and provides a cloud storage service.

[0015] The computer system further includes a hybrid cloud management device 10. The hybrid cloud management device 10 manages the storage systems 210 at location A(20-1) and location B(20-2) and the cloud storage system 310. The hybrid cloud management device 10, location A(20-1), location B(20-2), and the cloud system 30 can communicate via a network 40. The hybrid cloud management device 10 may be arranged at any location, for example, may be included in the cloud system 30.

[0016] The storage system 210 includes one or more controllers (not shown) and one or more physical storage devices (also called storage drives), and processes IO requests (read requests or write requests) from the host device 220. The storage device provides a physical storage area for storing host data from the host device 220.

[0017] The controller includes a front-end interface, a processor (main processor), a memory, and a back-end interface. The front-end interface is a communication interface with the host device 220, and the back-end interface is a communication interface with the storage device. The controller applies a logical volume for storing host data to the host device 220, and the storage area (address) of the logical volume is mapped to the physical storage areas of one or more storage devices.

[0018] The storage system 210 executes a plurality of programs. Each program can be executed by a processor included in the main processor of the controller or another device (e.g., the front-end interface). In the configuration example shown in FIG. 1, the storage system 210 executes a snapshot program 211, a backup program 212, a restore program 213, a storage management program 215, and a differential extraction program 216.

[0019] FIG. 1 shows the internal configuration of the storage system 210 at site B (20-2), and the storage system 210 at site A (20-1) has a similar configuration. The storage management program 215 executes volume generation and management, host IO processing, and overall management and control of the storage system 210.

[0020] The storage system 2 is storing a snapshot group 214 for each specified volume. For example, the first-generation snapshot stores all the data of the volume, and each subsequent snapshot stores the differential data from the immediately preceding-generation snapshot. The snapshot program 211 generates snapshots of the specified volumes.

[0021] The backup program 212 sends a backup of the specified volume to the cloud storage system 310. In this example, the backup program 212 sends a copy of the snapshot group 214 to the cloud storage system 310, and the cloud storage system 310 stores the data.

[0022] In Figure 1, the snapshot data (Snapshot1 Data311, etc.) stored in the cloud storage system 310 is a copy of the snapshot generated by the storage system 210 at site A (20-1). Additionally, a portion of the snapshots from site A (20-1) is copied from the cloud storage system 310 to the snapshot group 214 at site B (20-2). The snapshot group 214 at site B (20-2) can be used, for example, for data analysis.

[0023] The difference extraction program 216 generates a bitmap showing the differences between any two generations of snapshots. The bitmap assigns, for example, "0" to addresses of identical data and "1" to addresses of different data. The bitmap is stored in the cloud storage system 310 along with the snapshot data.

[0024] The hybrid cloud management device 10 executes the restore configuration program 113. The restore configuration program 113 manages the volume restore. In the example in Figure 1, if a failure occurs in the storage system 210 at site A (20-1), or if data from site A (20-1) is acquired and analyzed at site B (20-2), the storage system 210 at site B (20-2) will perform the restore of the volume at site A (20-1).

[0025] The following describes the process of the restore configuration program 113. The restore configuration program 113 obtains snapshot information from the storage system 210 at site B (20-2) (S1). The snapshot information, for example, indicates the generation of snapshots for each volume held by the storage system 210 at site B (20-2).

[0026] The restore configuration program 113 retrieves backup information from the cloud storage system 310 (S2). The backup information, for example, indicates the filenames of the bitmaps for each volume held by the cloud storage system 310.

[0027] The restore configuration program 113 stores the acquired snapshot information and backup information in the hybrid cloud management model 114 (S3). The hybrid cloud management model 114 includes information about the storage systems at each site, the volumes they hold, and the storage location of the snapshots for each volume. The format of the hybrid cloud management model 114 is arbitrary.

[0028] The restore configuration program 113 converts the backup information obtained from the cloud storage system 310 into a format that can be used for searching on the cloud storage system 310, such as JSON or CSV, into a backup catalog 320, and stores it on the cloud storage system 310 (S4). The backup catalog 320 is the target of search requests from users (S5).

[0029] If a user requests that a volume from site A(20-1) be restored at site B(20-2), the restore configuration program 113 calculates the volume to be restored (S6). The restore configuration program 113 refers to the hybrid cloud management model 114 to identify the snapshots of the volume to be restored held by the storage system 210 at site B(B-1). The restore configuration program 113 identifies the missing generations of snapshots for the specified restore.

[0030] The restore configuration program 113 sends an instruction to perform a differential restore to the storage system 210 at site B (20-2), along with information about the missing generation of snapshots (e.g., "Snapshot02 Data") (S7).

[0031] The restore program 213 of the storage system 210, in response to instructions from the restore configuration program 113, obtains the missing generation of snapshots from the cloud storage system 310 and uses them together with the snapshots it maintains to restore the target volume (S8).

[0032] Figure 2 shows an example configuration of the hybrid cloud management device 10. The hybrid cloud management device 10 includes a CPU 101, which is a processor that executes various programs; a memory 102, which is a primary storage device that stores various programs; and an auxiliary storage device 103, which stores various data. The CPU 101 can include one or more cores, and the memory 102 is, for example, DRAM that includes volatile storage areas. The auxiliary storage device 103 is, for example, an HDD (Hard Disk Drive) or flash memory, and can be provided with non-volatile storage areas.

[0033] The hybrid cloud management device 10 further includes an output device 105 for presenting information to the device's user, an input device 104 for inputting instructions, images, etc., from the user, and a communication device 106 for communicating with other devices. The components of the hybrid cloud management device 10 are interconnected by a bus. The user may use a terminal that connects to the hybrid cloud management device 10 via a network instead of the input / output devices of the hybrid cloud management device 10.

[0034] The functional unit of the hybrid cloud management device 10 can be implemented, for example, by the CPU 101 operating according to a program. The CPU 101 reads and executes various programs from memory 102 as needed. Memory 102 can store programs and the data they use. Each program and reference data is loaded into memory 102 from, for example, auxiliary storage device 103, and executed and processed by the CPU 101. At least a part of the functional unit may be composed of logic circuits.

[0035] The output device 105 may include devices such as a display, printer, and speaker. The input device 104 may include devices such as a keyboard, mouse, and microphone. The output device 105 displays the input results from the user as well as the processing results from the hybrid cloud management device 10. User instructions are input to the hybrid cloud management device 10 via the input device 104. If other terminals are used, their input / output devices will function similarly, and the output device 105 and input device 104 can be omitted.

[0036] The communication device 106 receives data transmitted from other devices connected via a network, for example, and also transmits the processing results from the hybrid cloud management device 10 to other devices. Some devices may be omitted.

[0037] In the configuration example shown in Figure 2, memory 102 stores the storage system management interface program 110, the cloud storage management interface program 111, the backup configuration program 112, the restore configuration program 113, the hybrid cloud management model 114, and the operating system 115.

[0038] The storage system management interface program 110 is a communication interface with the storage system 210. The cloud storage management interface program 11 is a communication interface with the cloud storage system 310. These programs retrieve and manage the backup targets and schedules set by the user and send instructions indicating these to the storage system 210 and the cloud storage system 310.

[0039] Figure 3 shows an example configuration of the hybrid cloud management model 114. As shown in Figure 3, the hybrid cloud management model 114 shows information about the storage systems (devices) of each site and cloud system, the volumes they hold, and snapshots of those volumes. The snapshot information includes the time of the snapshot and information about the device that stores it.

[0040] In the example shown in Figure 3, devices A-1 (1141-1) and A-2 (1141-2) are installed at site A (1140-1). "Device" refers to a storage system. Furthermore, device A-1 (1141-1) stores volumes A-1 (1142-1) and A-2 (1142-2).

[0041] Devices B-1 (1141-3) and B-2 (1141-4) are installed at site B (1140-2). Furthermore, device B-1 (1141-3) stores volumes B-1 (1142-3) and B-2 (1142-4). Volume B-1 (1142-3) is a volume restored from volume A-1 (1142-1). Volume B-2 (1142-4) is a volume restored from volume A-2 (1142-2).

[0042] LocalSS1143 represents snapshots of volume B-1(1142-3) stored in device B-1(1141-3). These are snapshots SS_00(1145-1) and SS_01(1145-2).

[0043] RemoteSS1144 represents snapshots of volume B-1 (1142-3) stored in cloud system 1140-3. These are snapshot SS_00 (1146-1), snapshot SS_01 (1146-2), and snapshot SS_02 (1146-3).

[0044] In the example in Figure 3, the information for each snapshot shows the creation time and the size of the target volume. In the example in Figure 3, snapshot SS_02 exists only in cloud system 1140-3. Cloud system 1140-3 includes device C-1 (1141-5), which is cloud storage system 310.

[0045] Figure 4 shows the directory structure of data stored in the cloud storage system 310. Figure 4 shows information about volume A stored in storage system A at site A.

[0046] Directory 312 stores information about volume A, which is stored by storage system A located at site A. Directory 313 below it stores bitmaps of snapshots of volume A. The object name of each bitmap indicates the site name, storage system number, volume number, snapshot name, snapshot time, and volume size.

[0047] For example, the object name of "Management File 00" is "siteA_deviceA_volA_snapshot00_202401101200_10TB.bitmap". This indicates that it is a bitmap of snapshot 00 of volume A stored on storage system A installed at site A. Furthermore, it indicates that the snapshot was created on January 10, 2024 at 12:00, and that the volume size is 10TB.

[0048] Directory 314, directly under directory 312, stores snapshots (snapshot data) of volume A. Three generations of snapshots are stored here, and each snapshot is divided into two parts. The data structure of each snapshot generation is arbitrary. The snapshot object name indicates the location name, storage system number, volume number, snapshot name, snapshot time, and the corresponding area of ​​the volume.

[0049] For example, the object name for "Snapshot00 Data1" is "siteA_deviceA_volA_snapshot00_202401101200_0-5TB". This indicates that it is data from snapshot 00 of volume A stored on storage system A located at site A. Furthermore, it indicates that the snapshot was created on January 10, 2024 at 12:00, and that the corresponding volume area is 0-5TB.

[0050] The directory 315, directly under directory 312, stores the backup catalog. Its object name indicates the site name, storage system number, volume number, snapshot name, snapshot time, and volume size. "siteA_deviceA_volA_20240121000_10TB.catalog" shown in Figure 4 is the backup catalog for volume A stored on storage system A at site A, indicating that it was created on January 21, 2024 at 00:00 and has a volume size of 10TB.

[0051] Figure 5 shows an example of a backup catalog 320 for volume A. The backup catalog 320 represents snapshot information for volume A in a format searchable by the cloud storage system 310. In the example shown in Figure 5, the backup catalog 320 shows the identifier (generation), backup time (snapshot creation time), and source volume size for each snapshot. The backup catalog 320, generated from bitmap object names, manages backup data at low cost and with high scalability, enabling fast restore.

[0052] Next, we will explain the processing of the computer system. Figure 6 shows an example flowchart of backup process 14000.

[0053] The backup program 212 of the storage system 210 checks if the time of the configured backup schedule matches the current time (S14001). If they do not match (S14002: NO), the flow returns to step S14001. If they do match (S14002: YES), the backup program 212 instructs the snapshot program 211 of the same storage system 310 to create a snapshot (S14003).

[0054] The snapshot program 211 creates a snapshot of the specified volume and returns a response (S14004). The backup program 212 mounts the created snapshot (S14005).

[0055] Next, the backup program 212 instructs the difference extraction program 216 to extract the differences between snapshots (S14006). The difference extraction program 216 extracts the differences between snapshots and responds with a bitmap (difference bitmap) (S14007). Based on the bitmap, the backup program 212 transfers the difference data to the cloud storage system 310 (S14008). Specifically, the backup program 212 reads the difference block data from the mounted snapshots, converts it to a file format, and sends it to the cloud storage system 310.

[0056] The backup program 212 obtains the snapshot site name, storage system number (serial number), and volume number from the storage management program 215 (S14009). These items are included in the snapshot object name. The backup program 212 includes the site name, serial number, volume number, snapshot name, backup date and time, and volume size in the bitmap object name and transfers the bitmap to the cloud storage system 310 (S14010). In this way, the source information is included in the bitmap object name. This makes it easy to generate a backup catalog for searching.

[0057] Several modes of restore processing are described below. The restore processing 9000 shown in Figure 7 displays all backup catalogs in the hybrid cloud management device 10. The display device may be included in the user terminal connected to the hybrid cloud management device 10. This restore processing omits the search for backup catalogs. For example, the restore processing is executed in response to user instructions.

[0058] The restore configuration program 113 retrieves snapshot information from the storage system 210 and stores it in the LocalSS information of the hybrid cloud management model 114 (S9001). The restore configuration program 113 uses the LIST API to retrieve a list of object names of management files (bitmaps) from the cloud storage system 310, converts them into backup information, and stores it in the Remote SS information of the hybrid cloud management model 114 (S9002).

[0059] The restore configuration program 113 displays backup information of the object name list of the management file on the screen (S9003). The displayed object names may, for example, be information about all volumes at all locations. The displayed backup information may include information identifying the location, storage system, volume, and snapshot, as well as information such as backup time and volume size. Some of these items may be omitted.

[0060] The restore configuration program 113 receives a restore request from the user (S9004). The restore request specifies the snapshot of the volume to be restored and the storage system to which it will be restored.

[0061] Next, the restore setting program 113 executes the restore source determination process (11000). The restore source determination process refers to the LocalSS information and RemoteSS information and determines the restore source for each generation. Details will be described later.

[0062] Next, the restore configuration program 113 specifies the restore source and instructs the restore program 213 on the storage system 210 to perform the restore (S9006). The restore program 213 on the storage system 210 performs the restore according to the instructions from the hybrid cloud management device 10 (S9007).

[0063] Next, with reference to Figure 8, another embodiment of the restore process will be described. The restore process 10000 shown in Figure 8 enables the user to search for backup information using the Select command of the cloud storage system 310.

[0064] The restore configuration program 113 retrieves snapshot information from the storage system 210 and stores it in the LocalSS information of the hybrid cloud management model 114 (S10001). The restore configuration program 113 uses the LIST API to retrieve a list of object names of management files (bitmaps) from the cloud storage system 310, converts them into backup information, and stores it in the Remote SS information of the hybrid cloud management model 114 (S10002).

[0065] The restore configuration program 113 converts the backup information from the object name list of the management file (bitmap), includes it in a backup catalog 320 in a specific format, such as JSON, and stores it in the cloud storage system 310. The backup information included in the backup catalog 320 may be, for example, information about all volumes at all locations.

[0066] The restore configuration program 113 receives a search term from the user and uses the SELECT API to retrieve information matching the search term from the backup information (backup catalog 320) stored in JSON format (S10004). The search term may, for example, indicate information about the volume from which the restore is to be performed, or it may specify the volume to be restored and its time.

[0067] The restore configuration program 113 receives a restore request from the user (S10005). The restore request specifies the snapshot of the volume to be restored and the storage system to which it will be restored. The user can easily create a restore request based on the search results.

[0068] Next, the restore setting program 113 executes the restore source determination process (11000). The restore source determination process refers to the LocalSS information and RemoteSS information and determines the restore source for each generation. Details will be described later.

[0069] Next, the restore configuration program 113 specifies the restore source and instructs the restore program 213 on the storage system 210 to perform the restore (S10007). The restore program 213 on the storage system 210 performs the restore according to the instructions from the hybrid cloud management device 10 (S10008).

[0070] Next, with reference to Figure 9, another embodiment of the restore process will be described. The restore process 12000 shown in Figure 9 involves the hybrid cloud management device 10 searching for backup information.

[0071] The restore configuration program 113 retrieves snapshot information from the storage system 210 and stores it in the LocalSS information of the hybrid cloud management model 114 (S12001). The restore configuration program 113 uses the LIST API to retrieve a list of object names of management files (bitmaps) from the cloud storage system 310, converts them into backup information, and stores it in the Remote SS information of the hybrid cloud management model 114 (S12002).

[0072] The restore configuration program 113 stores the backup information converted from the object name list of the management file (bitmap) in the hybrid cloud management device 10. The file format is arbitrary and can be text format or a more complex database. The backup information may be, for example, information about all volumes at all locations.

[0073] The restore configuration program 113 receives a search term from the user and retrieves information matching the search term from the backup information stored in the hybrid cloud management device 10 (S12004). The search term may, for example, indicate information about the volume from which the restore is to be performed, or it may specify, for example, the volume to be restored and its time.

[0074] The restore configuration program 113 receives a restore request from the user (S12005). The restore request specifies the snapshot of the volume to be restored and the storage system to which it will be restored. The user can easily create a restore request based on the search results.

[0075] Next, the restore setting program 113 executes the restore source determination process (11000). The restore source determination process refers to the LocalSS information and RemoteSS information and determines the restore source for each generation. Details will be described later.

[0076] Next, the restore configuration program 113 specifies the restore source and instructs the restore program 213 on the storage system 210 to perform the restore (S12007). The restore program 213 on the storage system 210 performs the restore according to the instructions from the hybrid cloud management device 10 (S12008).

[0077] Next, the restore source determination process 11000 will be explained. Figure 10 shows an example flowchart of the restore source determination process 11000. The restore source determination process 11000 refers to LocalSS information and RemoteSS information and determines the restore source for each generation.

[0078] The restore configuration program 113 determines whether all the data necessary to restore the volume generation (restore generation) specified by the user is stored in LocalSS (restore destination storage system 210) (S11002).

[0079] For example, if storage system 210 stores data from the specified generation of snapshots and all older snapshots, the result of this determination is "YES". Note that each snapshot stored in storage system 210 or cloud storage system 310 may be data merged from consecutive older generations of snapshots, or all the data (not just differences) from that generation. Note that unnecessary older generation snapshots may be discarded.

[0080] If all the data necessary to restore the volume generation specified by the user is stored in LocalSS (S11002:YES), the restore setting program 113 determines the restore source to be the local storage system 210 (S11003).

[0081] If there is insufficient data to restore the volume generation specified by the user (S11002: NO), the restore setting program 113 determines whether data to restore data from an older generation than the specified generation exists in LocalSS (S11004). For example, if only data from a newer generation than the specified generation exists in LocalSS, the result of the determination in step S11004 is NO.

[0082] If the data does not exist in LocalSS (S11004: NO), the restore configuration program 113 determines the restore source to RemoteSS, i.e., the cloud storage system 310 (S11005). In other words, the volume data is restored only from snapshot data backed up in the cloud storage system 310.

[0083] If data for restoring data from a generation older than the specified generation exists in LocalSS (S11004:YES), the restore setting program 113 determines whether the most recent generation in LocalSS also exists in RemoteSS (S11006).

[0084] If the generation in question does not exist in RemoteSS either (S11006: NO), the restore configuration program 113 determines the restore source to be RemoteSS, i.e., the cloud storage system 310 (S11007). In other words, if the latest generation of LocalSS is older than the specified generation and also older than the oldest generation of RemoteSS, RemoteSS is determined as the restore source. This allows for proper restoration from RemoteSS when the snapshots in LocalSS are too old.

[0085] If the most recent generation of LocalSS also exists in RemoteSS (S11006: YES), the restore configuration program 113 restores the most recent generation of LocalSS from LocalSS and determines that RemoteSS is the source for the restore from newer generations up to the current restore generation (S11008). This reduces the amount of data transferred from the cloud storage system 310.

[0086] It should be noted that the present invention is not limited to the embodiments described above, and various modifications are included. For example, the embodiments described above are described in detail to make the present invention easier to understand, and are not necessarily limited to those having all the configurations described. Furthermore, it is possible to replace parts of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add configurations from other embodiments to the configuration of one embodiment. In addition, it is possible to add, delete, or replace parts of the configuration of each embodiment with other configurations.

[0087] Furthermore, each of the above-mentioned configurations, functions, and processing units may be implemented in hardware, either partially or entirely, by designing them as integrated circuits, for example. Alternatively, each of the above-mentioned configurations and functions may be implemented in software by having the processor interpret and execute programs that implement each function. Information such as programs, tables, and files that implement each function can be stored in memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card or SD card.

[0088] Furthermore, the control lines and information lines shown are those deemed necessary for explanatory purposes, and not all control lines and information lines are necessarily shown in the actual product. In practice, it is reasonable to assume that almost all components are interconnected. [Explanation of symbols]

[0089] 10 Hybrid Cloud Management Device 114 Hybrid Cloud Management Model 210 Storage Systems 214 snapshots 310 Cloud Storage System 320 Backup Catalogs

Claims

1. A device for managing a storage system, Processor and Includes a storage device that stores a backup management model, The aforementioned backup management model is Information on the volume snapshot generation stored in the destination storage system, This includes information on the snapshot generations of the volume stored in the cloud storage system, The processor is a device that, by referring to the backup management model, selects the restore source for each snapshot generation to be used for restoring a specified generation on the restore destination storage system from the restore destination storage system and the cloud storage system.

2. The apparatus according to claim 1, If the destination storage system stores all snapshots for restoring the specified generation, the processor determines that the destination storage system is the source for restoring all generations of snapshots.

3. The apparatus according to claim 1, If the destination storage system does not contain snapshots of the specified generation or older generations, the processor determines that the cloud storage system is the source for restoring all generations of snapshots.

4. The apparatus according to claim 1, A device in which, if the destination storage system stores snapshots older than the specified generation, and the cloud storage system stores the latest generation snapshots stored in the destination storage system, the processor determines the destination storage system as the source for restoration up to the latest generation, and the cloud storage system as the source for restoration up to the specified generation after the latest generation.

5. The apparatus according to claim 1, A device that determines the cloud storage system to be the source for restoring all generations of snapshots if the latest generation of snapshots of the volume stored in the restore destination storage system is older than the specified generation and older than the oldest generation of snapshots of the volume stored in the cloud storage system.

6. The apparatus according to claim 1, The aforementioned processor, From the aforementioned cloud storage system, backup information including snapshot information stored in the cloud storage system is obtained. A device that generates searchable objects for snapshot information specified by the user from the aforementioned backup information.

7. The apparatus according to claim 6, The backup information includes a list of object names of the bitmap snapshots stored in the cloud storage system, The aforementioned object name is the device, including the information of the snapshot.

8. The apparatus according to claim 7, The processor stores the object to be searched in the cloud storage system. The object to be searched has a format that corresponds to the search command of the cloud storage system, The aforementioned processor, A search command is sent to the cloud storage system along with the user-specified search term. A device that receives search results from the aforementioned cloud storage system.

9. A method by which a device manages a storage system, The device stores the backup management model, The aforementioned backup management model is Information on the volume snapshot generation stored in the destination storage system, This includes information on the snapshot generations of the volume stored in the cloud storage system, The method described above is a method in which the device, by referring to the backup management model, selects from the restore destination storage system and the cloud storage system the restore source for each snapshot generation to be used to restore a specified generation on the restore destination storage system.

Images