Management device, management method and management program

Abstract

To restrict a choice that may lead to future impairment.SOLUTION: A management device that manages one or more platforms, each possessing a storage device with one or more volumes, stores a policy table defining policies concerning volumes as resources and policies concerning copying that specify operations to execute data copying onto the resources, an origin table defining the origin within the platform where the operation is executed, and a state table maintaining the state of the origin, where a processor extracts combinations of resources and operations from the combination of policies concerning volumes and policies concerning copying, identifies the origin of the operation from the combination of resources and operations, determines whether the origin is normal, and determines whether the combination of policies concerning volumes and policies concerning copying is one that would cause a failure at the origin determined to be abnormal, and outputs the same.SELECTED DRAWING: Figure 12

Description

[Technical Field]

[0001] The present invention relates to a management device, a management method, and a management program for managing a management target. [Background technology]

[0002] In a hybrid cloud storage environment consisting of various storage systems running on customer data centers and public clouds, operation management is achieved by combining many management tools. A certain operation on the storage is performed using commands from multiple management tools. If a failure occurs in a required management tool or storage function, the user may receive a failure notification long after the operation is performed. In such cases, the administrator may need to take action to recover from the failure.

[0003] Patent Document 1 below discloses a stack management device that manages stacks of virtual resources. When processing of any virtual resource targeted by a stack fails during stack creation, modification, or deletion, this stack management device deletes or retries the entire stack or the virtual resource for which processing failed, and performs a rollback or rollforward. Furthermore, when a virtual resource used in a stack is updated or deleted not only by a stack operation unit but also by an operation other than the stack operation unit, the stack management device reflects the change in the state of the virtual resource in a stack information DB that indicates the state of the virtual resource used in the stack. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-170344 Summary of the Invention [Problem to be solved by the invention]

[0005] In conventional technology, even if an automatic rollback is successful, it takes a long time for the user to receive a notification of the operation failure. Furthermore, rollback is not always successful. It is necessary to know in advance that an operation will fail due to a failure. Furthermore, when a failure is notified to the user, the user looks at the notification and determines which functions are available. However, when operation management is abstracted, such as policy-based, it is not possible to determine which abstract operations can be executed from the details of the failure notification.

[0006] The present invention aims to suppress choices that may lead to future problems. [Means for solving the problem]

[0007] A management device according to a first aspect of the invention disclosed in the present application is a management device that manages one or more platforms each having a storage device with one or more volumes, the management device comprising a processor that executes a program and a storage device that stores the program, the management device managing one or more platforms each having a storage device with one or more volumes, the management device comprising a processor that executes a program and a storage device that stores the program, the storage device stores a policy table, an operation source table, and a status table, the policy table defines a policy related to a volume that becomes a resource and a policy related to the copy that defines an operation to copy data to the resource, the operation source table defines an operation source within the platform that executes the operation, the status table holds the status of the operation source, the processor determines the status of the resource from a combination of the policy related to the volume and the policy related to the copy and an extraction process for extracting a combination of the operations; a specification process for specifying the operation source from the combination of the resources and the operations extracted by the extraction process; a first determination process for determining whether the operation source specified by the specification process is normal by referring to the status table; a second determination process for determining whether a combination of a policy related to the volume and a policy related to the copy is a combination that will cause a failure in the operation source determined to be abnormal by the first determination process; and an output process for outputting the determination result of the second determination process.

[0008] A management device according to a second aspect of the invention disclosed in the present application is a management device that manages one or more platforms, each having a storage device with one or more volumes, and that has a processor that executes a program and a storage device that stores the program, wherein the policy table specifies a policy regarding the volume that will become a resource and a policy regarding the copy that specifies an operation to perform a copy of data on the resource, the operation source table specifies an operation destination within the platform on which the operation is to be performed, and the status table holds the status of the operation destination, and the processor executes an extraction process that extracts a combination of the resource and the policy regarding the volume from a combination of the policy regarding the volume and the policy regarding the copy, a determination process that identifies the operation destination from the combination of the resource and the operation extracted by the extraction process, a first determination process that refers to the status table to determine whether the operation destination identified by the determination process is normal, a second determination process that determines whether the combination of the policy regarding the volume and the policy regarding the copy is a combination that will cause a failure at the operation destination determined to be abnormal by the first determination process, and an output process that outputs the determination result of the second determination process. [Effects of the Invention]

[0009] According to the exemplary embodiment of the present invention, it is possible to suppress selections that may cause problems in the future. Problems, configurations, and effects other than those described above will become apparent from the following description of the examples. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is an explanatory diagram illustrating an example of the configuration of a management system. [Figure 2] FIG. 2 is a block diagram showing an example of the hardware configuration of a computer. [Figure 3] FIG. 3 is a block diagram showing an example of the configuration of the board. [Figure 4] FIG. 4 is an explanatory diagram showing an example of a copy policy table. [Figure 5] FIG. 5 is an explanatory diagram showing an example of a volume policy table. [Figure 6] FIG. 6 is an explanatory diagram illustrating an example of the RTO policy table. [Figure 7] FIG. 7 is an explanatory diagram illustrating an example of the operation source table. [Figure 8] FIG. 8 is an explanatory diagram illustrating an example of the operation destination table. [Figure 9] FIG. 9 is an explanatory diagram illustrating an example of the state table. [Figure 10] FIG. 10 is a flowchart illustrating a status update process performed by the management device. [Figure 11] FIG. 11 is an explanatory diagram illustrating an example of the determination table. [Figure 12] FIG. 12 is a flowchart illustrating an example of a procedure for a failure occurrence policy identification process performed by the management device. [Figure 13] FIG. 13 is an explanatory diagram showing a display screen example 1. [Figure 14] FIG. 14 is an explanatory diagram showing a second example of a display screen. [Figure 15] FIG. 15 is an explanatory diagram showing another example of the operation source table. [Figure 16] FIG. 16 is an explanatory diagram showing another example of the state table. DETAILED DESCRIPTION OF THE INVENTION [Example]

