KR102415027B1 - Backup recovery method for large scale cloud data center autonomous operation - Google Patents

Abstract

The present invention relates to a backup recovery method structure and method for autonomous operation of a large-scale cloud data center,
This includes a node registration step of recognizing each of a plurality of nodes constituting a large-scale cloud data center, and collecting and storing hardware and software information of each of the nodes; an event monitoring step of collecting and analyzing hardware event logs and operating system event logs of each node in real time, and determining whether to proceed with backup or recovery of each of the nodes, a target, and a method; a recovery step of backing up a backup target of the node requiring backup to a permanent memory and then performing a secondary backup to a backup medium when a node requiring a backup is detected; and a recovery step of recovering the node requiring recovery based on the permanent memory when the node requiring recovery is detected, and further recovering the node based on the backup media if the permanent memory is in an unusable state.

Description

Backup recovery method for large scale cloud data center autonomous operation

The present invention relates to a backup recovery method for autonomous operation of a large-scale cloud data center that provides an autonomous backup recovery environment based on an integrated event (hardware, operating system, application) by connecting a plurality of computing devices constituting the cloud through a network. .

The most difficult task in Linux service is the task of system recovery. Because system recovery requires restoring a system created by someone rather than creating a new system, not only system analysis, but also the know-how and errors of ex-engineers hidden therein. It takes twice as much effort to catch it.

Existing companies have given sufficient consideration to data backup, and many solutions offer good solutions for this. The reality is that there is no adequate solution for system backup.

In the case of a Linux system, from installation to application installation, it takes about 3 to 4 hours to install.

The difficulty increases during reinstallation due to the complexity of the cloud data center (operating system, cloud middleware, applications).

In particular, as the demand for high availability in Equation 1 increases, reducing the recovery time is a technique for increasing availability.

[Equation 1]

In this case, A represents availability (%), MTBF means Mean Time Between Failures, and MTTR means Mean Time To Recover (time taken to recover). In practice, the more MTTR is minimized, the closer to 100% availability.

When defining downtime, many variables exist, and it is normal to see that Planned Downtime occupies a large proportion. The reason that software-caused downtime accounts for a large percentage is that bugs in server software (including operating systems), client software, and network software are the most uncontrollable areas for system stability.

As hardware becomes more stable, the proportion of downtime caused by software will increase, and as software becomes more complex, more failures due to software problems will occur. For this reason, recovery technology for software is required.

Domestic Patent Publication No. 10-2019-0106488 (published date: 2019.09.18)

Accordingly, in order to solve the above problems, the present invention provides a backup recovery method structure and method for autonomous operation of a large-scale cloud data center that enables to autonomously perform backup and recovery of a large-scale cloud data center more quickly, accurately, and safely would like to provide

The object of the present invention is not limited to the object mentioned above, and other objects not mentioned will be clearly understood by those of ordinary skill in the art from the description below.

As a means for solving the above problem, according to an embodiment of the present invention, a node registration step of recognizing each of a plurality of nodes constituting a large-scale cloud data center, and collecting and storing hardware and software information of each of the nodes; an event monitoring step of collecting and analyzing hardware event logs and operating system event logs of each node in real time, and determining whether to proceed with backup or recovery of each of the nodes, a target, and a method; a recovery step of backing up the backup target of the node needing backup to a permanent memory and then performing a secondary backup to a backup medium when a node requiring a backup is detected; and a recovery step of recovering the node requiring recovery based on the permanent memory when a node requiring recovery is detected, but additionally recovering the node based on the backup media if the permanent memory is unavailable It provides a backup recovery method for autonomous operation.

The event monitoring step checks whether HW failure occurs by selecting and using only temperature, fan, power, and hardware error related logs from the hardware event log, and selecting and using the operating system failure log and the number of failures from the OS operating system log. It checks whether an OS failure has occurred, and it is characterized by automatically determining whether to proceed with backup or recovery, the target, and the method according to the type, number, or degree of failure.

