Storage system and state management method of resource operation

Abstract

To easily execute an operation including a series of storage operations in a hybrid cloud.SOLUTION: A storage system has a first storage and a second storage on a cloud. The storage system executes operations composed of a plurality of resource operations including a resource operation of copying data of a server of another site to the second storage through a first volume of the first storage. The storage system manages a correspondence between each state of resources accompanied by execution of each of the resource operations, and a transition destination state transited from each of the states when the execution of each of the resource operations is completed, for each type of the operations. The storage system manages a current state of the resource accompanied by the execution of the resource operations, and determines the transition destination state associated with the current state as a state transited from the current state, on the basis of an execution result whether the resource operations are normally completed and the correspondence.SELECTED DRAWING: Figure 6

Description

Technical Field

[0001] The present invention relates to a storage system and a method for managing the state of resource operations.

Background Art

[0002] In an information system, there is a need to perform storage operations without requiring skills and labor. For example, Patent Document 1 discloses a system that prevents incorrect operations by evaluating the risk of incorrect operations by a user who executes storage operations for multiple tenants.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the prior art disclosed in Patent Document 1 described above, the state management of a series of storage operations from start to completion is not performed.

[0005] In recent years, the demand for hybrid clouds that combine on-premises computer resources and public cloud computer resources has been increasing. In a hybrid cloud, for example, a migration including a series of storage operations for migrating on-premises computer resources to a public cloud via an intermediate volume is executed.

[0006] Here, in the cloud, there may be inconveniences such as data loss when a storage operation is redone due to a user's incorrect operation or the like, or an increase in cloud capacity charges unless an unnecessary intermediate volume is deleted.

[0007] However, in the prior art, since the state management of storage operations is not performed, in order to avoid the above-mentioned inconveniences, when executing an operation including a series of storage operations in a hybrid cloud, it is unclear from which state it can be executed, and there is a problem that it cannot be easily executed.

[0008] The present invention has been made in consideration of the above circumstances, and an object thereof is to enable an operation including a series of storage operations to be easily executed in a hybrid cloud.

Means for Solving the Problems

[0009] In one aspect of the present invention, there is provided a storage system that has a first storage and a second storage on a cloud and executes an operation composed of a plurality of resource operations including a resource operation of copying data stored in a server arranged at another site to the second storage via a first volume provided by the first storage. The storage system has a processor and a memory. The processor manages a correspondence relationship between each state of the resource associated with the execution of each resource operation and a transition destination state indicating the state to transition from each state when the execution of each resource operation ends, for each type of the operation. The processor executes the resource operation included in the operation, manages the current state which is the state representing the execution of the resource operation, obtains an execution result indicating whether the execution of the resource operation has been normally completed, obtains the transition destination state associated with the current state based on the execution result and the correspondence relationship, and determines the state to transition from the current state based on the obtained transition destination state.

Effects of the Invention

[0010] According to the present invention, an operation including a series of storage operations can be easily executed in a hybrid cloud.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3A

Figure 3B

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

Mode for Carrying Out the Invention

[0012] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. It should be noted that the following description and drawings are examples for explaining the present invention, and for the sake of clarity of explanation, appropriate omissions and simplifications have been made. Also, not all combinations of features described in the embodiments are essential for the solution means of the invention. The present invention is not limited to the embodiments, and all application examples that conform to the idea of the present invention are included in the technical scope of the present invention. Those skilled in the art can make various additions and changes within the scope of the present invention. The present invention can also be implemented in various other forms. Unless otherwise particularly limited, each component may be plural or singular. In the following description, "CPU (Central Processing Unit)" is an example of one or more processor devices. At least one processor device is typically not limited to a CPU, but may also be other types of processor devices such as a GPU (Graphics Processing Unit). At least one processor device may be single-core or multi-core. At least one processor device may be a processor core.

[0013] At least one processor device may also be a circuit that is an aggregate of gate arrays described in a hardware description language for performing part or all of the processing. A circuit is a processor device in a broad sense such as, for example, an FPGA (Field-Programmable Gate Array), a CPLD (Complex Programmable Logic Device), or an ASIC (Application Specific Integrated Circuit).

[0014] In the following description, when a program is executed by a CPU, the processing function called "XXX section" is realized and becomes the execution entity of the processing. The processing function may be realized by one or more computer programs being executed by a processor, or may be realized by one or more hardware circuits (for example, an FPGA or an ASIC), or may be realized by a combination thereof.

[0015] When a function is realized by a program being executed by a processor, since the defined processing is performed while appropriately using a storage device and / or an interface device, etc., the function may be regarded as at least part of the processor. The processing described with a functional unit as the subject may also be the processing performed by a processor or a device having the processor.

