System configuration proposal device, system configuration proposal method, and system configuration proposal program

Abstract

To provide a technique capable of easily and properly proposing a storage system meeting a specified availability level.SOLUTION: A server 10 for proposing information on a system configuration of a storage system to a user comprises a processor and a memory. The memory stores an availability correlation data table 27, which includes availability level information related to availability levels about a plurality of storage systems. The processor is configured to accept conditions including a required availability level for a storage system from the user, identify a storage system candidate satisfying the availability level included in the conditions on the basis of the availability level information, and output information related to the system configuration of the identified storage system candidate.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a technique for proposing a configuration of a storage system. [Background technology]

[0002] When building or considering the operation of a storage system, it is important to ensure availability so that the storage system can continue to operate. However, there is a shortage of skilled engineers who can consider ensuring availability. For this reason, in recent years, there has been a demand for support that allows users to consider ensuring availability without the need for skilled engineers.

[0003] Known as a technology for proposing storage system configuration patterns is, for example, the technology disclosed in Patent Document 1. Patent Document 1 discloses a technology for selecting a system configuration pattern that satisfies a capacity, which is a required condition, and determining the order of proposals using evaluation weighting and evaluation coefficients.

[0004] Furthermore, a technology for evaluating the reliability of a storage system is disclosed in, for example, Non-Patent Document 1. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Publication No. 2020-008944 [Non-patent literature]

[0006] [Non-Patent Document 1] Tomohiro Kawaguchi and Hideo Saito, "Reliability Evaluation Method for Data Center High Availability Systems Using Markkov Chains," IPSJ Technical Report, Vol. 2015-ARC-215 No. 9 Summary of the Invention [Problem to be solved by the invention]

[0007] From the viewpoint of storage system operators, the availability level is important as described above, and there is a demand to provide an appropriate system configuration based on the availability level of such a storage system.

[0008] The present invention has been made in view of the above circumstances, and its object is to provide a technique that can easily and appropriately propose a storage system that satisfies a specified availability level. [Means for solving the problem]

[0009] In order to achieve the above-mentioned object, one aspect of the system configuration proposal device is a system configuration proposal device that proposes information regarding the system configuration of a storage system to a user, the system configuration proposal device comprising a processor and a storage device, the storage device stores availability level information regarding availability levels for a plurality of storage systems, the processor accepts conditions from the user including the availability level required of the storage system, and based on the availability level information, identifies candidate storage systems that satisfy the availability level included in the conditions, and outputs information regarding the system configuration of the identified candidate storage system. [Effects of the Invention]

[0010] According to the present invention, it is possible to easily and appropriately propose a storage system that satisfies a specified availability level. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram showing the overall configuration of a computer system according to one embodiment. [Figure 2] FIG. 2 is a hardware configuration diagram of a server according to an embodiment. [Figure 3] FIG. 3 is a diagram showing the configuration of a failure probability data table according to an embodiment. [Figure 4]FIG. 4 is a diagram showing the structure of a repair probability data table according to an embodiment. [Figure 5] FIG. 5 is a diagram illustrating the configuration of a system model data table according to an embodiment. [Figure 6] FIG. 6 is a diagram illustrating the configuration of an availability correlation data table according to an embodiment. [Figure 7] FIG. 7 is a graph showing the relationship between the maintenance cycle and the availability level in the availability correlation data table according to one embodiment. [Figure 8] FIG. 8 is a diagram showing the configuration of an availability data table according to an embodiment. [Figure 9] FIG. 9 is a diagram showing the structure of a comparison result data table according to one embodiment. [Figure 10] FIG. 10 is a flowchart of a system configuration proposal process according to an embodiment. [Figure 11] FIG. 11 is a first diagram illustrating a system configuration proposal process according to an embodiment. [Figure 12] FIG. 12 is a second diagram illustrating the system configuration proposal process according to an embodiment. [Figure 13] FIG. 13 is a third diagram illustrating the system configuration proposal process according to an embodiment. [Figure 14] FIG. 14 is a fourth diagram illustrating the system configuration proposal process according to an embodiment. [Figure 15] FIG. 15 is a fifth diagram illustrating the system configuration proposal process according to an embodiment. [Figure 16] FIG. 16 is a sixth diagram illustrating the system configuration proposal process according to an embodiment. [Figure 17] FIG. 17 is a diagram showing a first example of a configuration proposal screen according to an embodiment. [Figure 18] FIG. 18 is a diagram illustrating an input area on a configuration proposal screen according to an embodiment. [Figure 19] FIG. 19 is a diagram showing a second example of a configuration proposal screen according to an embodiment. [Figure 20]FIG. 20 is a diagram showing a third example of a configuration proposal screen according to an embodiment. [Figure 21] FIG. 21 is a diagram showing a fourth example of a configuration proposal screen according to an embodiment. [Figure 22] FIG. 22 is a diagram showing a fifth example of a configuration proposal screen according to an embodiment. [Figure 23] FIG. 23 is a diagram showing a sixth example of a configuration proposal screen according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] The following description of the embodiments will be given with reference to the drawings. Note that the embodiments described below do not limit the scope of the invention as claimed, and not all of the elements and combinations thereof described in the embodiments are necessarily essential to the solution of the invention.

