CN111382006A - Operating system recovery method, device, device and medium - Google Patents

Abstract

Embodiments of the present invention provide a method, apparatus, device, and medium for recovering an operating system. The method includes: backing up the operating system of the host to be backed up to obtain multiple operating system backups; when the host to be backed up fails, flipping the multiple operating system backups to form multiple emergency systems; mapping the multiple emergency systems to The host to be restored, so that the host to be restored is activated through one of multiple emergency systems when it is activated. Using the above solution of the embodiment of the present invention, by mapping the emergency system to the host to be restored, the host to be restored can be directly started through the emergency system without data transmission and restoration, which greatly saves the time for system restoration.

Description

Operating system recovery method, device, device and medium

technical field

The present invention relates to the field of communication technologies, and in particular, to a method, apparatus, device and medium for restoring an operating system.

Background technique

In the prior art, the backup and recovery of the operating system, including the configuration information in the operating system and the protection of installed program files, are generally divided into two ways:

First, file-based backup and recovery: backup is performed according to the file method, that is, the relative files in the operating system are backed up as a whole according to the directory structure.

When the system is damaged and needs to be recovered, under the condition that the required hardware host is prepared, first reinstall the operating system software that is consistent with the original operating system platform and version on the hardware host, and complete the patch installation and other operations; then deploy the corresponding hardware host. The backup software reads the data to be backed up in the original operating system through the backup software, restores each file in the backed up operating system to the reinstalled operating system through the network link, and finally completes the recovery of the entire system.

Second, backup and recovery based on bare metal: when backing up the operating system, collect operating system-related information, such as disk partition information, network configuration information, etc., and create a configurable network boot image.

When the system is damaged and needs to be recovered, under the condition that the required hardware host is prepared, the boot image will boot the host and configure the network, and then the backup software will write the information related to the backed up operating system: to the new host The disk is partitioned, and all the backed up files are restored at the same time, and the whole process is automatically realized by the backup software.

The shortcomings of the existing two operating system backup protection methods are described below, and the details are as follows:

First, file-based backup and recovery requires multiple restarts (operating system installation, patch installation, parameter modification production, application installation, etc.) The deviation brought to the overall system is relatively large, for example, the version of the system or program, the specific value of parameter settings, etc.

Second, the backup and recovery based on bare metal, compared with the backup and recovery based on files, saves some steps and time, and avoids a large number of deviations caused by human operations, but the recovery based on bare metal requires more backup operation and maintenance. High, usually a boot image needs to be created for each different physical hardware and operating system. During recovery, a targeted boot image needs to be used to complete the recovery, and the boot image needs to be updated continuously, otherwise it may be affected when a fault occurs. The speed of recovery and the state after recovery.

To sum up, under the above two operating system recovery methods, it is still necessary to complete the operating system installation and complete the file recovery in the operating system manually or automatically. It is still necessary to transfer the recovery data and restore the system. The time consuming is more dependent on the link bandwidth for data recovery transmission.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a method, device, device and medium for restoring an operating system. By mapping the emergency system to the host to be restored, the host to be restored can be directly started through the emergency system without data transmission and restoration. It greatly saves the time for system recovery.

In a first aspect, an embodiment of the present invention provides a method for recovering an operating system, including:

Back up the operating system of the host to be backed up to obtain multiple operating system backups;

When the host to be backed up fails, flip the multiple operating system backups to form multiple emergency systems;

The multiple emergency systems are mapped to the host to be restored, so that the host to be restored starts up through one of the multiple emergency systems when starting.

According to the method for restoring an operating system according to the embodiment of the present invention, each of the multiple operating system backups includes at least one of the following items:

Boot information, network configuration, disk partitions, and content files.

According to the operating system recovery method according to the embodiment of the present invention, the flipping of the multiple operating system backups includes:

directly inverting the boot information backed up by the multiple operating systems into the boot information of the multiple emergency systems;

reversing the network configurations backed up by the multiple operating systems to the network configurations of the multiple emergency systems;

Correcting and flipping each disk partition backed up by the multiple operating systems to each disk partition of the multiple emergency systems;

The content files backed up by the plurality of operating systems are directly reversed to the content files of the plurality of emergency systems.

According to the method for restoring an operating system according to the embodiment of the present invention, the modifying and reversing the network configurations backed up by the multiple operating systems to the network configurations of the multiple emergency systems includes:

Based on user requirements, the media access control MAC addresses, IP addresses or gateways of the network configurations backed up by the multiple operating systems are corrected and reversed to the MAC addresses, IP addresses or gateways of the network configurations of the multiple emergency systems.

According to the operating system recovery method according to the embodiment of the present invention, the correction and flipping of each disk partition backed up by the multiple operating systems into the respective disk partitions of the multiple emergency systems includes:

Based on the used space size and the total space size of the respective disk partitions backed up by the multiple operating systems, the respective disk partitions backed up by the multiple operating systems are corrected and flipped to the respective disk partitions of the multiple emergency systems, so that all The space size of each disk partition of the multiple emergency systems is larger than the used space size of each disk partition backed up by the multiple operating systems and smaller than the total space size of each disk partition backed up by the multiple operating systems.

According to the operating system recovery method according to the embodiment of the present invention, the mapping of the multiple emergency systems to the host to be recovered includes:

In a read-only manner, the multiple emergency systems are mapped to the host to be restored through the switching network.

According to the method for recovering an operating system according to the embodiment of the present invention, the booting through one of the multiple emergency systems includes:

When starting through one of the multiple emergency systems, a recovery log is created in the local disk of the host to be recovered, and the recovery log is used to store newly written data.

The operating system recovery method according to the embodiment of the present invention further includes:

Through reverse cloning, one of the multiple emergency systems is solidified into the local disk of the host to be restored.

According to the method for recovering an operating system according to the embodiment of the present invention, solidifying one of the multiple emergency systems into the local disk of the host to be recovered by reverse cloning includes:

directly clone the boot information of one of the multiple emergency systems as the boot information of the local disk of the host to be restored;

Correcting and cloning the network configuration of one of the multiple emergency systems into the network configuration of the local disk of the host to be restored;

Correcting and cloning the disk partition of one of the multiple emergency systems into the disk partition of the local disk of the host to be restored;

The content file of one of the multiple emergency systems is directly cloned into the content file of the local disk of the host to be restored.

The operating system recovery method according to the embodiment of the present invention further includes:

The host to be restored is restarted, the mapping with the emergency system is disconnected, and the local disk of the host to be restored is selected for booting, so as to realize recovery.

In a second aspect, an embodiment of the present invention provides an apparatus for restoring an operating system, and the apparatus includes:

The operating system backup module is used to back up the operating system of the host to be backed up to obtain multiple operating system backups;

an emergency system, used for flipping the multiple operating system backups to form multiple emergency systems when the host to be backed up fails;

A mapping module, configured to map the multiple emergency systems to the host to be restored, so that the host to be restored starts up through one of the multiple emergency systems when it is started.

According to the apparatus for restoring an operating system according to the embodiment of the present invention, each of the multiple operating system backups includes at least one of the following items:

Boot information, network configuration, disk partitions, and content files.

According to the operating system recovery device according to the embodiment of the present invention, the emergency system is specifically used for:

directly inverting the boot information backed up by the multiple operating systems into the boot information of the multiple emergency systems;

reversing the network configurations backed up by the multiple operating systems to the network configurations of the multiple emergency systems;

Correcting and flipping each disk partition backed up by the multiple operating systems to each disk partition of the multiple emergency systems;

The content files backed up by the plurality of operating systems are directly reversed to the content files of the plurality of emergency systems.

According to the operating system recovery device according to the embodiment of the present invention, the emergency system is specifically used for:

Based on user requirements, the media access control MAC addresses, IP addresses or gateways of the network configurations backed up by the multiple operating systems are corrected and reversed to the MAC addresses, IP addresses or gateways of the network configurations of the multiple emergency systems.

According to the operating system recovery device according to the embodiment of the present invention, the emergency system is specifically used for:

Based on the used space size and the total space size of the respective disk partitions backed up by the multiple operating systems, the respective disk partitions backed up by the multiple operating systems are corrected and flipped to the respective disk partitions of the multiple emergency systems, so that all The space size of each disk partition of the multiple emergency systems is larger than the used space size of each disk partition backed up by the multiple operating systems and smaller than the total space size of each disk partition backed up by the multiple operating systems.

According to the operating system recovery device according to the embodiment of the present invention, the mapping module is specifically used for:

In a read-only manner, the multiple emergency systems are mapped to the host to be restored through the switching network.