[0011] <Figure 1 Management System> 1 is an explanatory diagram showing an example of the configuration of a management system. The management system 100 has a management device 101 and a base 102. The management device 101 and the bases 102, and the bases 102 themselves, are communicatively connected via a network such as the Internet, a LAN (Local Area Network), or a WAN (Wide Area Network). The management device 101 is a computer that manages the base 102. The base 102 is a computer that has a storage device.

[0012] <Figure 2: Example of hardware configuration of computer (management device 101)> FIG. 2 is a block diagram showing an example of the hardware configuration of a computer. The computer 200 includes a processor 201, a storage device 202, an input device 203, an output device 204, and a communication interface (communication IF) 205. The processor 201, the storage device 202, the input device 203, the output device 204, and the communication IF 205 are connected via a bus 206. The processor 201 controls the computer 200. The storage device 202 serves as a working area for the processor 201. The storage device 202 is a non-transitory or temporary recording medium that stores various programs and data. Examples of the storage device 202 include a read-only memory (ROM), a random access memory (RAM), a hard disk drive (HDD), and a flash memory. The input device 203 inputs data. Examples of the input device 203 include a keyboard, a mouse, a touch panel, a numeric keypad, a scanner, a microphone, and a sensor. The output device 204 outputs data. The output device 204 may be, for example, a display, a printer, or a speaker. The communication IF 205 connects to the network 103 and transmits and receives data.

[0013] <Figure 3: Example of the configuration of the base 102> Fig. 3 is a block diagram showing an example of the configuration of the boards 102. In Fig. 3, the explanation will be given assuming that there are three boards 102, but there may be two, four or more boards 102. In order to distinguish between the three boards 102, they are assigned sub-numbers 102-1 to 102-3.

[0014] The boards 102-1 to 102-3 have monitoring tools W1 to W3, respectively. When the monitoring tools W1 to W3 are not distinguished from one another, they are referred to as monitoring tool W. The board 102-1 has management tools M1, M2, and M2-1. The board 102-2 has management tools M3 and M2-2. The board 102-3 has management tools M4 and M2-3. When the management tools M1, M2, M2-1 to M2-3, M3, and M4 are not distinguished from one another, they are referred to as management tool M. When the management tools M2-1 to M2-3 are not distinguished from one another, they are referred to as management tool M2. The monitoring tools W and management tool M may run on a single computer, or may run on separate computers.

[0015] The platform 102-3 includes a management console MC, which is a tool for managing the cloud provided by a cloud vendor.

[0016] The boards 102-1 to 102-3 have storage devices ST1 to ST3, respectively. When the storage devices ST1 to ST3 are not distinguished from one another, they are referred to as storage device ST. Storage device ST1 has volumes V1 and V2, and an inter-device connector C1. Storage device ST2 has a volume V3 and an inter-device connector C2. Storage device ST3 has a volume V4 and an inter-device connector C3. When the volumes V1 to V4 are not distinguished from one another, they are referred to as volume V. When the inter-device connectors C1 to C3 are not distinguished from one another, they are referred to as inter-device connector C.

[0017] The monitoring tool W is a program that monitors the status of components in the platform 102 that holds the monitoring tool W. A component is a structural element in the storage device ST, such as a volume V or an inter-device connector C.

[0018] The management tool M is a program that executes operations on the storage apparatus ST, either by itself or in combination with other management tools M. Operations on the storage apparatus ST include, for example, provisioning, copy source pair operations, copy destination pair operations, and snapshots.

[0019] Provisioning is a process of generating a storage area of ​​a specified capacity from volume V. A copy source pair operation is a process of setting a specified volume as the copy source of a copy operation. A copy destination pair operation is a process of setting a volume as the copy destination of a copy operation. A snapshot is a process of creating a replica of the provisioned storage area in the storage device ST.

[0020] <Figure 4 Copy Policy Table> 4 is an explanatory diagram showing an example of a copy policy table 400. The copy policy table 400 is a table for managing data copying policies, and is held in the management device 101.

[0021] The copy policy table 400 has the following fields: copy policy 401, resource type 402, and operation 403. The copy policy 401 indicates the type of copy policy. The copy policy 401 is a policy related to copying data, and includes, for example, remote copy and snapshot. Remote copy is a process of replicating data in a storage apparatus ST to another storage apparatus ST. The resource type 402 indicates the type of resource used in the copy policy 401. The operation 403 is a process applied in the copy policy 401 using a resource of the resource type 402.