[0016] The program may be installed from a program source. The program source may be, for example, a program distribution computer or a computer-readable recording medium (e.g., a non-transitory recording medium). The description of each function is an example, and a plurality of functions may be combined into one function, or one function may be divided into a plurality of functions.

[0017] Also, in the following description, when various information is described in a table format, the data format of the information may be a format other than the table format (e.g., CSV (Comma Separated Values) format, etc.). Also, the various information may be stored in the storage unit as a table, or may be embedded as logic in the program.

[0018] Also, in the following description, when describing without distinguishing between elements of the same type, common reference signs among the reference signs are used, and when describing while distinguishing between elements of the same type, reference signs may be used.

[0019] (Configuration of the cloud system S according to the embodiment) FIG. 1 is a diagram showing the configuration of a cloud system S according to the embodiment. The cloud system S is a storage system on a hybrid cloud installed at a cloud site. The cloud system S has a private cloud infrastructure 1 managed for each customer and a multi-tenant public cloud infrastructure 2.

[0020] The private cloud infrastructure 1 has virtual machines 11, storage 12, and an aggregation server 13. Within the private cloud infrastructure 1, the virtual machines 11, storage 12, and aggregation server 13 are communicably connected.

[0021] The virtual machine 11 is a virtual server to which program data and user data have been migrated from an on-premises physical server (not shown) and storage (not shown) installed at a site different from the cloud site. Also, the virtual machine 11 is a virtual server to be migrated that migrates user data migrated from on-premises to the public cloud infrastructure 2. The virtual machine 11 has a business application execution unit 111 and a volume 112 provided to the virtual machine 11 by the storage 12.

[0022] The business application execution unit 111 executes business applications. The volume 112 stores the program data of the virtual machine 11 migrated from on-premises and the user data of customers who use the virtual machine 11. The volume 112 is an example of a first volume and is an intermediate volume described later.

[0023] The storage 12 is, for example, object storage. The storage 12 acquires and stores a snapshot 121 of the user data of the virtual machine 11 stored in the volume 112. The storage 12 is an example of a first storage.

[0024] The aggregation server 13 is a virtual machine and has a storage operation completion status notification unit 131 and a storage operation instruction unit 132. The storage operation completion status notification unit 131 transmits, as the post-execution state, the storage operation completion status notification output from the storage 12 after the execution of the storage operation executed in response to an execution instruction to a storage operation status notification reception unit 232 described later. The storage operation instruction unit 132 transmits an execution instruction for a storage operation according to the state received from a state management unit 234 described later to the storage 12.

[0025] The public cloud infrastructure 2 includes a storage 21, an SDS (Software-Defined Storage) cluster 22, a status management server 23, a display server 24, and an aggregation server 25. In the public cloud infrastructure 2, the storage 21, the SDS cluster 22, the status management server 23, the display server 24, and the aggregation server 25 are communicably connected.

[0026] The storage 21 is, for example, block storage and stores a snapshot 121 shared from the private cloud infrastructure 1. The SDS cluster 22 is a storage cluster included in the public cloud infrastructure 2 and takes in the snapshot 121 into a volume 221 via the storage 21. The SDS cluster 22 is an example of a second storage.

[0027] The status management server 23 is a virtual machine and includes a screen operation status receiving unit 231, a storage operation status notification receiving unit 232, a status management unit 234, and a storage unit 235.

[0028] The screen operation status receiving unit 231 receives the operation status of various screens (Figs. 10 to 15) displayed on a display unit 241 described later by a user and transmits it to the status management unit 234. The storage operation status notification receiving unit 232 receives a notification of the completion status of a storage operation from the storage operation completion status notification units 131, 251 of the aggregation servers 13, 25 and transmits it to the status management unit 234.

[0029] The status management unit 234 updates a status management table 236 described later based on the completion status of the storage operation received from the storage operation status notification receiving unit 232. Also, the status management unit 234 refers to a transition destination list table 237 and a storage resource management table 238, and determines the next state to transition based on the operation status of the user received from the screen operation status receiving unit 231. Then, the status management unit 234 transmits the determined state to the storage operation instruction units 132, 252 of the aggregation servers 13, 25.

[0030] The storage unit 235 is a temporary storage device such as a memory or a permanent storage device such as a storage. The storage unit 235 stores a state management table 236, a destination list table 237, and a storage resource management table 238. Details of the state management table 236, the destination list table 237, and the storage resource management table 238 will be described later with reference to FIGS. 2, 3A, 3B, and 4 respectively.

[0031] The display server 24 is a virtual machine and has a display unit 241. The display unit 241 has a display screen (not shown) and controls the display of various screens (FIGS. 10 to 15) described later. The display unit 241 displays the information received from the state management unit 234 on the display screen and transmits the operation status of the user who operates the display screen to the screen operation status receiving unit 231.