The event monitoring step is characterized in that the target of backup or recovery is divided into system and data, and the method of backup or recovery is divided into full backup and snapshot backup.

The node registration step includes CPU configuration, user configuration options, boot mode, boot device, RAID (Redundant Array of Independent Disks), iSCSI (Internet Small Computer System Interface) and PXE (Pre-boot eXecution Environment), PXE (Pre-boot). eXecution Environment) is acquired and stored as hardware information, and at least one of an OS type, boot manager, partition, and file system is acquired and provided as software information.

The method considers at least one of the boot mode of the hardware information and the boot manager of the software information to build a live media-based backup and recovery environment, or a network-based backup and recovery environment construction step of establishing a backup and recovery environment. It is characterized in that it further comprises.

The present invention can be applied to a large-scale cloud data center, and enables a system structure to be built with a low system construction cost (comprehensive cost including equipment cost and labor cost) compared to the same performance.

1 is a view for explaining a backup recovery method for autonomous operation of a large-scale cloud data center according to an embodiment of the present invention.
2 to 4 are diagrams for explaining in more detail a node registration step according to an embodiment of the present invention.
5 to 7 are diagrams for explaining in more detail an event collection step according to an embodiment of the present invention.
8 and 9 are diagrams for explaining in more detail a backup step according to an embodiment of the present invention.
10 to 12 are diagrams for explaining in more detail a recovery step according to an embodiment of the present invention.

The following is merely illustrative of the principles of the invention. Therefore, those skilled in the art will be able to devise various devices that, although not explicitly described or shown herein, embody the principles of the present invention and are included within the spirit and scope of the present invention. Further, it is to be understood that all conditional terms and examples listed herein are, in principle, expressly intended solely for the purpose of enabling the concept of the present invention to be understood, and not limited to the specifically enumerated embodiments and states as such. should be

Moreover, it is to be understood that all detailed description reciting the principles, aspects, and embodiments of the invention, as well as specific embodiments, are intended to cover structural and functional equivalents of such matters. It should also be understood that such equivalents include not only currently known equivalents, but also equivalents developed in the future, i.e., all devices invented to perform the same function, regardless of structure.

Thus, for example, the block diagrams herein are to be understood as representing conceptual views of illustrative circuitry embodying the principles of the present invention. Similarly, all flowcharts, state transition diagrams, pseudo code, etc. may be tangibly embodied on computer-readable media and be understood to represent various processes performed by a computer or processor, whether or not a computer or processor is explicitly shown. should be

The functions of the various elements shown in the drawings including a processor or functional blocks represented by similar concepts may be provided by the use of dedicated hardware as well as hardware having the ability to execute software in association with appropriate software. When provided by a processor, the functionality may be provided by a single dedicated processor, a single shared processor, or a plurality of separate processors, some of which may be shared.

In addition, the clear use of terms presented as processor, control, or similar concepts should not be construed as exclusively referring to hardware having the ability to execute software, and without limitation, digital signal processor (DSP) hardware, ROM for storing software. It should be understood to implicitly include (ROM), RAM (RAM) and non-volatile memory. Other common hardware may also be included.

In the claims of the present specification, a component expressed as a means for performing the function described in the detailed description includes, for example, a combination of circuit elements that perform the function or software in any form including firmware/microcode, etc. It is intended to include all methods of performing the functions of the device, coupled with suitable circuitry for executing the software to perform the functions. Since the present invention defined by these claims is combined with the functions provided by the various enumerated means and in a manner required by the claims, any means capable of providing the functions are equivalent to those contemplated from the present specification. should be understood as

The above objects, features and advantages will become more apparent through the following detailed description in relation to the accompanying drawings, and accordingly, those of ordinary skill in the art to which the present invention pertains can easily implement the technical idea of the present invention. There will be. In addition, in the description of the present invention, if it is determined that a detailed description of a known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted.

1 is a view for explaining a backup recovery method for autonomous operation of a large-scale cloud data center according to an embodiment of the present invention.