[0022] <Figure 5 Volume Policy Table> 5 is an explanatory diagram showing an example of a volume policy table 500. The volume policy table 500 is a table for managing policies regarding the volume V, and is held in the management device 101.

[0023] The volume policy table 500 has the following fields: volume policy 501, resource 502, and type 503. The volume policy 501 is a policy related to volume V, and is classified into, for example, gold, silver, and bronze. Storage devices with better performance are allocated in the order of gold, silver, and bronze.

[0024] Resources 502 are resources used in volume policies 501. Type 503 indicates which resource type 402 the resource 502 corresponds to, i.e., whether it is a copy source or a copy destination. Note that volume policies 501 are not limited to the three types of gold, silver, and bronze.

[0025] <Figure 6 RTO policy table> 6 is an explanatory diagram showing an example of an RTO policy table. The RTO policy table 600 is a table for managing policies related to RTO (Recovery Time Objective), and is held in the management device 101. The RTO policy table 600 has an RTO policy 601 and a resource 602 as fields.

[0026] The RTO policy 601 is classified into, for example, gold, silver, and bronze, similar to the volume policy 501. For example, if the RTO policy 601 is gold, the RTO is 10 minutes, if it is silver, the RTO is 30 minutes, and if it is bronze, the RTO is 60 minutes. The resource 602 is a resource used in the RTO policy 601. Specifically, for example, the resource 602 is configured by a combination of a copy source storage apparatus ST and a copy destination storage apparatus ST.

[0027] <Figure 7 Operation source table> 7 is an explanatory diagram showing an example of an operation source table 700. The operation source table 700 is a table that defines the correspondence between an operation 701 and an operation source 702, and is held in the management apparatus 101.

[0028] The operation source table 700 has fields of operation 701 and operation source 702. The operation 701 includes, for example, provisioning, copy source pair operation, copy destination pair operation, and snapshot. The operation source 702 is the entity that executes the operation 701, and is defined for each storage apparatus ST. For example, when a provisioning operation 701 is executed on storage apparatus ST1, the management tool M1 becomes the operation source 702.

[0029] <Figure 8 Operation destination table> 8 is an explanatory diagram showing an example of an operation destination table 800. The operation destination table 800 is a table that defines the correspondence between an operation 701 and an operation destination 802, and is held in the management apparatus 101.

[0030] The operation destination table 800 has fields of an operation 701 and an operation destination 802. The operation destination 802 is an object executed by the operation 701, and is defined for each combination of a storage apparatus ST and a volume N. For example, when the provisioning operation 701 is executed on the volume V1 of the storage apparatus ST1, the volume V1 becomes the operation destination 802. Also, when the copy source pair operation operation 701 is executed on the volume V1 of the storage apparatus ST1, the inter-apparatus connector C1 becomes the operation object.

[0031] <Figure 9 Status table> 9 is an explanatory diagram showing an example of a status table. The status table 900 is a table that holds the status of components, and is held in the management device 101. The status table 900 has fields of component 901, status 902, and estimated recovery time 903.

[0032] A component 901 is a constituent element within the storage apparatus ST, or a management tool M or a management console MC. The constituent elements within the storage apparatus ST are, for example, a volume V or an inter-device connection unit C. A state 902 is the state of the component 901 that changes over time. The state 902 is updated by a monitoring tool W. An estimated recovery time 903 is the time when the state 902 is expected to return to "normal" if it is "abnormal." The estimated recovery time 903 is set by input from the management apparatus 101.

[0033] <Figure 10 Status update process> FIG. 10 is a flowchart showing the status update processing procedure performed by the management device 101.

[0034] (Step S1001) The management apparatus 101 periodically selects an unselected monitoring tool W, or when an update operation input is received, and proceeds to step S1002.

[0035] (Step S1002) The management device 101 queries the selected monitoring tool W about the status 902 of the component 901. The selected monitoring tool W checks the status 902 of the component 901 in that storage device ST and returns the check result to the management device 101.

[0036] (Step S1003) The management apparatus 101 determines whether the confirmation result for each component 901 is "normal" or "abnormal." For components 901 that are determined to be "normal" (step S1003: Yes), the management apparatus 101 proceeds to step S1005. For components 901 that are determined to be "abnormal" (step S1003: No), the management apparatus 101 proceeds to step S1004.

[0037] (Step S1004) The management device 101 determines whether the state determined to be "abnormal" is temporary. For example, it instructs the selected monitoring tool W to recheck. For components 901 that have returned to "normal" after rechecking (step S1004: Yes), the process proceeds to step S1005. For components 901 that remain "abnormal" (step S1003: No), the process proceeds to step S1006.

[0038] (Step S1005) The management apparatus 101 updates the status 902 of the component 901 that has been determined to be "normal" to "normal" and clears the estimated recovery time 903. Then, the process proceeds to step S1007.

[0039] (Step S1006) The management apparatus 101 updates the status 902 of the component 901 that has been determined to be "abnormal" to "abnormal" and clears the estimated recovery time 903. Then, the process proceeds to step S1007.

[0040] (Step S1007) The management device 101 terminates the selected monitoring tool W, and if there is an unselected monitoring tool W, the process returns to step S1001, and if there is no unselected monitoring tool W, the management device 101 terminates the status update process.