[0032] The aggregation server 25 is a virtual machine and has a storage operation completion status notification unit 251 and a storage operation instruction unit 252. The aggregation server 25, the storage operation completion status notification unit 251, and the storage operation instruction unit 252 are the same as the aggregation server 13, the storage operation completion status notification unit 131, and the storage operation instruction unit 132.

[0033] In this embodiment, the virtual machine 11 to be migrated is assumed to be a virtual server migrated from a physical server provided on the customer's on-premises. However, it is not limited to this, and the virtual machine 11 may be a virtual server migrated from a virtual server provided in the customer's private cloud or any other server. The cloud system S has the merit of being able to flexibly combine the data source and destination by executing operations via an intermediate volume.

[0034] (Configuration of the state management table 236 according to the embodiment) FIG. 2 is a diagram showing the configuration of the state management table 236 according to the embodiment. The state management table 236 has columns of "project ID", "project name", "project type ID", "project type name", "status ID", and "last update date and time".

[0035] The "Case ID" is identification information of a case including a process identified by, for example, a customer name, a system name, a "Case Type ID", and a "Case Type Name". The "Case Name" is a name given to the "Case ID". The "Case Type ID" is a type of operation pattern including a series of storage operations executed in the case identified by the "Case ID". The "Case Type Name" is a name given to the "Case ID". The "Status ID" is identification information of a status representing the execution status of the process of the case identified by the "Case ID". The "Last Update Date and Time" is a timestamp of the corresponding record.

[0036] (Configuration of the Destination List Table 237 according to the embodiment) FIG. 3A is a diagram showing the configuration of the destination list table (migration) 237a according to the embodiment. FIG. 3B is a diagram showing the configuration of the destination list table (reuse) 237b according to the embodiment.

[0037] The destination list table 237 is defined for each case type. The destination list tables 237a and 237b shown in FIGS. 3A and 3B show the case where there are two case types, "migration" and "reuse". "Reuse" refers to an operation of using data such as the snapshot 121 related to this copy for purposes other than a copy of the original data, and there are, for example, analysis using data and batch processing such as monthly processing.

[0038] A case or a case type is an example of an operation composed of a plurality of resource operations. Also, the resource operation is a storage operation on the storage 12, the storage 21, and the SDS cluster 22 in this embodiment.

[0039] "Migration" and "reuse" are premised on the fact that the snapshot 121 has been created as a preparation. However, it is not limited to this, and the snapshot 121 may be created in the processes of "migration" and "reuse", and the range of the preparation stage can be changed as appropriate.

[0040] For each increase in the case type, an independent table is provided for the destination list table 237. A plurality of destination list tables 237a, 237b ··· are collectively referred to as the destination list table 237.

[0041] The destination list table 237 has columns of "Status ID", "Status Name", "Normal Transition Destination Status ID", "Normal Transition Destination Status Name", "Abnormal Transition Destination Status ID", and "Abnormal Transition Destination Status Name". The destination list table 237 manages the correspondence relationship of the information stored in these columns.

[0042] The "Status ID" is the identification information of the current status that transitions with the execution of resource operations in the corresponding case. The "Status Name" is the name given to the "Status ID".

[0043] The "Normal Transition Destination Status ID" indicates the "Status ID" of the transition destination that transitions from the status identified by the "Status ID" when the storage operation executed in the status of the corresponding record is completed normally. The "Normal Transition Destination Status Name" is the name given to the "Normal Transition Destination Status ID". The "Normal Transition Destination Status ID" and the "Normal Transition Destination Status Name" indicate the status that transitions from each status when the execution of each resource operation represented by each status is completed. Also, the "Normal Transition Destination Status ID" and the "Normal Transition Destination Status Name" indicate the status that transitions from each status when each resource operation represented by each status is completed normally.

[0044] The "Abnormal Transition Destination Status ID" indicates the "Status ID" of the transition destination that transitions from the status identified by the "Status ID" when the storage operation executed in the status of the corresponding record is not completed normally. The "Abnormal Transition Destination Status Name" is the name given to the "Abnormal Transition Destination Status ID". The "Abnormal Transition Destination Status ID" and the "Abnormal Transition Destination Status Name" indicate the status that transitions from each status when the execution of each resource operation represented by each status is completed. Also, the "Abnormal Transition Destination Status ID" and the "Abnormal Transition Destination Status Name" indicate the status that transitions from each status when each resource operation represented by each status is not completed normally and ends.

[0045] Comparing the destination list tables 237a and 237b shown in FIGS. 3A and 3B, the destination list table 237b is different in that the "normal transition destination state ID" corresponding to the "state ID" of "9" is "11" instead of "10". Also, the destination list table 237b is different in that no record with the "state ID" of "10" is defined. The destination list tables 237a and 237b are the same in other respects.

[0046] For example, "Copy to Volume 221" with the "state ID" of "5" in FIG. 3A represents the state of the resource by executing a resource operation to copy data to the second storage via the first volume.

