JP2007094604A - Computer backup system for countermeasure against disaster - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a computer backup system for countermeasures against disasters attaining immediate startup of a backup auxiliary system in occurrence of a disaster. <P>SOLUTION: The computer backup system for countermeasures against disasters is provided with a plurality of regular systems having storage devices and servers, and a center comprising storage devices corresponding to the storage devices of the regular systems. The center is provided with backup storage devices in the same number as the storage devices of the regular systems and holding data, OSes, patches and application programs held in the storage devices of the regular systems, and a server group for countermeasures against disasters with a smaller number of servers arranged. OSes, patches, application programs, and the like are stored in the backup storage devices besides user data. In occurrence of the disaster, the servers of the center can be started early using the OSes, patches, application programs, and the like. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a computer backup method for disaster countermeasures such as earthquakes and floods, and in particular, reduces the cost of constructing a backup system by sharing a server that is used for switching in the event of a disaster when constructing a disaster countermeasure system. This makes it possible to operate a disaster countermeasure system even for users who are difficult to construct a disaster countermeasure system at a remote location.

  In the enterprise, when the information system, that is, the computer system is stopped, the corporate activity itself is stopped. Therefore, in order to quickly recover the work in the event of a disaster of the computer system, for example, as shown in FIG. Build the same two systems.

  The primary system A is composed of a storage apparatus 100 having a remote copy 101, a server 102, a fiber channel switch 103, etc., and the secondary system B is a storage apparatus 200 having a remote copy 201, a server 202, a fiber channel switch 203, etc. Consists of. The primary system A and the secondary system B are connected by a wide area network WAN.

  Normally, for example, the primary system A is operated and the backup operation is performed by the secondary system B. When the primary system A is damaged, switching to the remaining secondary system B is performed.

  These two systems, the primary system A and the secondary system B, are composed of the servers 102 and 202 for processing, the storage apparatuses 100 and 200 for storing data, and related devices as described above.

  In order to continue business even in the event of a disaster, it is necessary to store equivalent data in the storage devices 100 and 200 of these two systems. For this purpose, a process of transferring data between the primary system A and the secondary system B is executed in parallel with the business. This processing is often realized by a data transfer function of a server or a storage device (in FIG. 13, illustrated as remote copies 101 and 201 for the storage devices 100 and 200, respectively).

  For example, data to be written in the storage apparatus 100 is transferred and written to the storage apparatus 200 by the remote copy 101 via the switch 103, the wide area network WAN, and the switch 203.

  When two systems are constructed in preparation for a disaster, the two systems often have a device configuration with an equivalent capability in order to ensure processing capability after system switching. This requires double the cost for a single system. In addition to fires, the two systems need to be separated from each other in order to prepare for natural disasters such as earthquakes and floods. For example, in order for two systems not to be affected by an earthquake at the same time, it is said that the distance between the systems needs to be separated by about 60 to 100 km. As a result, it was difficult for companies that consisted of only a single office and organizations such as local governments that had limited system installation areas to construct two systems for natural disasters.