Referring to FIG. 1, the method of the present invention recognizes each of a plurality of nodes constituting a large-scale cloud data center, and collects and stores hardware and software information of each node (S1), a node registration step (S1) of each of the nodes Event monitoring step (S2) of collecting and analyzing hardware event logs and operating system event logs in real time to determine whether to proceed, target, and method for each of the nodes to be backed up or restored. When a node requiring backup is detected, the node requiring backup A recovery step (S3) of backing up the primary backup target of the backup target to permanent memory and then secondary backing up to the backup media, and when a recovery node is detected, the recovery node is restored based on the permanent memory, but the permanent memory If is unavailable, a recovery step (S4) of additionally recovering the node based on the backup media may be included.

The present invention automatically tracks and recognizes node-level failures and new node additions, and provides an administrator for backup and recovery.

In addition, by having a heterogeneous node event collection and integrated manager, when configuring a large-scale cloud, it is possible to manage the integrated event with different devices for each vendor, and to manage the heterogeneous nodes as well.

And it automatically generates events through real-time system event log and OS log collection and analysis for node unit failure analysis.

By creating and using backup and recovery schedules and procedures based on the collected events, backup and recovery operations can be performed more efficiently and consistently.

In addition, it establishes a backup/restore environment using the live media/network boot function. That is, the present invention provides live booting through network booting (PXE booting) unlike the conventional method, supports backup and recovery by the user's selection, and automatic recovery according to a set rule. It also allows the work to proceed.

2 to 4 are diagrams for explaining in more detail a node registration step according to an embodiment of the present invention.

As shown in Fig. 2, the node registration step (S1) of the present invention may include a node recognition step (S11), a node hardware information registration step (S12), and a node software information registration step (S13). can

In the node recognition step S11, the backup manager configures the cloud data center or automatically recognizes each node newly added to the cloud data center.

In the node hardware information registration step (S12), the backup manager requests to provide hardware information to each node through IPMI (Intelligent Platform Management Interface), which is a standardized message-based hardware management interface as shown in FIG. It collects and provides its own hardware information by using the Base Mother Controller (BMC), an interface that monitors the hardware performance status. Then, the backup manager stores the hardware information collected and provided by each node into a database as basic data to be backed up.

At this time, hardware information includes CPU configuration, user configuration options, boot mode, boot device, RAID (Redundant Array of Independent Disks), iSCSI (Internet Small Computer System Interface) and PXE (Pre-boot eXecution Environment), PXE (Pre-boot). eXecution Environment) and the like.

In the node software information registration step (S13), the backup manager additionally acquires software information of each node using IPMI and BMC as shown in FIG. 4, and further stores it as a database as a backup target basic data.

In this case, the software information may be information about an OS type, a boot manager, a partition, a file system, and the like.

5 to 7 are diagrams for explaining in more detail an event collection step according to an embodiment of the present invention.

5, the event monitoring step (S2) of the present invention may be configured to include an event log collection step (S21) of each node, an event log analysis step (S22), and the like.

In the event log collection step (S21), the BMC of each node collects and provides a plurality of event logs in real time by monitoring the current state of the node using various hardware sensors and OS operating systems installed in the node as shown in FIG. 6 .

The backup manager receives them through IPMI, converts them into standard data format, and stores them in a database. In particular, in the present invention, the event log transmitted by each node is converted into a standard data format and stored. Considering that at least one or more of a plurality of nodes can be implemented as heterogeneous equipment, even heterogeneous node events are integrated and to be able to analyze it.

At this time, the event log is divided into a hardware event log and an OS operating system log. The hardware event log may be a temperature, fan, power, hardware error event log, user-defined event log, etc., and the OS operating system log is an operating system failure log, failure The number of occurrences may be the same.

In the event log analysis step (S22), the backup manager selects and analyzes the event logs of each node according to a preset event analysis criterion as shown in FIG. , the method is automatically determined.