[0047] (Configuration of the storage resource management table 238 according to the embodiment) FIG. 4 is a diagram showing the configuration of the storage resource management table 238 according to the embodiment. The storage resource management table 238 has columns of "project ID", "host name", "RAID group", "pool ID", "volume number", "cloud virtual machine instance ID", "intermediate volume ID", and "snapshot ID".

[0048] The "host name", "RAID group", "pool ID", and "volume number" are information related to the physical server or virtual server to be migrated in the customer's on-premises (not shown) or private cloud.

[0049] The "Case ID" is the same as the "Case ID" in the status management table 236. The "Host Name" is the host name of the on-premises physical server or virtual server to be migrated. The "RAID Group" is the configuration information of the RAID (Redundant Arrays of Inexpensive Disks) of the storage where the volume provided to the on-premises physical server or virtual server to be migrated is stored. The "Pool ID" is the identification information of the pool to which the volume provided to the on-premises physical server or virtual server to be migrated belongs. The "Volume Number" is the identification information of the volume provided to the on-premises physical server or virtual server to be migrated.

[0050] The "Cloud Virtual Machine Instance ID" is the identification information of the instance of the virtual machine 11. The "Intermediate Volume ID" is the identification information of the volume 112, which is the intermediate volume of the virtual machine 11. The "Snapshot ID" is the identification information of the snapshot 121.

[0051] (Status Management Process According to the Embodiment) FIG. 5 is a flowchart showing the status management process according to the embodiment. FIG. 10 is a diagram showing the configuration of the menu screen D1 according to the embodiment. FIG. 11 is a diagram showing the configuration of the case selection screen D2 according to the embodiment.

[0052] First, in step S11, the screen operation status receiving unit 231 displays the following-described menu screen D1 (FIG. 10) on the display screen of the display unit 241 and receives a menu selection by the user via the menu screen D1. In this embodiment, for example, there are three menus: "Normal Transition Destination Specification", "Redo Specification", and "Resource Deletion Inquiry". When the user selects "Normal Transition Destination Specification", the user selects and operates the display D11 (FIG. 10). When the user selects "Redo Specification", the user selects and operates the display D12 (FIG. 10). When the user selects "Resource Deletion Inquiry", the user selects and operates the display D13 (FIG. 10). The selection operation is an operation of the input device of the terminal such as click, tap, return, etc.

[0053] Next, in step S12, the screen operation status receiving unit 231 displays a case selection screen D2 (FIG. 11) described later on the display screen of the display unit 241, and accepts a case selection by the user via the case selection screen D2. The user performs a selection operation on the record of the case to be selected in the case selection display D21 (FIG. 11).

[0054] Next, in step S13, the screen operation status receiving unit 231 determines whether the menu for which the selection was accepted in step S11 is "normal transition destination designation". When the screen operation status receiving unit 231 determines that it is "normal transition destination designation" (step S13 YES), the process proceeds to step S14. On the other hand, when it is "redo designation" or "resource deletion inquiry" (step S13 NO), the process proceeds to step S15.

[0055] In step S14, the state management unit 234 executes a normal transition destination designation process, the details of which will be described later with reference to FIG. 6.

[0056] In step S15, the screen operation status receiving unit 231 determines whether the menu for which the selection was accepted in step S11 is "redo designation". When the screen operation status receiving unit 231 determines that it is "redo designation" (step S15 YES), the process proceeds to step S16. On the other hand, when it is "resource deletion inquiry" (step S15 NO), the process proceeds to step S17.

[0057] In step S16, the state management unit 234 executes an abnormal transition destination designation process, the details of which will be described later with reference to FIG. 8. In step S17, the state management unit 234 executes a deletion determination process, the details of which will be described later with reference to FIG. 9.

[0058] (Normal transition destination designation process according to the embodiment) FIG. 6 is a flowchart showing the normal transition destination designation process according to the embodiment. FIG. 12 is a diagram showing the configuration of the normal transition instruction screen D3 according to the embodiment. The normal transition destination designation process is executed with the current state ID of the target case stored in the state management table 236 as the starting state. When the normal transition destination designation process is executed for the first time for the target case, the current state ID of the target case stored in the state management table 236 is "1".

[0059] First, in step S14a, the state management unit 234 identifies the case type selected in step S12. Next, in step S14b, the state management unit 234 refers to the transition destination list table 237 corresponding to the case type identified in step S14a, identifies the normal transition destination state ID based on the current state ID, and sets the identified normal transition destination state ID as the new current state ID.