According to the operating system recovery device according to the embodiment of the present invention, the startup module is specifically used for:

When starting through one of the multiple emergency systems, a recovery log is created in the local disk of the host to be recovered, and the recovery log is used to store newly written data.

The operating system recovery device according to the embodiment of the present invention further includes:

The solidification module is used to solidify one of the multiple emergency systems into the local disk of the host to be restored by reverse cloning.

According to the operating system recovery device according to the embodiment of the present invention, the curing module is specifically used for:

directly clone the boot information of one of the multiple emergency systems as the boot information of the local disk of the host to be restored;

Correcting and cloning the network configuration of one of the multiple emergency systems into the network configuration of the local disk of the host to be restored;

Correcting and cloning the disk partition of one of the multiple emergency systems into the disk partition of the local disk of the host to be restored;

The content file of one of the multiple emergency systems is directly cloned into the content file of the local disk of the host to be restored.

The operating system recovery device according to the embodiment of the present invention further includes:

The booting module is used for restarting the host to be recovered, disconnecting the mapping with the emergency system, and selecting the local disk of the host to be recovered for booting, so as to realize recovery.

An embodiment of the present invention provides an operating system recovery device, including: at least one processor, at least one memory, and computer program instructions stored in the memory. method on the one hand.

In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium on which computer program instructions are stored, and when the computer program instructions are executed by a processor, the method of the first aspect in the foregoing embodiments is implemented.

The operating system recovery method, device, device, and medium provided by the embodiments of the present invention map the emergency system to the host to be recovered, so that the host to be recovered can be directly started through the emergency system without data transmission and recovery, greatly reducing the need for recovery. Save time for system recovery.

Description of drawings

In order to illustrate the technical solutions of the embodiments of the present invention more clearly, the accompanying drawings required in the embodiments of the present invention will be briefly introduced below. For those of ordinary skill in the art, without creative work, the Additional drawings can be obtained from these drawings.

FIG. 1 shows a schematic flowchart of a method for restoring an operating system according to an embodiment of the present invention;

FIG. 2 shows a schematic structural diagram of an apparatus for restoring an operating system according to an embodiment of the present invention;

3 shows a schematic diagram of a method for restoring an operating system according to another embodiment of the present invention;

FIG. 4 shows a schematic diagram of operating system backup rollover according to an embodiment of the present invention;

FIG. 5 shows a schematic diagram of emergency system mapping according to an embodiment of the present invention;

FIG. 6 shows a schematic diagram of starting an emergency system according to an embodiment of the present invention;

FIG. 7 shows a schematic diagram of the reverse clone of the emergency system according to an embodiment of the present invention being solidified to a local disk;

FIG. 8 shows a schematic diagram of a hardware structure of an operating system recovery device according to an embodiment of the present invention.

Detailed ways

The features and exemplary embodiments of various aspects of the present invention will be described in detail below. In order to make the objects, technical solutions and advantages of the present invention more clear, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only configured to explain the present invention, and are not configured to limit the present invention. It will be apparent to those skilled in the art that the present invention may be practiced without some of these specific details. The following description of the embodiments is only intended to provide a better understanding of the present invention by illustrating examples of the invention.

It should be noted that, in this document, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any relationship between these entities or operations. any such actual relationship or sequence exists. Moreover, the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article or device that includes a list of elements includes not only those elements, but also includes not explicitly listed or other elements inherent to such a process, method, article or apparatus. Without further limitation, an element defined by the phrase "comprises" does not preclude the presence of additional identical elements in a process, method, article, or device that includes the element.

Referring to FIG. 1, FIG. 1 shows a schematic flowchart of a method 100 for recovering an operating system according to an embodiment of the present invention. The method includes:

S110, back up the operating system of the host to be backed up to obtain multiple operating system backups;

S120, when the host to be backed up fails, flip multiple operating system backups to form multiple emergency systems;

S130: Map multiple emergency systems to the host to be restored, so that the host to be restored starts up through one of the multiple emergency systems when it is started.

Through the above solution provided by the embodiment of the present invention, by backing up the operating system of the backup host, flipping multiple operating system backups to form multiple emergency systems, and then mapping the emergency system to the host to be restored, so that the host to be restored can Direct startup through the emergency system does not require data transmission and recovery, which greatly saves the time for system recovery.

Referring to FIG. 2, FIG. 2 shows a schematic structural diagram of an operating system recovery apparatus 200 according to an embodiment of the present invention. The apparatus includes:

The operating system backup module 210 is used for backing up the operating system of the host to be backed up to obtain multiple operating system backups;

The emergency system 220 is used for flipping multiple operating system backups to form multiple emergency systems when the host to be backed up fails;

The mapping module 230 is configured to map multiple emergency systems to the host to be restored, so that the host to be restored starts up through one of the multiple emergency systems during startup.

Through the above solution provided by the embodiment of the present invention, by backing up the operating system of the backup host, flipping multiple operating system backups to form multiple emergency systems, and then mapping the emergency system to the host to be restored, so that the host to be restored can Direct startup through the emergency system does not require data transmission and recovery, which greatly saves the time for system recovery.

The rapid recovery method of the operating system proposed by the embodiment of the present invention can, after backing up the operating system to the emergency recovery platform, turn the operating system backup retained in the emergency recovery platform into the emergency system, and directly map the emergency system to the host that needs to be recovered , as the system disk of the recovery host, it supports the direct startup of the recovery host, avoids the data transfer process, completes the system recovery startup with the fastest speed and the most simplified steps, and can use the reverse clone of the disk after the recovery host is started. The emergency system is hardened into the local disk of the recovery host.

In order to implement the method of the embodiment of the present invention, the storage space of the emergency recovery platform will be divided into two parts: the emergency startup area and the recovery reserved area in advance. The emergency startup area and the recovery reserved area will be introduced below, and the details are as follows:

The emergency startup area is used as an emergency system when the operating system fails, and it does not need to perform data recovery and transmission, and directly starts the host to shorten the recovery preparation time;

The recovery reserve area is used for the reservation of historical copies of the operating system, so that in the event of a failure, the required historical version can be selected for emergency startup after rollover.

All operating system backups are written into the recovery reserve area. When historical data needs to be restored, the operating system backup can be flipped from the recovery reserve area to the emergency boot area. After booting, the operating system backup can be restored from the emergency by reverse cloning. The platform is solidified to the local disk of the recovery host, which is convenient for subsequent startup.

The following is a detailed description of an operating system quick recovery scheme according to an embodiment of the present invention with reference to FIG. 3 . FIG. 3 shows a schematic diagram of a method 300 for recovering an operating system according to another embodiment of the present invention, and the details are as follows:

The first step is to perform a full system backup;

When backing up, complete backup of the relevant configuration information of the operating system. The configuration information mainly includes boot information, disk partitions and content files, etc., to form a complete operating system backup. The following describes each component of the configuration information. as follows:

Boot information: It is used to transfer the system control to the specified operating system and registered in the partition table when the operating system hard disk is started (different operating systems have different boot information).

Network configuration: configuration of necessary network ports, including media access control (Media Access Control Address, MAC) address, IP information, etc. In order to facilitate network mapping startup in subsequent recovery, and connection verification after recovery.

Disk partition: The distribution of partitions or file systems on the operating system disk, which is responsible for describing which partitions or file systems exist in the operating system, the size and usage of each partition or file system.

Content files: What content is contained in each partition or file system in the operating system, and back up these content.

The above four parts will form a complete operating system backup, which will be stored in the recovery reserve area of the emergency recovery platform for preservation. Common data deduplication technology can be used during the preservation process.

Referring to Table 1, Table 1 shows a schematic diagram of the various components of the operating system backup:

Table 1

The second step is to select the backup to roll over in case of failure;

Through the full operating system backup in the first step, the operating system such as boot information, network configuration, disk partitions, and content files are recorded.

When a backup host fails, you can specify a historical copy of its operating system backup to turn an operating system backup into an emergency system.

When flipping, the partition size of the emergency system can be specified according to the disk partition size and content size, and its network configuration can be modified during universal recovery.

It should be noted that, in some embodiments, the backup host and the recovery host may be the same machine; in other embodiments, the backup host and the recovery host may be different machines.

As an example, referring to FIG. 4 , FIG. 4 shows a schematic diagram of operating system backup rollover according to an embodiment of the present invention.

When a complete operating system backup has been completed and stored in the recovery reserve area, it is necessary to turn an operating system backup into an emergency system and hand it over to a recovery host. The following describes the components of the operating system backup: How to flip, as follows:

First, the boot information, the original system is the Linux system, and it is directly turned into the boot information of the emergency system;