[0013] In the following explanation, information may be described using the expression "AAA table", but the information may be expressed in any data structure. In other words, to show that the information does not depend on the data structure, the "AAA table" can be called "AAA information".

[0014] FIG. 1 is a diagram showing the overall configuration of a computer system according to one embodiment.

[0015] The computer system 1 includes a terminal 3 and a data center 5. The terminal 3 and the data center 5 are connected via the Internet 2, which is an example of a network.

[0016] Terminal 3 is a terminal used by a system engineer (SE) as an example of a user. Terminal 3 accepts input of conditions and the like for a desired storage system from the SE, and displays a configuration proposal screen (100A to 100F, see FIGS. 17 to 23) that outputs information about the system configuration of a storage system that meets the conditions.

[0017] The data center 5 includes a switch 6 and a server 10. The switch 6 connects the server 10 to the Internet 2.

[0018] The server 10 is an example of a system configuration proposal device, and includes an availability correlation processing unit 21, an availability processing unit 22, a comparison calculation processing unit 23, a failure probability data table 24, a repair probability data table 25, a system model data table 26, an availability correlation data table 27, an availability data table 28, and a comparison result data table 29.

[0019] The availability correlation processing unit 21 performs a process of calculating the availability levels in multiple storage systems based on the failure probability data table 24, the repair probability data table 25, and the system model data table 26, and performs a process of updating the availability correlation data table 27.

[0020] The availability processing unit 22 refers to the availability correlation data table 27, selects a storage system that satisfies the input conditions, and performs processing to create an availability data table .

[0021] The comparison calculation processing unit 23 refers to the availability data table 28, selects the optimal storage system, stores it in the comparison result data table 29, and performs processing to display the proposal content on the configuration proposal screen (100A to 100F) based on the comparison result data table 29.

[0022] Next, the hardware configuration of the server 10 will be described.

[0023] FIG. 2 is a hardware configuration diagram of a server according to an embodiment.

[0024] The server 10 is configured by a computer such as a general-purpose server, for example. The server 10 includes a communication interface (I / F) 11, a CPU (Central Processing Unit) 12 as an example of a processor, an input device 13, a storage device 14, a memory 15 as an example of a storage device, a display device 16, and a disk drive 17. The communication I / F 11, the CPU 12, the input device 13, the storage device 14, the memory 15, the display device 16, and the disk drive 17 are connected via a bus 18.

[0025] The communication I / F 11 is an interface such as a wired LAN card or a wireless LAN card, and communicates with other devices (for example, the terminal 3) via the switch 6 and the Internet 2.

[0026] The CPU 12 executes various processes according to programs stored in the memory 15 and / or the storage device 14 .

[0027] The memory 15 is, for example, a RAM (RANDOM ACCESS MEMORY), and stores necessary information and programs executed by the CPU 12. In this embodiment, the memory 15 stores a system configuration proposal program 15a, a failure probability data table 24, a repair probability data table 25, a system model data table 26, an availability correlation data table 27, an availability data table 28, and a comparison result data table 29.

