JP2016181292A - Information processing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information processing system capable of performing a failover and a failback according to a scheduled power stoppage.SOLUTION: An information processing system includes a server device for storing a database and a plurality of client units connected to the server device to each other via a LAN, in which at least one of the client units is a client unit which can be driven with a battery. The server device executes: a step 1 to store scheduled power stoppage information including at least a scheduled power stoppage start time and a scheduled power stoppage termination time in the database; a step 2 to monitor whether time reaches predetermined time before the scheduled power stoppage start time; and a step 3 to request a failover to the client unit which can be driven with the battery when the time has reached the predetermined time before the scheduled power stoppage start time by the step 2.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an information processing system that performs failover and failback in response to a planned power outage.

  There is a system that can continue the system operation by taking over the process to a sub server when a failure such as a power failure occurs in the main server in charge of the service. For example, Patent Document 1 describes a process migration method between networks in which when a failure occurs in a server due to a fire or the like, the processing is switched to a remote backup server that does not reach the failure and the processing of the terminal is continued. Yes.

JP2009-282714

  When a power outage occurs over a wide area due to a planned power outage by dividing the target area into a planned power outage If the large-scale system has a backup server in a remote location, a remote backup server that does not suffer from a failure Failover that takes over processing can be implemented. However, there are many small systems that do not have backup servers in remote locations. For example, in the case of a hospital system, a hospital LAN is installed, and the server and client (terminal) are installed in the same building or in the same site to operate the system. In the case of such a system, when a planned power outage was implemented and the target area was reached, all servers and clients could not operate, and the system could not be operated. Therefore, in the present invention, even in a small-scale system that does not have a backup server in a remote place, when a planned power outage is planned, a failover is performed in advance and the system can be operated with a reduced scale configuration. / To provide a system.

  The present invention is an information processing system configured by connecting a server that stores a database and a client device via a LAN, and at least one of the client devices can be driven by a battery. Planned power outage information including at least a planned power outage start time and a planned power outage end time is acquired from the outside via a network, and the planned power outage information is stored in the database, and a predetermined time before the planned power outage start time By performing step 2 for monitoring whether or not it has reached a predetermined time before the planned power outage start time, and step 3 for requesting failover to a battery-operable client device. It solves the problem.

  According to the information processing system of the present invention, when a planned power outage is performed, the failover is performed a predetermined time before the planned power outage is started and the commercial power supply is turned off. Can be implemented. In addition, since servers and clients that are not backed up by a battery are shut down before a planned power outage is started and commercial power is cut off, it is possible to prevent an unexpected failure. In addition, since it is notified in advance that the system is shut down in preparation for a planned power outage and that a predetermined terminal is failed over, the operator can prepare for it and avoid unnecessary confusion.