[0041] <Figure 11 Judgment table> 11 is an explanatory diagram showing an example of a judgment table 1100. The judgment table 1100 is created when a fault occurrence policy identification process, which will be described later, is executed.

[0042] The judgment table 1100 has the following fields: policy combination 1101, resource 1102, operation 1103, judgment result 1104, faulty component 1105, and predicted recovery time 1106.

[0043] The policy combination 1101 is a combination of a volume policy 501, a copy policy 401, and an RTO policy 601. The resource 1102 is the resource 502 in the volume policy 501 in the policy combination 1101. However, it is not set for entries for which the policy combination 1101 does not exist. The operation 1103 is the operation 403 corresponding to the copy policy 401. However, it is not set for entries for which the policy combination 1101 does not exist.

[0044] The judgment result 1104 is a policy combination in the fault occurrence policy identification process described later. It indicates whether or not an error occurs when the operation 1103 is executed in the step 1101. If an error occurs, NG is recorded, and if no error occurs, OK is recorded.

[0045] A failed component 1105 is the component 901 that has been judged as NG in the judgment result 1104. An estimated recovery time 1106 is the estimated recovery time 903 of the failed component 1105.

[0046] <Figure 12 Failure occurrence policy identification process> 12 is a flowchart showing an example of a procedure for identifying a failure policy by the management device 101. Specifically, in FIG. 12, the management device 101 identifies a policy combination 1101 that will cause a failure in the storage device ST or the management tool M even if the operation 403 is executed.

[0047] (Step S1201) The management device 101 creates a policy combination 1101. Specifically, for example, the management device 101 creates the policy combination 1101 so as to cover all combinations of the volume policy 501, the copy policy 401, and the RTO policy 601.

[0048] (Step S1202) The management apparatus 101 selects one unselected policy combination 1101 and proceeds to step S1203. In step S1214, it is determined whether or not there is an unselected policy combination 1101, and if there is an unselected policy combination 1101, the process returns from step S1214 to step S1202. This loop is executed until there are no unselected combinations 1101.

[0049] (Step S1203) The management apparatus 101 adds the policy combination 1101 selected in step S1202 to a new entry in the decision table 1100, and then proceeds to step S1204.

[0050] (Step S1204) The management apparatus 101 extracts a resource group of the selected policy combination 1101, and proceeds to step S1205. Specifically, for example, the management apparatus 101 extracts the resource 502 of the volume policy 501 in the selected policy combination 1101 as a resource group.

[0051] [Resource group extraction example 1] For example, suppose the selection policy combination 1101 is a combination of "Gold" in the volume policy 501, "Snapshot" in the copy policy 401, and "Gold (10 minutes)" in the RTO policy 601. When the volume policy 501 is "Gold," the resource 502 is "Storage apparatus ST1, volume V1." Furthermore, the resource type 402 for "Snapshot" in the copy policy 401 is only "Copy source volume." Therefore, the resource 502: "Storage apparatus ST1, volume V1" is extracted (see entry 1111).

[0052] [Resource group extraction example 2] Also, the selected policy combination 1101 is a combination of "Silver" in the volume policy 501, "Remote Copy" in the copy policy 401, and "Silver (30 minutes)" in the RTO policy 601. When the volume policy 501 is "Silver", the resources 502 are "Storage device ST1 Volume V2", "Storage device ST3 Volume V3", and "Storage device ST4 Volume V4". These are "Storage device ST2 volume V3" and "Storage device ST3 volume V4."

[0053] Of these, the type 503 of the "storage device ST1 volume V2" of the resource 502 is "copy source", and the type 503 of "storage device ST2 volume V3" and "storage device ST3 volume V4" is "copy destination".

[0054] Furthermore, the resource type 402 of "remote copy" in the copy policy 401 is "source volume" and "destination volume." Therefore, in the entry 1112, the resource 502: "storage apparatus ST1 volume V1" is extracted as the resource type 402 "source volume," and the resource 502: "storage apparatus ST2 volume V3" is extracted as the resource type 402 "destination volume" (see the entry 1112).

[0055] It should be noted that a combination of resource 502: "storage apparatus ST1 volume V1" whose resource type 402 is "copy source volume" and resource 502: "storage apparatus ST3 volume V4" whose resource type 402 is "copy destination volume" is also extracted.

[0056] (Step S1205) The management apparatus 101 selects one unselected resource 1102 from the group of resources of the selected policy combination 1101 extracted in step S1204, and proceeds to step S1206. In step S1213, it is determined whether or not there is an unselected resource 1102, and if there is an unselected resource 1102, the process returns from step S1213 to step S1205. This loop is executed until there are no unselected resources 1102 in the entries of the selected policy combination 1101.

[0057] In the above-described example 1 of extracting a group of resources, the only extracted group of resources in the selection policy combination 1101 (volume policy 501: "Gold," copy policy 401: "Snapshot," and RTO policy 601: "Gold (10 minutes)") is "storage device ST1, volume V1." Therefore, resource 502: "storage device ST1, volume V1" is selected as resource 1102.

[0058] In the case of the above-mentioned resource group extraction example 2, for the selection policy combination 1101 (volume policy 501 "Silver", copy policy 401 "Remote Copy", and RTO policy 601 "Silver (30 minutes)"), the extracted resource groups are a combination of "storage device ST1 volume V1" (copy source volume) and "storage device ST2 volume V3" (copy destination volume), and a combination of "storage device ST1 volume V1" (copy source volume) and "storage device ST3 volume V4" (copy destination volume). Therefore, the above two combinations are selected sequentially as resources 1102.