[0028] The storage device 14 is, for example, a hard disk or flash memory, and stores programs executed by the CPU 12 and data used by the CPU 12.

[0029] The input device 13 is, for example, a mouse, a keyboard, etc., and accepts information input by a user of the server 10. The display device 16 is, for example, a display, and displays and outputs a screen including various types of information.

[0030] The disk drive 17 reads out programs and data recorded on the recording medium 19. The system configuration proposal program 15a stored in the memory 15 may be read out from the recording medium 19.

[0031] In this embodiment, the CPU 12 executes the system configuration proposal program 15a to configure an availability correlation processing unit 21, an availability processing unit 22, and a comparison calculation processing unit 23.

[0032] Next, the configuration of the failure probability data table 24 will be described.

[0033] FIG. 3 is a diagram showing the configuration of a failure probability data table according to an embodiment.

[0034] The failure probability data table 24 is an example of failure probability information, and stores the failure probability for the components that make up the storage system. The failure probability data table 24 stores an entry for each component. An entry in the failure probability data table 24 includes fields for component 24a and failure probability 24b. The component 24a stores the name of the component corresponding to the entry. The failure probability 24b stores the probability of a failure occurring in the component corresponding to the entry for a predetermined period (e.g., per day).

[0035] Next, the configuration of the repair probability data table 25 will be described.

[0036] FIG. 4 is a diagram showing the structure of a repair probability data table according to an embodiment.

[0037] The repair probability data table 25 stores the repair probability for the components that make up the storage system. Here, repair probability means the probability that a component can be repaired. In this embodiment, the repair probability data table 25 stores the repair probabilities for multiple maintenance cycles for the configuration, capacity, and components of the storage system. An entry in the repair probability data table 25 includes fields for configuration 25a, capacity 25b, component 25c, replacement time 25d, redundancy restoration time 25e, maintenance cycle 25f, and repair probability 25g.

[0038] The configuration 25a stores the redundancy configuration of the storage system corresponding to the entry. The capacity 25b stores the capacity of the storage system corresponding to the entry. The component 25c stores the name of the component corresponding to the entry. The replacement time 25d stores the time required to replace the component corresponding to the entry (replacement time). The replacement time is calculated, for example, based on the actual value of a storage system with the configuration and capacity corresponding to the entry. The redundancy restoration time 25e stores the time required to restore redundancy after replacing a component in a storage system with the configuration and capacity corresponding to the entry (redundancy restoration time). The redundancy restoration time varies depending on the configuration and capacity. The redundancy maintenance cycle 25f stores the cycle (maintenance cycle) at which maintenance is performed on the component corresponding to the entry. In this embodiment, entries corresponding to multiple maintenance cycles are stored for the same configuration, capacity, and component. The repair probability 25g stores the probability (repair probability) that the component corresponding to the entry will be repaired within a predetermined period (e.g., per day). The repair probability can be calculated, for example, using the following formula (1):

[0039] Repair probability [%] = 1 / (replacement time + redundancy restoration time + (maintenance cycle / 2)) (1) In this embodiment, the maintenance cycle is set to 1 / 2 to be the average time.

[0040] In this example, the repair probability is stored in the repair probability data table 25, but it is also possible to calculate the repair probability using equation (1) from the values ​​stored in the repair probability data table without storing it in the repair probability data table.

[0041] Next, the configuration of the system model data table 26 will be described.

[0042] FIG. 5 is a diagram illustrating the configuration of a system model data table according to an embodiment.

[0043] The system model data table 26 stores configuration information for multiple storage systems that can be used as a storage system. The system model data table 26 stores an entry for each storage system. The entry in the system model data table 26 includes fields for a system model 26a, a number of clusters 26b, a redundancy method 26c, a number of nodes 26d, a capacity 26e, a price 26f, and an overview diagram 26g.