For example, select and use only temperature, fan, power, and hardware error related logs among multiple hardware event logs to check whether HW failure occurs, and select and use the operating system error log and number of failures among OS operating system logs. You can check whether an OS failure has occurred.

And based on the type and number of failures, decide whether to perform a system backup or a node that needs data backup (i.e., the destination for backup or recovery), or alternatively whether to perform a Full Backup or a Snapshot backup Allows you to decide whether to proceed (ie how to backup or restore).

In addition, by directly determining whether to proceed with backup or recovery at the request of the user, the target, and the method, various user requirements can be handled more flexibly.

8 and 9 are diagrams for explaining in more detail a backup step according to an embodiment of the present invention.

As shown in FIG. 8, in the present invention, a backup scheduler is created based on the event log analysis result, and through this, which target of the system and data is backed up, and full backup and snapshot backup You can choose which method to use, the type of backup environment, etc.

In addition, the present invention additionally includes a permanent memory for high-performance backup in addition to the backup media (SSD, Disk) and the existing storage media, and then backs up node information to the permanent memory first, and then backs up the node information to the second backup media (SSD, Disk). ), it is possible to build and provide a real-time backup environment.

10 to 12 are diagrams for explaining in more detail a recovery step according to an embodiment of the present invention.

As shown in Figure 10, in the present invention, the recovery manager is configured according to the event log analysis result, and the recovery manager uses the same method as the backup scheduler to restore the system and data, and also selects which method between full restore and snapshot restore. It allows you to choose whether to use it or the type of restoration environment in a variety of ways.

In order to ensure fast recovery, the recovery manager first restores the node system based on the permanent memory, but if the permanent memory is unavailable, additionally recovers the node system based on the backup media.

In addition, the present invention establishes a backup/restore environment using live media and network boot functions, so that a backup or recovery procedure can be automatically performed through network booting without the need to use separate software as in the prior art. make it possible

In this case, the live media backup/restore environment and the network boot backup/restore environment may be determined in consideration of at least one of a boot mode of hardware information and a boot manager of the software information, but is not limited thereto.

In addition, live media is a model equipped with a standard hardware detector, network driver, and X-windows, and a self-developed backup recovery application or webpage supports backup/repair without a separate operating system and backup application. Allows you to build a recovery environment.

Network boot is an environment that allows you to boot a computer through a network interface, and it also allows you to build a backup/restore environment without a separate operating system and backup application.

13 is a diagram illustrating an example computing environment in which one or more embodiments disclosed herein may be implemented, and is an illustration of a system 1000 including a computing device 1100 configured to implement one or more embodiments described above. shows For example, computing device 1100 may be a personal computer, server computer, handheld or laptop device, mobile device (mobile phone, PDA, media player, etc.), multiprocessor system, consumer electronics, minicomputer, mainframe computer, distributed computing environments including any of the aforementioned systems or devices, and the like.

The computing device 1100 may include at least one processing unit 1110 and a memory 1120 . Here, the processing unit 1110 may include, for example, a central processing unit (CPU), a graphic processing unit (GPU), a microprocessor, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Arrays (FPGA), etc. and may have a plurality of cores. The memory 1120 may be a volatile memory (eg, RAM, etc.), a non-volatile memory (eg, ROM, flash memory, etc.), or a combination thereof.

Additionally, computing device 1100 may include additional storage 1130 . Storage 1130 includes, but is not limited to, magnetic storage, optical storage, and the like. The storage 1130 may store computer readable instructions for implementing one or more embodiments disclosed herein, and other computer readable instructions for implementing an operating system, an application program, and the like. Computer readable instructions stored in storage 1130 may be loaded into memory 1120 for execution by processing unit 1110 .

Computing device 1100 may also include input device(s) 1140 and output device(s) 1150 . Here, the input device(s) 1140 may include, for example, a keyboard, mouse, pen, voice input device, touch input device, infrared camera, video input device, or any other input device, or the like. Further, the output device(s) 1150 may include, for example, one or more displays, speakers, printers, or any other output device, or the like. Also, the computing device 1100 may use an input device or an output device included in another computing device as the input device(s) 1140 or the output device(s) 1150 .

