CN108932180A - A kind of disaster tolerance management method, device, storage medium and computer equipment matter - Google Patents
A kind of disaster tolerance management method, device, storage medium and computer equipment matter Download PDFInfo
- Publication number
- CN108932180A CN108932180A CN201810644529.5A CN201810644529A CN108932180A CN 108932180 A CN108932180 A CN 108932180A CN 201810644529 A CN201810644529 A CN 201810644529A CN 108932180 A CN108932180 A CN 108932180A
- Authority
- CN
- China
- Prior art keywords
- openstack
- managing device
- disaster tolerance
- resource
- standby
- 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.)
- Pending
Links
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/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention discloses a kind of disaster tolerance management methods, applied to the system comprising the first cloud computing platform OpenStack and the 2nd OpenStack, first OpenStack is main OpenStack, 2nd OpenStack is standby OpenStack, first OpenStack is equipped with the first disaster tolerance managing device, 2nd OpenStack is equipped with the second disaster tolerance managing device, the following steps are included: the first disaster tolerance managing device monitors the resource change of the first OpenStack, based on preset Disaster Recovery Strategy, the resource change is synchronized to the 2nd OpenStack by the first disaster tolerance managing device and the second disaster tolerance managing device；When the first OpenStack collapse, the second disaster tolerance managing device is switched the 2nd OpenStack for main OpenStack based on disaster recovery strategy and the synchronous resource, and the first OpenStack is switched to standby OpenStack by the first disaster tolerance managing device.The recovery process complicated compared to manual operation can be protected according to tenant's classification between the resource of disaster tolerance two centers, can also flexibly configure various Disaster Recovery Strategies, avoid manual operation fault bring disaster.
Description
Technical field
The present invention relates to computer technology, espespecially a kind of disaster tolerance management method, device, storage medium and computer equipment
Matter.
Background technique
Cloud computing is in fast-developing and landing stage, and OpenStack is by its open source, open and stable spy
Property, the fact that have become private clound standard.OpenStack landing at present most will urgently solve the problems, such as to be exactly data center
Disaster tolerance is substantially in the Disaster Tolerant Scheme used in OpenStack cloud platform actual production environment based on traditional data center
Disaster Tolerant Scheme realizes storage by means of technologies such as the remote copies of OpenStack bottom storage between active and standby Liang Ge data center
The either synchronously or asynchronously duplication of volume.Then, corresponding resource is created in Disaster Preparation Center manually, or manages work by upper layer disaster tolerance
Tool, maps the resource of Liang Ge data center, is also only limitted to the other mapping of virtual machine-level here.Although such manager
Method can achieve the disaster tolerance of virtual machine, still, manually than relatively time-consuming, also be easy error, can not be easily the money in tenant
Source carries out unified protection.
Summary of the invention
In order to solve the above-mentioned technical problems, the present invention provides a kind of disaster tolerance management method, device, storage medium and calculating
Machine equipment matter can be realized automatic backup and the disaster tolerance of data center.
In order to reach the object of the invention, the present invention provides a kind of disaster tolerance management method, it is applied to include the first cloud computing
The system of platform OpenStack and the 2nd OpenStack, the first OpenStack be main OpenStack, described second
OpenStack is that the first disaster tolerance managing device is equipped with for OpenStack, the first OpenStack, described second
OpenStack is equipped with the second disaster tolerance managing device, the described method comprises the following steps:
First disaster tolerance managing device monitors the resource change of the first OpenStack, is based on preset Disaster Recovery Strategy, and described the
The resource change is synchronized to the 2nd OpenStack by one disaster tolerance managing device and the second disaster tolerance managing device；
When the first OpenStack collapse when, the second disaster tolerance managing device be based on disaster recovery strategy with it is described synchronous
Resource the 2nd OpenStack is switched as main OpenStack, the first disaster tolerance managing device is by described first
OpenStack is switched to standby OpenStack.
Further, further include, after the first OpenStack restores, the first disaster tolerance managing device and the second disaster tolerance
The resource information of 2nd OpenStack is synchronized to the first OpenStack, the first disaster tolerance management by managing device
First OpenStack is switched back into main OpenStack by device, and the second disaster tolerance managing device is by described second
OpenStack switches back into standby OpenStack.
Further, described to be based on preset Disaster Recovery Strategy, the first disaster tolerance managing device and the second disaster tolerance management dress
It sets and the resource change is synchronized to the 2nd OpenStack, comprising:
Based on preset Disaster Recovery Strategy, the first disaster tolerance managing device is by the resource change of the first OpenStack
It is converted into resource information and is sent to the second disaster tolerance managing device；
The second disaster tolerance managing device receives and converts the resource information as the action command of establishing resource, is sent to
2nd OpenStack.
Further, the preset Disaster Recovery Strategy, including following one:
The resource change of all resources of all tenants is protected in monitoring；
Monitoring protection portion sublease family all resources resource change；
The resource change of the part resource of all tenants is protected in monitoring；
Monitoring protection portion sublease family part resource resource change.
Further, the disaster recovery strategy, including one or more of:
Start some or all of default tenant resource；
Successively starting resource is carried out according to priority；
Start resource according to the incidence relation of tenant and resource.
In order to reach the object of the invention, the present invention also provides a kind of disaster tolerance managing device, disaster tolerance managing device positions
In the first cloud computing platform OpenStack, and when the first OpenStack is main OpenStack, for monitoring first
The resource change of OpenStack, cooperating with the disaster tolerance managing device for being located at standby OpenStack, it is standby to be synchronized to the resource change
OpenStack；And in the first OpenStack collapse, the first OpenStack to be switched to standby OpenStack；
The disaster tolerance managing device is located at the 2nd OpenStack, and when the 2nd OpenStack is standby OpenStack,
The resource change is synchronized to the 2nd OpenStack for cooperating with the disaster tolerance managing device positioned at main OpenStack, and
For the 2nd OpenStack being cut with the synchronous resource based on disaster recovery strategy in main OpenStack collapse
It is changed to main OpenStack.
Further, it is also used to,
The disaster tolerance managing device is located at the 2nd OpenStack, and when the 2nd OpenStack is main OpenStack,
The resource change for monitoring the 2nd OpenStack, after the first OpenStack restores, with the disaster tolerance management for being located at standby OpenStack
The resource change is synchronized to the first OpenStack by device cooperation, the 2nd OpenStack is switched back into standby
OpenStack；
The disaster tolerance managing device is located at the first OpenStack, and when the first OpenStack is standby OpenStack,
After the first OpenStack restores, cooperates with the disaster tolerance managing device positioned at main OpenStack and be synchronized to the resource change
First OpenStack is switched back into main OpenStack by the first OpenStack.
Further, the disaster tolerance managing device cooperates with the disaster tolerance managing device for being located at standby OpenStack by the money
Source, which changes, is synchronized to standby OpenStack, comprising: the disaster tolerance managing device is based on preset Disaster Recovery Strategy, and the resource is become
Turn changes resource information into and is sent to standby OpenStack；
The disaster tolerance managing device and the disaster tolerance managing device cooperation positioned at main OpenStack are synchronous by the resource change
To the 2nd OpenStack, comprising: the disaster tolerance managing device is based on receiving and convert the resource information as the dynamic of establishing resource
It instructs, is sent to the standby OpenStack.
In order to reach the object of the invention, the present invention also provides a kind of computer readable storage mediums, are stored thereon with meter
Calculation machine program, when which is executed by processor the step of the realization above method.
In order to reach the object of the invention, the present invention also provides a kind of computer equipment, including memory, processor and
The computer program that can be run on a memory and on a processor is stored, the processor is realized above-mentioned when executing described program
Step in method.
Compared with prior art, the present invention includes the resource change that the first disaster tolerance managing device monitors the first OpenStack,
Based on preset Disaster Recovery Strategy, the resource change is synchronized to by the first disaster tolerance managing device and the second disaster tolerance managing device
2nd OpenStack；When the first OpenStack collapse, the second disaster tolerance managing device is based on disaster recovery strategy
The 2nd OpenStack is switched as main OpenStack with the synchronous resource, the first disaster tolerance managing device is by institute
It states the first OpenStack and is switched to standby OpenStack.Can the resource to data center flexibly back up and automatic disaster tolerance.
Other features and advantages of the present invention will be illustrated in the following description, also, partly becomes from specification
It obtains it is clear that understand through the implementation of the invention.The objectives and other advantages of the invention can be by specification, right
Specifically noted structure is achieved and obtained in claim and attached drawing.
Detailed description of the invention
Attached drawing is used to provide to further understand technical solution of the present invention, and constitutes part of specification, with this
The embodiment of application technical solution for explaining the present invention together, does not constitute the limitation to technical solution of the present invention.
Fig. 1 is the flow chart of one disaster tolerance management method of the embodiment of the present invention；
Fig. 2 is the integrated stand composition of two disaster tolerance management method of the embodiment of the present invention；
Fig. 3 is two disaster tolerance managing device architecture diagram of the embodiment of the present invention；
Fig. 4 is the structural schematic diagram of the computer equipment of the embodiment of the present invention three.
Specific embodiment
To make the objectives, technical solutions, and advantages of the present invention clearer, below in conjunction with attached drawing to the present invention
Embodiment be described in detail.It should be noted that in the absence of conflict, in the embodiment and embodiment in the application
Feature can mutual any combination.
Step shown in the flowchart of the accompanying drawings can be in a computer system such as a set of computer executable instructions
It executes.Also, although logical order is shown in flow charts, and it in some cases, can be to be different from herein suitable
Sequence executes shown or described step.
Embodiment one
A kind of disaster tolerance management method is present embodiments provided, is applied to include the first OpenStack and the 2nd OpenStack
System, the first OpenStack is main OpenStack, and the 2nd OpenStack is standby OpenStack, the first OpenStack peace
Equipped with the first disaster tolerance managing device, the 2nd OpenStack is equipped with the second disaster tolerance managing device, as shown in Figure 1, this method includes
S11-S12:
S11, the first disaster tolerance managing device monitor the resource change of the first OpenStack, are based on preset Disaster Recovery Strategy, the
Resource change is synchronized to the 2nd OpenStack by one disaster tolerance managing device and the second disaster tolerance managing device；
S12, when the first OpenStack collapse when, the second disaster tolerance managing device is based on disaster recovery strategy and synchronous money
Source switches the 2nd OpenStack for main OpenStack, and the first OpenStack is switched to standby by the first disaster tolerance managing device
OpenStack。
In the embodiment of the present invention, it is based on openstack cloud platform, by the way that the resource change of main OpenStack to be synchronized to
Standby OpenStack is restored when main OpenStack collapse based on disaster recovery strategy.It can be to the resource of data center
Flexibly backup and automatic disaster tolerance.
Calamity managing device monitors while connecting the OpenStack of other side, is detected, so when the first OpenStack collapses
When bursting, it can be detected simultaneously by the first OpenStack collapse.
Resource change refers to the other variation of resource change object level, such as creation virtual machine etc., then according to the behaviour of event
All information that the resource object is collected as object ID, are converted into resource information.Business datum rank is by the remote of storage
Journey duplication carrys out real-time synchronization；
Resource information do not include the data of virtual machine, roll up the data of rank, the system disk data of virtual machine, virtual machine volume
The business datums such as data；Above-mentioned business datum is still by the remote copy of storage come real-time synchronization.
The resource information includes: tenant's information, resource id information, resource specification information, resource network information, metadata
Id information, the volume information of information, the storage volume of corresponding bottom；
When the resource change is main OpenStack initialization procedure, all resources of the main OpenStack are inquired,
It is converted into resource information and is sent to the standby OpenStack.The standby OpenStack is equipped with standby disaster tolerance managing device for DR-
Manager；The main OpenStack initialization procedure inquires all resources of the main OpenStack, is converted into resource information
It is sent to the standby OpenStack, comprising: main DR-Manager inquires all resources of the main OpenStack, by the institute
There is resource to be converted to resource information and is sent to the standby DR-Manager；The standby DR-Manager converts the resource information
The standby OpenStack, which is sent to, at the action command of establishing resource carries out asset creation.
Optionally, the above method further include: after the first OpenStack restores, the first disaster tolerance managing device and second is held
The resource information of 2nd OpenStack is synchronized to the first OpenStack by calamity managing device, and the first disaster tolerance managing device is by first
OpenStack switches back into main OpenStack, and the 2nd OpenStack is switched back into standby OpenStack by the second disaster tolerance managing device.
According to concrete scene difference, the information for the process preamble that the former main OpenStack of switching is main OpenStack is not yet
Together；If it is the electricity went off by main OpenStack, after re-powering, it is only necessary to which standby OpenStack resource becomes in synchronous power-off time
It is dynamic；If it is main OpenStack data caused by the natural disasters such as earthquake are lost completely, then need to synchronize all standby
OpenStack resource.
When main OpenStack collapse, standby data center becomes main according to the recovery policy that DR-Manager is configured
OpenStack externally provides service.After the main OpenStack of original restores, the master of the synchronous distal end local DR-Manager
OpenStack resource information to local, can choose business it is less when, switch back to former main OpenStack and service be externally provided.
In one alternate embodiment, described to be based on preset Disaster Recovery Strategy, the first disaster tolerance managing device and the second disaster tolerance
Resource change is synchronized to the 2nd OpenStack by managing device, comprising:
Based on preset Disaster Recovery Strategy, the resource change of the first OpenStack is converted into providing by the first disaster tolerance managing device
Source information is sent to the second disaster tolerance managing device；
Second disaster tolerance managing device receives and Transition Resource Information is the action command of establishing resource, is sent to second
OpenStack。
In one alternate embodiment, the preset Disaster Recovery Strategy, including following one:
The resource change of all resources of all tenants is protected in monitoring；
Monitoring protection portion sublease family all resources resource change；
The resource change of the part resource of all tenants is protected in monitoring；
Monitoring protection portion sublease family part resource resource change.
In one alternate embodiment, the disaster recovery strategy, including one or more of:
Start some or all of default tenant resource；
Successively starting resource is carried out according to priority；
Start resource according to the incidence relation of tenant and resource.
Wherein, presetting some or all of tenant resource includes following one:
Start whole resources of whole tenants；
Whole resources of actuating section tenant；
Start the part resource in whole tenants；
The part resource of actuating section tenant
Herein in whole or in part refer to, configured in Disaster Recovery Strategy monitoring resource change on the basis of whole or
Person part.
In the embodiment of the present invention, the first disaster tolerance managing device monitors the resource change of the first OpenStack, based on preset
The resource change is synchronized to described second by Disaster Recovery Strategy, the first disaster tolerance managing device and the second disaster tolerance managing device
OpenStack；When the first OpenStack collapse, the second disaster tolerance managing device is based on disaster recovery strategy and described same
The resource of step switches the 2nd OpenStack for main OpenStack, and the first disaster tolerance managing device is by described first
OpenStack is switched to standby OpenStack.The recovery process complicated compared to manual operation, can be between disaster tolerance two centers
Resource is protected according to tenant's classification, can also flexibly configure various Disaster Recovery Strategies, and manual operation fault bring is avoided
Disaster.
Embodiment two
Above-described embodiment method is specifically described in the present embodiment, provides a kind of based on OpenStack cloud platform
The disaster tolerance management method of tenant's granularity, as shown in Fig. 2, disaster tolerance system overall architecture include in primary data center and standby data
The heart.
One disaster tolerance managing device of each self installation, referred to as DR- in the active and standby Liang Ge data center of OpenStack disaster tolerance
Manager, as shown in Fig. 3, the DR-Manager include: Event Collector, source synchronous device, actuator, disaster recovery
Device carries out the real-time duplication of storage volume between Liang Ge data center by storage remote copy technology.
The configuration work of OpenStack, comprising: it is completed in active and standby data center deployment, and after having configured bottom disaster tolerance,
Each self installation DR-Manager, receive the OpenStack of pipe local, and two DR_Manager are attached, configure as main DR_
Manager, standby DR_Manager.DR-Manager device includes: Event Collector, heartbeat detector, source synchronous device, executes
Device, disaster recovery device.
Data backup when main OpenStack is worked normally, between main OpenStack and standby OpenStack, comprising: when
It is all that the DR-Manager led is monitored when having new movement in main OpenStack, main DR-Manager collects master
Resource information in OpenStack then synchronizes in standby DR-Manager, sends instructions under standby DR-Manager to standby
OpenStack, standby OpenStack just have and identical tenant and resource in main OpenStack.Virtual machine VM and volume grade
Other data, which change, to be realized by the remote copy of storage, host virtual machine and standby virtual machine in active and standby OpenStack
System disk and volume are also real-time synchronization.
Resource after creation determines starting state or closed state according to the scheme of disaster tolerance, if being set as cold
Standby, then resource is in off state, and is starting state if it is hot standby then resource.It can also support dual-active, it is only necessary to upper layer application
Load balancing is accessed, the virtual machine of Liang Ge data center is accessed load balancing, network, which is got through, can be realized.
Start for the first time if it is DR-Manager, initialized, main DR-Manager inquires the master
All resources are converted to resource information and are sent to the standby DR-Manager by all resources of OpenStack；It is described standby
The action command that the resource information is converted into establishing resource is sent to the standby OpenStack and carries out resource by DR-Manager
Creation.
When main OpenStack collapse, standby DR-Manager prison executes under disaster recovery device according to disaster recovery strategy
It says the word to the order of actuator deactivation resource, standby OpenStack becomes main OpenStack, externally provides service, DR-
Manager is oneself being arranged as main DR-Manager.
After former main OpenStack restores, run standby OpenStack oneself is regarded, local DR-Manager is set as standby.
At this point, former standby OpenStack is main OpenStack, former main OpenStack is standby OpenStack.Former main OpenStack can be same
The resource information of the former standby OpenStack of step.When business is not busy at that time, switchback is carried out manually, i.e. original OpenStack becomes
Main, former standby OpenStack continues as standby center.
The concrete configuration of DR-Manager includes:
(1) basis instrument
Local DR-Manager is respectively disposed at the active and standby double centers of the disaster tolerance of OpenStack, and receive pipe local
Then OpenStack is attached mutually by network, be able to carry out communication, main DR-Manager based on oneself being arranged, and
It informs that other side DR-Manager allows it to be set as standby, detects whether other side deposits by beat detector between two DR-Manager
Living, the generation of fissure in order to prevent, the third-party arbitration of configuration one is arranged, and DR-Manager connects other side's simultaneously
OpenStack is detected, and the phenomenon that DR-Manager delay machine and OpenStack are survived is prevented.
(2) Disaster Recovery Strategy is configured on main DR-Manager, comprising:
A. all resources of all tenants are protected；
B. all resources of certain a part of tenant are protected；
C. the part resource of all tenants is protected；
D. protection portion is subleased the part resource at family；
Disaster Recovery Strategy is configured by tenant, relatively more flexible.
(3) main DR-Manager Event Collector carries out the event-monitoring of tenant according to the Disaster Recovery Strategy of configuration, such as creates
Virtual machine etc. is built, all information of the resource object are then collected according to the operation object ID of event, are converted into resource information.
Resource information includes:
A. tenant's information
B. resource ID, specification, the network information
C. metadata, such as: secure group, code key key
D. the ID of the storage volume of bottom is corresponded to
E. the resource of relationship associated therewith, such as: volume
(4) recovery policy:
A. start whole resources of whole tenants；
B. whole resources of actuating section tenant；
C. start the part resource in whole tenants；
D. the part resource of actuating section tenant；
E. successively starting resource is carried out according to priority；
F. according to incidence relation, starting resource is successively carried out；
Based on above-mentioned setting, when main OpenStack is worked normally, the source synchronous at master/slave data center includes: the master
The Event Collector of DR-Manager monitors the main OpenStack and resource change occurs, and the resource change is converted to
Resource information is sent to the source synchronous device of the main DR-Manager；The source synchronous device of the main DR-Manager will be described
Resource information is sent to the source synchronous device of the standby DR-Manager；The source synchronous device of the standby DR-Manager will be described
Resource information is sent to the actuator of the standby DR-Manager；The actuator of the standby DR-Manager is by the resource information
The action command for being converted into establishing resource is sent to the standby OpenStack and carries out asset creation.
Initialization procedure includes: to be when the Event Collector of the main DR-Manager monitors the main OpenStack
All resources of the main OpenStack are converted to resource information and are sent to the main DR-Manager's by initialization procedure
Source synchronous device；The resource information is sent to the standby DR-Manager's by the source synchronous device of the main DR-Manager
Source synchronous device；The resource information is sent to the standby DR-Manager's by the source synchronous device of the standby DR-Manager
Actuator；The action command that the resource information is converted into establishing resource is sent to institute by the actuator of the standby DR-Manager
It states standby OpenStack and carries out asset creation.
Embodiment three
A kind of disaster tolerance managing device is present embodiments provided, description is also applied for the present embodiment in above method embodiment
In, the disaster tolerance managing device is located at the first cloud computing platform OpenStack, and the first OpenStack is main OpenStack
When, for monitoring the resource change of the first OpenStack, cooperate with the disaster tolerance managing device for being located at standby OpenStack by resource
Variation is synchronized to standby OpenStack；And for the first OpenStack being switched to standby in the first OpenStack collapse
OpenStack；
The disaster tolerance managing device is located at the 2nd OpenStack, and when the 2nd OpenStack is standby OpenStack, is used for
It cooperates with the disaster tolerance managing device positioned at main OpenStack and resource change is synchronized to the 2nd OpenStack, and in master
When OpenStack collapses, the 2nd OpenStack is switched as main OpenStack with synchronous resource based on disaster recovery strategy.
Optionally, above-mentioned apparatus is also used to: the disaster tolerance managing device is located at the 2nd OpenStack, and second
When OpenStack is main OpenStack, the resource change of the 2nd OpenStack is monitored, after the first OpenStack restores, with
It cooperates positioned at the disaster tolerance managing device of standby OpenStack and resource change is synchronized to the first OpenStack, by second
OpenStack switches back into standby OpenStack；
The disaster tolerance managing device is located at the first OpenStack, and when the first OpenStack is standby OpenStack, when the
After one OpenStack restores, cooperates with the disaster tolerance managing device positioned at main OpenStack and resource change is synchronized to first
First OpenStack is switched back into main OpenStack by OpenStack；
In one alternate embodiment, disaster tolerance managing device cooperates with the disaster tolerance managing device for being located at standby OpenStack and incites somebody to action
Resource change is synchronized to standby OpenStack, comprising: disaster tolerance managing device is based on preset Disaster Recovery Strategy, and resource change is converted
Standby OpenStack is sent at resource information；
Disaster tolerance managing device cooperates with the disaster tolerance managing device positioned at main OpenStack resource change being synchronized to second
OpenStack, comprising: disaster tolerance managing device is sent to based on the action command that simultaneously Transition Resource Information is establishing resource is received
Standby OpenStack.
The embodiment of the present invention also provides a kind of computer storage medium, and the computer storage medium is stored with computer journey
Sequence；After the computer program is performed, the attack evidence collecting method of previous embodiment offer can be realized, for example, executing such as Fig. 1
In shown method.
The embodiment of the present invention also provides a kind of computer equipment, can be structure as shown in Figure 4, including processor
41, memory 42 and storage on a memory and the computer program that can run on a processor, processor execution institute
Part or Overall Steps in embodiment one or embodiment two can be realized when stating program.
Although disclosed herein embodiment it is as above, the content only for ease of understanding the present invention and use
Embodiment is not intended to limit the invention.Technical staff in any fields of the present invention is taken off not departing from the present invention
Under the premise of the spirit and scope of dew, any modification and variation, but the present invention can be carried out in the form and details of implementation
Scope of patent protection, still should be subject to the scope of the claims as defined in the appended claims.
It will appreciated by the skilled person that whole or certain steps, system, dress in method disclosed hereinabove
Functional module/unit in setting may be implemented as software, firmware, hardware and its combination appropriate.In hardware embodiment,
Division between the functional module/unit referred in the above description not necessarily corresponds to the division of physical assemblies；For example, one
Physical assemblies can have multiple functions or a function or step and can be executed by several physical assemblies cooperations.Certain groups
Part or all components may be implemented as by processor, such as the software that digital signal processor or microprocessor execute, or by
It is embodied as hardware, or is implemented as integrated circuit, such as specific integrated circuit.Such software can be distributed in computer-readable
On medium, computer-readable medium may include computer storage medium (or non-transitory medium) and communication media (or temporarily
Property medium).As known to a person of ordinary skill in the art, term computer storage medium is included in for storing information (such as
Computer readable instructions, data structure, program module or other data) any method or technique in the volatibility implemented and non-
Volatibility, removable and nonremovable medium.Computer storage medium include but is not limited to RAM, ROM, EEPROM, flash memory or its
His memory technology, CD-ROM, digital versatile disc (DVD) or other optical disc storages, magnetic holder, tape, disk storage or other
Magnetic memory apparatus or any other medium that can be used for storing desired information and can be accessed by a computer.This
Outside, known to a person of ordinary skill in the art to be, communication media generally comprises computer readable instructions, data structure, program mould
Other data in the modulated data signal of block or such as carrier wave or other transmission mechanisms etc, and may include any information
Delivery media.
Claims (10)
1. a kind of disaster tolerance management method is applied to comprising the first cloud computing platform OpenStack and the 2nd OpenStack
System, which is characterized in that the first OpenStack is main OpenStack, and the 2nd OpenStack is standby OpenStack,
First OpenStack is equipped with the first disaster tolerance managing device, and the 2nd OpenStack is equipped with the second disaster tolerance management dress
It sets, the described method comprises the following steps:
First disaster tolerance managing device monitors the resource change of the first OpenStack, is based on preset Disaster Recovery Strategy, and described first holds
The resource change is synchronized to the 2nd OpenStack by calamity managing device and the second disaster tolerance managing device；
When the first OpenStack collapse, the second disaster tolerance managing device is based on disaster recovery strategy and the synchronous money
Source switches the 2nd OpenStack for main OpenStack, and the first disaster tolerance managing device is by described first
OpenStack is switched to standby OpenStack.
2. the method according to claim 1, wherein further include, after the first OpenStack restores, described the
The resource information of 2nd OpenStack is synchronized to described first by one disaster tolerance managing device and the second disaster tolerance managing device
First OpenStack is switched back into main OpenStack by OpenStack, the first disaster tolerance managing device, and described second holds
2nd OpenStack is switched back into standby OpenStack by calamity managing device.
3. the method according to claim 1, wherein described be based on preset Disaster Recovery Strategy, first disaster tolerance
The resource change is synchronized to the 2nd OpenStack by managing device and the second disaster tolerance managing device, comprising:
Based on preset Disaster Recovery Strategy, the first disaster tolerance managing device converts the resource change of the first OpenStack
The second disaster tolerance managing device is sent at resource information；
The second disaster tolerance managing device receives and converts the resource information as the action command of establishing resource, is sent to described
2nd OpenStack.
4. method according to claim 1 or 3, which is characterized in that the preset Disaster Recovery Strategy, including following one:
The resource change of all resources of all tenants is protected in monitoring；
Monitoring protection portion sublease family all resources resource change；
The resource change of the part resource of all tenants is protected in monitoring；
Monitoring protection portion sublease family part resource resource change.
5. the method according to claim 1, wherein the disaster recovery strategy, including one or more of:
Start some or all of default tenant resource；
Successively starting resource is carried out according to priority；
Start resource according to the incidence relation of tenant and resource.
6. a kind of disaster tolerance managing device, which is characterized in that
The disaster tolerance managing device is located at the first cloud computing platform OpenStack, and based on the first OpenStack
When OpenStack, for monitoring the resource change of the first OpenStack, assisted with the disaster tolerance managing device for being located at standby OpenStack
Make for the resource change to be synchronized to standby OpenStack；And it is used in the first OpenStack collapse, by described first
OpenStack is switched to standby OpenStack；
The disaster tolerance managing device is located at the 2nd OpenStack, and when the 2nd OpenStack is standby OpenStack, is used for
It cooperates with the disaster tolerance managing device positioned at main OpenStack and the resource change is synchronized to the 2nd OpenStack, and be used for
In main OpenStack collapse, the 2nd OpenStack is switched to the synchronous resource based on disaster recovery strategy
Main OpenStack.
7. device according to claim 6, which is characterized in that it is also used to,
The disaster tolerance managing device is located at the 2nd OpenStack, and when the 2nd OpenStack is main OpenStack, monitoring
The resource change of 2nd OpenStack, after the first OpenStack restores, with the disaster tolerance managing device for being located at standby OpenStack
The resource change is synchronized to the first OpenStack by cooperation, and the 2nd OpenStack is switched back into standby OpenStack；
The disaster tolerance managing device is located at the first OpenStack, and when the first OpenStack is standby OpenStack, when the
After one OpenStack restores, cooperates with the disaster tolerance managing device positioned at main OpenStack and the resource change is synchronized to first
First OpenStack is switched back into main OpenStack by OpenStack.
8. device according to claim 6, which is characterized in that
The disaster tolerance managing device cooperate with the disaster tolerance managing device for being located at standby OpenStack the resource change is synchronized to it is standby
OpenStack, comprising: the disaster tolerance managing device is based on preset Disaster Recovery Strategy, and the resource change is converted into resource letter
Breath is sent to standby OpenStack；
The disaster tolerance managing device cooperates with the disaster tolerance managing device positioned at main OpenStack the resource change being synchronized to the
Two OpenStack, comprising: the disaster tolerance managing device is referred into the movement of establishing resource based on receiving and convert the resource information
It enables, is sent to the standby OpenStack.
9. a kind of computer readable storage medium, is stored thereon with computer program, which is characterized in that the program is held by processor
The step of any one of claim 1-5 the method is realized when row.
10. a kind of computer equipment, can run on a memory and on a processor including memory, processor and storage
Computer program, which is characterized in that realize that any one of claim 1-5 right such as is wanted when the processor executes described program
Seek the step in the method.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810644529.5A CN108932180A (en) | 2018-06-21 | 2018-06-21 | A kind of disaster tolerance management method, device, storage medium and computer equipment matter |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810644529.5A CN108932180A (en) | 2018-06-21 | 2018-06-21 | A kind of disaster tolerance management method, device, storage medium and computer equipment matter |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN108932180A true CN108932180A (en) | 2018-12-04 |
Family
ID=64446136
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810644529.5A Pending CN108932180A (en) | 2018-06-21 | 2018-06-21 | A kind of disaster tolerance management method, device, storage medium and computer equipment matter |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108932180A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112099835A (en) * | 2020-09-07 | 2020-12-18 | 紫光云(南京)数字技术有限公司 | Soft load balancing mirror image dynamic upgrading method and system |
| CN112929221A (en) * | 2021-03-02 | 2021-06-08 | 浪潮云信息技术股份公司 | Method for realizing disaster tolerance of main and standby cloud service products |
| CN113691342A (en) * | 2021-09-13 | 2021-11-23 | 上海云轴信息科技有限公司 | Method and system for time synchronization of virtualization platform |
| CN113821384A (en) * | 2021-08-20 | 2021-12-21 | 济南浪潮数据技术有限公司 | Cross-data-center and same-city disaster recovery method, device and equipment based on cloud platform |
| CN114745557A (en) * | 2022-03-22 | 2022-07-12 | 浙江大华技术股份有限公司 | Disaster recovery operation execution method and device, storage medium and electronic device |
| WO2023093379A1 (en) * | 2021-11-26 | 2023-06-01 | 中兴通讯股份有限公司 | Disaster recovery switching method and system, electronic device, and storage medium |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1851657A (en) * | 2005-07-21 | 2006-10-25 | 上海华为技术有限公司 | Dual-machine back-up realizing method and system |
| CN102629224A (en) * | 2012-04-26 | 2012-08-08 | 广东电子工业研究院有限公司 | Method and device of integrated data disaster recovery based on cloud platform |
| US20140280961A1 (en) * | 2013-03-15 | 2014-09-18 | Frank Martinez | System and method for a cloud computing abstraction with multi-tier deployment policy |
| CN104794012A (en) * | 2014-03-19 | 2015-07-22 | 北京中科同向信息技术有限公司 | Switching technique based on disaster recovery |
| CN104794028A (en) * | 2014-01-16 | 2015-07-22 | 中国移动通信集团浙江有限公司 | Disaster tolerance processing method and device, main data center and backup data center |
| US9582379B2 (en) * | 2014-06-16 | 2017-02-28 | International Business Machines Corporation | Multi-site disaster recovery mechanism for distributed cloud orchestration software |
| CN106506636A (en) * | 2016-11-04 | 2017-03-15 | 武汉噢易云计算股份有限公司 | A kind of cloud platform cluster method and system based on OpenStack |
| CN106502823A (en) * | 2016-09-29 | 2017-03-15 | 北京许继电气有限公司 | data cloud backup method and system |
| CN106776140A (en) * | 2016-12-21 | 2017-05-31 | 博飞信息科技（上海）有限公司 | The standby device and method for recovering all-in-one of super disaster tolerance |
| CN106844180A (en) * | 2017-02-07 | 2017-06-13 | 山东浪潮云服务信息科技有限公司 | A kind of monitoring and controlling forecast method of OpenStack platforms computing resource |
| CN107241430A (en) * | 2017-07-03 | 2017-10-10 | 国家电网公司 | A kind of enterprise-level disaster tolerance system and disaster tolerant control method based on distributed storage |
| CN107256184A (en) * | 2017-06-05 | 2017-10-17 | 郑州云海信息技术有限公司 | A kind of data disaster backup method and device based on storage pool |
| CN107995043A (en) * | 2017-12-15 | 2018-05-04 | 南京南瑞信息通信科技有限公司 | Application disaster recovery and backup systems and calamity based on mixing cloud platform are for collocation method |
-
2018
- 2018-06-21 CN CN201810644529.5A patent/CN108932180A/en active Pending
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1851657A (en) * | 2005-07-21 | 2006-10-25 | 上海华为技术有限公司 | Dual-machine back-up realizing method and system |
| CN102629224A (en) * | 2012-04-26 | 2012-08-08 | 广东电子工业研究院有限公司 | Method and device of integrated data disaster recovery based on cloud platform |
| CN102629224B (en) * | 2012-04-26 | 2014-11-26 | 广东电子工业研究院有限公司 | Method and device of integrated data disaster recovery based on cloud platform |
| US20140280961A1 (en) * | 2013-03-15 | 2014-09-18 | Frank Martinez | System and method for a cloud computing abstraction with multi-tier deployment policy |
| CN104794028A (en) * | 2014-01-16 | 2015-07-22 | 中国移动通信集团浙江有限公司 | Disaster tolerance processing method and device, main data center and backup data center |
| CN104794012A (en) * | 2014-03-19 | 2015-07-22 | 北京中科同向信息技术有限公司 | Switching technique based on disaster recovery |
| US9582379B2 (en) * | 2014-06-16 | 2017-02-28 | International Business Machines Corporation | Multi-site disaster recovery mechanism for distributed cloud orchestration software |
| CN106502823A (en) * | 2016-09-29 | 2017-03-15 | 北京许继电气有限公司 | data cloud backup method and system |
| CN106506636A (en) * | 2016-11-04 | 2017-03-15 | 武汉噢易云计算股份有限公司 | A kind of cloud platform cluster method and system based on OpenStack |
| CN106776140A (en) * | 2016-12-21 | 2017-05-31 | 博飞信息科技（上海）有限公司 | The standby device and method for recovering all-in-one of super disaster tolerance |
| CN106844180A (en) * | 2017-02-07 | 2017-06-13 | 山东浪潮云服务信息科技有限公司 | A kind of monitoring and controlling forecast method of OpenStack platforms computing resource |
| CN107256184A (en) * | 2017-06-05 | 2017-10-17 | 郑州云海信息技术有限公司 | A kind of data disaster backup method and device based on storage pool |
| CN107241430A (en) * | 2017-07-03 | 2017-10-10 | 国家电网公司 | A kind of enterprise-level disaster tolerance system and disaster tolerant control method based on distributed storage |
| CN107995043A (en) * | 2017-12-15 | 2018-05-04 | 南京南瑞信息通信科技有限公司 | Application disaster recovery and backup systems and calamity based on mixing cloud platform are for collocation method |
Non-Patent Citations (2)
| Title |
|---|
| MANISH POKHAREL 等: "Disaster Recovery for System Architecture Using Cloud Computing", 《2010 10TH IEEE/IPSJ INTERNATIONAL SYMPOSIUM ON APPLICATIONS AND THE INTERNET》 * |
| 于洪涛 等: "灾备场景下OpenStack虚机实时迁移网络研究", 《天津科技》 * |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112099835A (en) * | 2020-09-07 | 2020-12-18 | 紫光云(南京)数字技术有限公司 | Soft load balancing mirror image dynamic upgrading method and system |
| CN112099835B (en) * | 2020-09-07 | 2022-10-28 | 紫光云(南京)数字技术有限公司 | Soft load balancing mirror image dynamic upgrading method and system |
| CN112929221A (en) * | 2021-03-02 | 2021-06-08 | 浪潮云信息技术股份公司 | Method for realizing disaster tolerance of main and standby cloud service products |
| CN113821384A (en) * | 2021-08-20 | 2021-12-21 | 济南浪潮数据技术有限公司 | Cross-data-center and same-city disaster recovery method, device and equipment based on cloud platform |
| CN113691342A (en) * | 2021-09-13 | 2021-11-23 | 上海云轴信息科技有限公司 | Method and system for time synchronization of virtualization platform |
| WO2023093379A1 (en) * | 2021-11-26 | 2023-06-01 | 中兴通讯股份有限公司 | Disaster recovery switching method and system, electronic device, and storage medium |
| CN114745557A (en) * | 2022-03-22 | 2022-07-12 | 浙江大华技术股份有限公司 | Disaster recovery operation execution method and device, storage medium and electronic device |
| CN114745557B (en) * | 2022-03-22 | 2024-05-24 | 浙江大华技术股份有限公司 | Disaster recovery operation execution method and device, storage medium and electronic device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108932180A (en) | A kind of disaster tolerance management method, device, storage medium and computer equipment matter | |
| WO2018103318A1 (en) | Distributed transaction handling method and system | |
| US7865680B2 (en) | Remote copy system | |
| CN100489796C (en) | Methods and system for implementing shared disk array management functions | |
| US7594138B2 (en) | System and method of error recovery for backup applications | |
| CN105471622B (en) | A kind of high availability method and system of the control node active-standby switch based on Galera | |
| CN103414712B (en) | A kind of distributed virtual desktop management system and method | |
| CN106850260A (en) | A kind of dispositions method and device of virtual resources management platform | |
| US20040153719A1 (en) | Method for controlling information processing system, information processing system and information processing program | |
| JP2003076592A (en) | Data storage system | |
| US20170255528A1 (en) | Smart data replication recoverer | |
| CN103294701B (en) | A kind of method that distributed file system and data process | |
| WO2014101424A1 (en) | Method and system for synchronizing distributed database | |
| CN105760519A (en) | Cluster file system and file lock allocation method thereof | |
| EP2545467A1 (en) | Data synchronization between a data center environment and a cloud computing environment | |
| CN101441582A (en) | Backup and recovery method of computer data object and system and program product for implementing the same | |
| CN107111530B (en) | A kind of disaster recovery method, system and device | |
| CN108984107A (en) | Improve the availability of storage system | |
| CN104486438B (en) | The disaster recovery method and device of distributed memory system | |
| JP2008186142A (en) | Remote backup method and storage system | |
| EP2869199A2 (en) | Distributed reservation systems and methods | |
| US20090063486A1 (en) | Data replication using a shared resource | |
| CN115794499B (en) | Method and system for dual-activity replication data among distributed block storage clusters | |
| CN110175089A (en) | A kind of dual-active disaster recovery and backup systems with read and write abruption function | |
| US20110167235A1 (en) | Remote copy system and remote copy control method |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20181204 |