[0044] The system model 26a stores the type of system model corresponding to the entry. The system model types include a standalone system that is not connected to other systems, an asynchronous remote copy configuration in which two storage clusters perform asynchronous remote copying, an active-active HA configuration in which both of two duplicated storage clusters can be accessed simultaneously, and a hybrid cloud configuration that includes an on-premise storage cluster and a cloud storage cluster. The number of clusters 26b stores the number of clusters included in the storage system corresponding to the entry. The redundancy method 26c stores the redundancy method in the storage system corresponding to the entry. The number of nodes 26d stores the number of storage nodes in the storage system corresponding to the entry. The capacity 26e stores the capacity of the storage system corresponding to the entry. The price 26f stores the price of the storage system corresponding to the entry. Here, the price can be calculated as a function of capacity, for example, and if the storage system is sold out, the price can be calculated as follows: Price [yen] = Capacity unit price [yen / GB] × Capacity [GB]; if the storage system is used on a subscription basis, the price can be calculated as follows: Price [yen / month] = Capacity unit price per month [yen / GB·month] × Capacity [GB]. The overview diagram 26g stores data on or a link to an overview diagram of the storage system corresponding to the entry.

[0045] Next, the configuration of the availability correlation data table 27 will be described.

[0046] FIG. 6 is a diagram illustrating the configuration of an availability correlation data table according to an embodiment.

[0047] The availability correlation data table 27 is an example of availability level information, and includes an on-premise table 27A and a cloud table 27B. The on-premise table 27A and the cloud table 27B have similar configurations, so only the on-premise table 27A will be described here.

[0048] The on-premise table 27A includes a sub-table 27a that manages the relationship between the number of storage nodes, capacity, and price. In this sub-table 27a, for example, when the number of storage nodes is three, it is understood that the capacity is 50 TB or more and the price is 220 M yen (2.2 million yen) or more.

[0049] The on-premise table 27A includes fields for a system model 27b, a number of clusters 27c, a redundancy method 27d, a maintenance cycle 27e, and an availability level 27f. The system model 27b stores the type of system model corresponding to the entry. The number of clusters 27c stores the number of clusters included in the storage system corresponding to the entry. The redundancy method 27d stores the redundancy method of the storage system corresponding to the entry. The maintenance cycle 27e stores the maintenance cycle. In this embodiment, one or more maintenance cycles are stored for one redundancy method. The availability level 27f stores the availability level for the number of corresponding storage nodes (in the same column) in the configuration corresponding to the entry. According to the on-premise table 27A, when the system model is a single unit, the number of clusters is 1, the redundancy method is Mirroring, and the maintenance cycle is one month, it can be seen that if there are three storage nodes, the availability level is 90.12, and if there are four storage nodes, the availability level is 95.43.

[0050] Next, the correspondence between the maintenance cycle and availability level for each storage system according to the availability correlation data table 27 will be described.

[0051] FIG. 7 is a graph showing the relationship between the maintenance cycle and the availability level in the availability correlation data table according to one embodiment.

[0052] The information in the availability correlation data table 27 shown in Fig. 6 indicates the correspondence between the maintenance cycle and the availability level for each storage system, as shown in Fig. 7. Therefore, the information in the availability correlation data table 27 makes it possible to identify the maintenance cycle that will achieve the desired availability level for each type of storage system.

[0053] Next, the configuration of the availability data table 28 will be described.

[0054] FIG. 8 is a diagram showing the configuration of an availability data table according to an embodiment.

[0055] The availability data table 28 manages information such as availability levels for storage systems that satisfy input conditions. The availability data table 28 stores an entry for each storage system that satisfies the conditions. The entry in the availability data table 28 includes fields for the number of storage nodes 28a, the number of clusters 28b, a redundancy method 28c, a system model 28d, a capacity 28e, a price 28f, a maintenance cycle 28g, and an availability level 28h.

[0056] The number of storage nodes 28a stores the number of storage nodes in the storage system corresponding to the entry. The number of clusters 28b stores the number of clusters included in the storage system corresponding to the entry. The redundancy method 28c stores the redundancy method in the storage system corresponding to the entry. The system model 28d stores the type of system model corresponding to the entry. The capacity 28e stores the capacity of the storage system corresponding to the entry. The price 28f stores the price of the storage system corresponding to the entry. The maintenance cycle 28g stores the maintenance cycle of the storage system corresponding to the entry. The availability level 28h stores the availability level of the storage system corresponding to the entry.

[0057] Next, the configuration of the comparison result data table 29 will be described.