It is a figure which shows the structure of the information processing system of embodiment. It is a figure explaining the operation | movement procedure of embodiment. It is a figure explaining the operation | movement procedure of embodiment. It is a figure which shows the operation | movement procedure of the failover of embodiment. It is a figure which shows the operation | movement procedure of the failback of embodiment.

  FIG. 1 shows the configuration of the information processing system 10 in the embodiment of the present invention. This system assumes a hospital system where an electronic medical record terminal and a medical accounting terminal are connected to a LAN in a medical institution. A server computer 30 (server device 30; simply referred to as server 30 hereinafter) and a plurality of client computers 20, 20 (client device 20; client device 20; hereinafter simply referred to as client 20) such as an electronic medical record terminal and a medical accounting terminal. ), And the backup disk device 40 are communicably connected to each other via a LAN line 51 to constitute a hospital system. Further, a network control device 50 is connected to the LAN line 51 and is connected to an external network (Internet) 60 via the network control device 50.

  The server 30 is an information processing device including a computer, and includes a control unit configured by a CPU, a memory such as a RAM and a ROM, an input device such as a keyboard, a display device such as an LCD, and a hard disk drive (HDD). The configured file device and the communication control device are connected by an internal bus.

  The file device includes a basic program such as an OS (operating system) and files of business application software that provides various services to the clients 20 and 20 upon request of the clients 20 and 20, a database of the hospital system, and a planned power outage A control program S for acquiring information and controlling power on / off of the backup disk device 40 and a control program C for executing backup processing and shutdown are recorded. Information on the planned power outage acquired by the control program S is recorded in a data file in the file device. This data file functions as a planned power outage information storage unit for storing planned power outage information. It is assumed that location information, which is information on the location (address) where the server 30 or the information processing system 10 to which the server 30 belongs, is recorded in advance in the data file in the file device. The data file and the database may be integrated with the database without being divided.

  On the other hand, the clients 20 and 20 are also information processing devices including computers, like the server 30, and include a control unit configured by a CPU, a memory such as a RAM and a ROM, an input device such as a keyboard, and a display device such as an LCD. , A file device constituted by a hard disk drive (HDD) and the like, and a communication control device are connected by an internal bus.

  The file device stores a basic program such as an OS and various business software files, and a control program C that executes backup processing and shutdown in the same manner as the server 30. The CPU of each client introduces and executes this control program C, thereby backing up data recorded in the file device to a backup disk device 40 described later and shutting itself down.

  Here, at least one of the plurality of clients 20 and 20 is backed up by a battery, and is configured to be able to operate separately from a commercial power source. Hereinafter, this battery-backed client is referred to as client A, and the other non-battery-backed clients are referred to as client B. In the figure, there is one client B, but a plurality of clients B may be connected. Instead of the above-described control program C, the client A is recorded with a control program A for controlling on / off of the server and other clients B, that is, starting and stopping, and controlling failover and failback.

  The backup disk device 40 is a large-capacity file device composed of a hard disk drive (HDD) or the like, and functions as a backup device that records a copy of a file transmitted from each terminal device according to an instruction. The backup disk device 40 also includes a communication control device.

  The communication control devices of the server 30, the client 20, and the backup disk device 40 have a WOL (Wake On Lan) function, a PXE (Preboot eXecution Environment) function, a multicast reception function, and the like. For this reason, the server 30 and the communication control device of the client 20 are backed up by a battery.

  Next, with reference to FIG. 2 thru | or 3, the operation | movement which performs failover and failback in response to a planned power failure in this system is demonstrated. In this embodiment, the server 30 acquires information on the planned power failure in advance, and when the scheduled power failure start time approaches, a failover that takes over server processing to the client A that has been backed up by the battery is performed, and the planned power failure ends. After confirming this, failover is performed from the battery-backed client A to the original server.

  First, the failover operation will be described with reference to FIG.

<S11>
When the server 30 is activated or according to a predetermined schedule, the server 30 accesses the power company website 70 via the network control device 50 and the external network 60, and acquires information on the planned power outage. The acquired planned power outage information is recorded in a data file in the file device. The planned power outage information includes at least the planned power outage start time, the planned power outage end time, and information on the planned power outage implementation area.

  In addition, when acquiring information on the planned power outage, only information on the planned power outage start time and the planned power outage end time related to the location of the user may be acquired. Moreover, since it is conceivable that the information on the planned power outage is updated as needed, it is preferable that the information on the planned power outage is periodically acquired according to a predetermined schedule to obtain the latest information.

<S12>
The server collates its own location information recorded in the data file in the file device with information on the planned power outage area, and the planned power outage start time corresponding to the information on the planned power outage area including its own location is obtained. Monitor for approaching. That is, it is determined whether or not a predetermined time before the planned power outage start time has been reached. Here, the predetermined time is set to a time having a sufficient margin with respect to the time required for completing the failover operation. Further, the predetermined time may be set with a margin in anticipation that the start of the planned power outage slightly varies.

  In addition, although the own location information is set in advance by an operator or the like, a GPS (Global Positioning System) may be installed and automatically acquired and set from there.

<S13>
When the server determines that the predetermined time before the planned power outage start time has elapsed, it notifies all of the clients 20 and 20 that failover processing will be started. At the same time, the control program A of the client A backed up by the battery is activated. Here, the client B and the server 30 that have received the failover start notification are shut down in preparation for a planned power outage, and the client A is failed over to be displayed on the display device, and each operator is notified. Can do. In addition, the client A can display on the display device that the server 30 and other terminals are shut down in preparation for a planned power outage, and that the client A can fail over and continue processing, and notify the operator. it can.

<S14>
In response to this, the control program A of the client A copies the database of the server 30 and the data file in which the planned power outage information is recorded to the file device of the client A. Here, the file device of the client A functions as a database storage unit for copying and storing the server database.

<S15>
Then, the control program A of the client A activates the control program C of the server 30 and the control program C of the client B, respectively, and requests shutdown.

<S16>
In response to this, the control program C of the client B backs up the database of the client B to the backup disk device 40, and then shuts down the client B itself.

<S17>
On the other hand, the control program C of the server 30 backs up the database of the server 30 to the backup disk device 40.

<S18>
The control program A of the client A requests the control program S of the server 30 to turn off (turn off) the backup disk device 40 and shut down the server 30.