Secondly, network configuration, the IP address configured by the original system on the network card whose MAC address is 1A:2B:3C:4E is 192.168.0.100, and the gateway is 192.168.0.1; in the embodiment shown in Figure 4, the The flip is a universal recovery, so it is corrected and flipped. The modified MAC address is 4E:3C:2B:1A, the IP address is 192.168.0.101, and the gateway remains unchanged. In other embodiments, the rollover can be co-host recovery.

It should be noted that Figure 4 is just an example. In other embodiments, one or more of the rollover MAC address, IP address, and gateway may be modified.

Third, the disk partition, the original system is divided into 3 partitions: the total space of partition 1 is 10GB, and 5GB has been used; the total space of partition 2 is 20GB, and 10GB has been used; the total space of partition 3 is 30GB, and 15GB has been used.

In order to save the space of the emergency boot area, the disk partition is corrected and flipped, and partition 1 is divided into 8GB [>5GB (greater than used), <10GB (less than the total size)]; partition 2 is divided into 18GB [>10GB (greater than used) used), <20GB (less than total size)]; partition 3 into 28GB [>15GB (more than used), <30GB (less than total size)].

It should be noted that the correction value of the correction rollover can be customized according to the needs. In the above-mentioned embodiment, for consideration of the space utilization rate of the emergency start area, the modification to the partition size cannot be smaller than the used size and cannot be larger than the total size.

Finally, the content file, the content file will be flipped directly and cannot be corrected.

The third step is to start the emergency directly after mapping;

As an example, referring to FIG. 5 , FIG. 5 shows a schematic diagram of emergency system mapping according to an embodiment of the present invention.

The rollover process will be completed quickly in the emergency recovery platform. After the rollover is completed, one or more emergency systems will be formed, which can be mapped to the recovery host for direct use.

The emergency system can be read-only mapped in various ways, including but not limited to FC (fiber link) mapping or PXE boot (network link), so that the emergency system can be mapped to multiple recovery hosts through a switched network for identification boot.

(1) Emergency system mapping

Different emergency systems are backed up by different operating systems, and the emergency system is mapped to the recovery host in a read-only manner through the switching network.

There is no need to transfer recovery data during this process.

In the read-only mapping mode, the same emergency system can be mapped to multiple different recovery hosts and start at the same time.

The same recovery host can also accept the mapping of different emergency systems, and can select one of the mapped emergency systems to start when starting.

(2) Emergency system activation

Referring to FIG. 6 , FIG. 6 shows a schematic diagram of starting an emergency system according to an embodiment of the present invention.

As an example, when the recovery host starts up, it selects an available emergency system that has been mapped (for example, selects one emergency system from multiple emergency systems mapped in different ways), and when the recovery host starts through the emergency system, it will A recovery log is created in the disk space to store the newly written data, and the emergency system remains unchanged as a read-only mode, and the host can be restarted immediately.

The fourth step, the emergency system is reverse cloned and solidified;

After the recovery host completes the emergency startup through the emergency system, the emergency system can be solidified into the local disk of the recovery host through reverse cloning.

As shown in FIG. 7 , FIG. 7 shows a schematic diagram of a reverse clone of an emergency system according to an embodiment of the present invention and hardened to a local disk.

As an example, the following describes how each part of the emergency system is reverse cloned when the emergency system is reverse cloned to the local disk, as follows:

First, the boot information is directly cloned into the boot information of the local disk of the recovery host;

Secondly, the network configuration, since the mapping has been completed, the MAC address of the recovery host will not be modified, but the IP address can be modified again. In the emergency system, it is 192.168.0.101, and the gateway is 192.168.0.1; It is 192.168.0.103, and the gateway remains unchanged.

It should be noted that FIG. 6 is merely exemplary; in other embodiments, one or more of the MAC address, IP address, or gateway may be modified as needed.

Finally, the disk partition is divided into three partitions in the emergency system: partition 1 is 8GB; partition 2 is 18GB; partition 3 is 28GB.

According to the backup information in the recovery reserved area in the second step, with reference to Table 2, Table 2 shows a schematic table of each component of the operating system backup of the recovery reserved area as shown in Figure 4:

When cloning from the emergency system to the local disk, it can be corrected to divide partition 1 into 15GB [>5GB (greater than used), >10GB (greater than total size)]; partition 2 into 20GB [>10GB (greater than the total size) used), = 20GB (equal to total size)]; divide partition 3 into 28GB [>15GB (more than used), <30GB (less than total size)].