[0060] Next, in step S14c, the state management unit 234 displays the normal transition destination state display D31 of the normal transition instruction screen D3 (FIG. 12) corresponding to the abnormal transition destination state ID identified in step S14b on the display screen of the display unit 241. Next, in step S14d, the state management unit 234 determines whether the OK button of the normal transition destination state display D31 has been pressed. When the OK button of the normal transition destination state display D31 is pressed (step S14d YES), the state management unit 234 moves the process to step S14e. On the other hand, when the Cancel button of the normal transition destination state display D31 is pressed (step S14d NO), the state management unit 234 ends the normal transition destination designation process.

[0061] In step S14e, the state management unit 234 executes a case continuation process, the details of which will be described later with reference to FIG. 7.

[0062] (Case continuation process according to the embodiment) FIG. 7 is a flowchart showing the case continuation process according to the embodiment. In the case continuation process, with reference to the transition destination list table 237 for each case type, after executing the storage operation corresponding to the current state ID, the corresponding normal completion transition destination state ID or abnormal completion transition destination state ID is obtained according to normal completion and abnormal completion. Then, the storage operation corresponding to the obtained state ID is executed. After the execution of this storage operation, the corresponding normal completion transition destination state ID or abnormal completion transition destination state ID is obtained according to normal completion and abnormal completion. Thus, the case continuation process is a process of executing a series of storage operations defined in the transition destination list table 237 while transitioning the current state based on the normal completion transition destination state ID and the abnormal completion transition destination state ID.

[0063] First, in step S14e1, the state management unit 234 updates the state ID and the last update date and time of the corresponding case ID in the state management table 236. The state management unit 234 updates the state management table 236 with the current state ID and the current date and time corresponding to either the normal completion transition destination state ID (specified in steps S14b and S14e7) or the abnormal completion transition destination state ID (specified in steps S16b and S14e8).

[0064] Next, in step S14e2, the state management unit 234 determines whether the state ID updated in step S14e1 corresponds to, for example, "11" which is defined as the "completion state" in the transition destination list table 237 corresponding to the case type selected in step S14b or S16a. When the updated state ID is "11" (step S14e2 YES), the state management unit 234 ends the case continuation process, and when it is other than "11" (step S14e2 NO), the process proceeds to step S14e3.

[0065] Next, in step S14e3, the state management unit 234 refers to the transition destination list table and acquires the state name based on the state ID after the update in step S14e1. Next, in step S14e4, the state management unit 234 sends an instruction for a storage operation corresponding to the state name acquired in step S14e3 to either the storage operation instruction units 132, 252 of the aggregation servers 13, 25. The instruction for the storage operation is sent to the storage operation instruction unit 132 of the aggregation server 13 when the storage operation is mainly executed by the private cloud infrastructure 1 with state IDs such as "1" to "3", "12". Also, the instruction for the storage operation is sent to the storage operation instruction unit 252 of the aggregation server 25 when the storage operation is mainly executed by the public cloud infrastructure 2 with state IDs such as "4" to "11", "13". In this way, the state management unit 234 executes a resource operation corresponding to the state determined to transition from the current state.

[0066] Next, in step S14e5, the state management unit 234 receives a notification of the completion status of the storage operation obtained in response to the execution of the storage operation from the storage operation completion status notification units 131, 251 of the aggregation servers 13, 25 to which the storage operation was sent in step S14e4. The notification of the completion status of the storage operation (storage operation completion status notification) includes information on whether the storage operation instructed to be executed was completed normally. The storage operation completion status notification is an example of the execution result of the storage operation.

[0067] Next, in step S14e6, the state management unit 234 determines whether the storage operation completion status notification received in step S14e5 indicates normal completion of the storage operation. When the storage operation completion status notification indicates normal completion of the storage operation (step S14e6 YES), the state management unit 234 transfers the process to step S14e7, and when it indicates other than normal completion (abnormality, etc.) (step S14e6 NO), the state management unit 234 transfers the process to step S14e8.

[0068] In step S14e7, the state management unit 234 executes the same processing as in step S14b (FIG. 6). On the other hand, in step S14e8, the state management unit 234 refers to the transition destination list table 237 corresponding to the case type, specifies the abnormal transition destination state ID based on the current state ID, and sets the specified abnormal transition destination state ID as the new current state ID. When step S14e7 or S14e8 ends, the state management unit 234 transfers the processing to step S14e1.

[0069] Note that in the case of NO in step S14e6, the state management unit 234 may display on the display screen that the storage operation has not been completed normally, the state ID of the result of the storage operation that has been completed normally so far, and the corresponding state. Further, in the case of NO in step S14e6, the state management unit 234 may end the case continuation process.

[0070] Further, when the number of times the determination of NO in step S14e6 exceeds the threshold, the state management unit 234 may end the case continuation process without transferring the processing to step S14e8. For example, when the number of times the determination of NO in step S14e6 for the same state ID exceeds the threshold, the state management unit 234 may end the case continuation process without transferring the processing to step S14e8.