Computing device 1100 may also include communication connection(s) 1160 that enable computing device 1100 to communicate with another device (eg, computing device 1300 ). Here, communication connection(s) 1160 may be a modem, network interface card (NIC), integrated network interface, radio frequency transmitter/receiver, infrared port, USB connection, or other for connecting computing device 1100 to another computing device. It may include interfaces. Also, the communication connection(s) 1160 may include a wired connection or a wireless connection.

Each component of the above-described computing device 1100 may be connected by various interconnections such as a bus (eg, peripheral component interconnection (PCI), USB, firmware (IEEE 1394), optical bus structure, etc.) and may be interconnected by a network 1200 .

As used herein, terms such as "component," "module," "system," "interface," and the like, generally refer to a computer-related entity that is hardware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. For example, both an application running on a controller and a controller may be a component. One or more components may reside within a process and/or thread of execution, and a component may be localized on one computer or distributed between two or more computers.

In the above, preferred embodiments of the present invention have been illustrated and described, but the present invention is not limited to the specific embodiments described above, and it is common in the technical field to which the present invention pertains without departing from the gist of the present invention as claimed in the claims. Various modifications may be made by those having the knowledge of, of course, and these modifications should not be individually understood from the technical spirit or perspective of the present invention.

Claims (5)

A node registration step of recognizing each of a plurality of nodes constituting a large-scale cloud data center, and collecting and storing hardware and software information of each of the nodes;
an event monitoring step of collecting and analyzing hardware event logs and operating system event logs of each node in real time, and determining whether to proceed with backup or recovery of each of the nodes, a target, and a method;
A backup step of performing a secondary backup to a backup medium after the primary backup target of the backup node is detected in a backup node in a permanent memory; and
a recovery step of recovering the node requiring recovery based on the permanent memory when a node requiring recovery is detected, and further recovering the node based on the backup media if the permanent memory is unavailable;
The event monitoring step is
Each of the nodes collects and provides hardware event logs and operating system event logs in real time through BMC (Base Mother Controller), and the backup manager receives the event logs and operating system event logs through IPMI (Intelligent Platform Management Interface). A backup recovery method for autonomous operation of large-scale cloud data centers that enables integrated collection and analysis of heterogeneous node events by converting them into standard data format and storing them. According to claim 1, wherein the event monitoring step
Check whether HW failure occurs by selecting and using only temperature, fan, power, and hardware error related logs among the hardware event logs, and check whether an OS failure occurs by selecting and using the operating system failure log and number of failures from the OS operating system log. A backup recovery method for autonomous operation of a large-scale cloud data center, characterized in that it automatically determines whether to proceed with backup or recovery, the target, and the method according to the type, number, or degree of failure. The method of claim 2, wherein the event monitoring step
A backup recovery method for autonomous operation of a large-scale cloud data center, characterized in that the target of backup or recovery is divided into system and data, and the method of backup or recovery is divided into full backup and snapshot backup. The method of claim 1, wherein the node registration step
At least one of CPU configuration, user configuration options, boot mode, boot device, Redundant Array of Independent Disks (RAID), Internet Small Computer System Interface (iSCSI) and Pre-boot eXecution Environment (PXE), Pre-boot eXecution Environment (PXE) A backup recovery method for autonomous operation of a large-scale cloud data center, characterized in that one is acquired and stored as hardware information, and at least one of an OS type, boot manager, partition, and file system is acquired and provided as software information. 5. The method of claim 4,
In consideration of at least one of the boot mode of the hardware information and the boot manager of the software information, the step of constructing a live media-based backup and recovery environment or a network-based backup and recovery environment further comprising a backup and recovery environment construction step Backup recovery method for large-scale cloud data center autonomous operation, characterized in that.

Images