Table 2

Therefore, the correction value of the correction clone can be customized according to the needs, and the network configuration and disk partition can be adjusted according to the specific needs to deal with different recovery purposes.

After the reverse cloning is completed and the emergency system is solidified to the local disk, you can restart the recovery host at an appropriate time, disconnect the mapping with the emergency system, select the local disk for booting, and complete the recovery.

In the above solution provided by the embodiment of the present invention, by performing a complete backup of the operating system (for example, including boot information, network configuration, disk partition, content files, etc.) during backup, a complete operating system backup is formed and stored in the emergency recovery platform, When recovery is required, the operating system backup is rolled over to a specific area of the emergency recovery platform (such as the emergency startup area) as required to become a complete emergency system, and then the emergency system is mapped to the host that needs to be restored, so that the The host can be started directly through the emergency system.

The above solution provided by the embodiment of the present invention not only avoids a large number of redeployment steps, time and environment deviation, but also does not need to maintain a large number of boot images, and directly starts the host through the emergency system without data transmission and recovery, which greatly saves time to restore the system to use.

To sum up, when the operating system fails, the operating system backup image of the dedicated emergency recovery platform is turned over to become the emergency system in the emergency boot area, and the emergency system is directly mapped to the recovery host without transferring recovery data. The boot area starts directly.

In addition, flip from the recovery reserved area to the emergency boot area, start in the emergency boot area, and reverse clone the emergency boot area to the local disk of the recovery host.

It can be seen that the above solution provided by the present invention can not only retain the historical data copies of multiple operating systems to a great extent by means of backup and recovery methods, but also use general backup technologies such as deduplication; , and reverse cloning to solidify, to achieve rapid recovery of the operating system; and in the process of flipping and cloning, to meet different recovery needs and environments while ensuring that the operating system is not biased, it is a timeliness, performance, and functions. Very balanced means of operating system protection.

The above-mentioned scheme provided by the present invention can achieve the following technical effects:

First of all, there is no need for the traditional recovery data transmission process. The operating system backup is quickly flipped and mapped in the emergency recovery platform, which supports the direct startup of the recovery host, with high timeliness.

Secondly, in the recovery reserve area, the general backup technology can be used to retain the historical copies of multiple time nodes to effectively repair logical errors at each time point.

Thirdly, the emergency start area supports a variety of mapping links and mapping methods, and correction parameters can be set during the flipping and cloning process, which can effectively correspond to different environments and meet the needs of rapid recovery in large quantities.

In addition, the method for recovering the operating system according to the embodiment of the present invention described in conjunction with FIG. 1 may be implemented by a device for recovering the operating system. FIG. 8 shows a schematic diagram of a hardware structure of an operating system recovery device provided by an embodiment of the present invention.

The recovery device for the operating system may include a processor 1003 and a memory 1004 storing computer program instructions.

8 is a structural diagram illustrating an exemplary hardware architecture of a computing device capable of implementing a communication method and a network server according to an embodiment of the present invention. As shown in FIG. 8 , computing device 1000 includes input device 1001 , input interface 1002 , processor 1003 , memory 1004 , output interface 1005 , and output device 1006 .

The input interface 1002, the processor 1003, the memory 1004, and the output interface 1005 are connected to each other through the bus 1010, and the input device 1001 and the output device 1006 are respectively connected to the bus 1010 through the input interface 1002 and the output interface 1005, and then to the computing device 1000. other components are connected.

Specifically, the input device 1001 receives input information from the outside, and transmits the input information to the processor 1003 through the input interface 1002; the processor 1003 processes the input information based on the computer-executable instructions stored in the memory 1004 to generate output information, The output information is temporarily or permanently stored in the memory 1004, and then transmitted to the output device 1006 through the output interface 1005; the output device 1006 outputs the output information to the outside of the computing device 1000 for the user to use.

The computing device 1000 can execute the steps in the communication method described above in this application.

The processor 1003 may be one or more central processing units (English: Central Processing Unit, CPU). In the case where the processor 1003 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

The memory 1004 may be, but is not limited to, one of random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM), compact disk read only memory (CD-ROM), hard disk, etc. or variety. Memory 1004 is used to store program codes.