[0059] (Step S1206) The management device 101 extracts the operation 1103 for the selected resource 1102 in step S1205 from the operation 403 in the copy policy table 400. Specifically, for example, the management device 101 identifies the copy policy 401 of the selected policy combination 1101 that corresponds to the selected resource 1102, and extracts the operation 403 that corresponds to the identified copy policy 401 from the copy policy table 400. The management device 101 then adds the selected resource 1102 and the extracted operation 403 to the new entry, and proceeds to step S1207.

[0060] For example, when the selected resource 1102 is "storage device ST1 volume V1" in resource group extraction example 1, the copy policy 401 of the selected policy combination 1101 is "snapshot." The management device 101 extracts "provisioning and snapshot" from the copy policy table 400 as the operation 403 corresponding to "snapshot," and adds it to the entry 1111.

[0061] Furthermore, when the selected resource 1102 is a combination of "storage device ST1 volume V1" (copy source volume) and "storage device ST2 volume V3" (copy destination volume) in resource group extraction example 2, the copy policy 401 of the selected policy combination 1101 is "remote copy".

[0062] Of the operations 403 corresponding to "remote copy," the management device 101 extracts "source pair operation" as the operation 403 for "storage device ST1 volume V1" (source volume), and extracts "provisioning and destination pair operation" as the operation 403 for "storage device ST2 volume V3" (destination volume), and adds them to entry 1112.

[0063] (Step S1207) The management device 101 refers to the operation source table 700, identifies the operation source 702 that will operate the selected resource 1102 in the extraction operation 403, and proceeds to step S1208. Specifically, for example, the management device 101 identifies the operation 701 that corresponds to the extraction operation 403 in the operation source table 700. The management device 101 identifies the operation source 702 that corresponds to the column of the storage device ST of the selected resource 1102 in the row of the identified operation 701.

[0064] For example, when the selected resource 1102 is "storage device ST1 volume V1" in resource group extraction example 1, the extraction operation 403 is "provisioning and snapshot." Therefore, "management tool M1" is identified as the operation source 702.

[0065] Furthermore, when the selected resource 1102 is a combination of “storage device ST1 volume V1” (source volume) and “storage device ST2 volume V3” (destination volume) in resource group extraction example 2, the extraction operation 403 is “provisioning and source pair operation” and “provisioning and destination pair operation.”

[0066] When the extraction operation 403 is a "copy source pair operation," the operation source 702 that operates on the "storage apparatus ST1 volume V1" (copy source volume) is the "management tool M2 and management tool M2-1" identified by the operation 701: "copy source pair operation" and the storage apparatus ST1. Similarly, "management tool M2" is identified in "provisioning." Therefore, these together identify "management tool M2 and management tool M2-1."

[0067] When the extraction operation 403 is a "copy destination pair operation," the operation source 702 that operates on the "storage apparatus ST2 volume V3" (copy destination volume) is the "management tool M2 and management tool M2-2" identified by the operation 701: "copy destination pair operation" and the storage apparatus ST2. Similarly, in "provisioning," the "management tool M2" is identified. Therefore, combining these, the "management tool M2 and management tool M2-1" is identified.

[0068] (Step S1208) The management device 101 refers to the status table 900 and determines whether the status 902 is "normal" for each of the operation sources 702 (management tool M, management console MC) identified in step S1207. For a management tool M or management console MC whose status 902 is "normal" (step S1208: Yes), the management device 101 proceeds to step S1209, and for a management tool M or management console MC whose status 902 is "abnormal" (step S1208: No), the management device 101 proceeds to step S1212.

[0069] (Step S1209) The management device 101 refers to the operation destination table 800, identifies the operation destination 802 to be operated on by the extraction operation 403 for the selected resource 1102, and proceeds to step S1210. Specifically, for example, the management device 101 identifies the operation 701 that corresponds to the extraction operation 403 in the operation destination table 800. The management device 101 identifies the operation destination 802 that corresponds to the column of the selected resource 1102 in the row of the identified operation 701.

[0070] For example, when the selected resource 1102 is "storage device ST1 volume V1" in resource group extraction example 1, the extraction operation 403 is "snapshot." Therefore, "volume V1" is specified as the operation destination 802.

[0071] Furthermore, when the selected resource 1102 is a combination of “storage device ST1 volume V1” (copy source volume) and “storage device ST2 volume V3” (copy destination volume) in resource group extraction example 2, the extraction operation 403 is “copy source pair operation” and “copy destination pair operation.”

[0072] When the extraction operation 403 is a "copy source pair operation," the operation destination 802 operated on the "storage device ST1 volume V1" (copy source volume) is the "device-to-device connection part C1" identified by the operation 701: "copy source pair operation" and "storage device ST1 volume V1."

[0073] When the extraction operation 403 is a "copy destination pair operation," the operation destination 802 operated on the "storage apparatus ST2 volume V3" (copy destination volume) is the "inter-device connection part C3" identified by the operation 701: "copy destination pair operation" and the "storage apparatus ST2 volume V3."

