CN112367186A - Fault protection method and device based on 0penStack bare machine - Google Patents
Fault protection method and device based on 0penStack bare machine Download PDFInfo
- Publication number
- CN112367186A CN112367186A CN202011089740.9A CN202011089740A CN112367186A CN 112367186 A CN112367186 A CN 112367186A CN 202011089740 A CN202011089740 A CN 202011089740A CN 112367186 A CN112367186 A CN 112367186A
- Authority
- CN
- China
- Prior art keywords
- bare
- resource
- deployment
- machine
- network
- 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
- 238000000034 method Methods 0.000 title claims abstract description 26
- 238000011084 recovery Methods 0.000 claims abstract description 34
- 238000003860 storage Methods 0.000 claims abstract description 21
- 239000002184 metal Substances 0.000 claims description 46
- 238000002360 preparation method Methods 0.000 claims description 9
- RJKFOVLPORLFTN-LEKSSAKUSA-N Progesterone Chemical compound C1CC2=CC(=O)CC[C@]2(C)[C@@H]2[C@@H]1[C@@H]1CC[C@H](C(=O)C)[C@@]1(C)CC2 RJKFOVLPORLFTN-LEKSSAKUSA-N 0.000 claims description 3
- 239000000284 extract Substances 0.000 claims description 2
- 230000010076 replication Effects 0.000 abstract 1
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000005012 migration Effects 0.000 description 2
- 238000013508 migration Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
-
- 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/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/142—Reconfiguring to eliminate the error
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5046—Resolving address allocation conflicts; Testing of addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5061—Pools of addresses
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Hardware Redundancy (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a fault protection method and a fault protection device based on a 0penStack bare engine.A fault recovery instruction is acquired when a bare engine resource has a fault or is insufficient in storage resource, configuration information of an original bare engine resource is extracted, a target environment is matched, and a set of replication relation is generated; if the mirror image and the network information required by the bare computer exist in the target environment, executing a recovery instruction of the bare computer, otherwise, firstly copying the mirror image required by the bare computer and establishing network resources; and after bare machine resource deployment is carried out according to the copying relation, the recovered bare machine resource information is extracted and compared with the original bare machine resource information, if the comparison is inconsistent, a synchronization task is called to carry out data synchronization until the data are consistent, and the bare machine resource recovery is successful. Through the mode, the bare computer resource data recovery method and the bare computer resource data recovery system can ensure the accuracy of bare computer resource data recovery, avoid data loss, reduce time consumption and labor cost and improve system stability.
Description
Technical Field
The invention relates to the technical field of cloud platform resource management, in particular to a fault protection method and device based on a 0penStack bare computer.
Background
With continuous progress of the information age, cloud computing management platforms are more and more popular, management technologies for virtualized resources are more and more mature, but only the virtualized resources are insufficient, and users need to directly use physical server resources for certain high-performance computing, high security and reliability requirements, other database hosts and the like, so that the management of the physical resources is more and more popular.
The bare computer refers to a computer not equipped with an operating system. OpenStack manages the cloud physical machine to the platform, and the cloud physical machine is deployed to install an operating system, so that the seamless connection between virtualization and physical resources is realized, and the requirements of more users are met. The OpenStack is an open-source cloud computing management platform project and is a combination of a series of software open-source projects.
When a fault occurs or system resources are insufficient in the process of providing bare computer service by the OpenStack platform, bare computer resources cannot continuously provide service for users, and at this time, other platforms or bare computers need to be replaced to perform service deployment again. However, resources need to be set up again after switching, and the same migration of original resources and data cannot be performed, and deployment and debugging of bare computer services also need to consume a large amount of time and labor cost, so that data loss caused by the deployment and debugging may cause major production accidents in real life.
Disclosure of Invention
The invention mainly solves the technical problem of providing a fault protection method and a fault protection device based on a 0penStack bare engine, which are used for migrating and protecting relevant resources of the bare engine when the bare engine resources of an OpenStack platform have faults or are insufficient in resources, so that the accuracy of recovering bare engine resource data can be ensured, the data loss is avoided, the time and labor cost are reduced, the system stability is improved, and major production accidents caused by the faults of the bare engine resources can be avoided.
In order to solve the technical problems, the invention adopts a technical scheme that: the fault protection method based on the 0penStack bare machine comprises the following steps:
s1, generating a copy relation, and sending alarm information to the system when the bare metal resources are damaged and can not be recovered or the storage resources are insufficient and the service can not be provided continuously; when the system acquires and analyzes alarm information, acquires associated target environment information and issues a fault recovery request, detects whether target environment resources are sufficient, extracts original bare machine resource configuration information, matches the target environment and forms a copy relationship between bare machine resources matched with the target environment;
s2, recovering the environment configuration of the bare metal resources, and performing mirror image copying and network resource creation on the bare metal in the target environment;
s3, bare metal resource deployment recovery, after the bare metal resource recovery environment is configured, bare metal resource deployment is carried out on the target environment according to the copy relationship;
and S4, verifying the bare metal resource recovery result, after deployment is completed, extracting the recovered bare metal resource information, comparing the recovered bare metal resource information with the original bare metal resource information, and if the comparison is consistent, successfully recovering the bare metal resource.
Further, in step S1, the bare metal resource configuration information is stored on the shared storage system in a mount volume manner; the shared storage system is provided with a copy folder which takes the ID as a unique key word, and the resource configuration information of each bare metal is stored under the volume copy folder associated with the ID of each bare metal; the bare computer resource configuration information comprises resource quotas and network storage data in the running process of the cloud physical computer.
Further, the step S2 specifically includes the following steps:
s21, detecting whether a deployment mirror image, a system mirror image and drive information used in the bare metal deployment in the target environment exist, and if so, entering S22; otherwise, copying the deployment mirror image, the system mirror image and the drive information, selecting the deployment mirror image, the system mirror image, the drive information and the target position thereof, and reserving after copying;
s22, detecting whether a bare metal deployment network exists in the target environment, and if yes, entering S23; otherwise, a deployment network is created, and a network purpose CIDR and a next hop address are configured;
s23, detecting whether the bare machine tenant network exists in the target environment, and if yes, performing bare machine resource deployment recovery; and otherwise, creating a tenant network for creating and using the cloud physical machine.
Further, the step S3 specifically includes the following steps:
s31, detecting whether the available bare computers are registered in the target environment, and if so, directly entering S32; otherwise, registering the bare computer to OpenStack, inputting a BMC IP address, a user name and a password, and selecting the deployment mirror image and the drive information copied in the step S2;
s32, the bare engine is changed into a manageable state, a control node uses a netmiko library ssh to a switch through a network-generating-switch plug-in of a neutron during service deployment, a switch configuration command is issued, the obtained lldp information is configured to a switch port connected with a bare engine deployment network, and the lldp information comprises a network card address, a switch mac address and a port name;
and S33, the bare computer is converted into usable, the network is switched to a deployment network, a cloud physical computer is created, the port of the switch is switched to a tenant network after the creation is completed, then the tenant network enters an operating system of the cloud physical computer to restart the network service, and the IP is obtained.
Further, the step S4 specifically includes the following steps: and the recovered cloud physical machine acquires the original bare machine resource information through the copy relationship of the shared storage system, compares the recovered bare machine resource information with the original bare machine resource information, successfully recovers the bare machine fault after the comparison is consistent, and calls a synchronization task to perform data synchronization until the data are consistent if the comparison is inconsistent.
A fault protection device based on a 0penStack bare engine comprises: the bare metal resource recovery system comprises a bare metal resource information storage module, a bare metal resource recovery environment preparation module and a bare metal resource deployment recovery module;
the bare machine resource information storage module records a deployment network, an observation network, a switch configuration, a deployment mirror image and a system mirror image used in bare machine deployment and cloud physical machine creation processes;
when bare engine resources are in failure, the bare engine resource recovery environment preparation module recovers the existing bare engine resources to a new environment, and environment preparation of bare engine and cloud physical engine deployment is carried out on the new environment;
and the bare machine resource deployment recovery module performs bare machine registration and cloud physical machine deployment in a new environment, and compares the deployed bare machine registration and cloud physical machine deployment with the original resources after deployment is completed, so that the consistency of resource data is ensured.
The invention has the beneficial effects that: according to the invention, relevant resources of the bare machine do not need to be built again, bare machine resource data are restored again, one-to-one fault migration restoration is carried out according to the original bare machine resources, the accuracy of the data is ensured, high available technical support is provided for system service support of users, data loss, time consumption and labor cost are avoided, and the system stability is further improved.
Drawings
FIG. 1 is a flow chart of a preferred embodiment of a fault protection method based on a 0penStack bare metal of the present invention;
fig. 2 is a block diagram of a fault protection device based on a 0penStack bare chip according to the present invention.
Detailed Description
The following detailed description of the preferred embodiments of the present invention, taken in conjunction with the accompanying drawings, will make the advantages and features of the invention easier to understand by those skilled in the art, and thus will clearly and clearly define the scope of the invention.
Referring to fig. 1, an embodiment of the present invention includes:
a fault protection method based on a 0penStack bare machine comprises the following steps:
and S1, after the bare computer environment is configured, creating a cloud physical computer, and storing relevant data such as resource quotas, network storage and the like in the running process of the cloud physical computer into a copy folder which takes the ID as a unique key word on a corresponding shared storage system in a mount volume mode, wherein the running data of each cloud physical computer is stored under the volume copy folder which is associated with the cloud physical computer. When the bare computer resources are damaged and can not be recovered or the storage resources are insufficient and the service can not be provided continuously, alarm information is sent to the system. When the alarm information is acquired and the problem is analyzed, acquiring the associated target environment information and issuing a fault recovery request, and detecting whether the target environment resource is sufficient; and extracting the configuration information of the original bare machine resource, matching the target environment and forming a copy relation between the bare machine resources matched with the target environment.
S2, after obtaining the configuration information of the original bare metal resource, matching and detecting the configuration information of the target environment:
if the deployment mirror image and the system mirror image used in the bare computer deployment in the target environment exist, the next item is carried out; otherwise, copying the deployment image and the system image: after selecting the mirror image, selecting a target position, and copying the mirror image for later use;
if the bare computer deployment network exists in the target environment, carrying out tenant network detection; otherwise, a deployment network is created, and a network purpose CIDR and a next hop address are configured;
if the target environment has a bare tenant network, performing the next item; and otherwise, creating a tenant network for creating and using the cloud physical machine.
S3, firstly, detecting whether the available bare engine is registered in the new environment, and if so, directly carrying out the next step; otherwise, registering the bare computer to OpenStack, inputting a correct BMC IP address, a user name, a password and the like, and selecting the copied deployment mirror image and the drive information;
the bare computer is converted into a manageable bare computer, a control node uses a netmiko library ssh to a switch through a network-generic-switch plug-in of a neutron during service deployment, a switch configuration command is issued, the obtained lldp information is configured to a switch port connected with a bare computer deployment network, and the lldp information comprises a network card address, a switch mac address and a port name;
and (3) converting the bare computer into a usable bare computer, switching the network to a deployment network, creating a cloud physical computer, switching the switch port to a tenant network after creation is completed, then entering an operating system of the cloud physical computer to restart the network service, and acquiring the IP.
S4, the volume ID information of the original cloud physical machine is stored in the copy folder, so that the new cloud physical machine can acquire original service data through the copy relationship of the shared storage system, the original service data is compared with the original bare machine resource information through a consistency group, the bare machine fault recovery is successful after the consistency is compared, if the consistency is not compared, a synchronization task is called, and data synchronization is carried out until the data are consistent; and at this point, the bare metal resources are successfully recovered.
Based on the same inventive concept as the fault protection method based on the 0penStack bare engine in the foregoing embodiment, an embodiment of the present specification further provides a fault protection device based on the 0penStack bare engine, as shown in fig. 2, including: the bare metal resource recovery system comprises a bare metal resource information storage module, a bare metal resource recovery environment preparation module and a bare metal resource deployment recovery module;
the bare machine resource information storage module records a deployment network, an observation network, a switch configuration, a deployment mirror image and a system mirror image used in bare machine deployment and cloud physical machine creation processes;
when bare engine resources are in failure, the bare engine resource recovery environment preparation module recovers the existing bare engine resources to a new environment, and environment preparation of bare engine and cloud physical engine deployment is carried out on the new environment;
and the bare machine resource deployment recovery module performs bare machine registration and cloud physical machine deployment in a new environment, and compares the deployed bare machine registration and cloud physical machine deployment with the original resources after deployment is completed, so that the consistency of resource data is ensured.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes performed by the present specification and drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (9)
1. A fault protection method based on a 0penStack bare machine is characterized by comprising the following steps:
s1, generating a copy relationship, extracting the resource configuration information of the original bare computer after acquiring the fault recovery instruction, matching the target environment and generating a set of copy relationship;
s2, recovering the environment configuration of the bare metal resources, and performing mirror image copying and network resource creation on the bare metal in the target environment;
s3, bare metal resource deployment recovery, after the bare metal resource recovery environment is configured, bare metal resource deployment is carried out on the target environment according to the copy relationship;
and S4, verifying the bare metal resource recovery result, after deployment is completed, extracting the recovered bare metal resource information, comparing the recovered bare metal resource information with the original bare metal resource information, and if the comparison is consistent, successfully recovering the bare metal resource.
2. The fault protection method based on the 0penStack bare engine according to claim 1, characterized in that: in step S1, storing the raw machine resource configuration information on the shared storage system in a mount volume manner; and the shared storage system is provided with a copy folder which takes the ID as a unique key word, and the resource configuration information of each bare metal is stored under the volume copy folder associated with the ID.
3. The fault protection method based on the 0penStack bare engine according to claim 2, characterized in that: the bare computer resource configuration information comprises resource quotas and network storage data in the running process of the cloud physical computer.
4. The fault protection method based on the 0penStack bare engine according to claim 3, characterized in that: in step S1, when the bare metal resource is damaged and cannot be recovered or the storage resource is insufficient and cannot continue to provide service, an alarm message is sent to the system; when the system acquires and analyzes the alarm information, acquires the associated target environment information and issues a fault recovery request, detects whether the target environment resources are sufficient, extracts the original bare machine resource configuration information, matches the target environment and forms a copy relationship between the bare machine resources matched with the target environment.
5. The fault protection method based on the 0penStack bare engine according to claim 2, wherein the step S2 specifically includes the following steps:
s21, detecting whether a deployment mirror image, a system mirror image and drive information used in the bare metal deployment in the target environment exist, and if so, entering S22; otherwise, copying the deployment mirror image, the system mirror image and the drive information, selecting the deployment mirror image, the system mirror image, the drive information and the target position thereof, and reserving after copying;
s22, detecting whether a bare metal deployment network exists in the target environment, and if yes, entering S23; otherwise, a deployment network is created, and a network purpose CIDR and a next hop address are configured;
s23, detecting whether the bare machine tenant network exists in the target environment, and if yes, performing bare machine resource deployment recovery; and otherwise, creating a tenant network for creating and using the cloud physical machine.
6. The fault protection method based on the 0penStack bare engine according to claim 5, wherein the step S3 specifically comprises the following steps:
s31, detecting whether the available bare computers are registered in the target environment, and if so, directly entering S32; otherwise, registering the bare computer to OpenStack, inputting a BMC IP address, a user name and a password, and selecting the deployment mirror image and the drive information copied in the step S2;
s32, the bare engine is changed into manageable, a control node uses a netmiko library ssh to a switch through a network-generic-switch plug-in of a neutron during service deployment, a switch configuration command is issued, and the acquired lldp information is configured to a switch port connected with a bare engine deployment network;
and S33, the bare computer is converted into usable, the network is switched to a deployment network, a cloud physical computer is created, the port of the switch is switched to a tenant network after the creation is completed, then the tenant network enters an operating system of the cloud physical computer to restart the network service, and the IP is obtained.
7. The fault protection method based on the 0penStack bare metal according to claim 6, wherein the lldp information in step S32 includes a network card address, a switch mac address, and a port name.
8. The fault protection method based on the 0penStack bare engine according to claim 6, wherein the step S4 specifically comprises the following steps: and the recovered cloud physical machine acquires the original bare machine resource information through the copy relationship of the shared storage system, compares the recovered bare machine resource information with the original bare machine resource information, successfully recovers the bare machine fault after the comparison is consistent, and calls a synchronization task to perform data synchronization until the data are consistent if the comparison is inconsistent.
9. A fault protection device based on a 0penStack bare engine is characterized by comprising: the bare metal resource recovery system comprises a bare metal resource information storage module, a bare metal resource recovery environment preparation module and a bare metal resource deployment recovery module;
the bare machine resource information storage module records a deployment network, an observation network, a switch configuration, a deployment mirror image and a system mirror image used in bare machine deployment and cloud physical machine creation processes;
when bare engine resources are in failure, the bare engine resource recovery environment preparation module recovers the existing bare engine resources to a new environment, and environment preparation of bare engine and cloud physical engine deployment is carried out on the new environment;
and the bare machine resource deployment recovery module performs bare machine registration and cloud physical machine deployment in a new environment, and compares the deployed bare machine registration and cloud physical machine deployment with the original resources after deployment is completed, so that the consistency of resource data is ensured.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011089740.9A CN112367186B (en) | 2020-10-13 | 2020-10-13 | Fault protection method and device based on 0penStack bare computer |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011089740.9A CN112367186B (en) | 2020-10-13 | 2020-10-13 | Fault protection method and device based on 0penStack bare computer |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112367186A true CN112367186A (en) | 2021-02-12 |
| CN112367186B CN112367186B (en) | 2023-01-10 |
Family
ID=74507206
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011089740.9A Active CN112367186B (en) | 2020-10-13 | 2020-10-13 | Fault protection method and device based on 0penStack bare computer |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112367186B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114416434A (en) * | 2022-03-30 | 2022-04-29 | 苏州浪潮智能科技有限公司 | Bare metal disk backup method and device and computer readable storage medium |
| WO2023000672A1 (en) * | 2021-07-23 | 2023-01-26 | 苏州浪潮智能科技有限公司 | Network switching method and apparatus, electronic device, and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103618627A (en) * | 2013-11-27 | 2014-03-05 | 华为技术有限公司 | Method, device and system for managing virtual machines |
| CN107306277A (en) * | 2016-04-19 | 2017-10-31 | 中兴通讯股份有限公司 | A kind of method and device of server sync dilatation |
| CN107329769A (en) * | 2017-07-07 | 2017-11-07 | 郑州云海信息技术有限公司 | A kind of method and apparatus for configuring bare machine server |
| CN111371620A (en) * | 2020-03-11 | 2020-07-03 | 苏州浪潮智能科技有限公司 | Bare computer service deployment method and system based on distributed cache |
-
2020
- 2020-10-13 CN CN202011089740.9A patent/CN112367186B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103618627A (en) * | 2013-11-27 | 2014-03-05 | 华为技术有限公司 | Method, device and system for managing virtual machines |
| CN107306277A (en) * | 2016-04-19 | 2017-10-31 | 中兴通讯股份有限公司 | A kind of method and device of server sync dilatation |
| CN107329769A (en) * | 2017-07-07 | 2017-11-07 | 郑州云海信息技术有限公司 | A kind of method and apparatus for configuring bare machine server |
| CN111371620A (en) * | 2020-03-11 | 2020-07-03 | 苏州浪潮智能科技有限公司 | Bare computer service deployment method and system based on distributed cache |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023000672A1 (en) * | 2021-07-23 | 2023-01-26 | 苏州浪潮智能科技有限公司 | Network switching method and apparatus, electronic device, and storage medium |
| US11979307B2 (en) | 2021-07-23 | 2024-05-07 | Inspur Suzhou Intelligent Technology Co., Ltd. | Network switching method and apparatus, electronic device, and storage medium |
| CN114416434A (en) * | 2022-03-30 | 2022-04-29 | 苏州浪潮智能科技有限公司 | Bare metal disk backup method and device and computer readable storage medium |
| CN114416434B (en) * | 2022-03-30 | 2022-07-08 | 苏州浪潮智能科技有限公司 | Bare metal disk backup method and device and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112367186B (en) | 2023-01-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106850260A (en) | A kind of dispositions method and device of virtual resources management platform | |
| WO2017162032A1 (en) | Method and device for executing data recovery operation | |
| CN112367186B (en) | Fault protection method and device based on 0penStack bare computer | |
| TW201301027A (en) | Deploying environments for testing by providing instantaneous availability of prebuilt environments | |
| CN112506702B (en) | Disaster recovery method, device, equipment and storage medium for data center | |
| CN102214128A (en) | Repurposable recovery environment | |
| CN107656705B (en) | Computer storage medium and data migration method, device and system | |
| CN112596951A (en) | NAS data disaster tolerance method, device, equipment and storage medium | |
| CN107122229A (en) | A kind of virtual machine restoration methods and device | |
| WO2012171345A1 (en) | Method and distributed cache system for data recovery in temporary fault | |
| CN108228308A (en) | The monitoring method and device of virtual machine | |
| CN111078352A (en) | Dual-computer hot standby deployment method and system based on KVM virtualization system | |
| CN104407942A (en) | Off-site storage based Linux operation system backup recovery method | |
| CN106897063B (en) | Method and system for permanently adding OS boot entry to BIOS based on EFI | |
| CN115766405B (en) | Fault processing method, device, equipment and storage medium | |
| CN115221156A (en) | Database cluster capacity expansion method and device, computer equipment and storage medium | |
| CN111355605A (en) | Virtual machine fault recovery method and server of cloud platform | |
| CN111262963A (en) | Method and system for binding MAC address and IP address of virtual machine | |
| CN114598604B (en) | Monitoring method, monitoring device and terminal for virtual network function instance information | |
| CN110677469B (en) | Security disaster recovery system and disaster recovery implementation method | |
| CN103780433A (en) | Self-healing type virtual resource configuration management data architecture | |
| CN114584459A (en) | Method for realizing high availability of main and standby container cloud platforms | |
| CN110688259B (en) | Private cloud backup recovery system and backup recovery method thereof | |
| CN107172228A (en) | Change the method and apparatus and computer-readable recording medium of virtual machine IP address | |
| CN111858175A (en) | Method and equipment for backing up cloud platform data based on mobile storage 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 |