[0071] (Abnormal Transition Destination Designation Process According to Embodiment) FIG. 8 is a flowchart showing the abnormal transition destination designation process according to the embodiment. FIG. 13 is a diagram showing the configuration of the retry instruction screen D4 according to the embodiment. The abnormal transition destination designation process is executed to retry the storage operation when the storage operation included in the operation for a certain case has not been normally completed and the execution of the operation has stopped midway, or when there has been a user's incorrect operation.

[0072] First, in step S16a, the state management unit 234 specifies the case type selected in step S12. Next, in step S16b, the state management unit 234 refers to the transition destination list table 237 corresponding to the case type specified in step S16a, and specifies the abnormal transition destination state ID based on the current state ID.

[0073] Next, in step S16c, the state management unit 234 displays a retry instruction screen D4 (FIG. 13) corresponding to the abnormal transition destination state ID specified in step S16b on the display screen of the display unit 241. On the retry instruction screen D4, based on the "abnormal transition destination state name" in the transition destination list table 237, it may be displayed how many states to return to for a retry and whether it is necessary to re-acquire the snapshot 121.

[0074] Next, in step S16d, the state management unit 234 determines whether the OK button of the retry instruction display D41 on the retry instruction screen D4 has been pressed. When the OK button of the retry instruction display D41 is pressed (step S16d YES), the state management unit 234 transfers the process to step S16e. On the other hand, when the Cancel button of the retry instruction display D41 is pressed (step S16d NO), the state management unit 234 ends the abnormal transition destination designation process.

[0075] In step S16e, the state management unit 234 executes the case continuation process that has already been described in detail with reference to FIG. 7.

[0076] (Deletion determination process according to the embodiment) FIG. 9 is a flowchart showing the deletion determination process according to the embodiment. FIG. 14 is a diagram showing the configuration of a deletable display screen D5 according to the embodiment. FIG. 15 is a diagram showing the configuration of a non-deletable display screen D6 according to the embodiment.

[0077] First, in step S17a, the state management unit 234 refers to the state management table 236 and acquires the current state ID.

[0078] Next, in step S17b, the state management unit 234 determines whether the current state obtained in step S17b is a state in which volume 112 and snapshot 121 can be deleted or a state in which only snapshot 121 can be deleted. The state in which volume 112 and snapshot 121 can be deleted is the case where the state ID is from "1" to "5" in the transition destination list table 237 according to the case type. The state in which only snapshot 121 can be deleted without deleting volume 112 is the case where the state ID is "6" or "7" in the transition destination list table 237 according to the case type.

[0079] When the current state is a state in which volume 112 and snapshot 121 can be deleted or a state in which only snapshot 121 can be deleted (step S17b YES), the state management unit 234 transfers the process to step S17c. On the other hand, when deletion is impossible in either case (step S17b NO), the state management unit 234 transfers the process to step S17d.

[0080] In step S17c, the state management unit 234 displays a deletable display screen D5 (Fig. 14) indicating that the intermediate volume and snapshot 121 or only snapshot 121 can be deleted according to the current state ID on the display screen of the display unit 241. At this time, the state management unit 234 also displays the current state on the display screen of the display unit 241.

[0081] On the other hand, in step S17d, the state management unit 234 displays an undeleteable display screen D6 (Fig. 15) indicating that neither volume 112 nor snapshot 121 can be deleted with the current state ID on the display screen of the display unit 241. At this time, the state management unit 234 also displays the current state on the display screen of the display unit 241. Also at this time, the state management unit 234 may hold in which period (state) deletion is possible. When step S17c or S17d ends, the state management unit 234 transfers the process to step S17e.

[0082] In the case of an operation method that uses only the volume 112 and does not use the snapshot 121, it is determined whether only the volume 112 can be deleted, and this determination result is displayed.

[0083] In step S17e, the state management unit 234 determines whether the OK button of the deletable display D51 on the deletable display screen D5 or the non - deletable display D61 on the non - deletable display screen D6 has been pressed. The state management unit 234 waits until the OK button of the deletable display D51 or the non - deletable display D61 is pressed (step S17e NO), and ends the deletion determination process when the OK button is pressed (step S17e YES). When the OK button of the deletable display D51 is pressed, the state management unit 234 may send a deletion instruction for the intermediate volume and the snapshot 121 or only the snapshot 121 to the storage operation instruction unit 252. When receiving this deletion instruction, the storage operation instruction unit 252 instructs the storage 21 to delete the corresponding intermediate volume and the snapshot 121 or only the snapshot 121.

[0084] (Effect of the Embodiment) In this embodiment, based on the transition destination list table 237, the transition destination to transition from the current state is determined. Therefore, by defining the state transition destination according to the type of operation consisting of a plurality of resource operations, it is possible to manage the states of a plurality of operations with different types. Also, since it can be easily determined from which state the execution start or restart of each operation should be started, the operation can be easily executed.