[0074] (Step S1210) The management apparatus 101 refers to the status table 900 and determines whether the status 902 is "normal" for each of the operation destinations 802 identified in step S1209. For operation destinations 802 whose status 902 is "normal", the management apparatus 101 proceeds to step S1211, and for operation destinations 802 whose status 902 is "abnormal", the management apparatus 101 proceeds to step S1212.

[0075] (Step S1211) The management device 101 records "OK" in the judgment result 1104 of the new entry, and proceeds to step S1213.

[0076] (Step S1212) The management device 101 records "NG" in the judgment result 1104 of the new entry, and records the component 901 whose status 902 is judged to be "abnormal" as the faulty component 1105. Since the component 901 whose status 902 is judged to be "abnormal" in step S1208 is the operation source 702, that is, the management tool M2-2, the faulty component 1105 becomes the management tool M2-2 (see entry 1111).

[0077] The component 901 whose status 902 is determined to be "abnormal" in step S1210 is the operation destination 802, i.e., the volume V of the storage device ST or the device-to-device connector C, and therefore the failed component 1105 is the volume V of the storage device ST or the device-to-device connector C.

[0078] In this way, the management device 101 determines the policy combination 1101 as a combination that will cause a failure in the operation source 702 that was determined to be abnormal in step S1208, or determines the policy combination 1101 as a combination that will cause a failure in the operation destination 802 that was determined to be abnormal in step S1210.

[0079] (Step S1213) The management apparatus 101 determines whether or not there is an unselected resource 1102 among the resource group extracted in step S1204, and if there is an unselected resource 1102, the process returns to step S1205. If there is no unselected resource 1102, the process proceeds to step S1214.

[0080] (Step S1214) The management apparatus 101 determines whether or not there is an unselected policy combination 1101, and if there is an unselected policy combination 1101, the process returns to step S1202. If there is no unselected policy combination 1101, the fault-causing policy identification process ends.

[0081] In this way, the management device 101 identifies a policy combination 1101 that will cause a failure in the storage device ST or the management tool M even if the operation 403 is executed.

[0082] <Figure 13 Display screen 1> 13 is an explanatory diagram showing display screen example 1. Display screen 1300 shown in FIG. 13 is displayed on a display, which is an example of output device 204 of management device 101, or on a display of another computer that can communicate with management device 101. An instruction to display display screen 1300 is received by input device 203 of management device 101, or by input device 203 of another computer that can communicate with management device 101.

[0083] When an operation to display the display screen 1300 is performed, the management device 101 executes the failure occurrence policy identification process of Fig. 12 and then displays the display screen 1300. Fig. 13 is an example of a display screen when a failure occurrence policy is not identified as a result of executing the failure occurrence policy identification process of Fig. 12. Note that the failure occurrence policy identification process of Fig. 12 may be executed in advance, periodically, or after the display screen 1300 is displayed.

[0084] The display screen 1300 has a capacity input area 1301 , a volume policy selection field 1302 , a copy policy selection field 1303 , an RTO policy selection field 1304 , and an execute button 1305 .

[0085] The capacity input area 1301 is an area for accepting input of the capacity of data to be provisioned. The volume policy selection section 1302 is a user interface for accepting selection of the volume policy 501. The copy policy selection section 1303 is a user interface for accepting selection of the copy policy 401. The RTO policy selection section 1304 is a user interface for accepting selection of the RTO policy 601. The execute button 1305 is a user interface for accepting execution of provisioning when pressed.

[0086] By pressing the execute button 1305, the management device 101 executes the provisioning of the capacity input in the capacity input area 1301 in the volume policy selection area 1302 and the copy policy selection area 1303. The policy combination 1101 is selected by the selection unit 1303 and the RTO policy selection unit 1304, and the policy combination 1101 is executed for the resource 1102 specified by the policy combination 1101.

[0087] <Figure 14 Display screen 2> Fig. 14 is an explanatory diagram showing display screen example 2. Fig. 14 is an example of a display screen when a failure occurrence policy is identified as a result of executing the failure occurrence policy identification process of Fig. 12. Fig. 14 is an example of a display screen when a policy combination 1101 (entry 1112 in which the failed component 1105 of Fig. 11 is recorded) of "Silver" in the volume policy 501, "Remote Copy" in the copy policy 401, and "Silver" in the RTO policy 601 is identified as the failure occurrence policy.

[0088] Specifically, for example, in the volume policy selection section 1302, "Silver" of the volume policy 501 is displayed in outline characters, in the copy policy selection section 1303, "Remote Copy" of the copy policy 401 is displayed in outline characters, and in the RTO policy selection section 1304, "Silver" of the RTO policy 601 is displayed in outline characters. If even one outline character is selected, the Execute 1300 button cannot be pressed. Note that the failure occurrence policy may be hidden in the volume policy selection section 1302, copy policy selection section 1303, and RTO policy selection section 1304.

[0089] Furthermore, when a combination of failure occurrence policies is selected, the management apparatus 101 displays failure information 1400 on the display screen 1300. The failure information 1400 displays information including a failed component 1105 and an expected recovery time 1106.

[0090] Thus, according to the first embodiment, the management device 101 manages the policy combination 1101, thereby making it possible to identify the source of operation 702 and the destination of operation 802, and by referring to the status table 900, identifies and displays the policy combination 1101 (fault policy) that will cause a fault even if executed.

[0091] This makes it possible to suppress the user from selecting a policy combination 1101 that will cause a failure. Also, by displaying the policy combination 1101 (fault policy) that will cause a failure even if executed as unexecutable, it is possible to prevent the execution of the operation 701 that will cause a failure. Also, by referring to the fault information 1400, the user can understand which component 901 has the failure. [Example]

[0092] Next, a description will be given of Example 2. In Example 1, the management device 101 specified the management tool M as the operation source 702 in the operation source table 700, but in Example 2, the granularity of the operation source 702 is set finely, and an API (Application Programming Interface) used by the management tool M to execute the operation 701 is specified as the operation source. In Example 2, differences from Example 1 will be mainly described, and a description of common parts with Example 1 will be omitted.

[0093] <Figure 15 Operation source table> 15 is an explanatory diagram showing another example of the operation source table. The operation source table 1500 is a table that defines the correspondence between the operation 701 and the operation source 1502, and is held in the management device 101. The difference from the operation source table 700 in FIG. 7 is the operation source 1502.

[0094] The operation source 702 specifies the management tool M that is the operation source for each storage device ST, while the operation source 1502 specifies the API that the management tool M uses to execute the operation 701 as the operation source. The API includes functions and commands required to execute the operation 701. For example, the operation 7 When 01 is a copy source pair operation, in the storage apparatus ST1, the management tool M2 executes an API called Path setting, while the management tool M2-2 executes an API called Pair setting.

[0095] Furthermore, if operation 701 is provisioning, then in storage device ST1, management tool M1 executes an API called volume creation, but if operation 701 is snapshot, then in storage device ST1, management tool M1 executes an API called snapshot creation, which is different from volume creation.

[0096] <Figure 16 Status table> 16 is an explanatory diagram showing another example of a status table. The status table 1600 is a table that holds the status of components, and is held in the management device 101. The difference from the status table 900 in FIG. 9 is that the component 1601 defines the management tool M and the API used to execute its operation 701, corresponding to FIG. 15.

[0097] As a result, in the failure occurrence policy identification process of FIG. 12, in step S1207, The management device 101 refers to the operation source table 1500, identifies the operation source 1502 that operates the resource 1102 selected in the extraction operation 403, and proceeds to step S1208.

[0098] Furthermore, in step S1208, the management device 101 refers to the status table 1600 and determines whether the status 902 is "normal" for each of the operation sources 1502 identified in step S1207. For the management tool M whose status 902 is "abnormal" (step S1208: No), in step S1212 the management device 101 records "NG" in the judgment result 1104 of the new entry, and records the component 901 (the management tool M and the API used to execute its operation 701) whose status 902 is determined to be "abnormal" as the faulty component 1105.

[0099] In this way, according to the second embodiment, it is possible to identify the faulty component 1105 with finer granularity than in the first embodiment. Therefore, the fault information 1400 on the display screen 1300 in Fig. 14 displays the fault information 1400 as follows: "API of management tool M2-2: temporarily unavailable for selection due to a pair setting error." Therefore, by referring to the fault information 1400, the user can also understand which API of which management tool M has a fault.

[0100] <Variation 1> In the above-described first and second embodiments, a combination of the copy policy 401, the volume policy 501, and the RTO policy 601 is used as the policy combination 1101, but the policy combination 1101 only needs to include at least the copy policy 401 and the volume policy.

[0101] <Variation 2> In the first and second embodiments described above, the management apparatus 101 identifies the operation source 702, 1502 (step S1207), determines whether it is normal or not (step S1208), and identifies the operation destination 802 (step S1209), and determines whether it is normal or not (step S1210). In contrast, the management apparatus 101 may be configured to identify the operation source 702, 1502 (step S1207), determine whether it is normal or not (step S1208), and not execute steps S1209 and S1210. The management apparatus 101 may also be configured to identify the operation destination 802 (step S1209), and determine whether it is normal or not (step S1210) without executing steps S1207 and S1208.

[0102] The present invention is not limited to the above-described embodiments, and includes various modifications and equivalent configurations within the spirit and scope of the appended claims. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to configurations including all of the described configurations. Furthermore, part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Furthermore, the configuration of another embodiment may be added to the configuration of one embodiment. Furthermore, part of the configuration of each embodiment may be added to, deleted from, or replaced with other configurations.

[0103] Furthermore, the aforementioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole in hardware, for example by designing them as integrated circuits, or may be realized in software by a processor interpreting and executing a program that realizes each function.

[0104] Information such as programs, tables, and files that realize each function can be stored in storage devices such as memory, hard disks, and SSDs (Solid State Drives), or on recording media such as IC (Integrated Circuit) cards, SD cards, and DVDs (Digital Versatile Discs).

[0105] In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and do not necessarily show all the control lines and information lines that are necessary for implementation. In reality, it can be considered that almost all components are interconnected. [Explanation of symbols]

[0106] 100 Management Systems 101 Management device 102 Foundation 201 processor 202 Storage Devices 400 Copy Policy Table 401 Copy Policy 403 operations 500 Volume Policy Table 501 Volume Policy 502 resources 600 RTO Policy Table 601 RTO Policy 602 resources 700 Operation Source Table 701 Operation 702 Operation source 800 Operation Destination Table 802 Operation Destination 900 State Table 901 Components 902 Status 903 Estimated restoration time 1100 Decision Table 1105 Faulty Component 1106 Estimated restoration time 1300 display screen 1400 Fault Information 1500 Source table 1502 Operation source 1600 Status Table

Claims

1. A management device that manages one or more platforms each having a storage device with one or more volumes, A processor that executes a program and a storage device that stores the program, the storage device stores a policy table, an operation source table, and a status table; the policy table defines a policy regarding a volume that serves as a resource, and a policy regarding the copy that defines an operation for copying data to the resource; the operation source table defines an operation source in the platform that executes the operation; the state table holds the state of the operation source; The processor: an extraction process of extracting a combination of the resource and the operation from a combination of the policy related to the volume and the policy related to the copy; an identification process for identifying the source of the operation from the combination of the resource and the operation extracted by the extraction process; a first determination process for determining whether the operation source identified by the identification process is normal or not by referring to the status table; a second determination process for determining whether a combination of the policy related to the volume and the policy related to the copy is a combination that will cause a failure in the operation source determined to be abnormal by the first determination process; an output process for outputting a determination result of the second determination process; A management device that executes the above.

2. The management device according to claim 1 , The processor: Execute an update process to monitor the operation source and update the status of the status table; In the first determination process, the processor refers to the latest state table obtained by the update process and determines whether the operation source identified by the identification process is normal. A management device characterized by:

3. The management device according to claim 1 , The operation source is a management program that is installed on the board and manages the board or other boards. A management device characterized by:

4. The management device according to claim 1 , The operation source is a program implemented on the platform and managing the platform or other platforms, and an API used to execute the program. A management device characterized by:

5. The management device according to claim 1 , the policy regarding the volume includes the resource and a type that distinguishes whether the resource is a source of data or a destination of data; The policy regarding the copy includes a resource type that specifies whether the resource to be copied is a copy source or a copy destination, and an operation that executes the copy on a resource of the resource type. A management device characterized by:

6. The management device according to claim 1 , the policy table defines an RTO policy that defines a storage device to which a policy regarding a recovery time objective is applied; the operation source table defines the operation source for each of the storage devices; In the extraction process, the processor extracts the combination of the resource and the operation from a combination of the policy related to the volume, the policy related to the copy, and the policy related to the recovery time objective. A management device characterized by:

7. The management device according to claim 1 , the storage device stores an operation destination table that specifies the operation and an operation destination in the storage device where the operation is to be executed; the state table holds the states of the operation source and the operation destination, The processor: a second identification process for identifying the operation destination for each combination of the resource and the operation extracted by the extraction process; a second determination process for determining whether the operation destination identified by the second determination process is normal or not by referring to the status table; In the second determination process, the processor determines whether or not a combination of the policy related to the volume and the policy related to the copy is a combination that will cause a failure in the operation destination determined to be abnormal by the second determination process. A management device characterized by:

8. The management device according to claim 1 , In the output process, the processor displays the combination in which the failure occurs as unselectable, and displays combinations other than the combination in which the failure occurs as selectable. A management device characterized by:

9. The management device according to claim 1 , In the output process, the processor hides the combination in which the failure occurs and displays combinations other than the combination in which the failure occurs in a selectable manner. A management device characterized by:

10. A management method executed by a management device that manages one or more platforms each having a storage device with one or more volumes, comprising: the management device includes a processor that executes a program and a storage device that stores the program; the storage device stores a policy table, an operation source table, and a status table; the policy table defines a policy regarding a volume that serves as a resource, and a policy regarding the copy that defines an operation for copying data to the resource; the operation source table defines an operation source in the platform that executes the operation; the state table holds the state of the operation source; The processor: an extraction process of extracting a combination of the resource and the operation from a combination of the policy related to the volume and the policy related to the copy; an identification process for identifying the source of the operation from the combination of the resource and the operation extracted by the extraction process; a first determination process for determining whether the operation source identified by the identification process is normal or not by referring to the status table; a second determination process for determining whether a combination of the policy related to the volume and the policy related to the copy is a combination that will cause a failure in the operation source determined to be abnormal by the first determination process; an output process for outputting a determination result of the second determination process; A management method characterized by executing the following.

11. A management program that causes a processor to execute a process for managing one or more platforms each having a storage device with one or more volumes, the processor is capable of accessing a storage device that stores a volume policy table, a copy policy table, an operation source table, and a status table; the storage device stores a policy table, an operation source table, and a status table; the policy table defines a policy regarding a volume that serves as a resource, and a policy regarding the copy that defines an operation for copying data to the resource; the operation source table defines an operation source in the platform that executes the operation; the state table holds the state of the operation source; the processor, an extraction process of extracting a combination of the resource and the operation from a combination of the policy related to the volume and the policy related to the copy; an identification process for identifying the source of the operation from the combination of the resource and the operation extracted by the extraction process; a first determination process for determining whether the operation source identified by the identification process is normal or not by referring to the status table; a second determination process for determining whether a combination of the policy related to the volume and the policy related to the copy is a combination that will cause a failure in the operation source determined to be abnormal by the first determination process; an output process for outputting a determination result of the second determination process; A management program characterized by causing the program to execute the above.

Images