It can be understood that, in this embodiment of the present application, the functions of any or all modules from the operating system backup module provided in FIG. 2 to the startup module may be implemented by the central processing unit 1003 shown in FIG. 8 .

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in whole or in part in the form of a computer program product, the computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.)). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that includes an integration of one or more available media. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), among others.

Each part of this specification is described in a progressive manner, and the same and similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the points that are different from other embodiments. In particular, as for the apparatus and system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and for related parts, please refer to the descriptions in the method embodiments.

Claims (13)

1. A recovery method for an operating system, comprising: Back up the operating system of the host to be backed up to obtain multiple operating system backups; When the host to be backed up fails, flip the multiple operating system backups to form multiple emergency systems; The multiple emergency systems are mapped to the host to be restored, so that the host to be restored starts up through one of the multiple emergency systems when starting. 2. The method of claim 1, wherein each of the plurality of operating system backups comprises at least one of the following: Boot information, network configuration, disk partitions, and content files. 3. The method according to claim 2, wherein the rolling over the plurality of operating system backups comprises: directly inverting the boot information backed up by the multiple operating systems into the boot information of the multiple emergency systems; reversing the network configurations backed up by the multiple operating systems to the network configurations of the multiple emergency systems; Correcting and flipping each disk partition backed up by the multiple operating systems to each disk partition of the multiple emergency systems; The content files backed up by the plurality of operating systems are directly reversed to the content files of the plurality of emergency systems. 4 . The method according to claim 3 , wherein the modifying and reversing the network configurations backed up by the multiple operating systems to the network configurations of the multiple emergency systems comprises: 4 . Based on user requirements, the media access control MAC addresses, IP addresses or gateways of the network configurations backed up by the multiple operating systems are corrected and reversed to the MAC addresses, IP addresses or gateways of the network configurations of the multiple emergency systems. 5 . The method according to claim 3 , wherein the modifying and flipping the respective disk partitions backed up by the multiple operating systems to the respective disk partitions of the multiple emergency systems comprises: 5 . Based on the used space size and the total space size of the respective disk partitions backed up by the multiple operating systems, the respective disk partitions backed up by the multiple operating systems are corrected and flipped to the respective disk partitions of the multiple emergency systems, so that all The space size of each disk partition of the multiple emergency systems is larger than the used space size of each disk partition backed up by the multiple operating systems and smaller than the total space size of each disk partition backed up by the multiple operating systems. 6. The method according to claim 1, wherein the mapping of the plurality of emergency systems to the host to be restored comprises: In a read-only manner, the multiple emergency systems are mapped to the host to be restored through the switching network. 7. The method of claim 1, wherein the activating by one of the plurality of emergency systems comprises: When starting through one of the multiple emergency systems, a recovery log is created in the local disk of the host to be recovered, and the recovery log is used to store newly written data. 8. The method of claim 1, wherein the method further comprises: Through reverse cloning, one of the multiple emergency systems is solidified into the local disk of the host to be restored. 9 . The method according to claim 8 , wherein, solidifying one of the multiple emergency systems into the local disk of the host to be restored by reverse cloning, comprising: 10 . directly clone the boot information of one of the multiple emergency systems as the boot information of the local disk of the host to be restored; Correcting and cloning the network configuration of one of the multiple emergency systems into the network configuration of the local disk of the host to be restored; Correcting and cloning the disk partition of one of the multiple emergency systems into the disk partition of the local disk of the host to be restored; The content file of one of the multiple emergency systems is directly cloned into the content file of the local disk of the host to be restored. 10. The method according to claim 9, wherein the method further comprises: The host to be restored is restarted, the mapping with the emergency system is disconnected, and the local disk of the host to be restored is selected for booting, so as to realize recovery. 11. An operating system recovery device, comprising: The operating system backup module is used to back up the operating system of the host to be backed up to obtain multiple operating system backups; an emergency system, used for flipping the multiple operating system backups to form multiple emergency systems when the host to be backed up fails; A mapping module, configured to map the multiple emergency systems to the host to be restored, so that the host to be restored starts up through one of the multiple emergency systems when it is started. 12. An operating system recovery device, comprising: at least one processor, at least one memory, and computer program instructions stored in the memory, which are implemented when the computer program instructions are executed by the processor The method of any of claims 1-10. 13. A computer-readable storage medium having computer program instructions stored thereon, wherein the computer program instructions, when executed by a processor, implement the method of any one of claims 1-10.

Images