CN111382006A - Recovery method, device, equipment and medium of operating system - Google Patents
Recovery method, device, equipment and medium of operating system Download PDFInfo
- Publication number
- CN111382006A CN111382006A CN201811615966.0A CN201811615966A CN111382006A CN 111382006 A CN111382006 A CN 111382006A CN 201811615966 A CN201811615966 A CN 201811615966A CN 111382006 A CN111382006 A CN 111382006A
- Authority
- CN
- China
- Prior art keywords
- host
- operating system
- emergency
- recovered
- systems
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1479—Generic software techniques for error detection or fault masking
- G06F11/1482—Generic software techniques for error detection or fault masking by means of middleware or OS functionality
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Hardware Redundancy (AREA)
Abstract
The embodiment of the invention provides a method, a device, equipment and a medium for recovering an operating system. The method comprises the following steps: backing up an operating system of a host to be backed up to obtain a plurality of operating system backups; when the host to be backed up fails, the multiple operating system backups are turned over to form multiple emergency systems; and mapping the plurality of emergency systems to the host to be recovered, so that the host to be recovered is started through one of the plurality of emergency systems when being started. By utilizing the scheme of the embodiment of the invention, the emergency system is mapped to the host to be recovered, so that the host to be recovered can be directly started through the emergency system without data transmission recovery, and the time for recovering the system is greatly saved.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a medium for recovering an operating system.
Background
In the prior art, backup and recovery of an operating system, including protection of configuration information and installed program files in the operating system, are generally divided into two ways:
first, file-based backup restore: and backing up the files, namely backing up the phase files in the operating system integrally according to a directory structure.
When the system is damaged due to failure and needs to be recovered, firstly, reinstalling operating system software which is consistent with the original operating system platform and version on the hardware host under the condition of preparing the required hardware host, and completing operations such as patch installation; and then deploying corresponding backup software, reading data to be backed up of the original operating system through the backup software, restoring each file in the backed up operating system to the reinstalled operating system through a network link, and finally completing the restoration of the whole system.
Secondly, back-up based on bare metal is recovered: when backing up the operating system, collecting the information related to the operating system, such as partition information of a disk, configuration information of a network and the like, and establishing a boot image of a configurable network.
When the system fault damage needs to be recovered, under the condition of preparing the required hardware host, the host is booted and configured with a network by the boot mirror image, and then the backup software writes the information related to the backed up operating system: and partitioning the magnetic disk of the new host, simultaneously recovering all backed-up files, and automatically realizing the whole process by backup software.
The following describes the disadvantages of the two existing backup protection methods for operating systems, specifically as follows:
first, file-based backup recovery requires multiple reboots (operating system installation, patch installation, parameter modification production, application installation, etc.) during recovery, requires cooperation of multiple persons and field attendance, has a complex operating process, and causes a large deviation to the overall system, such as the version of the system or program, and the specific value of parameter settings, etc.
Secondly, based on bare metal's backup recovery, for based on file's backup recovery, saved some steps and time, avoided the deviation that a large amount of manual operations brought, but the recovery based on bare metal is higher to backup operation maintenance requirement, generally need establish a guide mirror image to every different physical hardware and operating system, need utilize the guide mirror image of pertinence to accomplish the recovery when recovering, and the guide mirror image needs constantly to be updated moreover, otherwise can influence the speed of recovery and the state after recovering when the trouble appears.
In summary, in the two os recovery modes, it is still necessary to complete the os installation and complete the file recovery in the os in a manual or automatic mode, and it is still necessary to transmit recovery data, and the recovery time of the system is more time-consuming and depends on the link bandwidth of the data recovery transmission.
Disclosure of Invention
The embodiment of the invention provides a recovery method, a recovery device, equipment and a medium of an operating system.
In a first aspect, an embodiment of the present invention provides a method for recovering an operating system, where the method includes:
backing up an operating system of a host to be backed up to obtain a plurality of operating system backups;
when the host to be backed up fails, the plurality of operating system backups are turned over to form a plurality of emergency systems;
mapping the plurality of emergency systems to a host to be recovered, so that the host to be recovered is started through one of the plurality of emergency systems when being started.
According to the operating system recovery method of the embodiment of the present invention, each of the plurality of operating system backups includes at least one of:
boot information, network configuration, disk partitions, and content files.
According to the method for restoring the operating system, the step of turning over the operating system backups comprises the following steps:
directly converting the boot information backed up by the operating systems into the boot information of the emergency systems;
transferring the network configuration revision backed up by the plurality of operating systems to the network configuration of the plurality of emergency systems;
modifying and overturning each disk partition backed up by the operating systems into each disk partition of the emergency systems;
and directly turning the content files backed up by the operating systems into the content files of the emergency systems.
According to the method for restoring an operating system in an embodiment of the present invention, the step of transferring the network configuration revision backed up by the plurality of operating systems to the network configuration of the plurality of emergency systems includes:
and based on user requirements, the MAC addresses, the IP addresses or the gateway corrections of the network configuration backed up by the operating systems are turned into the MAC addresses, the IP addresses or the gateways of the network configuration of the emergency systems.
According to the method for restoring an operating system in an embodiment of the present invention, the modifying and flipping each disk partition backed up by the multiple operating systems to each disk partition of the multiple emergency systems includes:
and based on the used space size and the total space size of each disk partition of the multiple operating system backups, modifying and overturning each disk partition of the multiple operating system backups into each disk partition of the multiple emergency systems, so that the space size of each disk partition of the multiple emergency systems is larger than the used space size of each disk partition of the multiple operating system backups and smaller than the total space size of each disk partition of the multiple operating system backups.
According to the method for restoring an operating system in an embodiment of the present invention, mapping the plurality of emergency systems to a host to be restored includes:
and mapping the plurality of emergency systems to the host to be recovered through a switching network based on a read-only mode.
According to the method for recovering an operating system in an embodiment of the present invention, the starting by one of the plurality of emergency systems includes:
and when one of the emergency systems is started, creating a recovery log in a local disk of the host to be recovered, wherein the recovery log is used for storing newly written data.
The method for recovering the operating system according to the embodiment of the invention further comprises the following steps:
and solidifying one of the plurality of emergency systems into a local disk of the host to be recovered through reverse cloning.
According to the method for recovering an operating system in an embodiment of the present invention, the solidifying one of the plurality of emergency systems to the local disk of the host to be recovered by reverse cloning includes:
directly cloning the boot information of one of the plurality of emergency systems into the boot information of the local disk of the host to be recovered;
the network configuration of one of the emergency systems is revised and cloned into the network configuration of the local disk of the host to be recovered;
modifying and cloning the disk partition of one of the emergency systems into the disk partition of the local disk of the host to be recovered;
and directly cloning the content file of one of the emergency systems into the content file of the local disk of the host to be recovered.
The method for recovering the operating system according to the embodiment of the invention further comprises the following steps:
restarting the host to be recovered, disconnecting the mapping between the host to be recovered and the emergency system, and selecting the local disk of the host to be recovered for guiding so as to realize recovery.
In a second aspect, an embodiment of the present invention provides an apparatus for recovering an operating system, where the apparatus includes:
the operating system backup module is used for backing up the operating system of the host computer to be backed up to obtain a plurality of operating system backups;
the emergency system is used for turning over the operating system backups to form a plurality of emergency systems when the host to be backed up fails;
the mapping module is used for mapping the plurality of emergency systems to the host to be recovered, so that the host to be recovered is started through one of the plurality of emergency systems when being started.
According to the os recovery apparatus of the embodiment of the present invention, each of the plurality of os backups includes at least one of:
boot information, network configuration, disk partitions, and content files.
According to the recovery device of the operating system, the emergency system is specifically used for:
directly converting the boot information backed up by the operating systems into the boot information of the emergency systems;
transferring the network configuration revision backed up by the plurality of operating systems to the network configuration of the plurality of emergency systems;
modifying and overturning each disk partition backed up by the operating systems into each disk partition of the emergency systems;
and directly turning the content files backed up by the operating systems into the content files of the emergency systems.
According to the recovery device of the operating system, the emergency system is specifically used for:
and based on user requirements, the MAC addresses, the IP addresses or the gateway corrections of the network configuration backed up by the operating systems are turned into the MAC addresses, the IP addresses or the gateways of the network configuration of the emergency systems.
According to the recovery device of the operating system, the emergency system is specifically used for:
and based on the used space size and the total space size of each disk partition of the multiple operating system backups, modifying and overturning each disk partition of the multiple operating system backups into each disk partition of the multiple emergency systems, so that the space size of each disk partition of the multiple emergency systems is larger than the used space size of each disk partition of the multiple operating system backups and smaller than the total space size of each disk partition of the multiple operating system backups.
According to the recovery apparatus of the operating system in the embodiment of the present invention, the mapping module is specifically configured to:
and mapping the plurality of emergency systems to the host to be recovered through a switching network based on a read-only mode.
According to the recovery apparatus of the operating system in the embodiment of the present invention, the start module is specifically configured to:
and when one of the emergency systems is started, creating a recovery log in a local disk of the host to be recovered, wherein the recovery log is used for storing newly written data.
The recovery device of the operating system according to the embodiment of the present invention further includes:
and the curing module is used for curing one of the emergency systems to the local disk of the host to be recovered through reverse cloning.
According to the recovery device of the operating system in the embodiment of the present invention, the curing module is specifically configured to:
directly cloning the boot information of one of the plurality of emergency systems into the boot information of the local disk of the host to be recovered;
the network configuration of one of the emergency systems is revised and cloned into the network configuration of the local disk of the host to be recovered;
modifying and cloning the disk partition of one of the emergency systems into the disk partition of the local disk of the host to be recovered;
and directly cloning the content file of one of the emergency systems into the content file of the local disk of the host to be recovered.
The recovery device of the operating system according to the embodiment of the present invention further includes:
and the guiding module is used for restarting the host to be recovered, disconnecting the mapping between the host to be recovered and the emergency system, and selecting the local disk of the host to be recovered to guide so as to realize the recovery.
An embodiment of the present invention provides a recovery device for an operating system, including: at least one processor, at least one memory, and computer program instructions stored in the memory, which when executed by the processor, implement the method of the first aspect of the embodiments described above.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which computer program instructions are stored, which, when executed by a processor, implement the method of the first aspect in the foregoing embodiments.
According to the recovery method, the recovery device, the recovery equipment and the recovery medium of the operating system, provided by the embodiment of the invention, the emergency system is mapped to the host to be recovered, so that the host to be recovered can be directly started through the emergency system without data transmission recovery, and the recovery time of the system is greatly saved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments of the present invention will be briefly described below, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart illustrating a recovery method for an operating system according to an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a recovery apparatus of an operating system according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating a recovery method for an operating system according to another embodiment of the present invention;
FIG. 4 is a diagram illustrating an operating system backup roll-over of an embodiment of the invention;
FIG. 5 shows a schematic diagram of an emergency system mapping of an embodiment of the invention;
FIG. 6 shows a schematic diagram of the emergency system initiation of an embodiment of the present invention;
FIG. 7 is a schematic diagram illustrating reverse clone curing of an emergency system to a local disk according to an embodiment of the present invention;
fig. 8 is a schematic diagram illustrating a hardware configuration of a recovery device of an operating system according to an embodiment of the present invention.
Detailed Description
Features and exemplary embodiments of various aspects of the present invention will be described in detail below, and in order to make objects, technical solutions and advantages of the present invention more apparent, 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 merely illustrative of the invention and are not to be construed as limiting the invention. It will be apparent to one skilled in the art that the present invention may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present invention by illustrating examples of the present invention.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Referring to fig. 1, fig. 1 is a flow chart illustrating a recovery method 100 of an operating system according to an embodiment of the present invention, where the method includes:
s110, backing up the operating system of the host computer to be backed up to obtain a plurality of operating system backups;
s120, when the host to be backed up fails, the multiple operating system backups are turned over to form multiple emergency systems;
s130, mapping the multiple emergency systems to the host to be recovered, so that the host to be recovered is started through one of the multiple emergency systems when being started.
According to the scheme provided by the embodiment of the invention, the operating systems of the backup host are backed up, the multiple operating system backups are turned over to form multiple emergency systems, and then the emergency systems are mapped to the host to be recovered, so that the host to be recovered can be directly started through the emergency systems without data transmission recovery, and the time for recovering the system is greatly saved.
Referring to fig. 2, fig. 2 is a schematic structural diagram illustrating a recovery apparatus 200 for an operating system according to an embodiment of the present invention, where the apparatus includes:
an operating system backup module 210, configured to backup an operating system of a host to be backed up, and obtain multiple operating system backups;
the emergency system 220 is used for turning over the backups of the operating systems to form a plurality of emergency systems when the host to be backed up fails;
the mapping module 230 is configured to map the multiple emergency systems to the host to be recovered, so that the host to be recovered is started through one of the multiple emergency systems when the host to be recovered is started.
According to the scheme provided by the embodiment of the invention, the operating systems of the backup host are backed up, the multiple operating system backups are turned over to form multiple emergency systems, and then the emergency systems are mapped to the host to be recovered, so that the host to be recovered can be directly started through the emergency systems without data transmission recovery, and the time for recovering the system is greatly saved.
The quick recovery method for the operating system provided by the embodiment of the invention can turn the operating system backup reserved in the emergency recovery platform into the emergency system after the operating system is backed up to the emergency recovery platform, directly map the emergency system to the host needing to be recovered as the system disk of the recovery host, support the recovery host to be directly started, avoid the data transmission process, complete the recovery start of the system with the fastest speed and the simplest steps, and solidify the emergency system into the local disk of the recovery host by utilizing the reverse cloning of the disk after the recovery host is started.
In order to implement the method of the embodiment of the present invention, the storage space of the emergency recovery platform is pre-divided into two parts, namely an emergency boot area and a recovery reserved area, and the following description is provided for the emergency boot area and the recovery reserved area, specifically as follows:
the emergency starting area is used as an emergency system when the operating system fails, data recovery transmission is not needed, the host is directly started, and recovery preparation time is shortened;
and the recovery reserved area is used for reserving the historical copy of the operating system so as to select the required historical version to be turned over and then to be started in an emergency mode under the fault condition.
All the operating system backups are written into the recovery reserved area, when the historical data needs to be recovered, the operating system backups are turned over from the recovery reserved area to the emergency starting area, and the operating system backups can be solidified from the emergency recovery platform to a local disk of the recovery host machine through reverse cloning after being started, so that subsequent starting is facilitated.
Referring to fig. 3, a fast reply scheme of an operating system according to an embodiment of the present invention is described in detail, and fig. 3 shows a schematic diagram of a recovery method 300 of an operating system according to another embodiment of the present invention, which is specifically as follows:
the first step, executing the backup of the complete system;
during backup, complete backup is performed on the relevant configuration information of the operating system, wherein the configuration information mainly includes boot information, disk partitions, content files and the like, so as to form a complete operating system backup, and each component of the configuration information is introduced as follows:
guiding information: for transferring system control to a designated operating system (different operating systems have different boot information) that is registered in the partition table at startup of the operating system hard disk.
Network configuration: the configuration of the necessary network ports includes Media Access Control (MAC) addresses, IP information, and the like. So as to facilitate the network mapping start in the subsequent recovery and the connection verification after the recovery.
Partitioning a disk: the distribution of the partitions or the file systems on the operating system disk is responsible for explaining which partitions or file systems exist in the operating system, and the size and the use condition of each partition or file system.
Content file: what contents are contained in each partition or file system in the operating system and backed up.
The above 4 parts of contents form a complete operating system backup, the operating system backup is stored in a recovery reserved area of the emergency recovery platform for storage, and a general data de-duplication technology and the like can be adopted in the storage process.
Referring to table 1, table 1 shows an exemplary table of operating system backup components:
TABLE 1
Secondly, selecting backup to overturn when a fault occurs;
through the first step of the full operating system backup, the operating system such as boot information, network configuration, disk partitions, content files, and the like are recorded.
When the backup host fails, a historical copy of the operating system backup can be designated, and the operating system backup is turned into an emergency system.
During turning over, the partition size of the emergency system can be specified according to the partition size and the content size of the disk, and the network configuration of the emergency system can be modified during abnormal recovery.
It should be noted that in some embodiments, the backup host and the restore host may be the same host; in other embodiments, the backup host and the restore host may be heterogeneous.
As an example, referring to fig. 4, fig. 4 shows a schematic diagram of an operating system backup roll-over according to an embodiment of the present invention.
When a complete os backup is completed and stored in a recovery reserved area, an os backup needs to be turned into an emergency system and delivered to a recovery host for use, and how to turn over each component of the os backup is described as follows:
firstly, directly converting guide information, namely an original system is a Linux system, into guide information of an emergency system;
secondly, network configuration, wherein an IP address configured on a network card with MAC addresses of 1A:2B:3C:4E of the original system is 192.168.0.100, and a gateway is 192.168.0.1; in the embodiment shown in fig. 4, the roll-over is modified for the recovery of the different machine, the MAC address of the roll-over is modified to be 4E:3C:2B:1A, the IP address is modified to be 192.168.0.101, and the gateway is not changed. In other embodiments, the roll-over may be a same machine recovery.
It should be noted that fig. 4 is only one example. In other embodiments, one or more of the flipped MAC address, IP address, and gateway may be modified.
Thirdly, partitioning a disk, wherein 3 partitions are divided in an original system: partition 1 has a total space of 10GB, and 5GB is used; the total space of the partition 2 is 20GB, and 10GB is used; partition 3 has a total space of 30GB and has used 15 GB.
In order to save the space of an emergency starting area, the disk subareas are corrected and turned, and the subarea 1 is divided into 8GB (more than 5GB (used), and <10GB (less than the total size)); partition 2 is divided into 18GB >10GB (greater than used), <20GB (less than total size) ]; partition 3 is divided into 28GB >15GB (greater than used), <30GB (less than total size).
It should be noted that the correction value for correcting the roll-over can be custom set as desired. In the above embodiment, in consideration of space utilization of the emergency starting area, the modification to the size of the partition cannot be smaller than the used partition and cannot be larger than the total size.
Finally, the content file, will be directly flipped over, and cannot be corrected.
Thirdly, directly starting emergency after mapping;
as an example, referring to fig. 5, fig. 5 shows an emergency system mapping diagram of an embodiment of the invention.
The overturning process is rapidly completed in the emergency recovery platform, and one or more emergency systems are formed after the overturning is completed and can be mapped to the recovery host for direct use.
The emergency system may be read-only mapped in a number of ways, including but not limited to FC (fiber Link) mapping or PXE boot (network Link), to map the emergency system to multiple recovery hosts through a switched network for an identified boot.
(1) Emergency system mapping
Different emergency systems are backed up and turned out by different operating systems, the emergency systems are mapped to the recovery host through a switching network in a read-only mode, and the emergency systems support the recovery host to be started through a system disk serving as the recovery host.
During which no recovery data need be transmitted.
In a read-only mapping mode, the same emergency system can be mapped to a plurality of different recovery hosts and simultaneously started.
The same recovery host may also accept mappings for different emergency systems, and upon startup one of the mapped emergency systems may be selected for startup.
(2) Emergency system start-up
Referring to fig. 6, fig. 6 shows a schematic diagram of the emergency system activation of an embodiment of the present invention.
As an example, the recovery host selects the available emergency systems that have been mapped (e.g., 1 from a plurality of emergency systems that have been mapped in different ways) at startup, and when the recovery host is started up by the emergency systems, a recovery log is created in the local disk space of the recovery host, where the recovery log is used to store newly written data, and the emergency systems are left unchanged as being in read-only mode, i.e., the host can be recovered immediately.
Fourthly, reverse cloning and curing of the emergency system;
after the recovery host completes emergency start through the emergency system, the emergency system can be solidified into a local disk of the recovery host through reverse cloning.
As shown in fig. 7, fig. 7 is a schematic diagram illustrating reverse clone curing of an emergency system to a local disk according to an embodiment of the present invention.
As an example, how the parts of the emergency system are reversely cloned when the emergency system is reversely cloned and solidified to the local disk is described as follows:
firstly, directly cloning the guide information into the guide information of a local disk of a recovery host;
secondly, the network configuration, because the mapping is completed, the MAC address of the recovery host is not modified, but the IP address can be modified again, the MAC address is 192.168.0.101 in the emergency system, and the gateway is 192.168.0.1; at the time of cloning, the IP address is corrected to 192.168.0.103, and the gateway is not changed.
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 desired.
And finally, partitioning a disk, wherein 3 partitions are divided in the emergency system: partition 1 is 8 GB; partition 2 is 18 GB; partition 3 is 28 GB.
Referring to table 2, table 2 shows an exemplary table of the operating system backup components of the restoration reserved area shown in fig. 4, according to the backup information in the restoration reserved area in the second step:
when the emergency system clones the local disk, the emergency system can correct the local disk, and the partition 1 is divided into 15GB (greater than 5GB (used) and greater than 10GB (total size)); partition 2 is divided into 20GB >10GB (greater than used), 20GB (equal to total size); partition 3 is divided into 28GB >15GB (greater than used), <30GB (less than total size).
TABLE 2
Therefore, the correction value of the correction clone can be set by self according to requirements, and the network configuration and the disk partition can be adjusted according to specific requirements so as to deal with different recovery purposes.
And completing reverse cloning, namely after the emergency system is solidified to the local disk, restarting the recovery host computer at a proper time, disconnecting the mapping with the emergency system, selecting the local disk for guiding, and completing recovery.
According to the scheme provided by the embodiment of the invention, the operating system is completely backed up (for example, the operating system comprises guide information, network configuration, a disk partition, a content file and the like) during backup to form a complete operating system backup and store the complete operating system backup in the emergency recovery platform, when recovery is needed, the operating system backup is turned to a specific area (for example, an emergency starting area) of the emergency recovery platform according to requirements to form a complete emergency system, and then the emergency system is mapped to the host computer needing recovery, so that the host computer needing recovery can be directly started through the emergency system.
The scheme provided by the embodiment of the invention not only avoids a large number of steps, time and environmental deviation of redeployment, but also does not need to maintain a large number of guide images, directly starts the host computer through the emergency system, does not need to carry out data transmission recovery, and greatly saves the time for recovering the system.
In summary, when the operating system fails, the operating system backup image of the dedicated emergency recovery platform is turned over to become the emergency system of the emergency boot area, and the emergency system is directly mapped to the recovery host, without transmitting recovery data, and the recovery host is directly booted through the emergency boot area.
In addition, the recovery reserved area is turned to the emergency starting area, the emergency starting area is started, and the emergency starting area can be reversely cloned to the local disk of the recovery host.
Therefore, the scheme provided by the invention not only can retain the historical data copies of a plurality of operating systems to the greatest extent by means of backup recovery and by means of common backup technologies such as data de-duplication and the like; meanwhile, the rapid recovery of the operating system is realized by means of mapping after the emergency recovery platform is turned over at the highest speed and reverse cloning and curing; in the process of turning and cloning, different recovery requirements and environments are met under the condition that the operating system is ensured to be free of deviation, and the method is an operating system protection means with very balanced timeliness, performance and functions.
The technical effects of the scheme provided by the invention can be achieved as follows:
firstly, the traditional recovery data transmission process is not needed, the backup of the operating system is mapped after being turned over at the highest speed in the emergency recovery platform, the support recovery host is directly started, and the timeliness is very high.
Secondly, a plurality of time node historical copies can be reserved in the recovery reserved area by using a universal backup technology, and logic errors at each time point can be effectively repaired.
And thirdly, the emergency starting area supports various mapping links and mapping modes, correction parameters can be set in the turning and cloning processes, different environments can be effectively corresponded, and the requirement for large-batch quick recovery is met.
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 recovery device of the operating system. Fig. 8 is a schematic diagram illustrating a hardware structure of a recovery device of an operating system according to an embodiment of the present invention.
The operating system recovery device may include a processor 1003 and a memory 1004 that stores computer program instructions.
Fig. 8 is a block 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 via a bus 1010, and the input device 1001 and the output device 1006 are connected to the bus 1010 via the input interface 1002 and the output interface 1005, respectively, and further connected to other components of the computing device 1000.
Specifically, the input device 1001 receives input information from the outside and transmits the input information to the processor 1003 via the input interface 1002; the processor 1003 processes the input information based on computer-executable instructions stored in the memory 1004 to generate output information, stores the output information temporarily or permanently in the memory 1004, and then transmits the output information to the output device 1006 through the output interface 1005; output device 1006 outputs the output information external to computing device 1000 for use by a user.
The computing device 1000 may perform the steps of the communication method described herein.
Processor 1003 may be one or more Central Processing Units (CPUs). In the case where the processor 1003 is one 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 or more of Random Access Memory (RAM), Read Only Memory (ROM), Erasable Programmable Read Only Memory (EPROM), compact disc read only memory (CD-ROM), a hard disk, and the like. The memory 1004 is used to store program codes.
It is understood that, in this embodiment of the application, the functions of any one or all of the modules from the operating system backup module to the boot module provided in fig. 2 may be implemented by the central processor 1003 shown in fig. 8.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When used in whole or in part, can be implemented in a computer program product that includes one or more computer instructions. When loaded or executed on a computer, cause the flow or functions according to embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL), or wireless (e.g., 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, etc., that includes one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
All parts of the specification are described in a progressive mode, the same and similar parts of all embodiments can be referred to each other, and each embodiment is mainly introduced to be different from other embodiments. In particular, as to the apparatus and system embodiments, since they are substantially similar to the method embodiments, the description is relatively simple and reference may be made to the description of the method embodiments in relevant places.
Claims (13)
1. A method of operating system recovery, comprising:
backing up an operating system of a host to be backed up to obtain a plurality of operating system backups;
when the host to be backed up fails, the plurality of operating system backups are turned over to form a plurality of emergency systems;
mapping the plurality of emergency systems to a host to be recovered, so that the host to be recovered is started through one of the plurality of emergency systems when being started.
2. The method of claim 1, wherein each of the plurality of operating system backups comprises at least one of:
boot information, network configuration, disk partitions, and content files.
3. The method of claim 2, wherein the flipping the plurality of operating system backups comprises:
directly converting the boot information backed up by the operating systems into the boot information of the emergency systems;
transferring the network configuration revision backed up by the plurality of operating systems to the network configuration of the plurality of emergency systems;
modifying and overturning each disk partition backed up by the operating systems into each disk partition of the emergency systems;
and directly turning the content files backed up by the operating systems into the content files of the emergency systems.
4. The method of claim 3, wherein the flipping the network configuration revision of the plurality of operating system backups to the network configuration of the plurality of emergency systems comprises:
and based on user requirements, the MAC addresses, the IP addresses or the gateway corrections of the network configuration backed up by the operating systems are turned into the MAC addresses, the IP addresses or the gateways of the network configuration of the emergency systems.
5. The method of claim 3, wherein the flipping the disk partition modifications of the plurality of operating system backups to disk partitions of the plurality of emergency systems comprises:
and based on the used space size and the total space size of each disk partition of the multiple operating system backups, modifying and overturning each disk partition of the multiple operating system backups into each disk partition of the multiple emergency systems, so that the space size of each disk partition of the multiple emergency systems is larger than the used space size of each disk partition of the multiple operating system backups and smaller than the total space size of each disk partition of the multiple operating system backups.
6. The method of claim 1, wherein mapping the plurality of emergency systems to a host to be recovered comprises:
and mapping the plurality of emergency systems to the host to be recovered through a switching network based on a read-only mode.
7. The method of claim 1, wherein the initiating by one of the plurality of emergency systems comprises:
and when one of the emergency systems is started, creating a recovery log in a local disk of the host to be recovered, wherein the recovery log is used for storing newly written data.
8. The method of claim 1, further comprising:
and solidifying one of the plurality of emergency systems into a local disk of the host to be recovered through reverse cloning.
9. The method of claim 8, wherein the solidifying of the one of the plurality of emergency systems to the local disk of the host to be recovered by reverse cloning comprises:
directly cloning the boot information of one of the plurality of emergency systems into the boot information of the local disk of the host to be recovered;
the network configuration of one of the emergency systems is revised and cloned into the network configuration of the local disk of the host to be recovered;
modifying and cloning the disk partition of one of the emergency systems into the disk partition of the local disk of the host to be recovered;
and directly cloning the content file of one of the emergency systems into the content file of the local disk of the host to be recovered.
10. The method of claim 9, further comprising:
restarting the host to be recovered, disconnecting the mapping between the host to be recovered and the emergency system, and selecting the local disk of the host to be recovered for guiding so as to realize recovery.
11. An operating system recovery apparatus comprising:
the operating system backup module is used for backing up the operating system of the host computer to be backed up to obtain a plurality of operating system backups;
the emergency system is used for turning over the operating system backups to form a plurality of emergency systems when the host to be backed up fails;
the mapping module is used for mapping the plurality of emergency systems to the host to be recovered, so that the host to be recovered is started through one of the plurality of emergency systems when being started.
12. An operating system recovery apparatus, comprising: at least one processor, at least one memory, and computer program instructions stored in the memory that, when executed by the processor, implement the method of any of claims 1-10.
13. A computer-readable storage medium having computer program instructions stored thereon, which when executed by a processor implement the method of any one of claims 1-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811615966.0A CN111382006B (en) | 2018-12-27 | 2018-12-27 | Recovery method, device, equipment and medium of operating system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811615966.0A CN111382006B (en) | 2018-12-27 | 2018-12-27 | Recovery method, device, equipment and medium of operating system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111382006A true CN111382006A (en) | 2020-07-07 |
| CN111382006B CN111382006B (en) | 2023-04-07 |
Family
ID=71214503
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811615966.0A Active CN111382006B (en) | 2018-12-27 | 2018-12-27 | Recovery method, device, equipment and medium of operating system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111382006B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113708981A (en) * | 2021-10-28 | 2021-11-26 | 广东睿江云计算股份有限公司 | Method and system for repairing fault of cloud host system |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103221924A (en) * | 2010-11-22 | 2013-07-24 | 蓝弧英国有限公司 | File cloning and de-cloning in a data storage system |
| US20170075765A1 (en) * | 2015-09-14 | 2017-03-16 | Prophetstor Data Services, Inc. | Hybrid backup and recovery management system for database versioning and virtualization with data transformation |
| CN106528345A (en) * | 2016-11-11 | 2017-03-22 | 郑州云海信息技术有限公司 | Cloud platform-based node hard disk automated recovery method |
| CN106648957A (en) * | 2015-11-03 | 2017-05-10 | 中国移动通信集团安徽有限公司 | Operating system backup and recovery method and system |
| US20170132089A1 (en) * | 2015-11-10 | 2017-05-11 | International Business Machines Corporation | Scheduling and executing a backup |
| CN107273246A (en) * | 2017-06-15 | 2017-10-20 | 郑州云海信息技术有限公司 | A kind of server system backup method and device |
| CN107729177A (en) * | 2017-09-18 | 2018-02-23 | 中国科学院信息工程研究所 | Backup data store management method, device and system based on cloud storage |
| CN108241550A (en) * | 2016-12-23 | 2018-07-03 | 研祥智能科技股份有限公司 | A kind of operating system backup and reduction method |
-
2018
- 2018-12-27 CN CN201811615966.0A patent/CN111382006B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103221924A (en) * | 2010-11-22 | 2013-07-24 | 蓝弧英国有限公司 | File cloning and de-cloning in a data storage system |
| US20170075765A1 (en) * | 2015-09-14 | 2017-03-16 | Prophetstor Data Services, Inc. | Hybrid backup and recovery management system for database versioning and virtualization with data transformation |
| CN106648957A (en) * | 2015-11-03 | 2017-05-10 | 中国移动通信集团安徽有限公司 | Operating system backup and recovery method and system |
| US20170132089A1 (en) * | 2015-11-10 | 2017-05-11 | International Business Machines Corporation | Scheduling and executing a backup |
| CN106528345A (en) * | 2016-11-11 | 2017-03-22 | 郑州云海信息技术有限公司 | Cloud platform-based node hard disk automated recovery method |
| CN108241550A (en) * | 2016-12-23 | 2018-07-03 | 研祥智能科技股份有限公司 | A kind of operating system backup and reduction method |
| CN107273246A (en) * | 2017-06-15 | 2017-10-20 | 郑州云海信息技术有限公司 | A kind of server system backup method and device |
| CN107729177A (en) * | 2017-09-18 | 2018-02-23 | 中国科学院信息工程研究所 | Backup data store management method, device and system based on cloud storage |
Non-Patent Citations (3)
| Title |
|---|
| HONGLIANG YU: ""BIRDS: A Bare-Metal Recovery System for Instant Restoration of Data Services"", 《IEEE TRANSACTIONS ON COMPUTERS》 * |
| LOSTARK: ""Windows Server Backup 裸机恢复"", 《HTTPS://WWW.CNBLOGS.COM/LIANGWANG/P/6339444.HTML》 * |
| 林森: ""面向NTFS的已损坏文件恢复技术研究"", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113708981A (en) * | 2021-10-28 | 2021-11-26 | 广东睿江云计算股份有限公司 | Method and system for repairing fault of cloud host system |
| CN113708981B (en) * | 2021-10-28 | 2022-04-15 | 广东睿江云计算股份有限公司 | Method and system for repairing fault of cloud host system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111382006B (en) | 2023-04-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8352720B2 (en) | Method for changing booting configuration and computer system capable of booting OS | |
| US8156373B2 (en) | System for disaster recovery backup and a method thereof | |
| US20080091746A1 (en) | Disaster recovery method for computer system | |
| CN106775610B (en) | Electronic equipment starting method and electronic equipment | |
| US9792181B2 (en) | Pool of devices providing operating system redundancy | |
| US20140122860A1 (en) | Cloud system and boot deployment method for the cloud system | |
| JP6455898B2 (en) | Data replication method, primary data storage controller, apparatus, system, and program | |
| CN104915226A (en) | Network device software starting method, device and network device | |
| EP3848809A1 (en) | Data disaster recovery method and site | |
| RU2653254C1 (en) | Method, node and system for managing data for database cluster | |
| US20170052779A1 (en) | Method and Device for Running Version File | |
| CN105635216A (en) | Distributed application upgrade method, device and distributed system | |
| CN112055087A (en) | Method and system for rapid deployment, migration and maintenance of Mongodb cluster | |
| US8880472B2 (en) | Method of backing-up, and making available, electronic data and software initially stored on a client server | |
| CN111382006B (en) | Recovery method, device, equipment and medium of operating system | |
| EP2542976A1 (en) | Method and apparatus of backing-up subversion repository | |
| US20150269237A1 (en) | Disaster Recovery of Converged Infrastructure Platforms | |
| CN110532134B (en) | NAS data backup disaster recovery method and device | |
| US20060253668A1 (en) | Method and apparatus for preserving operating system and configuration files against a system failure | |
| JP5798056B2 (en) | Call processing information redundancy control system and spare maintenance server used therefor | |
| CN110377400B (en) | Virtual machine recovery method, device, system and medium | |
| CN111240895A (en) | OpenStack-oriented node batch backup system method | |
| CN105938417B (en) | Update the method and device of configuration data | |
| CN111756562B (en) | Cluster takeover method, system and related components | |
| CN111142921A (en) | Software upgrading method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |