JP6286251B2 - Distributed file system and data availability management control method thereof - Google Patents

Description

  The present invention relates to a distributed file system and a data availability management control method thereof, and more particularly, to a distributed file system (DFS: Distributed) employing a data management method for copying and managing data stored in one node to a plurality of nodes. (File System).

  Conventionally, there is a distributed file system as one of data management methods. The distributed file system is a data management system that allows a folder group to be easily accessed from a shared folder by treating the folder group held by a plurality of computers as a subfolder of one shared folder.

  In connection with such a distributed file system, for example, in Patent Document 1, a plurality of devices (hereinafter referred to as nodes) respectively installed at different bases, each having a storage medium, are connected via a network. A technique for improving data integrity by duplicating data stored in one node to a plurality of nodes is disclosed.

  Specifically, in Patent Document 1, access to data caused by a network failure or a node failure is made by copying data stored in any node to another node when a predetermined trigger condition is satisfied. Inability, loss of data and loss of data integrity are prevented.

JP 2006-350470 A

  However, according to the data management method disclosed in the cited document 1, although the possibility of data loss in the distributed file system can be reduced, the building in which the node is installed and the physical line to which the node is connected It does not consider the risks to physical facilities such as pipelines where lines are laid, power supply facilities that supply power to nodes, and buildings of circuit operators that accommodate physical lines. When the physical equipment of the system is damaged, there is a possibility that the user cannot access the node (data).

  Therefore, when adopting a data management method in which data stored in one node is replicated to a plurality of nodes in a distributed file system, the data replication destination node (hereinafter referred to as a data replication destination node) that takes into account the damage of physical facilities due to natural disasters. This is called a replication destination node).

  The present invention has been made in consideration of the above points. In a distributed file system, data can be prevented from being lost, and data can be maintained in a state where data can be accessed even in the event of a presumed disaster. A distributed file system capable of providing information for managing the availability of data and a data availability management control method thereof are proposed.

In order to solve such a problem, in the present invention, in a distributed file system, a management device connected to a plurality of nodes via a network and managing data held by each of the nodes, and the data held by each of the nodes A data availability management control device for managing and controlling availability against a disaster , wherein the data availability management control device is a disaster risk value for a disaster between a node installation location and a facility installation location used by the node; Receiving information on the network wiring path information and the maintenance schedule of the node, network , power supply equipment or power distribution equipment from the management device, and relating to the disaster risk value, the wiring path equipment path information and the maintenance schedule. Based on information before the node holds It calculates the accessibility of the data, in association with the accessibility of the node and the node which is located in the data output to the screen, also lower than the value accessibility that the calculated predetermined For the node, a node to be a replication destination of the data held by the node is determined, and the management device notifies the management device of a data replication source and a replication destination. Based on the above, the data of the node is replicated.

Further, in the present invention, in the data availability management control method, the data availability management control device in the distributed file system uses the risk value of disaster against the disaster of the installation location of the node and the installation location of the equipment used by the node, the node uses Receive data on network wiring path equipment route information and maintenance schedule of the node, network , power supply equipment or power distribution equipment from a management device that manages data respectively held by a plurality of nodes connected via the network , and data availability The management control device calculates the accessibility to the data held by the node based on the disaster risk value , the wiring path facility route information, and the maintenance schedule information , and the data availability management control device The node being placed and the node And output to the screen in association with Seth possibilities, also for lower nodes than the value accessibility that the calculated predetermined to determine the destination and to be a node of the data that the node is held, The management apparatus is notified of a data replication source and a replication destination, and the management apparatus replicates the data of the node based on the data replication source and the replication destination.

  According to the present invention, in the distributed file system, information for managing the availability of data so as to avoid the loss of data and to maintain a state in which the data can be accessed even in the event of a presumed disaster occurs. A distributed file system and a data availability management control method that can be provided can be realized.

It is a block diagram which shows the whole structure of the distributed file system by this Embodiment. It is a conceptual diagram which shows the structural example of a node management table. It is a conceptual diagram which shows the structural example of a network information management table. It is a conceptual diagram which shows the structural example of an indoor electric power equipment information management table. It is a conceptual diagram which shows the structural example of a commercial power equipment information management table. It is a conceptual diagram which shows the structural example of a wiring installation information management table. It is a conceptual diagram which shows the structural example of a disaster risk management table. (A)-(C) is a basic diagram which shows the structural example of the various GUI screens for a main screen and node management. (A)-(E) is a basic diagram which shows the structural example of the various GUI screens for setting an assumption risk. (A)-(I) is a basic diagram which shows the structural example of the various GUI screens for setting the conditions at the time of a node search in detail. It is a basic diagram which shows the structural example of a search key priority designation | designated table edit screen. (A)-(D) is a basic diagram which shows the structural example of the various GUI screens for setting the conditions at the time of a node search simply. It is a basic diagram which shows the structural example of a simulation execution screen. (A)-(C) is a basic diagram which shows the structural example of the various GUI screens regarding accessibility simulation. It is a flowchart which shows the process sequence of a data availability management control process. It is a flowchart which shows the process sequence of a node information acquisition process. It is a flowchart which shows the process sequence of a simulation screen display and a list creation process. It is a flowchart which shows the process sequence of a simulation screen display and a list creation process.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

(1) Configuration of Distributed File System According to this Embodiment In FIG. 1, reference numeral 1 denotes a distributed file system according to this embodiment as a whole. The distributed file system 1 includes a plurality of nodes 3, a distributed file system management apparatus (hereinafter referred to as a DFS management apparatus) 4, and a data availability management control apparatus 5 connected to each other via a network 2. Is done.

  Each node 3 includes a distributed file system data processing unit (hereinafter referred to as a DFS data processing unit) 10 and a storage device 11.

  The storage device 11 is composed of, for example, a hard disk device, and is installed in the node 3 installation location and the node 3 in addition to the file data of the shared file stored by the user or the like (hereinafter simply referred to as data). Various information related to the hardware (CPU (Central Processing Unit) usage rate, remaining memory capacity, etc.), various information related to the software installed in the node 3, and settings necessary for the node 3 to use the network 2 Information and so on are stored.

  In the following, various information related to the hardware of the node 3, various information related to the software executed on the node 3, and setting information necessary for the node 3 to use the network 2, etc. Information is collectively referred to as node information.

  The DFS data processing unit 10 reads / writes data from / to the storage device 11, transmits data written in the storage device 11 and its attribute information (hereinafter referred to as data attribute information) to the DFS management device 4, DFS Data operation processing according to a data operation request from the management device 4 (for example, copying of data to another node 3), notification of the data processing result to the DFS management device 4, and the like are performed.

  The DFS management device 4 has a function of managing data held by each node 3 in the distributed file system 1, and includes a distributed file system management unit (hereinafter referred to as DFS management unit) 20 and a storage device 21. It is prepared for.

  The DFS management unit 20 periodically collects the node information of each node 3 to be managed, the location of each data existing on the distributed file system 1 and the data attribute information of these data from each node 3. The collected information is stored in the storage device 21 and managed. Further, the storage device 21 is composed of, for example, a hard disk device, and stores node information collected by the DFS management unit 20 from each node 3, data location, data attribute information, and the like.

  An existing distributed file system is constructed by each of the nodes 3 and the DFS management apparatus 4 described above. Therefore, the distributed file system 1 further includes a data availability management control device 5 in addition to such a configuration.

  The data availability management control device 5 is a computer device that includes a screen processing unit 30, a data availability management control unit 31, and a storage device 32. Among these, the screen processing unit 30 has a function of displaying various GUI (Graphical User Interface) screens described later with reference to FIGS. 8 to 14 on a display device such as a liquid crystal display (not shown) under the control of the data availability management control unit 31. Have.

  In addition, the data availability management control unit 31 can generate a natural disaster based on the node information of each node 3 acquired from the DFS management device 4 and the input from the system administrator using the GUI screen displayed by the screen processing unit 30. Node 3 whose data availability is low is extracted, and a replication destination node (hereinafter referred to as an encouragement replication destination node) 3 for data held by the node 3 and a node (not to be a data replication destination) Hereinafter, this is referred to as a duplication prohibition node) 3.

  Then, the data availability management control unit 31 notifies the DFS management apparatus 4 of the node 3 with low data availability with respect to the natural disaster extracted as described above and the recommended replication destination node 3 or the replication prohibited node 3 of the node 3. Thus, based on this notification, the DFS management device 4 transmits the above-described data operation request to the node 3 with low data availability against a natural disaster, thereby causing the data availability management control unit 31 to store the data held by the node 3. Is replicated to the recommended replication destination node 3 notified from the above, or is replicated to a node 3 other than the replication prohibition node 3.

  The storage device 32 is composed of, for example, a hard disk device, and stores various management tables and the like necessary for the data availability management control unit 31 to execute the above-described processing. Specifically, the storage device 32 includes a node management table 40, a network information management table 41, an indoor power equipment information management table 42, a commercial power equipment information management table 43, a wiring equipment information management table 44, a disaster risk management table 45, and A search key priority specification table 46, copy destination node list information 47, and copy prohibition node list information 48 are stored.

  Note that the function of the DFS management device 4 and the function of the data availability management control device 5 may be mounted on the same device. Further, the function of the data availability management control device 5 may be installed in any one of the nodes 3.

  Furthermore, a part or all of the DFS data processing unit 10 of the node 3, the DFS management unit 20 of the DFS management device 4, and the screen processing unit 30 and the data availability management control unit 31 of the data availability management control device 5 are dedicated. It may be configured by hardware or may be configured as a function embodied by executing a corresponding program.

  The DFS data processing unit 10 of the node 3, the DFS management unit 20 of the DFS management device 4, the screen processing unit 30 of the data availability management control device 5 and / or the data availability management control unit 31 are realized by executing a program. When configured as a function, the node 3, the DFS management device 4 and / or the data availability management control device 5 include a CPU, a memory connected to each other via an internal bus in addition to the storage devices 11, 21 and 32 described above. And a computer device including a communication device, an input / output device, and a display device. The CPU reads the program into the memory and executes the read program, thereby realizing the DFS data processing unit 10, the DFS management unit 20, the screen processing unit 30, and the data availability management control unit 31.

  In this case, the program may be stored in advance in the storage devices 11, 21, 32, or from a storage medium such as a CD-ROM (Compact Disk-Read Only Memory), the node 3, the DFS management device 4, or the data. The data may be supplied to the availability management control device 5, or may be acquired by the node 3, the DFS management device 4, or the data availability management control device 5 by downloading from another device via the network.

(2) Configuration of Various Tables Held by Data Availability Management Control Device FIG. 2 shows a schematic configuration of the node management table 40 held by the data availability management control device 5. The node management table 40 is a table used by the data availability management control unit 31 to manage the node information of each node 3. As shown in FIG. 2, for example, the node identifier column 40A, the remaining capacity column 40B, the node name Column 40C, network address column 40D, management information update date column 40E, installation location column 40F, failure occurrence frequency column 40G, manufacturer warranty deadline column 40H, CPU core number column 40I, memory amount column 40J, network management information identifier column 40K, The indoor power facility management information identifier column 40L and the commercial power facility management information identifier column 40M are provided.

  The node identifier column 40A stores a unique identifier (node identifier) assigned to the corresponding node 3, and the remaining capacity column 40B stores the storage device 11 (FIG. 1) of the node 3. The remaining capacity is stored. The node name column 40C stores the node name of the corresponding node 3, and the network address column 40D stores an address on the network assigned to the node 3, such as an IP (Internet Protocol) address. When the node 3 is connected to a plurality of networks, addresses on the respective networks are stored in the network address column 40D.

  Further, the management information update date column 40E stores the date when the node information of the node 3 was last updated, and the installation location column 40F shows the physical location where the node 3 such as address, latitude / longitude is installed. A character string representing a specific position is stored. Further, the failure occurrence number column 40G stores the number of failures and failures that have occurred in the node 3 so far, and the manufacturer warranty deadline column 40H stores the manufacturer's warranty deadline and maintenance deadline for the node 3. .

  The CPU core number column 40I stores the specifications of the CPU mounted on the node 3 (the number of sockets, the number of cores, the drive frequency, etc.), and the memory amount column 40J stores the specifications of the memory mounted on the node 3. (Capacity etc.) is stored. Further, the network management information identifier column 40K stores a management identifier (network management information identifier) assigned to the network to which the node 3 is connected. In this case, when the node 3 is connected to a plurality of networks, the network management information identifier of each network to which the node 3 is connected is stored in the network management information identifier column 40K.

  Furthermore, an identifier (indoor power facility management information identifier) assigned to an indoor power facility that supplies power to the node 3 is stored in the indoor power facility management information identifier column 40L, and a commercial power facility management information identifier column 40M. The identifier (commercial power facility management information identifier) assigned to the commercial power facility that supplies power to the node 3 is stored.

  Note that the information stored in the node management table 40 may be information acquired from the DFS management apparatus 4 by the data availability management control unit 31 of the data availability management control apparatus 5 or stored in advance by the system administrator. There may be. However, regarding the remaining capacity stored in the remaining capacity column 40B, what is periodically collected from each node 3 by the DFS management unit 20 of the DFS management apparatus 4 is stored in the node management table 40.

  In the present embodiment, as described above, information such as the node identifier and the remaining capacity for each node 3 is stored and managed in the node management table 40. However, as the node information, the data availability management control device 5 is used. Can be acquired, for example, the CPU usage rate of the node 3, the memory usage, the maximum communication rate performance of the communication interface installed in the node 3, the node failure rate, the installed storage devices 11, 21, 32 Failure prediction information, communication performance such as delay time, throughput, and fluctuation of the network to which the node 3 is connected may be stored.

  FIG. 3 shows a configuration example of the network information management table 41 held by the data availability management control device 5. The network information management table 41 is a table used by the data availability management control unit 31 to manage a network to which any node 3 in the distributed file system 1 is connected, and is created for each node 3.

  As shown in FIG. 3, the network information management table 41 includes a network management information identifier column 41A, a network service provider column 41B, a network service name column 41C, a service maintenance plan column 41D, a physical line supplier column 41E, a physical line accommodation base. / Base station location column 41F, physical line type column 41G, physical line maintenance plan column 41H, wiring path facility route information (2) column 41I and wiring path facility maintenance plan (1) column 41J.

  The network management information identifier column 41A stores identifiers (network management information identifiers) assigned to the corresponding networks, and the network service provider column 41B and the network service name column 41C each store the network provider. The name and the type of network service are stored. The service maintenance plan field 41D stores the execution date and time of maintenance work planned for the network in advance.

  The physical line supplier column 41E stores the name of the supplier that provides the physical line used by the network, and the physical line accommodating base / base station location column 41F stores the physical line such as the base name and base station name. Stores information representing the accommodation base. Further, the physical line type column 41G stores the type of the physical line (optical fiber, metal, wireless, etc.), and the physical line maintenance plan column 41H stores a schedule (execution of maintenance work) planned in advance for the physical line. (Scheduled date) is stored.

  Furthermore, the “wiring line facility route information (2)” column 41I stores “information relating to wiring facilities” for laying physical lines and line facilities, and the wiring route facility maintenance plan (1) column 41J stores the wiring facilities in advance. The planned maintenance check and construction schedule (execution date and time) are stored.

  Here, the wiring facilities are underground wiring facilities such as pipes, caves, manholes and / or hand holes for laying physical lines, aerial wiring facilities such as utility poles, steel towers and bridges, junction boxes, and terminations. Points to a box. “Information about wiring equipment” refers to an identifier for uniquely identifying a place where wiring equipment is installed or laid, for example, an optical fiber line address specification related to optical fiber line monitoring defined by the Ministry of Land, Infrastructure, Transport and Tourism. . In this embodiment, the “information about the wiring facility” is exemplified according to the optical fiber route address specification. However, if the installation or laying location of the wiring facility can be uniquely identified, it is not necessary to limit to this specification.

  FIG. 4 shows a configuration example of the indoor power equipment information management table 42 held by the data availability management control device 5. The indoor power facility information management table 42 is a table used by the data availability management control unit 31 to manage each indoor power facility that supplies power to each node 3, and is created for each node 3.

  As shown in FIG. 4, the indoor power equipment information management table 42 includes an indoor power management information identifier field 42A, a breaker number field 42B, a standby power generator number field 42C, an uninterruptible power supply number field 42D, and an indoor power facility plan. It consists of a maintenance date column 42E.

  The indoor power management information identifier column 42A stores an identifier (indoor power facility information identifier) assigned to the indoor power facility that supplies power to the corresponding node 3, and the breaker number column 42B stores the identifier. An identifier (breaker number) such as a breaker number assigned to a breaker (breaker or the like) that cuts off power supply to the corresponding node 3 in the indoor power facility is stored.

  The standby power generator number column 42C and the uninterruptible power supply number column 42D include identifiers (standby power generator number, uninterruptible power supply number assigned to the standby power generator and uninterruptible power supply held by the indoor power facility. ) Are stored, and the indoor power facility planned maintenance date column 42E stores a maintenance inspection schedule and a power outage schedule (execution date and time) planned for the indoor power facility in advance.

  Information of the network information management table 41 and the indoor power equipment information management table 42 may be input by the user using the man-machine interface of the data availability management control device 5, but is a company that provides a communication line connected by a network If it is obtained from this server, it becomes easy to update to the latest information.

  FIG. 5 shows a configuration example of the commercial power equipment information management table 43 held by the data availability management control device 5. The commercial power equipment information management table 43 is a table used by the data availability management control unit 31 to manage the commercial power equipment that supplies power to each node 3, and is created for each node 3.

  As shown in FIG. 5, the commercial power facility information management table 43 includes a commercial power management information identifier column 43A, a contract commercial power source column 43B, a commercial power distribution area column 43C, a commercial power plan blackout date column 43D, a wiring path facility route. An information (2) column 43E and a wiring path equipment maintenance plan (2) column 43F are included.

  The commercial power management information identifier column 43A stores an identifier (commercial power facility information identifier) assigned to the commercial power facility that supplies power to the corresponding node 3, and the contracted commercial power source column 43B stores the identifier. Stores the company name of a power company (such as a power generation company or a distribution company) that has contracted to use commercial power equipment.

  In the commercial power distribution area column 43C, information for uniquely identifying the distribution area, distribution route, or substation of the commercial power facility (for identifying the area name, substation name, accounting pipeline and utility pole). Are stored, and the schedule (execution date and time) of maintenance inspections and planned power outages scheduled in advance for the corresponding commercial power facilities is stored in the commercial power supply planned power outage date column 43D.

  Furthermore, the wiring path facility route information (2) column 43E stores “information about wiring facilities” of the corresponding physical line and line facility according to the above-mentioned optical fiber route address specification, and the wiring path facility maintenance plan (2). The column 43F stores a maintenance inspection and construction schedule (execution date and time) planned in advance for the wiring facility.

  On the other hand, FIG. 6 shows a configuration example of the wiring facility information management table 44 held by the data availability management control device 5. The wiring facility information management table 44 is a table used by the data availability management control unit 31 to manage the contents and locations of various facilities related to domestic communication.

  The wiring facility information management table 44 includes a facility information column 44A, a facility content column 44B, and an installation location column 44C. The facility information column 44A stores “information about wiring facilities” in accordance with the above-mentioned optical fiber route address specifications given to each facility, and the facility content column 44B stores the specific contents of the corresponding facility. Stored. The installation location column 44C stores a character string representing the address of the location where the corresponding equipment is installed or laid.

  Each information stored in the wiring facility information management table 44, the commercial power facility information management table 43, and information on the facilities used by other nodes are obtained from an organization that manages the wiring facilities such as an electric power company, a line company, or a public office. It is assumed that the system administrator registers in the data availability management control device 5 based on the obtained management information. However, the data management system operated and managed by the organization and the data availability management control device 5 are connected online, and the data availability management control device 5 automatically stores information to be stored in the wiring facility information management table 44 from the data management system. If it is made to acquire, it will become easy to update to the newest information.

  On the other hand, FIG. 7 shows a configuration example of the disaster risk management table 45 held by the data availability management control device 5. The disaster risk management table 45 is a table used by the data availability management control unit 31 to manage the disaster risk value for each municipality for each assumed risk.

  Here, the assumed risk refers to a combination of an assumed natural disaster type (earthquake, flood, tsunami, volcanic eruption, etc.) and its scale. In the following, the scale of natural disasters is “small”, where damage is expected to remain within the municipality, “medium”, where damage is expected to cover the entire prefecture, There are four types: “Large-scale”, which is expected to reach the entire departmental block, and “Super-large-scale”, where the damage scale is expected to cover the entire country. Therefore, as the assumed risk, for example, “small earthquake”, “medium-scale flood”, “super-large-scale volcanic eruption”, etc. are defined. However, the scale of the natural disaster may be defined based on the predicted disaster area, the distance to the cause of the disaster, or the time required for recovery.

  The damage risk value is the ratio of the collapsed area (earthquake) in each place when natural disasters such as earthquakes, floods, tsunamis, and volcanic eruptions occur, the rate of flooding on the floor (flood damage), and the probability of tsunami arrival of 3 m or more ( A numerical value that indicates the degree of damage at the time of a natural disaster or the possibility of being damaged by a natural disaster, such as a tsunami) or damage occurrence rate (volcanic eruption). The disaster risk value is calculated based on the type and scale of the natural disaster.

As shown in FIG. 7, the disaster risk management table 45 includes a location column 45A and a plurality of assumed risk columns 45B to 45E . The location column 45A stores the names of all related municipalities, and the assumed risk columns 45B to 45E store the disaster risk values of the municipalities for the corresponding assumed risks.

In FIG. 7, only four assumed risk columns 45B to 45E of “large-scale earthquake”, “medium-scale flood damage”, “large-scale tsunami”, and “small-scale volcanic eruption” are illustrated. The disaster risk management table 45 includes all possible natural disasters such as “earthquake”, “water damage”, “tsunami” and “volcanic eruption” as well as “small”, “medium” and “large”. And the number of assumed risk columns is the same as the number of combinations with all the scales of “very large scale”.

  For each information stored in the disaster risk management table 45, a hazard map published by the Ministry of Land, Infrastructure, Transport and Tourism and local governments and numerical information on disaster risk are obtained, and the system administrator registers them in the data availability management control device 5. However, the data management system operated and managed by the Ministry of Land, Infrastructure, Transport and Tourism and the data availability management control device 5 are connected online, and the data availability management control device 5 should store information in the disaster risk management table 45 from the data management system. If it is automatically acquired, it becomes easy to update to the latest information.

  On the other hand, the search key priority specification table 46 holds the conditions for the data availability management control unit 31 of the data availability management control device 5 to search for the above-mentioned encouraged duplication destination node 3 and duplication prohibited node 3 as described later. It is a table used for this purpose. Details of the search key priority designation table 46 will be described later.

  The replication destination node list information 47 is information of a list of the recommended replication destination nodes 3 detected by the data availability management control unit 31 by the above-described search, and is created for each corresponding node 3. The copy prohibition node list information 48 is information on a list of copy prohibition nodes 3 detected by the data availability management control unit 31 by the above-described search, and is created for each corresponding node 3.

  Among the management tables 40 to 46 described above, the information stored in the network information management table 41, the indoor power equipment information management table 42, and the commercial power equipment information management table 43 is the node management described later with reference to FIG. In the information editing screen 70, additional writing and editing can be performed. Of the information stored in the search key priority specification table 46, the priority described later can be set for each condition using the search key priority specification table editing screen 120 described later with reference to FIG.

(3) Configuration of Various Screens (3-1) Main Screen Next, GUI screens that are appropriately displayed on a display device (not shown) by the screen processing unit 30 of the data availability management control device 5 will be described.

  FIG. 8A shows a main screen 50 that can be displayed on the display device of the data availability management control device 5 when the system administrator performs a predetermined operation on the data availability management control device 5. As apparent from FIG. 8A, the main screen 50 includes a node information management button 51, an assumed risk setting button 52, a condition setting (details) button 53, a condition setting (simple) button 54, and a simulation start button. 55 is provided.

(3-2) Various GUI Screens for Node Management The system administrator can display the node management screen 60 shown in FIG. 8B by clicking the node information management button 51 on the main screen 50. . The node management screen 60 is a screen for managing the node 3, and a text box 61 is provided in the lower center portion of the screen.

  This text box 61 is a box for designating an update cycle of the node management table 40 (FIG. 2). When the system administrator inputs a desired time in this text box 61, the data availability management control unit 31 acquires the node information of each node 3 from the DFS management device 4 (FIG. 1) in the time period. Based on the node information of each node 3, the node management table 40 is updated to the latest information.

  A node list display area 62 is provided at the center of the screen of the node management screen 60, and a node list display button 63, a newly discovered node display button 64, and an undiscovered node display button 65 are displayed on the upper side.

  Then, by clicking the node list display button 63, the system administrator can cause the node list display area 62 to display a node list in which all the nodes 3 that are operating at that time are posted. By clicking the button 64, a node list in which only the newly discovered node 3 when the previous node management table 40 is updated can be displayed in the node list display area 62.

  The system administrator clicks the undiscovered node display button 65 to register the node 3 (for example, node information that has been registered in the node management table 40 but failed to acquire node information when the node management table 40 was updated immediately before). A node list in which only the nodes 3) that have been removed from the network or turned off can be displayed in the node list display area 62.

  In this node list, the node name, the installation location, the presence / absence of management information, and the update date / time of the management information are listed.

  Further, a return button 66 and a node management information edit button 67 are displayed below the node list display area 62. The system administrator can close the node management screen 60 and return to the main screen 50 by clicking the return button 66.

  In addition, the system administrator selects a node 3 displayed in the node list displayed in the node list display area 62 by clicking on the line corresponding to the desired node 3, and then selects the node management information edit button 67. By clicking, the node management information editing screen 70 shown in FIG. 8C can be displayed instead of the node management screen 60.

  The node management information editing screen 70 edits various management information (including node information) managed by the data availability management control device 5 for the node 3 selected in the node list of the node management screen 60 as described above. As shown in FIG. 8C, the screen includes a node management information list 71 and a completion button 72.

  The node management information list 71 is selected from the item names of some items set in advance (hereinafter referred to as node management information items) and the node list on the node management screen 60 as described above. The value of the node management information item held by the data availability management control device 5 for the node 3 is displayed.

  Then, the system administrator can select one node management information item by clicking a desired node management information item from among the node management information items posted in the node management information list 71. By selecting one node management information item, the value of the node management information item can be freely edited. However, among the node management information items, “management information update date / time” cannot be edited by the system administrator. Therefore, in the node management information list 71, the “management information update date / time” line is disabled. Is displayed.

  Further, the system administrator can click the completion button 72 to close the node management information editing screen 70 and return to the node management screen 60 (FIG. 8B). At this time, the edited content in the node management information editing screen 70 is reflected in the corresponding node management table 40, network information management table 41, indoor power equipment information management table 42 and / or commercial power equipment information management table 43.

(3-3) Various GUI screens for setting the assumed risk In addition, the system administrator clicks the assumed risk setting button 52 on the main screen 50 (FIG. 8A) to replace the main screen 50, An assumed risk setting screen 80 shown in FIG. 9A can be displayed.

  As will be described later, the assumed risk setting screen 80 sets a natural disaster and its scale (assumed risk) from among four natural disasters of earthquake, tsunami, flood damage, and volcanic eruption, and the natural disaster is at that scale. It is a screen for setting the assumed risk when simulating the possibility of accessing the data held by each node 3 when it occurs (hereinafter referred to as the accessibility simulation).

  As is apparent from FIG. 9A, the assumed risk setting screen 80 includes a risk information capture button 81, an earthquake button 82, a tsunami button 83, a flood button 84, a volcanic eruption button 85, a text box 86, a main box, And a button 87.

  Then, the system administrator clicks the risk information capture button 81 to capture the information registered in the data availability management controller 5 by the system administrator at that time and store it in the disaster risk management table 45 (FIG. 7). Alternatively, the data availability management control device 5 can acquire necessary information from a data management system operated and managed by the Ministry of Land, Infrastructure, Transport and Tourism or local government, and the acquired information can be stored in the disaster risk management table 45. The information captured at this time is a disaster risk value for each location.

  Further, the system administrator can display the assumed earthquake scale setting screen 90 shown in FIG. 9B by clicking the earthquake button 82. The assumed earthquake scale setting screen 90 is a screen for setting an earthquake and its magnitude as an assumed risk, and a scale setting area 91 is displayed at the center of the screen. In the scale setting area 91, toggle buttons 92 </ b> A to 92 </ b> D are displayed corresponding to “super large scale”, “large scale”, “medium scale”, and “small scale”, respectively.

  Thus, the system administrator clicks one of the toggle buttons 92A to 92D on the assumed earthquake magnitude setting screen 90, thereby selecting the assumed natural disaster as “earthquake”, the magnitude as the assumed risk at the time of the accessibility simulation. Can be selected on a scale corresponding to the toggle buttons 92A to 92D. In this case, the toggle buttons 92A to 92D clicked at that time change to a state indicating that the display state is selected.

  The system administrator can close the assumed earthquake magnitude setting screen 90 and return to the assumed risk setting screen 80 by clicking the close button 93 after selecting the magnitude of the earthquake as described above. At this time, the earthquake and the scale set on the assumed earthquake scale setting screen 90 are set as the assumed risk during the accessibility simulation.

  The assumed earthquake scale setting screen 90 also displays a toggle button 92E corresponding to “no condition designation” meaning that no earthquake is set as an assumed risk during the accessibility simulation. When this toggle button 92E is selected (“no condition specified” is selected), no earthquake is set as an assumed risk during the accessibility simulation.

  Further, the system administrator can display the assumed tsunami scale setting screen 94 shown in FIG. 9C by clicking the tsunami button 83 on the assumed risk setting screen 80, and the flood damage button 84 on the assumed risk setting screen 80. By clicking, it is possible to display the assumed flood damage scale setting screen 95 shown in FIG. 9D, and by clicking the volcanic eruption button 85 on the assumed risk setting screen 80, the assumption shown in FIG. A volcanic eruption scale setting screen 96 can be displayed.

  The assumed tsunami scale setting screen 94, the assumed flood damage scale setting screen 95, and the assumed volcanic eruption scale setting screen 96 are screens for setting the scale of a disaster caused by an assumed tsunami, flood damage, or volcanic eruption, respectively. Since the screen configuration and the like of the assumed tsunami scale setting screen 94, the assumed flood damage scale setting screen 95, and the assumed volcanic eruption scale setting screen 96 are the same as those of the assumed earthquake scale setting screen 90, detailed description thereof will be omitted. The setting contents using the assumed earthquake scale setting screen 90, the assumed tsunami scale setting screen 94, the assumed flood damage scale setting screen 95, and the assumed volcanic eruption scale setting screen 96 are applied during the accessibility simulation as described above.

  Two or more assumed risks can be set as the assumed risk at the time of the accessibility simulation. In this case, in the accessibility simulation, the accessibility to the data held by each node 3 when all the set assumed risks occur simultaneously is simulated.

  On the other hand, on the assumed risk setting screen 80, when the assumed risk set as described above occurs, a threshold value of data accessibility (hereinafter referred to as the accessibility lower limit value) is input to the text box 86. Can be set. As will be described later, if the accessibility to the data held by a certain node 3 is less than this accessibility lower limit as a result of the accessibility simulation, the data availability management control unit 31 encourages the node 3 The replication destination node 3 and the replication prohibition node 3 are searched and presented to the system administrator.

  Further, on the assumed risk setting screen 80, by clicking the main button 87, the assumed risk setting screen 80 can be closed to return to the main screen 50 (FIG. 8A).

  In the present embodiment, as described above, the disaster scale is set to “ultra-large scale”, “expected tsunami scale setting screen 94, assumed flood damage scale setting screen 95, and assumed volcanic eruption scale setting screen 96 as described above. It is possible to select from five types of “large scale”, “medium scale”, “small scale”, and “no condition designation”. For example, a larger scale designation such as “national land scale” or “continental scale”, “ It may be possible to designate a smaller scale such as “town scale” or “address scale”, or a scale designation with a numerical area.

(3-4) Various GUI screens for setting detailed conditions for node search On the other hand, the system administrator clicks the setting condition (details) button 53 on the main screen 50 (FIG. 8A). Instead of the main screen 50, a condition setting (detailed) screen 100 shown in FIG. 10A can be displayed.

  In the condition setting (details) screen 100, as described above, as a result of the accessibility simulation, the access possibility to the data held by a certain node 3 is input to the text box 86 of the assumed risk setting screen 80 as described above. It is a screen for setting in detail the conditions when the data availability management control unit 31 searches for the recommended duplication destination node or duplication prohibited node of the data when it is less than the lower limit of possibility.

  As is clear from FIG. 10A, the condition setting (detail) screen 100 includes a replication destination distance button 101, a replication destination node failure frequency button 102, a replication destination node performance button 103, a replication destination power equipment configuration button 104, The data replication basic setting button 105, the replication destination node remaining maintenance period button 106, the network transmission performance button 107, the replication destination network facility configuration button 108, the main button 109, and the search key priority editing button 110 are configured.

  Then, the system administrator can display the inter-node distance designation screen 111 as shown in FIG. 10B by clicking the duplication destination distance button 101 on the condition setting (details) screen 100. This inter-node distance designation screen 111 is a node 3 (hereinafter referred to as a replication source node) that is a data replication source whose data accessibility is less than the accessibility lower limit value as a result of the accessibility simulation. This is a screen for designating the maximum straight line distance from the replication destination node 3 to the replication destination node 3.

  On the inter-node distance designation screen 111, “There is a condition designation (distance is long) that the linear distance from the replication source node 3 to the replication destination node 3 is longer than the preset distance (“ 100 km ”in FIG. 10B)”. ) ”Or“ no condition designation ”that does not designate a straight line distance from the duplication source node 3 to the duplication destination node 3 as a search condition for the duplication destination node 3 or the like. On the inter-node distance designation screen 111, when “with condition designation (distance is long)” is selected, a desired distance can be set as a linear distance from the replication source node 3 to the replication destination node 3.

  The inter-node distance designation screen 111 can be closed by clicking the close button 111A. In this case, the contents designated by the system administrator using the inter-node distance designation screen 111 are reflected in the search key priority designation table 46 (FIG. 1).

  Further, the system administrator can display the duplication destination node failure frequency designation screen 112 as shown in FIG. 10C by clicking the duplication destination node failure frequency button 102 on the condition setting (details) screen 100. it can. The replication destination node failure occurrence count designation screen 112 is a screen for designating the number of failures that occur in the replication destination node 3 that is allowed by the system administrator.

  Then, on the replication destination node failure occurrence count designation screen 112, the number of failures occurring in the replication destination node 3 is less than the predetermined number of times (“3” or less in FIG. 10C) “There is a condition designation (the number of times is small). ) ”Or“ no condition specified ”that does not specify the number of failures in the replication destination node 3 as a condition when searching for the replication destination node 3 can be selected. On the replication destination node failure occurrence count designation screen 112, when “Condition designation (less frequent)” is selected, a specific number of failures can be designated as the number of failure occurrences in the replication destination node 3.

  The copy destination node failure occurrence count designation screen 112 can be closed by clicking the close button 112A. In this case, the contents designated by the system administrator using the duplication destination node failure occurrence count designation screen 112 are reflected in the search key priority designation table 46.

  Furthermore, the system administrator can display the replication destination node performance designation screen 113 as shown in FIG. 10D by clicking the replication destination node performance button 103 on the condition setting (details) screen 100. This duplication destination node performance designation screen 113 is a screen for designating the performance of the duplication destination node 3 desired by the system administrator (the number of CPU cores and the memory capacity in this embodiment).

  In the replication destination node performance designation screen 113, the performance of the replication destination node 3 is higher than the predetermined performance (in FIG. 10D, the number of CPU cores is “4” or more and the memory capacity is “4” GByte or more). It is possible to select “with condition specified (large numerical value)” or “without condition specified” in which the performance of the replication destination node 3 is not specified as a search condition for the replication destination node 3. On the replication destination node performance designation screen 113, when “Condition designation (large numerical value)” is selected, the CPU core number and the memory capacity lower limit value in the replication destination node 3 can be separately designated.

  The replication destination node performance designation screen 113 can be closed by clicking the close button 113A. In this case, the contents designated by the system administrator using the replication destination node performance designation screen 113 are reflected in the search key priority designation table 46.

  Furthermore, the system administrator can display the duplication destination node power equipment configuration designation screen 114 as shown in FIG. 10E by clicking the duplication destination power equipment configuration button 104 on the condition setting (details) screen 100. it can. The duplication destination node power equipment configuration designation screen 114 displays power equipment that supplies power to the duplication source node 3 (hereinafter referred to as duplication source node power equipment) and power equipment that feeds power to the duplication destination node 3. This is a screen for designating a relationship with (hereinafter referred to as a replication destination node power facility).

  In the replication destination node power facility configuration designation screen 114, the relationship between the replication source node power facility and the replication destination node power facility is “all different” which means that they are all different, and some of these are different. It is possible to select either “partially different”, which means that, or “no condition specification” which does not specify these relationships as conditions when searching for the replication destination node 3. In addition, when “partially different” is selected on the duplication destination node power equipment configuration designation screen 114, the power equipment (breaker, spare) that should be further differentiated between the duplication source node power equipment and the duplication destination node power equipment. A power generator, an uninterruptible power supply, etc.) can be specified individually.

  The copy destination node power equipment configuration designation screen 114 can be closed by clicking the close button 114A. In this case, the contents designated by the system administrator using the duplication destination node power equipment configuration designation screen 114 are reflected in the search key priority designation table 46.

  Further, the system administrator can display the data replication number designation screen 115 as shown in FIG. 10F by clicking the data replication basic setting button 105 on the condition setting (details) screen 100. This data replication number designation screen 115 is a screen for designating the number of data replications.

  On the data replication number designation screen 115, the number of data replications can be specifically designated. For example, when “2” is designated as the number of copies, each data is held in the copy source node 3 and the two copy destination nodes 3, respectively. On the data copy number designation screen 115, when a copy exceeding the specified number of copies is created, it is possible to specify whether or not to delete the excess copy.

  The data replication number designation screen 115 can be closed by clicking the close button 115A. In this case, the contents designated by the system administrator using the data replication number designation screen 115 are reflected in the search key priority designation table 46.

  Further, the system administrator clicks the replication destination node remaining maintenance period button 106 on the condition setting (details) screen 100 to display the replication destination node remaining maintenance period designation screen 116 as shown in FIG. Can do. This copy destination node remaining maintenance period designation screen 116 is displayed on the basis of the execution time of the accessibility simulation, and the minimum maintenance period remaining for the copy destination node 3 desired by the system administrator (hereinafter referred to as the remaining maintenance period). This is a screen for specifying "

  Then, on the replication destination node remaining maintenance period designation screen 116, “remaining maintenance period of the replication destination node 3 is longer than a predetermined period (“ 365 ”days or more in the drawing)”, “conditions are specified (remaining period is long)”. One of “no condition designation” that does not designate the remaining maintenance period of the replication destination node 3 as a condition when searching for the replication destination node 3 can be selected. On the replication destination node remaining maintenance period designation screen 116, when “with condition designation (long remaining period)” is selected, the remaining maintenance period in the replication destination node 3 can be specifically specified.

  The copy destination node remaining maintenance period designation screen 116 can be closed by clicking the close button 116A. In this case, the contents designated by the system administrator using the copy destination node remaining maintenance period designation screen 116 are reflected in the search key priority designation table 46.

  Furthermore, the system administrator can display the network transmission performance designation screen 117 as shown in FIG. 10H by clicking the network transmission performance button 107 on the condition setting (details) screen 100. This network transmission performance designation screen 117 is a screen for designating the transmission performance of the network 2 from the DFS management apparatus 4 (or the replication source node 3) to the replication destination node 3 as desired by the system administrator.

  On the network transmission performance designation screen 117, the delay time and the throughput in the network 2 from the DFS management apparatus 4 (or the replication source node 3) to the replication destination node 3 are predetermined delay times (“50 in FIG. 10H). "Msec or less" and the throughput ("200" kbps or more in FIG. 10H) "performance is specified (good performance)" indicating that the performance is better, and the delay time and throughput are set to the destination node 3 It is possible to select one of “no condition designation” that is not designated as a condition when searching. On the network transmission performance designation screen 117, if “conditions are specified (performance is good)” is selected, the upper limit of the delay time in the network 2 from the DFS management device 4 (or the replication source node 3) to the replication destination node 3 is further selected. The value and the lower limit value of the throughput can be specified separately.

  The network transmission performance designation screen 117 can be closed by clicking the close button 117A. In this case, the contents designated by the system administrator using the network transmission performance designation screen 117 are reflected in the search key priority designation table 46.

  Furthermore, the system administrator can display the duplication destination network equipment configuration designation screen 118 as shown in FIG. 10I by clicking the duplication destination network equipment configuration button 108 on the condition setting (details) screen 100. . The duplication destination network equipment configuration designation screen 118 displays the equipment environment of the network 2 used by the duplication source node 3 (hereinafter referred to as the duplication source node network equipment environment) and the network equipment used by the duplication destination node 3. This is a screen for designating the relationship with the environment (hereinafter referred to as the replication destination node network equipment environment).

  On the duplication destination network equipment configuration designation screen 118, the relation between the duplication source node network equipment environment and the duplication destination node network equipment environment means that they are all different, and all of them are different. It is possible to select either “partially different”, which means that, or “no condition specification” which does not specify these relationships as conditions when searching for the replication destination node 3. In addition, when “partially different” is selected on the replication destination network equipment configuration designation screen 118, network equipment (network service company, network service company, Network service type and service maintenance date) can be individually specified.

  The duplication destination network equipment configuration designation screen 118 can be closed by clicking a close button 118A. In this case, the contents designated by the system administrator using this duplication destination network equipment configuration designation screen 118 are reflected in the search key priority designation table 46.

  The system administrator can close the condition setting (detail) screen 100 and return to the main screen 50 (FIG. 8A) by clicking the main button 109 on the condition setting (detail) screen 100. .

  Further, the system administrator clicks the search key priority edit button 110 on the condition setting (detail) screen 100 to replace the condition setting (detail) screen 100 with a search key priority designation table as shown in FIG. The edit screen 120 can be displayed.

  The search key priority specification table editing screen 120 is configured to include a search key priority list 121 and a close button 122. In the search key priority list 121, the contents of the search key priority specification table 46 (FIG. 1) are stored as they are with the same configuration as the table configuration of the search key priority specification table 46.

  Specifically, the search key priority list 121 includes a key item (“Key Item”) column 121A, a check (“Check”) column 121B, an evaluation (“Evaluation”) column 121C, and a priority (“Priority”) column 121D. Composed. The key item column 121A stores the name of each condition that can be set on each screen described above with reference to FIGS. 8 to 10, and the check column 121B indicates a flag (whether or not the corresponding condition is set). “1” is stored when it is set, and “0” is stored when it is not set.

  For example, in the example of FIG. 11, since the distance from the replication source node 3 to the replication destination node 3 is not specified on the internode distance specification screen 111 described above with reference to FIG. 10B, “DISTANCE” in the key item column 121A. Since “0” is stored in the check column 121B of the row No. and the number of failure occurrences in the replication destination node 3 is not specified in the replication destination node failure frequency specification screen 112 described above with reference to FIG. “1” is stored in the check field 121B of the “NODE_FAILURE” line of 121A.

  Further, in the evaluation column 121C, when the corresponding condition is specified on the screen described above with reference to FIGS. 8 to 10, the contents of the specified condition are stored, and when the corresponding condition is not specified, A predetermined value for the condition is stored.

  For example, in the example of FIG. 11, the distance from the replication source node 3 to the replication destination node 3 is not specified on the above-described inter-node distance designation screen 111 (FIG. 10B), and the default value is “100 km or more”. Therefore, “> 100 km” is stored in the evaluation column 121C of the “DISTANCE” row in the key item column 121A, and the failure in the replication destination node 3 also occurs in the replication destination node failure frequency designation screen 112 (FIG. 10C). Since the number of occurrences is not specified and the default value is “3 times or less”, “<3” is stored in the evaluation column 121C of the “NODE_FAILURE” line of the key item column 121A.

  Further, the priority column 121D stores the priority of each condition set by the system administrator using the search key priority designation table editing screen 120. As for the priority, “1” is the highest and the priority is lower in descending order. On the search key priority designation table editing screen 120, the system administrator can edit only this priority. Note that for a condition in which “0” is stored in the check column 121B (that is, a condition for which a value is not specified by the system administrator), the priority is also set to “0” (that is, set to have no priority). The

  The search key priority designation table editing screen 120 can be closed by clicking the close button 122. In this case, the setting content (priority value of each condition) set by the system administrator using the search key priority specification table edit screen 120 is reflected in the search key priority specification table 46.

(3-5) Various GUI screens for simply setting conditions for node search On the other hand, the system administrator clicks the setting condition (simple) button 54 on the main screen 50 (FIG. 8A). Instead of the main screen 50, a condition setting (simple) screen 130 shown in FIG. 12A can be displayed. This condition setting (simple) screen 130 is a screen for enabling easy setting of conditions for selecting a replication destination node 3 for data held by each node 3. A button 132, a customization button 133, and a main button 134 are provided.

  Then, the system administrator clicks the data availability emphasis button 131 on the condition setting (simple) screen 130 to display a data availability emphasis condition setting screen (hereinafter referred to as data availability emphasis as shown in FIG. 12B). 140 (referred to as a condition setting screen).

  This data availability emphasis condition setting screen 140 places importance on the availability of data. As a search condition for the replication destination node 3, the distance between the replication source node 3 and the replication destination node 3 and the number of failures occurring in the replication destination node 3 are displayed. The upper limit value, the power facility environment for supplying power to the replication destination node 3, the upper limit value of the number of data replications in the system, the remaining maintenance period of the replication destination node 3, and the DFS management device 4 (or the replication source node 3) ) To the replication destination node 3 is a screen for setting only the network performance.

  For this reason, on the condition setting screen 140 for emphasizing data availability, the replication destination distance button 141, the replication destination node failure frequency button 142, and the replication destination node performance button 143 similar to the condition setting (details) screen 100 described above with reference to FIG. , Replication destination power equipment configuration button 144, data replication basic setting button 145, replication destination node remaining maintenance period button 146, network transmission performance button 147, and replication destination network equipment configuration button 148 are displayed. Only the button 141, the duplication destination node failure frequency button 142, the duplication destination power equipment configuration button 144, the data duplication basic setting button 145, the duplication destination node remaining maintenance period button 146, and the duplication destination network equipment configuration button 148 are effectively displayed. Button (replication destination node performance button 143 and Ttowaku transmission performance button 147) is invalid display.

  On the condition setting screen 140 for emphasizing data availability, the replication destination distance button 141, the replication destination node failure frequency button 142, the replication destination power equipment configuration button 144, the data replication basic setting button 145, the remaining replication destination node remaining maintenance period, which are effectively displayed, are displayed. By clicking a desired button among the buttons 146 and the duplication destination network equipment configuration button 148, the internode distance designation screen 111, the duplication destination node failure occurrence frequency designation screen 112, the duplication destination node power equipment configuration described above with reference to FIG. Corresponding screens among the designation screen 114, the data replication number designation screen 115, the duplication destination node remaining maintenance period designation screen 116, and the duplication destination network facility configuration designation screen 118 can be displayed. Thus, the system administrator can specify a desired condition as a search condition for the replication destination node 3 using the screen in the same manner as described above.

  The system administrator can click the main button 149 on the data availability emphasis condition setting screen 140 to close the data availability emphasis condition setting screen 140 and return to the main screen 50 (FIG. 8A). it can.

  On the other hand, the system administrator clicks on the performance emphasis button 132 on the condition setting (simple) screen 130 to display a performance emphasis condition setting screen as shown in FIG. 150 (referred to as a setting screen) can be displayed. This performance-oriented condition setting screen 150 places importance on the data transfer performance of data and the performance of the node 3, and sets only the performance of the replication destination node 3 and the performance of the network 2 as search conditions for the replication destination node 3. This is the screen.

For this reason, on the performance-oriented condition setting screen 150, the same replication destination distance button 151 , replication destination node failure frequency button 152 , replication destination node performance button 153 , as in the condition setting (detailed) screen 100 described above with reference to FIG. A replication destination power equipment configuration button 154 , a data replication basic setting button 155 , a replication destination node remaining maintenance period button 156 , a network transmission performance button 157, and a replication destination network equipment configuration button 158 are displayed. Only the button 153 and the network transmission performance button 157 are displayed as valid, and the other buttons are displayed as invalid.

  Then, on the performance-oriented condition setting screen 150, by clicking a desired button among the effectively displayed duplication destination node performance button 153 and network transmission performance button 157, the duplication destination node performance described above with reference to FIG. A corresponding screen of the network transmission performance designation screen 117 described above with reference to the designation screen 113 or FIG. 10 (H) can be displayed. Thus, the system administrator can specify a desired condition as a search condition for the replication destination node 3 using the screen in the same manner as described above.

  The system administrator can click the main button 159 on the performance-oriented condition setting screen 150 to close the performance-oriented condition setting screen 150 and return to the main screen 50 (FIG. 8A).

  On the other hand, the system administrator clicks the customize button 133 on the condition setting (simple) screen 130 to display a condition setting screen for emphasizing maintainability as shown in FIG. 160) (called a screen) can be displayed. This customization condition setting screen 160 places importance on maintainability, and sets only the power equipment environment for supplying power to the replication destination node 3 and the remaining maintenance period of the replication destination node 3 as search conditions for the replication destination node 3 It is a screen to do.

  For this reason, on the customization condition setting screen 160, the same replication destination distance button 161, replication destination node failure frequency button 162, replication destination node performance button 163, replication as in the condition setting (detail) screen 100 described above with reference to FIG. A destination power equipment configuration button 164, a data replication basic setting button 165, a replication destination node remaining maintenance period button 166, a network transmission performance button 167, and a destination network equipment configuration button 168 are displayed. Only the button 164 and the copy destination node remaining maintenance period button 166 are displayed as valid, and the other buttons are displayed as invalid.

  Then, on the customization condition setting screen 160, by clicking the desired button of the duplication destination power equipment configuration button 164 and duplication destination node remaining maintenance period button 166 that are effectively displayed, the duplication described above with reference to FIG. The corresponding screen of the destination node power equipment configuration designation screen 114 or the copy destination node remaining maintenance period designation screen 116 described above with reference to FIG. 10G can be displayed. Thus, the system administrator can specify a desired condition as a search condition for the replication destination node 3 using the screen in the same manner as described above.

  The system administrator can close the customization condition setting screen 160 and return to the main screen 50 (FIG. 8A) by clicking the main button 169 on the customization condition setting screen 160.

  The system administrator can close the condition setting (simple) screen 130 and return to the main screen 50 by clicking the main button 134 of the condition setting (simple) screen 130 (FIG. 12A).

(3-6) Various GUI Screens Related to Accessibility Simulation The system administrator clicks on the simulation start button 55 on the main screen 50 (FIG. 8A), thereby replacing the main screen 50 with the one shown in FIG. A simulation execution screen 170 can be displayed. This simulation execution screen 170 indicates the possibility of access to the data held by each node 3 when the assumed risk set using each screen described above with reference to FIGS. 9A to 9E occurs. This is a screen for displaying a simulation result, and includes an assumed risk map display area 171, an accessibility display area 172, a cancel button 173, and a confirmation button 174.

  In the assumed risk map display area 171 of the simulation execution screen 170, an assumed risk map 175 corresponding to the set assumed risk is displayed. In this assumed risk map 175, the same disaster risk value ranges (“30% or more”, “50% or more”, and “80% or more” in FIG. 13) are indicated in contour lines on the map. FIG. 13 is a display example when “medium scale” “water damage” is set as the assumed risk.

  The range of each disaster risk value is obtained by extracting the target assumed risk (in this case, the region indicated by the broken line K in FIG. 7) from the disaster risk management table 45 described above with reference to FIG. Among them, by connecting several municipalities of the same predetermined risk value of damage with broken lines L1 to L3, they are displayed on the map as contour lines as described above.

  Further, in the accessibility display area 172 of the simulation execution screen 170, when a set assumed risk occurs for each node 3 to be managed, the installation location (“installation location”) of the node 3 and the node Damage to several locations related to the node 3, such as the location of the physical line facility 3 ("location of the line facility") and the accommodation location of the circuit used by the node 3 ("circuit accommodation location") Information such as the risk value ("damage probability" in FIG. 13) and the accessibility of the data held by the node 3 ("data accessibility during a disaster") is tabulated as a data accessibility list. Is displayed.

  In the case of the present embodiment, the accessibility to the data held by the node 3 is from the maximum value of accessibility, which is 100%, to the maximum of the disaster risk values at each location related to the node 3 Calculated by subtracting the damage risk value. For example, in the case of node 3 “Node0001”, when the maximum value of the disaster risk value is “39%”, “61%” obtained by subtracting 39% from 100% is the data held by the node 3 That means accessibility.

  The system administrator can cancel the accessibility simulation by clicking the stop button 173 on the simulation execution screen 170, close the simulation execution screen 170, and return to the main screen 50 (FIG. 8A). it can.

  Also, the system administrator can click the confirmation button 174 on the simulation execution screen 170 to close the simulation execution screen 170 and display the replication source node list screen 180 shown in FIG.

  This duplication source node list screen 180 is a text box of the assumed risk setting screen 80 described above with reference to FIG. 9A when the possibility of setting the assumed risk occurs as a result of the accessibility simulation. 86 is a screen for the system administrator to confirm the node 3 that is less than the lower limit of accessibility that is input in 86.

  As apparent from FIG. 14A, the copy source node list screen 180 includes a copy source node list display area 181, a condition change button 182, a copy destination list button 183, a copy prohibition list button 184, and a policy notification button. 185.

  In the replication source node list display area 181, as a result of the above-described accessibility simulation, each node 3 whose accessibility to the held data was less than the accessibility lower limit value when the set assumed risk occurred. A node list (hereinafter referred to as a replication source node list) on which the node name, installation location, management information update date and notes, etc. are posted is displayed.

  After the system administrator selects the desired node 3 from among the nodes 3 listed in the replication source node list displayed in the replication source node list display area 181 of the replication source node list screen 180, the system administrator clicks. By clicking the copy destination list button 183, the copy destination node list screen 190 shown in FIG. 14B can be displayed.

  This duplication destination node list screen 190 is a system in which node 3 (recommended duplication destination node 3) recommended as a duplication destination of data held by the node 3 selected in the duplication source node list of the duplication source node list screen 180 is a system. This is a screen for presenting to the administrator, and includes a recommended duplication destination node list display area 191, a management information reference button 192, and a return button 193.

  In the replication destination node list screen 190, all the recommended replication destinations of the data held in the node 3 selected in the replication source node list of the replication source node list screen 180 as described above are displayed in the recommended replication destination node list display area 191. For node 3, a list of recommended duplication destination nodes in which the node name, installation location, and free space are posted is displayed.

  Then, the system administrator selects after selecting one of the recommended replication destination nodes 3 listed in the recommended replication destination node list on the replication destination node list screen 190 by clicking on one of the recommended replication destination nodes 3. By clicking the information reference button 192, the node management information editing screen 70 described above with reference to FIG. 8C on which the node management information of the encouraged duplication destination node 3 is posted can be displayed.

  Further, the system administrator can close the replication destination node list screen 190 and return to the replication source node list screen 180 by clicking the return button 193 on the replication destination node list screen 190.

  On the other hand, the system administrator clicks a desired node 3 from among the nodes 3 listed in the replication source node list displayed in the replication source node list display area 181 of the replication source node list screen 180. Then, by clicking the copy prohibition list button 184, the copy prohibition node list screen 200 shown in FIG. 14C can be displayed.

  This copy prohibition node list screen 200 is a screen for presenting the system administrator with a copy prohibition node 3 of data held by the node 3 selected in the copy source node list of the copy source node list screen 180 described above. The copy prohibition node list display area 201, a management information reference button 202, and a return button 203 are provided.

  In the duplication prohibition node list screen 200, the duplication prohibition node list display area 201 displays the node for all duplication prohibition nodes 3 for the node 3 selected in the duplication source node list on the duplication source node list screen 180 as described above. A list of copy-prohibited nodes that displays the name, installation location, and available capacity is displayed.

  Then, the system administrator selects a copy-prohibited node 3 by clicking any one of the copy-prohibited nodes 3 listed in the copy-prohibited node list on the copy-prohibited node list screen 200, and then clicks a management information reference button. By clicking 202, the node management information editing screen 70 described above with reference to FIG. 8C on which the node management information of the copy-prohibited node 3 is posted can be displayed.

  In addition, the system administrator can close the duplication prohibited node list screen 200 and return to the duplication source node list screen 180 by clicking the return button 203 on the duplication prohibited node list screen 200.

  In the case of the present embodiment, information on the replication source node list on the replication source node list screen 180, information on the replication destination node list on the replication destination node list screen 190 corresponding to each node 3 that can be the replication source node 3, The information on the copy-prohibited node list on the copy-prohibited node list screen 200 corresponding to each node 3 that can be the copy source node 3 is the stage where the confirmation button 174 of the simulation execution screen 170 described above with reference to FIG. 13 is clicked. Is generated.

  Then, the information on the replication destination node list on the replication destination node list screen 190 corresponding to each node 3 that can become the replication source node 3 among them is the data availability management control device 5 as the replication destination node list information 47 (FIG. 1). The copy-prohibited node list information on the copy-prohibited node list screen 200 corresponding to each node 3 that can be stored and managed in the storage device 32 (FIG. 1) and can be the copy-source node 3 is the copy-prohibited node list information 48 ( FIG. 1) is stored in the storage device 32 and managed.

  Thereafter, when the policy notification button 185 on the replication source node list screen 180 is clicked, information on the replication source node list displayed in the replication source node list display area 181 of the replication source node list screen 180 (hereinafter, referred to as the replication source node list screen 180). This is referred to as replication source node list information) and all the above-mentioned replication destination node list information 47 or replication prohibited node list information 48 stored in the storage device 32 of the data availability management control device 5 are the DFS management device 4. Sent to.

  Thus, the DFS management apparatus 4 controls each node 3 listed in the replication source node list based on the replication source node list information and the replication destination node list information 47 or the replication prohibition node list information 48 (these The data operation request described above is transmitted to each node 3 of the node 3 to cause the data held by these nodes 3 to be replicated to the recommended replication destination node 3 of the node 3 or to the replication prohibited node 3 of the node 3. Duplicate to other node 3.

  The system administrator can click the condition change button 182 on the copy source node list screen 180 to close the copy source node list screen 180 and return to the main screen 50 (FIG. 8A). .

  Further, the system administrator specifies the recommended duplication destination node 3 in which the replicated data is held by executing a command for specifying the node in which the data is held in the DFS management unit 20, and further specifies By searching the node management table 40 using the node 3 of the encouragement duplication destination as a key, it is possible to grasp that the data has been duplicated and to know the encouragement duplication destination node 3 to which the data has been duplicated and its location.

(4) Processing of Data Availability Management Control Unit Next, a series of processing (hereinafter referred to as data processing) executed by the data availability management control unit 31 of the data availability management control device 5 in relation to the display of the various GUI screens described above. Will be described).

  FIG. 15 shows a flow of a series of such data availability management control processing. The data availability management control unit 31 starts the data availability management control process shown in FIG. 15 in response to a display instruction for the main screen 50 (FIG. 8A) by the system administrator. ) Stored in the node management table 40, network information management table 41, indoor power equipment information management table 42, commercial power equipment information management table 43, wiring equipment information management table 44, disaster risk management table 45, and search key priority The designation table 46 is read into the memory (SP1).

  Subsequently, the data availability management control unit 31 requests the DFS management device 4 to transfer the latest node information of each node 3, and as a result, the node information of each node 3 transferred from the DFS management device 4. Are stored in the node management table 40 (SP2).

  Next, the data availability management control unit 31 displays the screen processing unit 30 (FIG. 1) so as to appropriately display the corresponding GUI screen among the various GUI screens described above with reference to FIGS. 8 to 14 according to the operation of the system administrator. Control and accept input from the system administrator using the displayed GUI screen, and appropriately, node management table 40, network information management table 41, indoor power equipment information management table 42, commercial power equipment information management table 43, The wiring facility information management table 44, the disaster risk management table 45, and the search key priority designation table 46 are updated as necessary (SP3).

  Thereafter, when the simulation start button 55 on the main screen 50 (FIG. 8A) is clicked, the data availability management control unit 31 sets the assumed risk set using the assumed risk setting screen 80 shown in FIG. The disaster risk management table shows disaster risk values such as the location where each node 3 is installed, the location of the physical line facility used by the node 3, and the circuit accommodation location used by the node 3 45 (FIG. 7), and the possibility of accessing the data held by each node 3 is calculated. Further, the data availability management control unit 31 calculates the accessibility to the data held by each node 3 based on the information acquired or calculated as described above, and displays the simulation execution screen 170 based on the calculation result on the screen processing. It is displayed on the part 30 (SP4).

  Thereafter, when the policy notification button 185 on the replication source node list screen 180 (FIG. 14A) is clicked, the data availability management control unit 31 performs the above-described replication source data Iran information and the data availability management control device. The replication destination node list information 47 and the replication prohibition node list information 48 of each node 3 listed in the replication source node list stored in the storage device 32 of 5 are transmitted to the DFS management apparatus 4 (SP5). Thereafter, the data availability management control process is terminated.

  FIG. 16 shows more specific processing contents of the data availability management control unit 31 in step SP2 of the data availability management control processing described above. When the data availability management control unit 31 proceeds to step SP2 of the data availability management control process, it starts the node information acquisition process shown in FIG. 16, and first acquires the current time (SP10).

  Subsequently, the data availability management control unit 31 accesses the DFS management apparatus 4 to acquire node information of each node 3 to be managed (SP11), and performs node management based on the acquired node information of each node 3. The table 40 (FIG. 2) is updated to the latest state (SP12). The data availability management control unit 31 thereafter ends this node information acquisition process.

  Incidentally, this node information acquisition process is executed at the time period set in the text box 61 of the node management screen 60 described above with reference to FIG.

  On the other hand, FIGS. 17A and 17B show the display of the simulation execution screen 170 (FIG. 13), among the accessibility simulation processing executed by the data availability management control unit 31 in step SP4 of the data availability management control processing described above. A specific processing procedure of a series of processes relating to the creation of the copy destination node list information 47 and the copy prohibition node list information 48 (hereinafter referred to as simulation screen display and list creation process) will be described.

  When the data availability management control unit 31 proceeds to step SP4 of the data availability management control process, the data availability management control unit 31 starts the simulation screen display and list creation process shown in FIGS. 17A and 17B. First, FIG. 9A to FIG. The column information corresponding to the search key is extracted from the disaster risk management table 45 (FIG. 7) using the assumed risk set by the system administrator using the assumed risk setting screen 80 and the like described above for the search key (SP20). ). For example, when “medium-scale flood damage” is set as the assumed risk, the data availability management control unit 31 indicates the damage risk value for each location registered in the disaster risk management table 45 by a broken line K in FIG. Each disaster risk value in the enclosed area is extracted.

  Subsequently, for each node 3 registered in the node management table 40 (FIG. 2), the data availability management control unit 31 is a disaster risk value at the place where the node 3 is installed when the assumed risk occurs. Is acquired (SP21). Specifically, the data availability management control unit 31 reads the installation location of each node 3 from the installation location column 40F (FIG. 2) of the node management table 40, and the disaster risk of these locations when the set assumed risk occurs. Each value is acquired by reading from the disaster risk management table 45.

  Next, the data availability management control unit 31 obtains the disaster risk values of the locations where the respective wiring facilities registered in the wiring facility information management table 44 (FIG. 6) are respectively installed when the set assumed risk occurs. (SP22). Specifically, the data availability management control unit 31 reads the location where each wiring facility registered in the wiring facility information management table 44 is installed from the wiring facility information management table 44, and when the set assumed risk occurs Are read out from the disaster risk management table 45, respectively.

  Further, the data availability management control unit 31 has, for each node 3 registered in the node management table 40, a place where the wiring facility of the network 2 to which the node 3 is connected is installed, and a commercial that supplies power to the node 3. Each predetermined location such as the location where the power equipment is installed is acquired (SP23).

  Specifically, for each node 3 registered in the node management table 40, the data availability management control unit 31 displays “wiring facility information” of the wiring facility of the network 2 to which the node 3 is connected. Read from the wiring facility route information (2) column 41I (FIG. 3) of the management table 41 (FIG. 3), and refer to the wiring facility information management table 44 on the basis of the read “information about the wiring facility”. Acquire the location where the wiring equipment is installed. Similarly, for each node 3 registered in the node management table 40, the data availability management control unit 31 displays “information relating to the wiring facility” of the commercial power facility that supplies power to the node 3, and the corresponding commercial power facility information. Read from the management table 43 (FIG. 5), and based on the read “information about the wiring facility”, refer to the wiring facility information management table 44 to obtain the place where the commercial power facility that supplies power to the node 3 is installed. To do. Further, the data availability management control unit 31 similarly obtains a location related to the predetermined node 3 other than the installation location of the wiring facility and the commercial power facility of the network 2.

  The data availability management control unit 31 then determines predetermined locations such as the installation location of each wiring facility and the installation location of each commercial power facility acquired at step SP23 when the set assumed risk occurs. Are obtained by reading out the respective disaster risk values from the disaster risk management table 45 (SP24).

  Further, the data availability management control unit 31 for each node 3, the disaster risk value of the installation location of the node 3 acquired in step SP21, the installation location of each wiring facility acquired in step SP23, and the installation of each commercial power facility Based on the disaster risk value such as the location, the possibility of accessing the data held in the node 3 is calculated (SP25), and thereafter, the information obtained by the processing of step SP21 to step SP25 is displayed on the screen processing unit. 30 (FIG. 1) causes the simulation execution screen 170 described above with reference to FIG. 13 to be displayed.

  Subsequently, the data availability management control unit 31 waits for the confirmation button 174 (FIG. 13) on the simulation execution screen 170 to be clicked (SP27), and when the confirmation button 174 is eventually clicked, the data availability management control unit 31 calculates each step calculated in step SP25. Based on the accessibility of the node 3 and the accessibility lower limit value set on the assumed risk setting screen 80 described above with reference to FIG. 9A, the node 3 whose accessibility is less than the accessibility lower limit value. Extracting as a replication source node and providing the screen processing unit 30 with necessary information regarding all the extracted replication source nodes 3, the replication source node list screen 180 described above with reference to FIG. 14 is displayed (SP28).

  Further, the data availability management control unit 31 creates, for each replication source node 3, a replication destination node list in which all the nodes 3 whose accessibility calculated in step SP25 exceeds the accessibility lower limit value are registered. SP29).

  Next, the data availability management control unit 31 reads the search key priority designation table 46 (see FIG. 1 and FIG. 11) (SP30), and from among the conditions registered in the read search key priority designation table 46 The condition where the numerical value stored in the check column is “0” is excluded (SP31).

  Further, the data availability management control unit 31 sorts the conditions registered in the search key priority designation table 46 excluding unnecessary conditions in step SP31 in ascending order according to the priorities stored in the priority column. Specifically, the data availability management control unit 31 sets the condition where the priority is “1” as the top level, and searches so that the priority level becomes lower as “2”, “3”,. The rows of the key priority designation table 46 are rearranged (SP32).

  Subsequently, the data availability management control unit 31 selects one replication source node 3 from the replication source nodes 3 (SP33), and the node 3 registered in the replication destination node list corresponding to the replication source node 3 One of the nodes 3 is selected (SP34), and for the replication source node 3 selected in step SP33, the replication source node 3 is selected in descending order of the priority registered in the search key priority specification table 46. Are compared with the values of all the nodes 3 registered in the replication destination node list corresponding to (SP35).

  Next, the data availability management control unit 31 determines whether or not the node 3 selected in step SP34 satisfies all the conditions (SP36), and if an affirmative result is obtained in this determination, the process proceeds to step SP38. On the other hand, if the data availability management control unit 31 obtains a negative result in the determination at step SP36, it deletes the node 3 selected at step SP34 from the replication destination node list corresponding to the replication source node 3 selected at step SP33. At the same time, the node 3 is registered in the duplication prohibited node list associated with the duplication source node 3 selected in step SP33 (SP37).

  Thereafter, the data availability management control unit 31 finishes executing the processing of step SP34 to step SP37 for all the nodes 3 registered in the replication destination node list associated with the replication source node 3 selected in step SP33. It is determined whether or not (SP38). If the data availability management control unit 31 obtains a negative result in this determination, the data availability management control unit 31 returns to step SP34, and then sequentially switches the node 3 selected in step SP34 to another node 3 that has not been processed, step SP34 to step SP38. Repeat the process.

  Then, the data availability management control unit 31 eventually finishes executing the processing of step SP34 to step SP37 for all the nodes 3 registered in the manufacturer node list associated with the replication source node 3 selected in step SP33. If an affirmative result is obtained in step SP38, it is determined whether or not the processing in steps SP33 to SP38 has been executed for all the replication source nodes 3 (all the nodes 3 whose accessibility is less than the accessibility lower limit value). (SP39).

  If the data availability management control unit 31 obtains a negative result in this determination, the data availability management control unit 31 returns to step SP33, and then sequentially switches the replication source node 3 selected in step SP33 to another replication source node 3 that has not been processed. The processing from SP33 to step SP39 is repeated.

  When the data availability management control unit 31 finally obtains a positive result in step SP39 by completing the execution of the processing of step SP33 to step SP38 for all the replication source nodes 3, it ends this simulation screen display and list creation processing. .

(5) Effects of this Embodiment As described above, in the distributed file system 1 according to this embodiment, the data availability management control device 5 can access the data held by each node 3 when a setting risk occurs. The node 3 where the data is arranged and the accessibility of the node 3 are associated with each other and displayed on the screen. Therefore, according to the distributed file system 1, it is possible to identify the node 3 selected by the system administrator to satisfy the availability of data, the location of the node 3, and the data stored in the node 3. As described above, according to the present distributed file system 1, it is possible to avoid the loss of data, and to manage the availability of data so that the state in which data can be accessed can be maintained even in the event of a natural disaster that is anticipated in advance. Information can be provided.

  In the distributed file system 1, for each node 3 whose accessibility is less than the accessibility lower limit value, the recommended replication destination node 3 and the replication prohibition node 3 are respectively determined and notified to the DFS management apparatus 4. Further, the DFS management apparatus 4 is notified from the data availability management control apparatus 5 and should be the replication source node 3 other than the recommended replication destination node 3 or the replication prohibited node 3 notified of the data held by the node 3. The node 3 that should be the replication source node is controlled so as to be replicated to the node 3.

  Therefore, according to this distributed file system 1, it is possible to avoid loss of data held by each node 3 in the distributed file system 1, and to make it possible to access data even in the event of a natural disaster assumed in advance. Data availability can be managed and controlled so that it can be maintained. Thus, according to the distributed file system 1, a highly reliable distributed file system can be constructed.

(6) Other Embodiments In the above-described embodiments, each management table is configured as shown in FIGS. 2 to 7 and each GUI screen is configured as shown in FIGS. However, the present invention is not limited to this, and various other configurations can be widely applied.

  In the above embodiment, the case where “earthquake”, “water damage”, “tsunami” and “volcanic eruption” are applied as natural disasters that can be set as set risks has been described. The invention is not limited to this, but instead of these, or in addition to these, other natural disasters (storm surges and earth and sand disasters, ground disasters such as liquefaction, landslides and landslides) are similarly set as set risks, The above accessibility simulation may be executed for the natural disaster.

  Furthermore, in the above-described embodiment, the case where only a natural disaster is applied as a disaster has been described. However, the present invention is not limited to this, and a fire accident other than a natural disaster, a traffic accident, a post-work situation, and / or a situation of status It is also possible to execute an accessibility simulation similar to that described above with a disaster (such as a conflict) as a disaster.

  Furthermore, in the above-described embodiment, the node management table 40 (FIG. 2), the network information management table 41 (FIG. 3), the commercial power equipment information management table 43 (FIG. 5), and the wiring equipment information management table 44 (FIG. 6). ) And the disaster risk management table 45 (FIG. 7), the address of the node 3 and each facility is managed as a character string or a code according to “information about wiring facilities” according to the optical fiber route address specification. Although the present invention has been described, the present invention is not limited to this, for example, an area code defined by ISO (ISO 3166, ISO 3166-2, etc.), a prefecture code (JIS X0401) defined by JIS, and a city code (JIS X0402). ), National local government codes established by the Ministry of Internal Affairs and Communications, and numerical values indicating background and latitude. May be.

  DESCRIPTION OF SYMBOLS 1 ... Distributed file system, 2 ... Network, 3 ... Node, 4 ... DFS management apparatus, 5 ... Data availability management control apparatus, 30 ... Screen processing part, 31 ... Data availability management control part, 32 ... Storage device, 40 ... Node management table, 41 ... Network information management table, 42 ... Indoor power equipment information table, 42 ... Commercial power equipment information management table, 44 ... Wiring equipment information management table, 45 ... ... disaster risk management table, 46 ... search key priority specification table, 47 ... replication destination node list information, 48 ... replication prohibition node list information, 50 ... main screen, 60 ... node management screen, 70 ... Node management information editing screen, 80 ... Assumed risk setting screen, 90 ... Assumed earthquake scale setting screen, 94 ... Assumed tsunami scale setting screen, 95 ... Assumed water Scale setting screen, 96 …… Expected volcanic eruption scale setting screen, 100 …… Condition setting (details) screen, 120 …… Search key priority specification table editing screen, 130 …… Condition setting (simple) screen, 140 …… Data Availability-oriented condition setting screen, 150 …… Performance-oriented condition setting screen, 160 …… Customizing condition setting screen, 170 …… Simulation execution screen, 180 …… Replication source node list screen, 190 …… Replication destination node list screen , 200 ... Duplication prohibited node list screen.

Claims (12)

A management device connected to a plurality of nodes via a network and managing data held by each of the nodes;
A data availability management control device for managing and controlling availability of the data held by the nodes with respect to disasters,
The data availability management control device includes:
Damage risk value for disasters between the installation location of the node and the installation location of the equipment used by the node, wiring path facility route information of the network used by the node, and maintenance schedule of the node, network , power supply facility or distribution facility , Information from the management device,
Based on the damage risk value, the wiring path facility route information and the information related to the maintenance schedule, calculate the accessibility to the data held by the node,
Correlate the node where the data is located and the accessibility of the node to the screen ,
Further, for a node whose calculated accessibility is lower than a predetermined value, a node to be a copy destination of the data held by the node is determined, and the copy source and the copy destination of the data are set in the management apparatus. Notify
The distributed file system , wherein the management device replicates data of the node based on a replication source and a replication destination of the data . The data availability management control device includes:
Holds the installation location of the node and the damage risk value of the equipment used by the node,
2. The distributed file system according to claim 1 , wherein the accessibility to the data held by the node at the time of disaster is calculated based on the held disaster risk value. The damage risk value is
The distributed file system according to claim 2 , wherein the distributed file system is calculated based on a disaster type and scale. The data availability management control device includes:
Displays the input request for the assumed risk,
The distributed file system according to claim 2 , wherein the access possibility to the data held by each of the nodes at the time of occurrence of an assumed risk is calculated. The data availability management control device includes:
2. The distributed file system according to claim 1 , wherein a node satisfying a preset condition is determined as a data replication destination. The data availability management control device includes:
Display the data replication destination node condition input request,
6. The distributed file system according to claim 5 , wherein a node satisfying the received condition is selected from a node management table and determined as a data replication destination. Data availability management and control device in distributed file system, disaster risk value for disaster at location of node and installation location of equipment used by node, wiring path facility route information of network used by node, and node and network Receiving information on the maintenance schedule of the power supply facility or distribution facility from the management device that manages the data held by each of the plurality of nodes connected via the network
The data availability management control device calculates the accessibility to the data held by the node based on the disaster risk value , the wiring path facility route information and the information related to the maintenance schedule ,
The data availability management control device associates the node where the data is located with the accessibility of the node and outputs it on the screen,
Further, for a node whose calculated accessibility is lower than a predetermined value, a node to be a copy destination of the data held by the node is determined,
Notifying the management device of the data source and destination,
A data availability management control method in a distributed file system , wherein the management device replicates data of the node based on a replication source and a replication destination of the data. The data availability management control device holds the installation location of the node and the disaster risk value of the equipment used by the node,
8. The data availability management control method according to claim 7 , wherein the accessibility to the data held by the node at the time of a disaster is calculated based on the held disaster risk value. The damage risk value is
9. The data availability management control method according to claim 8 , wherein the data availability management control method is a combination with a calculation based on a disaster type and a scale. The data availability management control device displays an input request for an assumed risk,
8. The data availability management control method according to claim 7 , wherein the access possibility to the data held by each of the nodes at the time of occurrence of an assumed risk is calculated. The data availability management control device includes:
8. The data availability management control method according to claim 7 , wherein a node satisfying a preset condition is selected from a node management table and determined as a data replication destination. The data availability management control device displays a data replication destination node condition input request,
12. The data availability management control method according to claim 11 , wherein a node satisfying the received condition is selected from a node management table and determined as a data replication destination.

Images