[0058] FIG. 9 is a diagram showing the structure of a comparison result data table according to one embodiment.

[0059] The comparison result data table 29 stores the entry for the storage system with the fewest number of storage nodes among the entries in the availability data table 28, or, if there are multiple entries with the same number of storage nodes, the entry for the storage system with the lowest price. The entries in the comparison result data table 29 include the same fields as those in the availability data table 28.

[0060] Next, the system configuration proposal process of the server 10 will be described.

[0061] Fig. 10 is a flowchart of a system configuration proposal process according to an embodiment. Fig. 11 is a first diagram illustrating the system configuration proposal process according to an embodiment. Fig. 12 is a second diagram illustrating the system configuration proposal process according to an embodiment. Fig. 13 is a third diagram illustrating the system configuration proposal process according to an embodiment. Fig. 14 is a fourth diagram illustrating the system configuration proposal process according to an embodiment. Fig. 15 is a fifth diagram illustrating the system configuration proposal process according to an embodiment. Fig. 16 is a sixth diagram illustrating the system configuration proposal process according to an embodiment.

[0062] In the system configuration proposal process, the availability correlation processor 21 determines whether or not it has received conditions (input values) for a desired storage system input from the terminal 3 as shown in Fig. 11 (S1). As a result, if it has not received the conditions (S1: No), the availability correlation processor 21 proceeds to step S1.

[0063] On the other hand, if a condition has been received (S1: Yes), the availability correlation processing unit 21 accepts the received condition (S2).

[0064] Next, the availability correlation processor 21 reads the failure probability data table 24, the repair probability data table 25, and the system model data table 26, as shown in Fig. 12, and updates the availability correlation data table 27 based on these tables, as shown in Fig. 13 (S3). In this process, the availability correlation processor 21 executes a process of calculating the availability level of each storage system.

[0065] Here, a method for calculating the availability level in each storage system will be explained. In this embodiment, an absorbing Markov chain model is used. A Markov chain is a model that represents a probabilistic transition from one state to another, and expresses the probability of progressing from the current state to the next state. An absorbing Markov chain is a chain that, once it reaches a specific state, is "absorbed" into that state and does not progress to another state. By using an absorbing Markov chain model in this way, it is possible to calculate the expected time required to progress from the initial state to the absorbing state.

[0066] Specifically, an absorbing Markov chain model is created by listing all possible states for the system configuration of the storage system and expressing the transition probability between any of these states using the failure probability and repair probability of the components that occur per unit time. In this case, states resulting from data loss or system shutdown are treated as absorbing states that cannot transition to other states. In other words, they are states that transition to the same state with a probability of 1. For the failure probability, values ​​from failure probability data table 24 are used. For the repair probability, values ​​from repair probability data table 25 are used. The absorbing Markov chain model is then used to calculate the expected time from the initial state to the absorbing state, and the availability level is calculated by taking the reciprocal of the expected time. For example, for storage systems with the same system configuration, the availability level for each maintenance cycle can be calculated by using the corresponding repair probability for each maintenance cycle.

[0067] Next, the availability processing unit 22, as shown in FIG. 14, refers to the availability correlation data table 27 and registers entries for storage systems that satisfy the accepted conditions in the availability data table 28 (S4).

[0068] Next, the comparison calculation processing unit 23 determines whether or not an entry with a configuration that satisfies the conditions exists in the availability data table 28 (S5).

[0069] As a result, if an entry exists in the availability data table 28 (S5: Yes), the comparison calculation processing unit 23 identifies an entry for an appropriate storage system from the availability data table 28, for example, a storage system with a small number of storage nodes, and stores it in the comparison result data table 29 (S6), and displays a configuration proposal screen (100A, 100B, 100D-100F) including information showing the configuration of the storage system based on the comparison result data table 29 (S7), and proceeds to step S1. Thereafter, each time a condition is input (changed) on the configuration proposal screen, the subsequent steps are executed, and processing is performed to update the configuration proposal screen in real time.

[0070] On the other hand, if there is no entry in the availability data table 28 (S5: No), the comparison calculation processing unit 23 displays a configuration proposal screen (e.g., 100C) containing information indicating that there was no configuration that met the conditions (S8), and proceeds to step S1.

