CN113849340B - Disaster recovery backup docking method and device for virtualization platform and multi-storage system - Google Patents
Disaster recovery backup docking method and device for virtualization platform and multi-storage system Download PDFInfo
- Publication number
- CN113849340B CN113849340B CN202110933974.5A CN202110933974A CN113849340B CN 113849340 B CN113849340 B CN 113849340B CN 202110933974 A CN202110933974 A CN 202110933974A CN 113849340 B CN113849340 B CN 113849340B
- Authority
- CN
- China
- Prior art keywords
- storage system
- command
- disaster recovery
- flow
- data
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 70
- 238000011084 recovery Methods 0.000 title claims abstract description 52
- 238000003032 molecular docking Methods 0.000 title claims abstract description 18
- 230000008569 process Effects 0.000 claims abstract description 37
- 210000001503 joint Anatomy 0.000 claims abstract description 5
- 238000012545 processing Methods 0.000 claims description 11
- 238000005206 flow analysis Methods 0.000 claims description 8
- 238000004806 packaging method and process Methods 0.000 claims description 7
- 239000003999 initiator Substances 0.000 claims description 4
- 238000004140 cleaning Methods 0.000 claims description 3
- 238000012360 testing method Methods 0.000 claims description 3
- 238000004891 communication Methods 0.000 description 9
- 230000000694 effects Effects 0.000 description 4
- 239000007858 starting material Substances 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
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/1448—Management of the data involved in backup or backup restore
-
- 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
- G06F11/1484—Generic software techniques for error detection or fault masking by means of middleware or OS functionality involving virtual machines
Abstract
The invention provides a disaster recovery backup butt joint method and device for a virtualized platform and a multi-storage system, wherein the butt joint method comprises the steps of receiving a data packet containing a disaster recovery backup flow issued by the virtualized platform and obtaining formatted data in the data packet; analyzing the formatted data to obtain a flow command and command parameters; based on the flow command and command parameters, an implementation interface of the storage system is called, and a disaster recovery backup flow is executed. The invention analyzes the formatted data issued by the virtual platform to obtain the flow command and command parameters, and calls the realization interface of the storage system based on the flow command to realize the execution of the disaster recovery backup strategy set by the virtual platform by the storage system. And docking the disaster recovery backup scheme of the virtualization manufacturer with a storage system of the storage manufacturer to provide disaster recovery backup service for clients. Meanwhile, in the implementation process of the invention, the difference of the bottom storage is shielded, and different storage systems can be adapted to the same virtualization solution.
Description
Technical Field
The invention relates to the technical field of disaster recovery backup of data, in particular to a disaster recovery backup butt joint method and device of a virtualization platform and a multi-storage system.
Background
To improve the data's resistance to catastrophic events, virtualization vendors typically provide independent disaster-tolerant backup schemes to ensure continuity of customer business data.
Disaster recovery backup schemes provided by virtualization vendors are generally compatible with their virtualization solutions. Because customer service data may be stored in storage systems of different storage vendors, solutions provided by the different storage systems to the storage vendors cannot be applied compatibly, resulting in failure of data backup and thus loss of customer data.
Disclosure of Invention
The invention provides a disaster recovery backup butt joint method and device for a virtualization platform and a multi-storage system, which are used for solving the problem that the solutions provided by different storage systems for storage manufacturers cannot be applied in a compatible manner, so that data backup fails.
In order to achieve the above purpose, the present invention adopts the following technical scheme:
the first aspect of the present invention provides a disaster recovery backup docking method for a virtualized platform and a multi-storage system, the docking method comprising the steps of:
receiving a data packet which is issued by a virtualization platform and contains a disaster recovery backup process, and acquiring formatted data in the data packet;
analyzing the formatted data to obtain a flow command and command parameters;
and calling an implementation interface of a storage system based on the flow command and the command parameter, and executing the disaster recovery backup flow.
Further, the disaster recovery backup process includes a data synchronization process, a test process, a data cleaning process and a re-protection process.
Further, the formatted data includes xml formatted data and json formatted data.
Further, the specific process of analyzing the xml format data is as follows:
identifying an xml tag in the formatted data, the xml tag comprising a initiator and a terminator, parsing a flow command through the initiator and/or terminator;
and packaging the parameters in the xml label and the corresponding parameter values into key value pairs, traversing the formatted data, and obtaining key value pairs corresponding to a plurality of command parameters.
Further, the specific process of parsing json format data is as follows:
analyzing the value type and judging whether the value type corresponds to a flow command or a parameter list;
if the parameter list is the parameter list, traversing the parameter list to obtain a plurality of command parameters and corresponding parameter values.
Further, after the process command is obtained, before the implementation interface of the storage system is called, the method further comprises the steps of:
judging whether the current flow command meets the realization or not based on a support function list provided in advance by a current storage system;
if the flow command is in the support function list, the realization is satisfied, and an realization interface of a storage system is called;
if the flow command is not in the support function list, the realization is not satisfied, and error information is returned to the virtual platform.
Further, after executing the disaster recovery backup procedure, the method further includes the steps of:
and packaging the execution result and sending the execution result to the virtual platform.
The second aspect of the present invention provides a disaster recovery backup docking apparatus for a virtualized platform and a multi-storage system, the docking apparatus comprising:
the data forwarding module is used for receiving a data packet which is issued by the virtualization platform and contains a disaster recovery backup process and acquiring formatted data in the data packet;
the flow analysis module is used for analyzing the formatted data and acquiring a flow command and command parameters;
and the service execution module calls an implementation interface of the storage system based on the flow command and the command parameter to execute the disaster recovery backup flow.
Further, the flow parsing module includes:
a command parsing unit parsing a flow command and a command parameter based on a data format of the structured data;
and the flow distribution unit distributes the flow command to an implementation interface of the storage system based on the flow command and a support function list provided by the storage system in advance.
Further, the flow analysis module further comprises an execution result processing unit, and the execution result processing unit is used for packaging the execution result of the storage system and sending the execution result to the virtual platform.
The disaster recovery backup docking device according to the second aspect of the present invention can implement the methods in the first aspect and the implementations of the first aspect, and achieve the same effects.
The effects provided in the summary of the invention are merely effects of embodiments, not all effects of the invention, and one of the above technical solutions has the following advantages or beneficial effects:
the invention analyzes the formatted data issued by the virtual platform to obtain the flow command and command parameters, and calls the realization interface of the storage system based on the flow command to realize the execution of the disaster recovery backup strategy set by the virtual platform by the storage system. And docking the disaster recovery backup scheme of the virtualization manufacturer with a storage system of the storage manufacturer to provide disaster recovery backup service for clients. Meanwhile, in the implementation process of the invention, the difference of the bottom storage is shielded, and different storage systems can be adapted to the same virtualization solution.
The invention realizes the analysis of data with different formats, improves the application scene of the device and realizes the adaptation to various storage systems.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required to be used in the description of the embodiments or the prior art will be briefly described below, and it will be obvious to those skilled in the art that other drawings can be obtained from these drawings without inventive effort.
FIG. 1 is a schematic flow chart of an embodiment of the method of the present invention;
FIG. 2 is a schematic view of an embodiment of the apparatus of the present invention;
fig. 3 is a schematic diagram of the topology of the device according to the present invention.
Detailed Description
In order to clearly illustrate the technical features of the present solution, the present invention will be described in detail below with reference to the following detailed description and the accompanying drawings. The following disclosure provides many different embodiments, or examples, for implementing different structures of the invention. In order to simplify the present disclosure, components and arrangements of specific examples are described below. Furthermore, the present invention may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed. It should be noted that the components illustrated in the figures are not necessarily drawn to scale. Descriptions of well-known components and processing techniques and processes are omitted so as to not unnecessarily obscure the present invention.
As shown in FIG. 1, the disaster recovery backup docking method of the virtualization platform and the multi-storage system comprises the following steps:
s1, receiving a data packet which is issued by a virtualization platform and contains a disaster recovery backup process, and acquiring formatted data in the data packet;
s2, analyzing the formatted data to obtain a flow command and command parameters;
s3, calling an implementation interface of a storage system based on the flow command and the command parameter, and executing the disaster recovery backup flow.
In step S1, the disaster recovery backup process includes a plurality of processes related to disaster recovery backup, such as a data synchronization process, a test process, a data cleaning process, and a re-protection process.
The data packet contains the flow name and the parameters used by the current flow.
The formatted data includes xml formatted data and json formatted data. An xml format is exemplified as follows:
one tag per action, such as < procedure >, < procedure name >, </procedure name >, etc. The labels include a starter and a terminator, such as < flow name >, < parameter > is the starter, and < flow name >, < parameter > is the terminator, and the content between the starter and the terminator represents the label value.
Step S1 establishes a bridge for interfacing the disaster recovery backup solution of the virtualization manufacturer with the storage system, realizes the identification and forwarding of the formatted data, and does not perform any data processing. If the non-formatted data is identified, an error is reported to the virtual platform. The forwarding process stores the formatted data in a temporary file called by a flow through https network transmission and the like, and then issues the temporary file.
In step S2, the formatted data is parsed to obtain the flow command and the command parameters.
The specific process for analyzing the xml format data is as follows: identifying an xml label in the formatted data, and analyzing a flow command through a start character and/or a stop character; and packaging the parameters in the xml label and the corresponding parameter values into key value pairs, traversing the formatted data, and obtaining key value pairs corresponding to a plurality of command parameters.
The specific process of analyzing json format data is as follows: analyzing the value type and judging whether the value type corresponds to a flow command or a parameter list; if the parameter list is the parameter list, traversing the parameter list to obtain a plurality of command parameters and corresponding parameter values, and if the parameter list is the flow command, directly obtaining the flow command.
In one embodiment of the present invention, after the process command is obtained, before the implementation interface of the storage system is invoked, the method further includes the steps of:
judging whether the current flow command meets the realization or not based on a support function list provided in advance by a current storage system; if the flow command is in the support function list, the realization is satisfied, and an realization interface of a storage system is called; if the flow command is not in the support function list, the realization is not satisfied, and error information is returned to the virtual platform.
In one embodiment of the present invention, after executing the disaster recovery backup procedure, the method further includes the steps of: and packaging the execution result and sending the execution result to the virtual platform. The package content includes execution results, failure reasons, repair methods, and the like. Taking xml format as an example, examples are as follows:
in step S3, the executing of the disaster recovery backup procedure includes: establishing communication with a storage system; and executing corresponding storage operation to meet the specific disaster recovery backup flow.
The communication with the storage is established as a general operation, so that the function can be realized by a single communication class in technical implementation, and other flow execution classes inherit the class through an inherited method to acquire the function of communication with the storage. The separate communication class is a flow execution class, and is mainly used for establishing connection with the storage system and processing operations related to connection. Other flow execution classes, such as data synchronization, snapshot establishment, etc., all of which are connected with the storage system before the business operation, and the connection establishment is realized in the communication class. Therefore, the other flow execution class refers to another flow execution class than the processing communication flow.
After establishing communication with the storage system, the stored implementation interface is called to realize a specific business process.
As shown in fig. 2, the disaster recovery backup docking apparatus for a virtualization platform and a multi-storage system includes a data forwarding module 1, a flow analysis module 2, and a service execution module 3.
The data forwarding module 1 is used for receiving a data packet which is issued by the virtualization platform and contains a disaster recovery backup process, and obtaining formatted data in the data packet; the flow analysis module 2 is used for analyzing the formatted data and obtaining a flow command and command parameters; and the service execution module 3 calls an implementation interface of the storage system based on the flow command and the command parameter to execute the disaster recovery backup flow.
The data forwarding module 1 identifies and forwards the formatted data issued by the virtual platform, and does not perform data processing. And establishing a bridge for interfacing the disaster recovery backup solution of the virtualization manufacturer with the storage system.
The flow analysis module 2 includes a command analysis unit 21, a flow distribution unit 22, and an execution result processing unit 23.
The command parsing unit 21 parses the flow commands and command parameters based on the data format of the structured data.
The flow distribution unit 22 distributes the flow command to the implementation interface of the storage system based on the flow command and the support function list provided in advance by the storage system.
The execution result processing unit 23 is configured to encapsulate an execution result of the storage system and send the execution result to the virtual platform.
The service execution module 3 establishes communication with the storage and executes corresponding storage operation to meet the specific disaster recovery backup service flow.
As shown in fig. 3, the docking device in the embodiment of the present invention is deployed in the disaster recovery backup system of the virtual platform, and may dock multiple storage systems at the same time.
While the foregoing description of the embodiments of the present invention has been presented in conjunction with the drawings, it should be understood that it is not intended to limit the scope of the invention, but rather, it is intended to cover all modifications or variations within the scope of the invention as defined by the claims of the present invention.
Claims (7)
1. The disaster recovery backup butt joint method of the virtualization platform and the multi-storage system is characterized by comprising the following steps of:
receiving a data packet which is issued by a virtualization platform and contains a disaster recovery backup process, and acquiring formatted data in the data packet;
analyzing the formatted data to obtain a flow command and command parameters;
calling an implementation interface of a storage system based on the flow command and the command parameter, and executing the disaster recovery backup flow;
the formatted data comprises xml format data and json format data;
after the process command is acquired, before the implementation interface of the storage system is called, the method further comprises the steps of:
judging whether the current flow command meets the realization or not based on a support function list provided in advance by a current storage system;
if the flow command is in the support function list, the realization is satisfied, and an realization interface of a storage system is called;
if the flow command is not in the support function list, the realization is not satisfied, and error information is returned to the virtualization platform.
2. The method for disaster recovery backup docking of a virtualized platform and a multi-storage system according to claim 1, wherein the disaster recovery backup process comprises a data synchronization process, a test process, a data cleaning process and a re-protection process.
3. The disaster recovery backup docking method of a virtualization platform and a multi-storage system according to claim 1, wherein the specific process of analyzing xml format data is as follows:
identifying an xml tag in the formatted data, the xml tag comprising a initiator and a terminator, parsing a flow command through the initiator and/or terminator;
and packaging the parameters in the xml label and the corresponding parameter values into key value pairs, traversing the formatted data, and obtaining key value pairs corresponding to a plurality of command parameters.
4. The disaster recovery backup docking method of a virtualization platform and a multi-storage system according to claim 1, wherein the specific process of parsing json format data is as follows:
analyzing the value type and judging whether the value type corresponds to a flow command or a parameter list;
if the parameter list is the parameter list, traversing the parameter list to obtain a plurality of command parameters and corresponding parameter values.
5. The method for disaster recovery backup docking of a virtualized platform and a multi-storage system according to claim 1, wherein after executing the disaster recovery backup procedure, the method further comprises the steps of:
and packaging the execution result and sending the execution result to the virtualization platform.
6. The disaster recovery backup docking device for the virtualization platform and the multi-storage system is characterized by comprising:
the data forwarding module is used for receiving a data packet which is issued by the virtualization platform and contains a disaster recovery backup process and acquiring formatted data in the data packet; the formatted data comprises xml format data and json format data;
the flow analysis module is used for analyzing the formatted data and acquiring a flow command and command parameters;
the service execution module calls an implementation interface of a storage system based on the flow command and the command parameter to execute the disaster recovery backup flow;
the flow analysis module comprises:
a command parsing unit parsing a flow command and a command parameter based on a data format of the structured data;
the flow distribution unit distributes the flow command to an implementation interface of the storage system based on the flow command and a support function list provided by the storage system in advance;
after the process command is acquired, before the implementation interface of the storage system is called, the method further comprises the following steps:
judging whether the current flow command meets the realization or not based on a support function list provided in advance by a current storage system;
if the flow command is in the support function list, the realization is satisfied, and an realization interface of a storage system is called;
if the flow command is not in the support function list, the realization is not satisfied, and error information is returned to the virtualization platform.
7. The disaster recovery backup docking apparatus for a virtualized platform and a multi-storage system according to claim 6, wherein the flow analysis module further comprises an execution result processing unit, and the execution result processing unit is configured to package an execution result of the storage system and send the execution result to the virtualized platform.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110933974.5A CN113849340B (en) | 2021-08-13 | 2021-08-13 | Disaster recovery backup docking method and device for virtualization platform and multi-storage system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110933974.5A CN113849340B (en) | 2021-08-13 | 2021-08-13 | Disaster recovery backup docking method and device for virtualization platform and multi-storage system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113849340A CN113849340A (en) | 2021-12-28 |
| CN113849340B true CN113849340B (en) | 2024-02-27 |
Family
ID=78975412
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110933974.5A Active CN113849340B (en) | 2021-08-13 | 2021-08-13 | Disaster recovery backup docking method and device for virtualization platform and multi-storage system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113849340B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105022678A (en) * | 2015-07-02 | 2015-11-04 | 深圳市深信服电子科技有限公司 | Data backup method and apparatus for virtual machine |
| CN109842526A (en) * | 2019-03-12 | 2019-06-04 | 中国联合网络通信集团有限公司 | A kind of disaster recovery method and device |
| CN110187998A (en) * | 2019-05-09 | 2019-08-30 | 上海爱数信息技术股份有限公司 | The application disaster tolerance system and method stored based on virtual platform and ceph |
| CN110972497A (en) * | 2018-11-02 | 2020-04-07 | 深信服科技股份有限公司 | Disaster recovery method and device for virtualization platform |
| CN111367722A (en) * | 2020-03-06 | 2020-07-03 | 苏州浪潮智能科技有限公司 | Virtual machine backup method, device, equipment and readable storage medium |
-
2021
- 2021-08-13 CN CN202110933974.5A patent/CN113849340B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105022678A (en) * | 2015-07-02 | 2015-11-04 | 深圳市深信服电子科技有限公司 | Data backup method and apparatus for virtual machine |
| CN110972497A (en) * | 2018-11-02 | 2020-04-07 | 深信服科技股份有限公司 | Disaster recovery method and device for virtualization platform |
| CN109842526A (en) * | 2019-03-12 | 2019-06-04 | 中国联合网络通信集团有限公司 | A kind of disaster recovery method and device |
| CN110187998A (en) * | 2019-05-09 | 2019-08-30 | 上海爱数信息技术股份有限公司 | The application disaster tolerance system and method stored based on virtual platform and ceph |
| CN111367722A (en) * | 2020-03-06 | 2020-07-03 | 苏州浪潮智能科技有限公司 | Virtual machine backup method, device, equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113849340A (en) | 2021-12-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2019085079A1 (en) | Interface test method and apparatus, computer device and storage medium | |
| US8275586B2 (en) | Enabling end-to-end testing of applications across networks | |
| CN113259430A (en) | Message calling method and device, electronic equipment and storage medium | |
| EP2608585A1 (en) | Method, device and system for triggering terminal operation | |
| CN111767226B (en) | Cloud computing platform resource testing method, system and equipment | |
| KR20130077846A (en) | Exception handling test device and method thereof | |
| CN112953983A (en) | SFTP transmission method and device | |
| CN110138753B (en) | Distributed message service system, method, apparatus, and computer-readable storage medium | |
| CN113849340B (en) | Disaster recovery backup docking method and device for virtualization platform and multi-storage system | |
| CN109787789B (en) | Compatibility management method, device and equipment for software upgrading and storage medium | |
| CN107124326B (en) | Automatic testing method and system | |
| US8725901B2 (en) | Analysis tool for intra-node application messaging | |
| CN112099814B (en) | System and method for managing vehicle-mounted machine application software installation environment | |
| CN114003470B (en) | User mode process exception handling method, device, equipment and medium | |
| CN113031569B (en) | Monitoring method, system, terminal and medium of nuclear fusion control system | |
| CN112291254B (en) | Message processing method and device for reliable transaction | |
| CN115373916A (en) | Abnormality detection method, abnormality detection device, electronic apparatus, and computer-readable storage medium | |
| CN113360386A (en) | Switching chip drive test method, device, electronic equipment and storage medium | |
| CN114338347A (en) | Ampere platform-based fault information out-of-band acquisition method and device | |
| CN111314805B (en) | Debugging method and device for intercommunication OMCI (OMCI) messages of GPON (gigabit passive optical network) system | |
| CN112910697A (en) | Fault processing method and device | |
| CN112948195A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN112596750A (en) | Application testing method and device, electronic equipment and computer readable storage medium | |
| CN111198721A (en) | Application program running method and device | |
| CN109639525A (en) | Network interface detection method based on production domesticization operating system |
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 |