[0085] Also in this embodiment, based on the transition destination list table 237, either the normal - time transition destination state to which it transitions when the resource operation corresponding to the current state is normally completed or the abnormal - time transition destination state to which it transitions when the resource operation is abnormally completed is determined as the transition destination, and the corresponding resource operation is executed. Therefore, it can be easily determined which state should be transitioned to next according to the normal completion and abnormal completion of the resource operation, and the operation can be automatically performed.

[0086] Also, in the present embodiment, when the abnormal transition destination state is acquired based on the execution result of each resource operation of the operation and the transition destination list table 237, the current state and the abnormal transition destination state are displayed on the retry instruction screen D4. Therefore, it can be easily determined to what state the operation can be retried.

[0087] Also, in the present embodiment, based on the current state, it is determined whether the first volume (volume 112) and the snapshot 121 or only the snapshot 121 can be deleted. Then, the determination result as to whether the first volume can be deleted is displayed on the deletable display screen D5 or the non-deletable display screen D6 together with the current state. Therefore, in the current state, it can be easily determined whether it is possible to delete the source first volume and the snapshot 121 or only the snapshot 121.

[0088] In the present embodiment, the operation is migration. Therefore, the present embodiment can be applied to the case of migrating data from a storage device on-premises to a storage device in a public cloud via an intermediate volume in a customer-managed private cloud. Also, in the present embodiment, the operation is secondary use. Therefore, the present embodiment can be applied to the secondary use of the data stored in the intermediate volume when migrating data from a storage device on-premises to a storage device in a public cloud via an intermediate volume in a customer-managed private cloud.

[0089] (Configuration of the hardware of the computer 1000) FIG. 16 is a diagram showing the hardware configuration of the computer 100. The computer 1000 realizes each server and storage (FIG. 1) of the private cloud infrastructure 1 and the public cloud infrastructure 2, various input / output terminals, etc. by executing a predetermined program.

[0090] The computer 1000 includes a processor 1001 including a CPU, a main memory device 1002, an auxiliary storage device 1003, a network interface 1004, an input device 1005, and an output device 1006, which are interconnected via an internal communication line 1007 such as a bus.

[0091] The processor 1001 controls the operation of the entire computer 1000. The main memory device 1002 is composed of, for example, a volatile semiconductor memory and is used as a work memory of the processor 1001. The auxiliary storage device 1003 is composed of a large-capacity non-volatile storage device such as a hard disk device, an SSD (Solid State Drive), or a flash memory, and is used to hold various programs and data for a long period of time.

[0092] The executable program 1003a stored in the auxiliary storage device 1003 is loaded into the main memory device 1002 when the computer 1000 is started up or when necessary, and is executed by the processor 1001.

[0093] Note that the executable program 1003a may be recorded on a non-transitory recording medium, read from the non-transitory recording medium by a medium reading device, and loaded into the main memory device 1002. Alternatively, the executable program 1003a may be acquired from an external computer via a network and loaded into the main memory device 1002.

[0094] The auxiliary storage device 1003 stores an executable program 1003a that realizes each server and storage of the private cloud infrastructure 1 and the public cloud infrastructure 2.

[0095] The network interface 1004 is an interface device for connecting the computer 1000 to each network in the system or for communicating with other computers. The network interface 1004 is composed of, for example, a NIC (Network Interface Card) such as a wired LAN (Local Area Network) or a wireless LAN.

[0096] The input device 1005 is composed of a keyboard, a pointing device such as a mouse, etc., and is used for a user to input various instructions and information into the computer 1000. The output device 1006 is composed of, for example, a display device such as a liquid crystal display or an organic EL (Electro Luminescence) display, and an audio output device such as a speaker, and is used to present necessary information to the user when necessary.

[0097] Although the embodiments according to the present disclosure have been described in detail above, the present disclosure is not limited to the above-described embodiments, and various modifications can be made without departing from the gist thereof. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described. Also, for a part of the configurations of the above-described embodiments, addition, deletion, or replacement with other configurations is possible.

[0098] Also, each of the above-described configurations, functional units, processing units, etc. may be realized in hardware by designing a part or all of them, for example, by an integrated circuit. Also, each of the above-described configurations, functions, etc. may be realized in software by a processor interpreting and executing a program for realizing each function. Information such as a program, table, file, etc. for realizing each function can be placed in a storage device such as a memory, HDD, SSD, etc., or a recording medium such as an IC card, SD card, DVD.

[0099] Also, in each of the above-described figures, control lines and information lines show those considered necessary for explanation, and do not necessarily show all the control lines and information lines in actual implementation. For example, it may be considered that almost all the configurations are actually connected to each other.