[0071] Next, an example of a configuration proposal screen displayed by the comparison calculation processing unit 23 will be described.

[0072] Fig. 17 is a diagram showing a first example of a configuration proposal screen according to an embodiment. Fig. 18 is a diagram illustrating an input area of ​​the configuration proposal screen according to an embodiment. The configuration proposal screen 100A shown in Fig. 17 is an example of a configuration proposal screen when only required input items are specified as conditions, for example, when an availability level of 99.9% is specified.

[0073] The configuration proposal screen 100A includes an input area 110 and a proposed configuration display area 120. The input area 110 is an area where the user inputs conditions for the desired storage system, and includes a required input item area 111 and an optional input item area 112.

[0074] The required input item area 111 is an area for inputting required conditions. In this embodiment, the required conditions are availability levels.

[0075] The required input item area 111 includes a gauge 211, a unit selection area 213, and a candidate display button 214. The gauge 211 is a gauge that displays a specifiable availability level value, and displays the minimum and maximum specifiable values. The gauge 211 includes a bar 212 that indicates the specified value. The specified availability level value is displayed on the bar 212. The user can easily change the specified availability level by changing the size of the bar 212 using an input device. In this embodiment, when the specified availability level is changed, a system configuration proposal process is executed, and the display content of the proposed configuration display area 120 is updated in real time.

[0076] The selected unit for the availability level is displayed in unit selection area 213. Candidate display button 214 is a button that accepts the display of selectable units for the availability level. When candidate display button 214 is pressed, a plurality of unit candidates are displayed in unit selection area 213, as shown in FIG. 18.

[0077] For example, in this embodiment, when "minutes / months" or "hours / years" is selected in the unit selection area 213, an input area 215 for the allowable downtime, which is an example of an availability level, is displayed, as shown in FIG. 18.

[0078] The optional input item area 112 is an area where the user can input any conditions that can be specified. In this embodiment, the optional conditions include, for example, a maintenance cycle, capacity, a cost limit, a desired system model, etc., but other conditions may also be included.

[0079] The optional input item area 112 has an input area for each optional condition. In the optional input item area 112, the input area for a condition for selecting a value includes, for example, an input presence / absence 221, a gauge 222, a unit selection area 223, and a candidate display button 224. The input presence / absence 221 is an area for specifying whether or not to input the corresponding optional condition, i.e., whether or not to specify it as a condition. The gauge 222 is a gauge that displays a value for the condition so that it can be specified, and displays the minimum and maximum values ​​that can be specified. The gauge 222 includes a bar that indicates the specified value. The user can easily change the value of the condition by changing the size of the bar using an input device.

[0080] The unit selection area 223 displays the selected unit for the condition. The candidate display button 224 is a button that accepts the display of selectable units for the condition. When the candidate display button 224 is pressed, a plurality of candidate units are displayed in the unit selection area 223, as shown in FIG. 18. For example, in the input area for the cost upper limit condition, the unit selection area allows the selection of cost units for a one-time sale, such as "10,000 yen" or "100 million yen," or cost units for a subscription, such as "10,000 yen / month."

[0081] Furthermore, in the optional input item area 112, an input area for selecting a candidate, such as specifying a desired system model, displays a candidate selection area 225 and a candidate display button 226. The candidate selection area 225 displays the candidates selected as the condition. The candidate display button 226 is a button that accepts the display of selectable units for the condition. When the candidate display button 226 is pressed, the candidate selection area 225 displays selectable candidates, as shown in FIG. 18. For example, in the input area for the condition of the system model type, the candidate selection area displays multiple selection candidates, such as "standalone," "Active Active HA configuration," "(asynchronous) remote copy configuration," and "hybrid cloud configuration."

[0082] The proposed configuration display area 120 displays information about a storage system proposed as a storage system that meets the conditions, as well as information to be provided to the user if there is no storage system that meets the conditions. The proposed configuration display area 120 displays a detailed display area 121 and a schematic diagram display area 122. The detailed display area 121 is an area that displays details about the proposed storage system. The detailed display area 121 displays, for example, information stored in the comparison result data table 29, specifically, the type of storage system, the number of storage nodes, the number of clusters, the redundancy method, the capacity, the maintenance cycle, the availability level, the price, etc. The schematic diagram display area 122 displays an example of a schematic diagram of the configuration of the proposed storage system. The schematic diagram can be obtained, for example, by referencing the system model data table 26.