Therefore, conventionally, in a backup apparatus that backs up an information processing system in which a failure has occurred in order to back up a plurality of remote systems distributed over a wide area with a single system and realize continuous data processing, the backup The apparatus includes a resource pool that holds configuration resources that are resources constituting the backup system, and the configuration resources necessary for the backup system configuration mechanism to configure a backup system having the same system configuration as the failure occurrence information processing system. A resource management mechanism that selects from the configuration resources held in the resource pool and allocates the selected configuration resources to the backup system, and the backup system configuration mechanism is allocated by the resource management mechanism. It has been proposed to configure the backup system by using a temple configuration resource.
JP 2001-306349 A

  In the above prior art, although user data is stored as backup data, the OS, patches, and application programs (hereinafter referred to as applications) necessary for computer operation are not backed up. Therefore, even if a disaster occurs and an attempt is made to start up a backup device, it is necessary to read and install the OS, patches, and applications required outside of the data separately, which is very long for the construction of a backup system. There was a problem of needing time.

  In order to solve the above-mentioned problems, the present invention provides a disaster countermeasure computer backup system as described in (1) and (2) below.

  (1) In a disaster countermeasure computer backup system comprising a plurality of primary systems having a storage device and a server, and a center having a storage device corresponding to the storage device of the primary system, the storage device of the primary system is installed in the center A disaster in which the same number of backup storage devices as the primary system storage device and the number of disaster countermeasure servers less than the number of backup storage devices are stored. First management in which the server group for countermeasures, the storage device function used in the primary system, the server name and function, and the server name of the center connected to the storage device of the center used in the event of a disaster are entered Table, center server name and function, server machine The second management table in which the status is written, the first management table, and the second management table are managed, and when the backup server used for the backup storage device is selected in the center at the time of disaster, the storage A management server that holds a network control table having network control data indicating a connection path between a device and the backup server, and when the center is notified that a disaster has occurred in the primary system, the management server A disaster countermeasure server suitable for the backup storage device corresponding to the primary system is selected from the disaster countermeasure server group with reference to the first management table and the second management table, and based on the network control table, This disaster recovery server is used as the backup storage. Characterized by connection control to location.

  (2) In the disaster countermeasure computer backup method according to (1), the storage system of the primary system has remote copy means for transferring the written data, OS, patch, and application to the center storage system. Features.

  The present invention has the following effects (1) and (2).

  (1) The secondary center's backup storage device holds information necessary for the operation of the computer, such as the OS, patches, and apps, in addition to the data essential for disaster recovery. Even if a system failure occurs, the server assigned at the time of system switching starts up using it, and the backup system can be started up quickly as a secondary system that can start up very quickly, ensuring system reliability. be able to.

  (2) Since the remote copy function of the storage device is used for transferring data, OS, patches, applications, etc. from the primary system to the storage device in the center, it is not necessary to use server resources on the center side. The amount of hardware can be reduced.

  An embodiment of the present invention will be described with reference to FIGS.

  FIG. 1 is an embodiment of the present invention, FIG. 2 is an explanatory diagram of a configuration state of the present invention, FIG. 3 is an explanatory diagram of normal operation of the present invention, FIG. 4 is an explanatory diagram of normal backup data of the present invention, and FIG. Is an operation explanatory diagram of the disaster countermeasure server according to the present invention, FIG. 6 is an operation explanatory diagram of the disaster countermeasure server at the time of disaster (Part 1), FIG. 7 is an operation explanatory diagram of the disaster countermeasure server at the time of disaster (Part 2), FIG. 8 is a diagram for explaining the operation of the disaster countermeasure server when a disaster occurs (part 3), FIG. 9 is a diagram for explaining the operation of the disaster countermeasure server when a disaster occurs (part 4), and FIG. 10 is a diagram for explaining the management table during normal operation. Is an explanatory diagram of the management table when a disaster occurs, and FIG. 12 is an explanatory diagram of the operation of the management server in the present invention.

  In FIG. 1, 1, 1-A to 1-N are primary systems, 2-A to 2-N are storage devices of the primary system, 3-A to 3-N are servers of the primary system, 10 is a center, 11- A 'to 11-N' are storage devices of the center 10, 12 is a management server, 13 is a hardware pool, 13-a to 13-m are disaster countermeasure servers, and have a size relationship of N> m, 14 A control unit, 15 is a first management table, 16 is a second management table, 17 is a network control table, 18 is resource allocation control means, and 19 is network control means.

  The primary system 1 is a data holding unit that stores data obtained as a result of data processing performed by the user, and also stores the OS, patches, applications, and the like necessary for the data processing as well as the data. For example, it has a primary system 1-A of user A company to a primary system 1-N of user N company.

  Each primary system, as will be described representatively with respect to the primary system 1-A, a storage device 2-A that stores the data, OS, patch, and application, and a read / write instruction to the storage device 2-A The server 3-A is provided. Similarly, the primary systems 1-B to 1-N of other users include storage apparatuses 2-B to 2-N and servers 3-B to 3-N.

  The center 10 holds and backs up the data, OS, patches, and applications stored in the primary system 1, and the storage devices 2-A to 2- provided in the primary systems 1-A to 1-N. Backup storage apparatuses 11-A ′ to 11-N ′ having the same number as N and corresponding functions to the storage apparatus are provided in the center. That is, the storage apparatuses 2-A and 11A ′ have the same function.

  When the primary system is damaged, the management server 12 recognizes the damaged primary system, selects a backup storage device in the center 10 corresponding to the primary system, and selects the backup storage device and the storage device. A server suitable for the apparatus is selected from the hardware pool 13 and combined to construct a sub-system, and processing for taking over the business from the damaged main system is performed.

  The management server 12 is provided with a control unit 14, a first management table 15, a second management table 16, and a network control table 17, and the control unit 14 is provided with resource allocation control means 18 and network control means 19.

  The control unit 14 is composed of a CPU, and the resource allocation control unit 18 and the network control unit 19 are programs for performing control described later. The first management table 15, the second management table 16, and the network control table 17 are composed of memories.

  The hardware pool 13 holds the disaster countermeasure servers 13-a to 13-m necessary for performing a backup operation of the storage device that backs up the damaged primary system when the primary system is damaged. The number m of the disaster countermeasure servers 13-a to 13-m held in the hardware 13 is smaller than the number N of the backup storage apparatuses 11-A ′ to 11-N ′, and the relationship N> m is satisfied. It is in.

  As shown in FIGS. 10 and 11, the first management table 15 includes a system name of the primary system (for example, company A system), a server name / function of the primary system, a storage name of the primary system, a system state, a storage name of the center, The server name of the center is entered.

  As shown in FIGS. 10 and 11, the second management table 16 is filled with the server name / function of the center, the usage status, and the like.

  In the management tables 15 and 16, an example in which a U model server and an I model server are used is shown, and the U model server and the I model server are not compatible.

  When a disaster occurs, the network control table 17 indicates a route for forming a connection circuit for connecting the disaster countermeasure servers corresponding to the backup storage device of the center 10 from the hardware pool. Thus, the selected disaster countermeasure server can be accurately connected to the backup storage apparatus.

  Next, the operation of the present invention will be described with reference to FIGS. 20 selectively stores backup storages 11-A ′, 11-B ′... 11-N ′ and disaster countermeasure servers 13-a 13-b 13-m in the center 10. It is a connection network to be connected.

  2 corresponds to the storage devices 2-A, 2-B,... 2-N in FIG. 1, and the servers A, B,... N in FIG. It corresponds to the servers 3-A, 3-B, 3-N. The storage apparatuses A ′, B ′... N ′ of the center 10 in FIG. 2 correspond to the storage apparatuses 11-A ′, 11-B ′.

  The storage device A includes a storage unit A that stores data, OS, patches, and applications, which will be described later, and a controller A that performs a read / write operation based on instructions from the server A. Similarly to the storage apparatus 2-A, the other storage apparatuses 2-B,..., 2-N include storage units B.

  The storage device A ′ for backup provided in the center 10 also stores a storage unit A ′ for storing data, OS, patches, and applications, which will be described later, and reads the data, OS, patches, and applications to the storage unit A ′. A controller A ′ that performs a write operation is provided. Similarly to the storage apparatus 11-A ′, the other storage apparatuses 11-B ′... 11-N ′ of the center 10 also have storage units B ′... N ′ and controllers B ′. It has.

  The disaster countermeasure servers a,... M provided in the center 10 correspond to the disaster countermeasure servers 13a.

  When the management server selects the backup storage apparatuses 11-A ′... 11-N ′ and the disaster countermeasure servers a, b. A connection circuit between the storage apparatus and the disaster countermeasure server is formed.

  As shown in FIG. 3, when each primary system is operating normally in the present invention, the server A performs read / write control on the storage apparatus A. The data, OS, patch, and application written in the storage unit A are accumulated in the storage unit A ′ of the backup storage device provided in the center 10 by the remote copy function of the storage device A.

  Similarly, data, OS, patches, applications, etc. written to the storage devices B... N of the primary system are accumulated in the storage devices B ′. At this time, the connection network 20 is off, and the storage apparatuses A ′, B ′... N ′ are not connected to any of the disaster countermeasure servers a, b.

  The normal backup data of the present invention is shown in FIG. As shown in FIG. 4, in the main system including the storage apparatus B and the server B, when write processing is performed on the storage unit B, the write data includes so-called user data, OS, patch, as shown in FIG. When these are stored in the storage unit B, the same backup data, OS, patch, and application are also stored in the storage unit B ′ of the backup storage device.

  The operation of the present invention when a disaster occurs will be described with reference to FIGS.

  As shown in FIG. 5, when a disaster occurs in the main system including the server B and the storage apparatus B, the management server 12 detects this and refers to the management table 1 and the management table 2 to refer to the same as the server B. The function disaster countermeasure server a is selected and connected to the storage apparatus B ′.

  Then, as shown in FIG. 6, the disaster countermeasure server a reads data stored in the storage unit B ′ of the storage apparatus B ′, backup data such as OS, patches, and applications, and the like, and the server of the primary system. Can operate as an alternative to B. FIG. 7 shows the details of the backup data read by the disaster countermeasure server a from the storage device B ′. Since the alternative data is stored, the server a is used to connect the secondary system together with the storage device B ′. You can see that it can be built.

  Thus, as shown in FIG. 8, the primary system A (Company A system) and N (Company N system) operate in the same configuration as before, but the primary system B (Company B system) has a disaster, This time, the secondary system can be constructed and operated using the disaster countermeasure server a instead of the storage device B ′ and the server B.

  At this time, as shown in FIG. 9, what is stored in the storage apparatus B ′ in the secondary system is data, OS, patches, and applications, which are the same as those in the normal operation shown in FIG.

  The operation process of the present invention will be described with reference to FIG.

  S1. Prior to the start of operation by constructing the primary system or center, etc., before the servers A, B,... N of each primary system operate, the management server 12 receives data (in this case, data and Represents user data, OS, patch, application, etc.)). For this reason, the contents of the storage devices A, B... N of the primary system and the storage devices A ′, B ′. If the matching operation is completed, a report is requested from the management server 12 so that the matching process can be performed.

  S2. The management server 12 waits for the data matching between all corresponding storage apparatuses to be completed.

  S3. After the match is completed, normal processing is started.

  S4. In the primary system, for example, if there is a data write request, the process proceeds to the next S5, and if there is no write request, the process proceeds to S6 described later.

  S5. In S4, if there is a data write request, write processing is performed on the storage device of the primary system, and it is transferred to the corresponding storage device (for example, storage device A ′ for storage device A) and stored therein. In this transfer, if the remote copy function of the storage apparatus A is used, it is not necessary to use the server resource of the center.

  S6. If the main system is not damaged, the process returns to S1 of S3 and waits for the next data write. However, if it is damaged, the process proceeds to the next S7. If the main system is damaged, the center 10 is notified, and the management server 12 can detect the damage and recognize the damage.

  S7. For example, when the management server 12 detects that the main system B company system shown in FIG. 8 has been damaged, the control unit (configured by the CPU) of the management server 12 controls its resource allocation control means 18 and the first management table 15 , The second management table 16 is accessed to recognize the server name and function of the server B of the company B system, and the server held in the hardware pool 13 of the center 10 applicable to this is the server a. And the server b is selected from the center side server. Then, the management server 12 controls the network control means 19, accesses the network control table 17, obtains connection data in the connection circuit network for selectively connecting the server a and the storage device B ', and selects and controls them. To do. Thereby, in the center 10, as shown in FIG. 5, the storage apparatus B 'and the server a are connected, and a secondary system is constructed.

  S8. Next, as shown in FIG. 6, the server a reads the data such as the OS from the corresponding storage apparatus B ′.

  S9. This reading is performed until completion.

  S10. When the reading is completed, as shown in FIG. 8, normal processing can be resumed using a sub-system constructed on the center side composed of the server a and the storage apparatus B ′.

  S11. When operating using the secondary system in this way, if the damaged system is recovered, this is reported to the management server 12.

  S12. As a result, this time, the OS, patch, application, user data, etc. are transferred from the storage system B ′ on the secondary system side to the server B on the primary system. Match the data content of B '.

  S13. If they match, all the alternative controls are completed, the normal process can be started, and the process can move to the circle 1 in FIG.

  In the present invention, software data necessary for the operation of the primary system such as the OS, patches, and applications is stored in the storage device on the center side in addition to the corresponding primary system user data. When the prepared disaster countermeasure server is started using the server, it is possible to quickly start operation as a secondary system.

  Further, when building a disaster countermeasure system in consideration of damage to the system, the construction cost can be reduced by sharing the system to be switched at the time of the disaster, that is, the center system. In addition, users who have difficulty building a disaster countermeasure system at physically distant locations can operate the disaster countermeasure system by sharing the center system.