<S19>
The control program S of the server 30 turns off the power of the backup disk device 40, and then shuts down the server 30 itself.

  In this way, failover is performed from the server 30 to the client A that is backed up by the battery. On the other hand, in preparation for a planned power outage, the server 30 and the client B that are not backed up by battery are shut down before the planned power outage start time so as not to cause an unexpected failure due to power interruption during operation. Thereafter, even if the planned power failure is started and the commercial power supply is interrupted, the client A switches from the commercial power supply to the battery drive, so that the processing can be continued.

  Note that the server 30 may continuously perform steps S17 and S19 in response to the request in step S15. In other words, after the database is backed up to the backup disk device 40, the backup disk device 40 may be continuously turned off and the server 30 itself may be shut down continuously.

  Next, the failback operation after the planned power outage will be described with reference to FIG.

<S51>
Client A's control program A collates the location information recorded in the data file copied from the server's file device with the information on the planned power outage area and supports the information on the planned power outage area including that location. The planned power outage end time is referred to and compared with the current time to monitor whether the planned power outage end time has been reached.

<S52>
When the control program A of the client A determines that the planned power outage end time has come, it reads information indicating the state of the AC power supply (commercial power supply) from the AC power supply unit and determines whether the commercial power supply has recovered. Here, the AC power supply unit functions as an energization information storage unit that stores energization presence / absence information indicating whether the commercial power supply is energized.

<S53>
When the control program A of the client A determines that the commercial power has been restored, the control program A transmits a WOL packet to the server 30 and the client B, and starts the server 30 and the client B.

<S54>
When the server 30 is started, the control program A of the client A reflects the update made to the database of the client A during the planned power outage period, that is, during the failover. Then, the client A fails back to the server 30 to return the processing to the server 30.

  Thereafter, the server 30 can continue the normal processing.

  As described above, according to the present embodiment, when a planned power failure is performed, the process can be continued with a minimum configuration by failing over to a battery-backed terminal. At that time, since the failover is performed a predetermined time before the planned power failure is started and the commercial power supply is cut off, the failover can be smoothly performed without any trouble. Further, since the server and the client B that are not backed up by the battery are shut down before the planned power failure is started and the commercial power supply is cut off, it is possible to prevent an unexpected failure from occurring. In addition, since the operator is notified of the shutdown in preparation for the planned power failure and the failover to the client A, the operator can prepare for it and avoid unnecessary confusion. .

10 Information processing system 20 Client computer 30 Server computer 40 Backup disk device 50 Network control device 60 External network

The present invention is an information processing system including a server device that stores a database and a client device that are connected via a LAN, and at least one of the client devices can be driven by a battery. A possible client device includes a database storage unit that copies and stores the database of the server, and an energization information storage unit that stores energization presence / absence information indicating whether the commercial power supply is energized .

Claims (3)

A server device for storing a database and a client device are connected to a LAN, and at least one of the client devices is an information processing system including a client device capable of battery driving,
The server device is
Step 1 for acquiring planned power outage information including at least a planned power outage start time and a planned power outage end time from outside via a network, and storing the planned power outage information in the database;
Step 2 for monitoring whether a predetermined time before the planned power outage start time has been reached,
If it is determined in the step that a predetermined time before the planned power outage start time has been reached, a step 3 of requesting a failover to the client device capable of battery driving;
An information processing system characterized by executing The battery-driven client device is
A database storage for copying and storing the server database;
An energization information storage unit for storing energization presence / absence information indicating the presence / absence of energization of a commercial power supply;
With
In response to a failover request from the server device, step 4 for reading the database of the server device and copying it to its own database storage unit a predetermined time before the planned power outage start time;
Step 5 for requesting the server device and other client devices to shut down;
Step 6 of taking over the processing of the server device and failing over,
Reading planned power outage information from the database and monitoring whether the planned power outage end time has been reached,
Step 7 for determining whether or not the commercial power source is in an energized state with reference to the energization presence / absence information in the energization information storage unit when it is determined that the planned power outage end time has been reached by the step;
If it is determined in the step that the commercial power source is in an energized state, step 8 for controlling the activation of the server device and other client devices;
Step 9 of reflecting the update contents of the own database to the database of the server device and failing back to the server device;
The information processing system according to claim 1, wherein: The information processing system further comprises a backup device,
3. The information processing system according to claim 2, wherein in accordance with step 5, the server apparatus and another client apparatus execute step 10 of shutting down after performing backup processing to the backup apparatus.

Images