[0083] Next, a second example of the configuration proposal screen will be described.

[0084] FIG. 19 is a diagram showing a second example of a configuration proposal screen according to an embodiment.

[0085] The configuration proposal screen 100B is a screen when the conditions input are that the availability level is 99.9%, the maintenance cycle is 60 days, the capacity is 500 TB, and the system model type is a single unit.

[0086] In this example, a storage system that meets the input conditions was detected, so the proposed configuration display area 120 displays a detailed display area 121 for the storage system that meets the input conditions, and a corresponding overview diagram is displayed in the overview diagram display area 122.

[0087] Next, a third example of the configuration proposal screen will be described.

[0088] FIG. 20 is a diagram showing a third example of a configuration proposal screen according to an embodiment.

[0089] The configuration proposal screen 100C is a screen when conditions are input such that the availability level is 99.9%, the maintenance cycle is 60 days, the upper cost limit is 1 million yen, and the system model type is a single unit.

[0090] In this example, a storage system that satisfies the input conditions could not be found, so a condition change proposal 123 is displayed in the proposed configuration display area 120. The condition change proposal 123 includes information such as the fact that there is no configuration that satisfies the input value that is the condition, the type of condition that cannot be satisfied, and the input value that can be proposed, i.e., the content of the condition that can be satisfied.

[0091] According to the configuration proposal screen 100C, when a condition is not met, it is possible to easily and appropriately grasp which condition is not met and how the condition needs to be changed to find a storage system that meets the condition.

[0092] Next, a fourth example of the configuration proposal screen will be described.

[0093] FIG. 21 is a diagram showing a fourth example of a configuration proposal screen according to an embodiment.

[0094] The configuration proposal screen 100D is a screen that appears when the following conditions are entered: availability level is 99.99%, maintenance cycle is 50 days, capacity is 500TB, cost condition is 1 billion yen, and system model type is a single unit.

[0095] In this example, a storage system that satisfied the input conditions could not be detected, but a configuration that could be realized by changing only the type of system model was detected.In this example, the proposed configuration display area 120 does not display a condition change proposal 123 as shown in Figure 20, but instead displays a detailed display area 121 for storage systems that satisfy conditions other than the type of system model, and a corresponding overview diagram is displayed in the overview diagram display area 122.

[0096] Next, a fifth example of the configuration proposal screen will be described.

[0097] FIG. 22 is a diagram showing a fifth example of a configuration proposal screen according to an embodiment.

[0098] The configuration proposal screen 100E is a screen when the conditions input are that the availability level is 99.99%, the maintenance cycle is 50 days, the capacity is 500 TB, and the type of system model is an (asynchronous) remote copy configuration.

[0099] In this example, a storage system that satisfies the input conditions was found, so the proposed configuration display area 120 displays a detailed display area 121 for the storage system that satisfies the input conditions, and a corresponding schematic diagram is displayed in the schematic diagram display area 122. Note that if the storage system has an (asynchronous) remote copy configuration, the automatic failover function will not work, so monitoring timing information is added to the maintenance cycle displayed in the detailed display area 121.

[0100] Next, a sixth example of the configuration proposal screen will be described.

[0101] FIG. 23 is a diagram showing a sixth example of a configuration proposal screen according to an embodiment.

[0102] The configuration proposal screen 100F is a screen that appears when the conditions input are that the availability level is 99.0%, the capacity is 500 TB, and the type of system model is a hybrid cloud configuration.

[0103] In this example, a storage system that satisfies the input conditions is detected, so a detailed display area 121 for the storage system that satisfies the input conditions is displayed in the proposed configuration display area 120, and a corresponding overview diagram is displayed in the overview diagram display area 122. Here, in this example, the detected storage system is a hybrid cloud, so the detailed display area 121 includes information such as the on-premise configuration, availability level, price, etc., and information such as the cloud configuration, availability level, price, etc.