1 is an embodiment of the present invention. It is a configuration state explanatory view of the present invention. It is operation | movement explanatory drawing at the time of normal of this invention. It is backup data explanatory drawing of this invention. It is operation | movement explanatory drawing at the time of disaster of this invention. It is operation | movement explanatory drawing (the 1) of the disaster countermeasure server at the time of disaster occurrence. It is operation | movement explanatory drawing (the 2) of the disaster countermeasure server at the time of disaster occurrence. It is operation | movement explanatory drawing (the 3) of the disaster countermeasure server at the time of disaster occurrence. It is operation | movement explanatory drawing (the 4) of the disaster countermeasure server at the time of disaster occurrence. It is a management table explanatory drawing at the time of normal. It is a management table explanatory drawing at the time of disaster occurrence. It is operation | movement explanatory drawing of the management server in this invention. It is explanatory drawing of a prior art example.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Primary system 10 Center 12 Management server 13 Hardware pool 14 Control part 15 1st management table 16 2nd management table 17 Network control table 18 Resource allocation control means 19 Network control means 20 Connection circuit network

Claims (2)

In a disaster recovery computer backup system comprising a plurality of primary systems having a storage device and a server, and a center provided with a storage device corresponding to the storage device of the primary system,
In the center,
The same number of backup storage devices as the primary system storage device, which holds the data, OS, patches, and applications held in the primary system storage device;
A disaster recovery server group in which a number of disaster recovery servers smaller than the number of backup storage devices are arranged;
A first management table in which the function of the storage device used in the primary system, the name and function of the server, and the name of the server of the center connected to the storage device of the center used in the event of a disaster;
A second management table in which the name and function of the center server and the function status of the server are entered;
A connection path between the storage device and the backup server when the first management table and the second management table are managed and a backup server used for the backup storage device is selected at the center in the event of a disaster A management server that holds a network control table having network control data indicating
When the secondary center is notified that a disaster has occurred in the primary system, the management server designates a disaster countermeasure server suitable for the backup storage device corresponding to the primary system as the first management table and the second management table. Referring to the disaster countermeasure server group, the disaster countermeasure computer backup system is selected from the disaster countermeasure server group, and connection control of the disaster countermeasure server to the backup storage device is performed based on the network control table. 2. The disaster countermeasure computer backup system according to claim 1, wherein the storage system of the primary system has remote copy means for transferring the written data, OS, patch, and application to the storage apparatus of the center.

Images