[0100] Also, each of the above-described processing functions and data arrangement forms is merely an example. Each processing function and data arrangement form can be changed to an optimal arrangement form from viewpoints such as the performance of hardware and software, processing efficiency, and communication efficiency.

Description of Reference Numerals

[0101] S: Cloud system, 1: Private cloud infrastructure, 2: Public cloud infrastructure, 11: Virtual machine, 12: Storage, 21: Storage, 22: SDS cluster, 100: Computer, 112: Volume, 121: Snapshot, 131: Storage operation completion status notification unit, 221: Volume, 236: Status management table, 237, 237a, 237b: Transition destination list table, 241: Display unit, 1000: Computer, 1001: Processor, 1002: Main memory device.

Claims

1. A storage system that has resources including a first storage and a second storage on the cloud and executes an operation composed of a plurality of resource operations including a resource operation of copying data stored in a server located at another site to the second storage via a first volume provided by the first storage, wherein the storage system has a processor and a memory, the processor, for each type of the operation, manages a correspondence relationship between each state of the resources associated with the execution of each resource operation and a transition destination state indicating the state to which each state transitions when the execution of each resource operation ends, executes the resource operations included in the operation, manages a current state that is the state of the resources associated with the execution of the resource operation, obtains an execution result indicating whether the execution of the resource operation has been completed normally, obtains the transition destination state associated with the current state based on the execution result and the correspondence relationship, and determines the state to transition from the current state based on the obtained transition destination state characterized by a storage system.

2. The storage system according to claim 1, wherein the processor, for each type of the operation, manages the correspondence relationship between each state, a normal-time transition destination state indicating the state to which each state transitions when each resource operation ends normally, and an abnormal-time transition destination state indicating the state to which each state transitions when each resource operation ends without completing normally, obtains the normal-time transition destination state or the abnormal-time transition destination state associated with the current state based on the execution result and the correspondence relationship, determines the state to transition from the current state based on the obtained normal-time transition destination state or abnormal-time transition destination state, and executes the resource operation corresponding to the state determined to transition from the current state characterized by a storage system.

3. The storage system according to claim 2, wherein the processor, when obtaining the abnormal-time transition destination state based on the execution result and the correspondence relationship, displays the current state and the abnormal-time transition destination state on a display screen characterized by a storage system.

4. The storage system according to claim 1, wherein the processor, Based on the current state, determine whether the first volume can be deleted, and display the determination result as to whether the first volume can be deleted on a display screen together with the current state. A storage system characterized by the above.

5. A storage system according to claim 4, wherein the processor creates a snapshot of the data when copying the data from the first volume to the second storage, copies the snapshot from the first storage to the second storage, based on the current state, determines whether the first volume and the snapshot can be deleted or only the snapshot can be deleted, and displays the determination result as to whether the first volume and the snapshot can be deleted or only the snapshot can be deleted on a display screen together with the current state. A storage system characterized by the above.

6. A storage system according to claim 1, wherein the operation is the migration of the data from the first storage to the second storage. A storage system characterized by the above.

7. A storage system according to claim 1, wherein the operation is the secondary use of the data stored in the first storage for purposes other than the copy of the data. A storage system characterized by the above.

8. A method for managing the state of a resource operation executed by a storage system that executes an operation including a plurality of resource operations including a resource operation of copying data stored in a server located at another site to a second storage via a first volume provided by the first storage, the storage system having a resource including a first storage and a second storage on a cloud, wherein the storage system has a processor and a memory, and the processor manages, for each type of the operation, the correspondence between each state of the resource associated with the execution of each resource operation and the transition destination state indicating the state to which each state transitions when the execution of each resource operation ends, executes the resource operation included in the operation, manages the current state that is the state of the resource associated with the execution of the resource operation, and obtains an execution result indicating whether the execution of the resource operation has been completed normally. Based on the execution result and the correspondence relationship, obtain the transition destination state associated with the current state. Based on the obtained transition destination state, determine the state to transition from the current state. A method for managing the state of resource operations, characterized by having each process.

9. The method for managing the state of resource operations according to claim 8, wherein the processor manages the correspondence relationship between each state, the normal transition destination state indicating the state to transition from each state when each resource operation is completed normally, and the abnormal transition destination state indicating the state to transition from each state when each resource operation ends without being completed normally, for each type of operation. Based on the execution result and the correspondence relationship, obtain the normal transition destination state or the abnormal transition destination state associated with the current state. Based on the obtained normal transition destination state or abnormal transition destination state, determine the state to transition from the current state. Execute the resource operation corresponding to the state determined to transition from the current state. A method for managing the state of resource operations, characterized by having each process.

10. The method for managing the state of resource operations according to claim 8, wherein the processor determines whether the first volume is deletable based on the current state. Display the determination result of whether the first volume is deletable on the display screen together with the current state. A method for managing the state of resource operations, characterized by having each process.

Images