[0104] The present invention is not limited to the above-described embodiment, and can be modified appropriately without departing from the spirit of the present invention.

[0105] For example, in the above embodiment, the availability correlation data table 27 is created in the server 10, but the present invention is not limited to this, and availability correlation data that has been created in advance may be stored.

[0106] Furthermore, in the above embodiment, one storage system that satisfies the conditions is proposed, but multiple storage systems that satisfy the conditions may be proposed. In this case, information on the multiple storage systems may be displayed based on the information in the availability data table 28. Furthermore, the multiple storage systems may be displayed so that the priority order based on the number of storage nodes can be seen.

[0107] Furthermore, in the above embodiment, some or all of the processing performed by the CPU may be performed by a hardware circuit. [Explanation of symbols]

[0108] 1...Information processing system, 2...Internet, 3...Terminal, 5...Data center, 6...Switch, 10...Server, 12...CPU, 15...Memory, 15a...System configuration proposal program, 24...Failure probability data table, 25...Repair probability data table, 26...System model data table, 27...Availability correlation data table, 28...Availability data table, 29...Comparison result data table.

Claims

1. A system configuration proposal device that proposes information about a system configuration of a storage system to a user, comprising: the system configuration proposal device includes a processor and a storage device; the storage device stores availability level information relating to availability levels for a plurality of storage systems; The processor: accepting conditions including an availability level required for the storage system from the user; Identifying candidate storage systems that satisfy the availability level included in the condition based on the availability level information; Outputs information about the system configuration of the identified storage system candidates System configuration proposal device.

2. The storage device includes, as availability level information relating to availability levels, information on a maintenance cycle in the storage system and an availability level during the maintenance cycle. The system configuration proposal device according to claim 1 .

3. the conditions include a maintenance cycle required for the storage system; The processor identifies candidate storage systems that satisfy the availability level and maintenance cycle included in the conditions. The system configuration proposal device according to claim 2 .

4. the conditions include a type of system model required for the storage system; The processor: Identifying candidate storage systems that satisfy the availability level and the type of system model included in the conditions The system configuration proposal device according to claim 1 .

5. The type of the system model is: Includes hybrid clouds that include on-premise storage clusters and cloud storage clusters The system configuration proposal device according to claim 1 .

6. The information about the system configuration of the candidate storage system includes a schematic diagram of the system configuration of the candidate storage system. The system configuration proposal device according to claim 1 .

7. The storage device includes: Failure probability information regarding failure probabilities for a plurality of components constituting a plurality of storage systems; and configuration information relating to the system configuration of a plurality of storage systems; The processor: estimating an availability level for each storage system based on the failure probability information and the configuration information; The estimated availability level is stored in the storage device as availability level information. The system configuration proposal device according to claim 1 .

8. The processor: If there is no candidate storage system that satisfies the condition, the type of condition that is not satisfied and the content that can be satisfied for the type of condition are identified; Output the type of the condition and the content of the condition The system configuration proposal device according to claim 1 .

9. The processor: When there are multiple storage system candidates that satisfy the availability level included in the condition, the storage system candidate with the lowest cost is output with priority from among the multiple storage system candidates. The system configuration proposal device according to claim 1 .

10. The processor: Accepting a change in the availability level; The information about the system configuration of candidate storage systems that satisfy the accepted availability level is updated in real time and output. The system configuration proposal device according to claim 1 .

11. 1. A system configuration proposing method using a system configuration proposing device that proposes information about a system configuration of a storage system to a user, comprising: The system configuration proposal device includes: storing availability level information relating to availability levels for the plurality of storage systems; accepting conditions including an availability level required for the storage system from the user; Identifying candidate storage systems that satisfy the availability level included in the condition based on the availability level information; Outputs information about the system configuration of the identified storage system candidates System configuration proposal method.

12. 1. A system configuration proposal program to be executed by a computer that proposes information about a system configuration of a storage system to a user, The computer storing availability level information relating to availability levels for the plurality of storage systems; The computer, accepting conditions including an availability level required by the storage system from the user; Identifying candidate storage systems that satisfy the availability level included in the conditions based on the availability level information; Output information about the system configuration of the identified storage system candidates System configuration proposal program.

Images