CN110704249A - Method, device and system for ensuring application consistency - Google Patents
Method, device and system for ensuring application consistency Download PDFInfo
- Publication number
- CN110704249A CN110704249A CN201910872267.2A CN201910872267A CN110704249A CN 110704249 A CN110704249 A CN 110704249A CN 201910872267 A CN201910872267 A CN 201910872267A CN 110704249 A CN110704249 A CN 110704249A
- Authority
- CN
- China
- Prior art keywords
- node
- application
- data
- snapshot
- information
- 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
- 238000000034 method Methods 0.000 title claims abstract description 72
- 238000011084 recovery Methods 0.000 claims description 32
- 238000004891 communication Methods 0.000 description 26
- 230000006870 function Effects 0.000 description 15
- 238000012545 processing Methods 0.000 description 14
- 238000010586 diagram Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 9
- 230000009286 beneficial effect Effects 0.000 description 6
- 230000003068 static effect Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 210000001503 joint Anatomy 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000000638 solvent extraction Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 239000000725 suspension Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
- G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
- G06F11/2064—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring while ensuring consistency
-
- 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/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/073—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a memory management context, e.g. virtual memory or cache management
-
- 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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
- G06F11/2056—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant by mirroring
- G06F11/2082—Data synchronisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/815—Virtual
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/82—Solving problems relating to consistency
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/84—Using snapshots, i.e. a logical point-in-time copy of the data
Abstract
The embodiment of the invention provides a method, a device and a system for ensuring application consistency, relates to the field of computers, and can realize snapshot on a data volume of a container used by an application and ensure that a data protection service provided for the container achieves the application consistency. The method for ensuring the application consistency comprises the following steps: the first node receives data protection information, wherein the data protection information is used for requesting to protect data of the first application; the first node sends data synchronization information to the second node according to the data protection information, wherein the data synchronization information is used for indicating the second node to store the data of the first application in a data volume of a container used by the first application according to the first corresponding relation; the first node sends snapshot execution information to the second node, wherein the snapshot execution information is used for indicating the second node to execute a snapshot on a data volume of a container used by the first application so as to obtain a first snapshot; or the first node performs a snapshot on the data volume of the container used by the first application to obtain the first snapshot.
Description
Technical Field
The embodiment of the invention relates to the field of computers, in particular to a method, a device and a system for ensuring application consistency.
Background
The advent of virtualization technology has changed modern computing approaches, which can improve the efficiency of computer system resource usage, eliminate dependencies between applications and underlying hardware, and enhance load portability and security. Containers and virtual machines are two mainstream computing virtualization technologies at present, wherein the containers are paid extensive attention by virtue of the advantages of light weight, high mobility, strong hardware density, more efficient life cycle management and the like.
Containers need to be data protected (e.g., backed up, snapshotted, implemented to recover from application failures or disasters, etc.) when in use, and thus a consistency level partitioning of the data protection services provided by the containers is needed. As shown in fig. 1, the existing consistency classes can be divided into at least two categories: crash consistency (Crash consistency) and Application consistency (Application consistency). As can be seen from fig. 1: the crash consistency can only ensure the file consistency of the application using the container, and the cache consistency of the application cannot be ensured; the application consistency can not only ensure the file consistency of the application, but also ensure the cache consistency of the application. For example, if the consistency level of the application a is crash consistency, when the application fails, the data protection service provided by the container can only recover the file of the application, and cannot recover the cache of the application, which may result in the loss of the cache data of the application, and even cause a more serious failure (e.g., the application cannot be started due to inconsistent storage configuration).
Disclosure of Invention
Embodiments of the present invention provide a method, an apparatus, and a system for ensuring application consistency, which can implement a snapshot on a data volume of a container used by an application, and ensure that a data protection service provided for the container achieves application consistency.
In order to achieve the above purpose, the embodiment of the invention adopts the following technical scheme:
in a first aspect, an embodiment of the present invention provides a method for ensuring application consistency. First, a first node receives data protection information for requesting protection of data of a first application, the first application being any one of at least one application using a container; secondly, the first node sends data synchronization information to the second node according to the data protection information, wherein the data synchronization information is used for indicating the second node to store the data of the first application in the data volume of the container used by the first application according to a first corresponding relation, and the first corresponding relation comprises the corresponding relation among the first application, the container used by the first application and the data volume of the container used by the first application; and finally, the first node sends snapshot execution information to the second node, wherein the snapshot execution information is used for indicating the second node to execute snapshot on the data volume of the container used by the first application so as to obtain the first snapshot, or the first node executes snapshot on the data volume of the container used by the first application so as to obtain the first snapshot.
Therefore, the first node can send the data synchronization information to the second node according to the received data protection information, so that the second node stores the data of the first application in the data volume of the container used by the first application according to the first corresponding relationship. The first node or the second node can then perform a snapshot on the data volume of the container used by the first application in that state to obtain the first snapshot. Thus, it is ensured that the obtained first snapshot protects the data that the first application needs to protect. Thus, when the first application fails, the first node or the second node can restore the data of the first application through the snapshot.
In a first possible implementation manner of the first aspect, before the first node receives the data protection information, the method further includes: the first node receives the first corresponding relation sent by the second node. When the container is created, the second node is able to synchronize the first correspondence to the first node.
In a second possible implementation manner of the first aspect, after the first node sends the snapshot execution information to the second node, the method further includes: the first node receives the data recovery information and sends data recovery information for requesting to recover the data of the first application according to the first snapshot to the second node.
In a third possible implementation manner of the first aspect, after the first node performs a snapshot on a data volume of a container used by the first application to obtain the first snapshot, the method further includes: the first node receives data recovery information; and the first node restores the data of the first application through the first snapshot according to the data restoration information.
In a second aspect, an embodiment of the present invention provides a method for ensuring application consistency. Firstly, a second node receives data synchronization information sent by a first node; secondly, the second node stores the data of the first application in a data volume of a container used by the first application through a first corresponding relation according to the data synchronization information, wherein the first corresponding relation comprises the corresponding relation among the first application, the container used by the first application and the data volume of the container used by the first application; subsequently, the second node receives the execution snapshot information sent by the first node; and finally, the second node executes snapshot on the data volume of the container used by the first application according to the snapshot execution information to obtain the first snapshot.
As can be seen, the first node can send the data synchronization information to the second node according to the received data protection information, so that the second node stores the data of the first application in the data volume of the container used by the first application according to the first corresponding relationship, and performs the snapshot on the data volume of the container used by the first application in this state to obtain the first snapshot. Thus, it is ensured that the obtained first snapshot protects the data that the first application needs to protect. Thus, when the first application fails, the second node can restore the data of the first application through the snapshot.
In a first possible implementation manner of the second aspect, before the second node receives the data synchronization information sent by the first node, the method further includes: the second node sends the first correspondence to the first node. When the container is created, the second node is able to synchronize the first correspondence to the first node.
In a second possible implementation manner of the second aspect, after the second node performs snapshot on the data volume of the container used by the first application according to the snapshot execution information to obtain the first snapshot, the method further includes: the second node receives data recovery information sent by the first node; and the second node restores the data of the first application through the first snapshot according to the data restoration information.
In a third aspect, an embodiment of the present invention provides a node, where the node is a first node, and the node includes a receiving module, a sending module, and an executing module. Specifically, the receiving module is configured to receive data protection information, where the data protection information is used to request protection of data of a first application, and the first application is any one of at least one application that uses the container. The sending module is used for sending data synchronization information to the second node according to the data protection information received by the receiving module, wherein the data synchronization information is used for indicating the second node to store the data of the first application in the data volume of the container used by the first application according to a first corresponding relation, and the first corresponding relation comprises the corresponding relation among the first application, the container used by the first application and the data volume of the container used by the first application; and sending snapshot execution information to the second node, wherein the snapshot execution information is used for indicating the second node to execute snapshot on the data volume of the container used by the first application so as to obtain the first snapshot. The execution module is used for executing snapshot on the data volume of the container used by the first application after the sending module sends the data synchronization information to the second node, so as to obtain the first snapshot.
In a first possible implementation manner of the third aspect, the receiving module is further configured to receive the first corresponding relationship sent by the second node before the receiving module receives the data protection information.
In a second possible implementation manner of the third aspect, the receiving module is further configured to receive data recovery information after the sending module sends the execution snapshot information to the second node, where the data recovery information is used to request to recover the data of the first application according to the first snapshot. And the sending module is also used for sending the data recovery information received by the receiving module to the second node.
In a third possible implementation manner of the third aspect, the receiving module is further configured to receive the data recovery information after the executing module performs a snapshot on the data volume of the container used by the first application to obtain the first snapshot. And the execution module is further used for recovering the data of the first application through the first snapshot according to the data recovery information received by the receiving module.
For a detailed description of the third aspect and various implementations of the third aspect of the embodiments of the present invention, reference may be made to the detailed description of the first aspect and various implementations of the first aspect; in addition, for the beneficial effects of the third aspect and various implementation manners thereof, reference may be made to beneficial effect analysis in the first aspect and various implementation manners thereof, and details are not described here.
In a fourth aspect, an embodiment of the present invention provides a node, where the node is a second node, and the node includes a receiving module and an executing module. Specifically, the receiving module is configured to receive data synchronization information sent by the first node. The execution module is used for storing the data of the first application in the data volume of the container used by the first application through a first corresponding relation according to the data synchronization information received by the receiving module, wherein the first corresponding relation comprises the corresponding relation among the first application, the container used by the first application and the data volume of the container used by the first application. The receiving module is further configured to receive execution snapshot information sent by the first node after the executing module stores the data of the first application in the data volume of the container used by the first application through the first corresponding relationship. The execution module is further configured to execute the snapshot on the data volume of the container used by the first application according to the execution snapshot information received by the receiving module, so as to obtain a first snapshot.
In a first possible implementation manner of the fourth aspect, the second node further includes a sending module. Specifically, the sending module is configured to send the first corresponding relationship to the first node before the receiving module receives the data synchronization information sent by the first node.
In a second possible implementation manner of the fourth aspect, the receiving module is further configured to receive the data recovery information sent by the first node after the executing module performs snapshot on the data volume of the container used by the first application to obtain the first snapshot. And the execution module is further used for recovering the data of the first application through the first snapshot according to the data recovery information received by the receiving module.
For a detailed description of the fourth aspect and various implementations of the fourth aspect of the embodiments of the present invention, reference may be made to the detailed description of the second aspect and various implementations of the second aspect; moreover, for the beneficial effects of the fourth aspect and various implementation manners thereof, reference may be made to beneficial effect analysis in the second aspect and various implementation manners thereof, and details are not described here.
In a fifth aspect, an embodiment of the present invention provides a system for guaranteeing application consistency, including a node having any one of the features in the third aspect, and at least one node having any one of the features in the fourth aspect.
In a first possible implementation manner of the fifth aspect, the node having any feature of the third aspect is a first node, and the node having any feature of the fourth aspect is a second node.
For a detailed description of the fifth aspect and various implementations of the embodiments of the present invention, reference may be made to the detailed descriptions of the first aspect, the second aspect and various implementations of the first aspect; in addition, for the beneficial effects of the fifth aspect and various implementation manners thereof, reference may be made to beneficial effect analysis in the first aspect, the second aspect and various implementation manners thereof, and details are not described here.
In the embodiment of the present invention, the names of the first node and the second node do not limit the device or the functional module, and in an actual implementation, the device or the functional module may appear by other names. Insofar as the functions of the respective devices or functional blocks are similar to those of the embodiments of the present invention, they are within the scope of the claims for embodiments of the present invention and their equivalents.
These and other aspects of embodiments of the invention will be more readily apparent from the following description.
Drawings
FIG. 1 is a prior art arrangement for providing a level of consistency;
FIG. 2 is an architecture diagram of a system for ensuring application consistency according to an embodiment of the present invention;
fig. 3 is a first flowchart illustrating a method for ensuring application consistency according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating a second method for ensuring application consistency according to an embodiment of the present invention;
fig. 5 is a third schematic flowchart of a method for ensuring application consistency according to an embodiment of the present invention;
fig. 6 is a fourth schematic flowchart of a method for ensuring application consistency according to an embodiment of the present invention;
fig. 7 is a first schematic structural diagram of a first node according to an embodiment of the present invention;
fig. 8 is a second schematic structural diagram of a first node according to an embodiment of the present invention;
fig. 9 is a third schematic structural diagram of a first node according to an embodiment of the present invention;
fig. 10 is a first schematic structural diagram of a second node according to an embodiment of the present invention;
fig. 11 is a second schematic structural diagram of a second node according to an embodiment of the present invention;
fig. 12 is a third schematic structural diagram of a second node according to an embodiment of the present invention.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular system structures, interfaces, techniques, etc. in order to provide a thorough understanding of the embodiments of the invention. It will be apparent, however, to one skilled in the art that the embodiments of the invention may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the embodiments of the present invention with unnecessary detail.
The terms "system" and "network" are often used interchangeably herein. And the terms "including" and "having" and any variations thereof in the description and claims of embodiments of the invention and the drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
The techniques described in embodiments of the present invention may be applied in the context of a container with a data volume. The container is an interface set between the component and the platform in the application server, and is generally located in the application server, and the application server is responsible for loading and maintaining. Meanwhile, one container can only exist in one application server, and one application server can establish and maintain a plurality of containers.
Embodiments of the present invention provide a method for ensuring application consistency, which can implement a snapshot on a data volume of a container used by an application, and ensure that a data protection service provided for the container achieves application consistency.
FIG. 2 illustrates an architecture diagram of a system for ensuring application consistency. Taking the system for ensuring the application consistency includes two nodes (labeled as a first Node and a second Node in fig. 2) as an example, where the first Node is a management Node and the second Node is a common Node (also referred to as a managed Node).
The first node includes: an Application Programming Interface (API), a system Engine (Engine), a Container plug-in (Container plug-in), an extended Application plug-in (applicationplug-in), and a storage unit.
The API is responsible for providing an interface for receiving data protection information and data recovery information transmitted by an external device. The external device may be a backup device or other device capable of installing backup software.
And the system engine is responsible for executing work of the first node and realizes operation scheduling of executing a snapshot or a data recovery process.
The container plug-in realizes the butt joint of the container engine and the container plug-in, and calls a container engine interface to realize the snapshot execution of the data volume of the container used by the application.
The plug-in of the extended application realizes the butt joint of the plug-in of the extended application and the application, and can drive an input/output (I/O) port of the application to suspend the reading and writing of the application before the snapshot is executed; and after the snapshot is executed, the drive application releases the suspension I/O port and restores the reading and writing of the application.
The storage unit is used for storing the corresponding relation sent by the second node for use in data recovery, wherein the corresponding relation comprises an application, a container used by the application and a data volume of the container used by the application.
The second node includes: an Application (Application), a Container Engine (Container Engine), a Volume plug-in (Volume plug-in), and an execution unit.
An application refers to an application running in a container, such as a relational database management system (MySQL), and unlike an application on a traditional physical machine and a virtual machine, the application is in a container as a running state, or is understood as an application running in one container.
The container engine is responsible for operating the container to realize allocation and isolation of container resources, and takes Docker (an open source application container engine) as an example, that is, Docker Daemon.
Volume plug-ins, which are generally required to be provided when a container is stored, are used for managing storage, such as creating, deleting, mounting, uninstalling, querying and the like of a data volume of the container.
In addition, as shown in fig. 2, the system for ensuring application consistency may further include a storage device (also referred to as a data volume), an API that is generally capable of management and monitoring, and storing data blocks, files, and the like.
It should be noted that the first node and the second node provided in the embodiment of the present invention may be two nodes that exist independently from each other, or may be integrated in the same node, and this is not specifically limited in the embodiment of the present invention.
Fig. 3 is a method for ensuring application consistency according to an embodiment of the present invention, where the method for ensuring application consistency is applicable to a scenario with a container of a data volume, and a second node supports performing a snapshot and recovering the snapshot on the data volume of the container used by a first application.
Referring to fig. 3, the method for guaranteeing application consistency includes steps S101 to S109:
s101, the second node sends the first corresponding relation to the first node.
Since the method for ensuring application consistency provided by the embodiment of the present invention is applied to a scenario of a container with a data volume, before step S101, the method for ensuring application consistency may further include a process of creating a container. When the container is created, the second node may record the correspondence. The corresponding relation comprises the corresponding relation among the application, the container used by the application and the data volume of the container used by the application.
It is understood that, since one application server can establish and maintain a plurality of containers, there may be many groups of correspondences recorded by the second node.
For example, the correspondence relationship of the second node record may exist in the form of table 1.
TABLE 1
S102, the first node receives the first corresponding relation sent by the second node.
Taking the first correspondence in table 1 as an example, when the container 1 is created, the second node can record the first correspondence (for example, including application a-container 1-data volume one) and send the first correspondence to the first node, and accordingly, the first node receives the first correspondence sent by the second node.
S103, the first node receives the data protection information.
The data protection information is used for requesting to protect data of a first application, and the first application is any one of at least one application using the container.
It should be noted that, in order to ensure that the data of the first application can be recovered when the first application fails, the data protection information is used to request protection of the data of the first application, so that the application consistency can be ensured. The data protection information may be sent by an external device, where the external device may be a backup device or other device capable of installing backup software.
And S104, the first node sends data synchronization information to the second node according to the data protection information.
Before step S104 is executed, the first node can drive the application to suspend the I/O port, and suspend reading and writing of the application.
S105, the second node receives the data synchronization information sent by the first node.
S106, the second node stores the data of the first application in the data volume of the container used by the first application through the first corresponding relation according to the data synchronization information.
It is understood that, a data volume of a container used by the first application may originally store a part of data of the first application, and step S106 only needs to store other data of the first application (i.e. data of the first application indicated in step S106) that is not originally stored in the data volume. After the step S106 is completed, all data of the first application may be stored in the data volume of the container used by the first application.
It should be noted that, in the embodiment of the present invention, the data of the first application mentioned in step S106 includes, but is not limited to, various types of data such as a file of the application, a cache of the application, a memory of the application, transactional data of the application, and the like.
S107, after the second node stores the data of the first application in the data volume of the container used by the first application, the first node sends execution snapshot information to the second node.
It should be noted that, since the first node is a management node, the first node can know whether the second node has stored the data of the first application in the data volume of the container used by the first application. Or after the second node has stored the data of the first application in the data volume of the container used by the first application, the second node may send feedback information to the first node to inform the first node that the data of the first application has been stored in the data volume of the container used by the first application.
And S108, the second node receives the execution snapshot information sent by the first node.
And S109, the second node executes snapshot on the data volume of the container used by the first application according to the snapshot execution information to obtain a first snapshot.
Thus, the first snapshot records the data that the first application needs to protect. I.e. when the first application fails, the data of the first application can be restored by the first snapshot.
After step S109 is executed, the first node can drive the application to release the suspended I/O port, and resume reading and writing of the application.
Further, referring to fig. 4 in conjunction with fig. 3, the method for guaranteeing application consistency further includes steps S110 to S112:
s110, the first node receives the data recovery information and sends the data recovery information to the second node.
Wherein, the data recovery information may also be sent by the external device.
And S111, the second node receives the data recovery information sent by the first node.
And S112, the second node restores the data of the first application through the first snapshot according to the data restoration information.
It should be noted that, in step S112, after the second node performs the operation of restoring the data of the first application through the first snapshot, the second node may restart the container.
Fig. 5 is another method for ensuring application consistency according to an embodiment of the present invention, where the method for ensuring application consistency is applicable to a scenario with a container of a data volume, and a second node does not support snapshot execution and snapshot recovery on the data volume of the container used by the first application.
Referring to fig. 5, the method for guaranteeing application consistency includes steps S201 to S207:
s201, the second node sends the first corresponding relation to the first node.
Wherein the first correspondence includes a correspondence between the first application, the container used by the first application, and the data volume of the container used by the first application.
S202, the first node receives the first corresponding relation sent by the second node.
S203, the first node receives the data protection information.
The data protection information is used for requesting to protect data of a first application, and the first application is any one of at least one application using the container.
And S204, the first node sends data synchronization information to the second node according to the data protection information.
S205, the second node receives the data synchronization information sent by the first node.
S206, the second node stores the data of the first application in the data volume of the container used by the first application through the first corresponding relation according to the data synchronization information.
S207, after the second node stores the data of the first application in the data volume of the container used by the first application, the first node performs snapshot on the data volume of the container used by the first application to obtain a first snapshot.
The schemes described in steps S201 to S206 are similar to the schemes described in steps S101 to S106 in the above embodiments, and for brevity, are not described again here.
Unlike the embodiments corresponding to fig. 3 and 4, the second node in the embodiments corresponding to fig. 3 and 4 supports snapshot execution on the data volume of the container used by the first application, whereas the second node in the embodiments corresponding to fig. 5 and 6 described below does not support snapshot execution on the data volume of the container used by the first application. Therefore, the first node can perform the snapshot on the data volume of the container used by the first application instead of the second node in the above embodiment to obtain the first snapshot.
Further, referring to fig. 6 in conjunction with fig. 5, the method for guaranteeing application consistency further includes steps S208-S209:
s208, the first node receives the data recovery information.
S209, the first node restores the data of the first application through the first snapshot according to the data restoration information.
Similar to step S207, since the second node in the embodiment corresponding to fig. 3 and 4 supports the recovery snapshot, the second node in the embodiment corresponding to fig. 5 and 6 described below does not support the recovery snapshot. Therefore, the first node can restore the data of the first application through the first snapshot instead of the second node in the above embodiment.
It should be added that, because the first node is a management node, the first node may manage multiple nodes at the same time, and therefore in the two application scenarios provided in the embodiment of the present invention, the first node supports performing snapshot and recovering snapshot on the data volume of the container used by the first application. When the first node and the second node both support to execute snapshot and restore snapshot on the data volume of the container used by the first application, the second node is selected to execute the operations of executing snapshot and restoring snapshot on the data volume of the container used by the first application, so that the load of the first node can be reduced, and the performance of the system for ensuring the consistency of the application is improved.
The embodiment of the invention provides a method for ensuring application consistency, which comprises the steps of receiving data protection information through a first node, wherein the data protection information is used for requesting to protect data of a first application, and the first application is any one of at least one application using a container; the first node sends data synchronization information to the second node according to the data protection information, wherein the data synchronization information is used for indicating the second node to store the data of the first application in a data volume of a container used by the first application according to a first corresponding relation, and the first corresponding relation comprises the first application, the container used by the first application and the data volume of the container used by the first application; the first node sends execution snapshot information to the second node, wherein the execution snapshot information is used for indicating the second node to execute snapshot on the data volume of the container used by the first application so as to obtain the first snapshot. Based on the description of the above embodiment, since the first node can send the data synchronization information to the second node according to the received data protection information, the second node stores the data of the first application in the data volume of the container used by the first application according to the first corresponding relationship. The first node or the second node can then perform a snapshot on the data volume of the container used by the first application in that state to obtain the first snapshot. Thus, it is ensured that the obtained first snapshot protects the data that the first application needs to protect. Thus, when the first application fails, the first node or the second node can restore the data of the first application through the snapshot.
The embodiment of the invention provides a first node, which is used for executing the steps executed by the first node in the method for ensuring the application consistency. The first node provided by the embodiment of the present invention may include modules corresponding to the respective steps.
In the embodiment of the present invention, the first node may be divided into functional modules according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one functional module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The division of the modules in the embodiment of the present invention is illustrative, and is only a logic function division, and there may be another division manner in actual implementation.
Fig. 7 shows a possible structure diagram of the first node involved in the above embodiment, in the case of dividing each functional module by corresponding functions. As shown in fig. 7, the first node includes a receiving module 10, a transmitting module 11, and an executing module 12. The receiving module 10 is configured to support the first node to perform S102 and S103 in fig. 3 and 4, S110 in fig. 4, S202 and S203 in fig. 5 and 6, and S208 in fig. 6; the sending module 11 is configured to support the first node to perform S104 and S107 in fig. 3 and 4, and S204 in fig. 5 and 6; the executing module 12 is configured to support the first node to execute S207 in fig. 5 and fig. 6, and S209 in fig. 6. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.
In case of integrated units, fig. 8 shows a possible structural schematic of the first node involved in the above embodiments. As shown in fig. 8, the first node includes: a processing module 20 and a communication module 21. Processing module 20 is configured to control and manage the actions of the first node, e.g., processing module 20 is configured to support the first node to perform S207 in fig. 5 and 6, and S209 in fig. 6 and/or other processes for the techniques described herein. The communication module 21 is configured to support the first node to communicate with other nodes, for example, the communication module 21 is configured to support the first node to perform S102-S104, S107 in fig. 3 and 4, S110 in fig. 4, S202-S204 in fig. 5 and 6, and S208 in fig. 6. The first node may also include a storage module 22 for storing program code and data for the first node.
The processing module 20 may be a Processor or a controller, and may be, for example, a Central Processing Unit (CPU) or a Digital Signal Processor (DSP). Which may implement or execute the various illustrative logical blocks, modules, and circuits described in connection with the embodiment disclosure. The communication module 21 may be a transceiver, a transceiving circuit or a communication interface, etc. The storage module 22 may be a memory.
When the processing module 20 is a processor, the communication module 21 is a communication interface, and the storage module 22 is a memory, the first node according to the embodiment of the present invention may be the first node shown in fig. 9.
As shown in fig. 9, the first node includes: a communication interface 30, a processor 31 and a memory 32. The communication interface 30, the processor 31 and the memory 32 are connected by a system bus 33, and perform mutual communication.
When the first node is running, the first node performs the method of guaranteeing application consistency as the embodiments shown in fig. 3-6. For a specific method for ensuring application consistency, reference may be made to the related description in the embodiments shown in fig. 3 to fig. 6, and details are not described herein again.
Wherein the communication interface 30 is used for communicating with other nodes or communication networks, such as a second node or the like.
The memory 32 may be used for storing software programs and application modules, and the processor 31 executes various functional applications and data processing of the first node by running the software programs and application modules stored in the memory 32.
The memory 32 may mainly include a storage program area 320 and a storage data area 321, wherein the storage program area 320 may store an operating system, an application program required for at least one function; the storage data area 321 may store control information, a first correspondence relationship, and the like.
The Memory 32 may be a Read-Only Memory (ROM), or other types of static storage devices that can store static information and instructions, a Random Access Memory (RAM), or other types of dynamic storage devices that can store information and instructions, or an Electrically Erasable Programmable Read-Only Memory (EEPROM), a magnetic disk storage medium, or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by the first node, but is not limited thereto.
The memory 32 may be self-contained and coupled to the processor 31 via a system bus 33. The memory 32 may also be integrated with the processor 31.
The processor 31 is the control center of the first node. The processor 31 connects various parts of the entire first node using various interfaces and lines, performs various functions of the first node and processes data by running or executing software programs and/or application modules stored in the memory 32, and calling data stored in the memory 32, thereby performing overall monitoring of the first node.
In a specific implementation, the processor 31 may include one or more CPUs, for example, the processor 31 in fig. 9 includes a CPU 0 and a CPU 1.
The system bus 33 may be divided into an address bus, a data bus, a control bus, and the like. For clarity of illustration in the embodiments of the present invention, the various buses are illustrated in FIG. 9 as system bus 33.
Embodiments of the present invention provide a second node, where the second node is configured to perform the steps performed by the second node in the above method for ensuring application consistency. The second node provided by the embodiment of the present invention may include modules corresponding to the respective steps.
In the embodiment of the present invention, the second node may be divided into functional modules according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one functional module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The division of the modules in the embodiment of the present invention is illustrative, and is only a logic function division, and there may be another division manner in actual implementation.
In the case of dividing the functional modules by corresponding functions, fig. 10 shows a possible structural diagram of the second node involved in the above embodiment. As shown in fig. 10, the second node includes a receiving module 40, a transmitting module 41, and an executing module 42. The receiving module 40 is configured to support the second node to perform S105 and S108 in fig. 3 and 4, S111 in fig. 4, and S205 in fig. 5 and 6; the sending module 41 is configured to support the second node to execute S201 in fig. 3 and 4, and S201 in fig. 5 and 6; the execution module 42 is configured to support the second node to execute S106 and S109 in fig. 3 and 4, S112 in fig. 4, and S206 in fig. 5 and 6. All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.
In case of integrated units, fig. 11 shows a possible structural schematic of the second node involved in the above embodiments. As shown in fig. 11, the second node includes: a processing module 50 and a communication module 51. Processing module 50 is configured to control and manage the actions of the second node, e.g., processing module 50 is configured to support the second node to perform steps S106 and S109 in fig. 3 and 4, S112 in fig. 4, and S206 in fig. 5 and 6, and/or other processes for the techniques described herein. The communication module 51 is used to support the second node to communicate with other nodes, for example, the communication module 51 is used to support the second node to execute S105, S106, S108 and S109 in fig. 3 and 4, S111 and S112 in fig. 4, and S205 and S206 in fig. 5 and 6. The second node may also include a storage module 22 for storing program code and data for the second node.
The processing module 50 may be a processor or a controller, and may be a CPU, a DSP, for example. Which may implement or execute the various illustrative logical blocks, modules, and circuits described in connection with the embodiment disclosure. The communication module 51 may be a transceiver, a transceiving circuit or a communication interface, etc. The storage module 52 may be a memory.
When the processing module 50 is a processor, the communication module 51 is a communication interface, and the storage module 52 is a memory, the second node according to the embodiment of the present invention may be the second node shown in fig. 12.
As shown in fig. 12, the second node includes: a communication interface 60, a processor 61 and a memory 62. The communication interface 60, the processor 61 and the memory 62 are connected by a system bus 63, and perform mutual communication.
When the second node is running, it performs the method of guaranteeing application consistency as the embodiments shown in fig. 3-6. For a specific method for ensuring application consistency, reference may be made to the related description in the embodiments shown in fig. 3 to fig. 6, and details are not described herein again.
Wherein the communication interface 60 is used for communicating with other nodes or a communication network, such as a first node or the like.
The memory 62 may be used for storing software programs and application modules, and the processor 61 executes various functional applications and data processing of the second node by running the software programs and application modules stored in the memory 62.
The memory 62 may mainly include a storage program area 620 and a storage data area 621, wherein the storage program area 620 may store an operating system, an application program required for at least one function; the storage data area 621 may store control information and the like.
The memory 62 may be, but is not limited to, ROM or other type of static storage device that can store static information and instructions, RAM or other type of dynamic storage device that can store information and instructions, EEPROM, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by the second node.
The memory 62 may be self-contained and coupled to the processor 61 via a system bus 63. The memory 62 may also be integrated with the processor 61.
The processor 61 is the control center of the second node. The processor 61 connects various parts of the entire second node using various interfaces and lines, performs various functions of the second node and processes data by running or executing software programs and/or application modules stored in the memory 62, and calling data stored in the memory 62, thereby performing overall monitoring of the second node.
In a specific implementation, as an embodiment, the processor 61 may include one or more CPUs, for example, the processor 61 in fig. 12 includes a CPU 0 and a CPU 1.
The system bus 63 may be divided into an address bus, a data bus, a control bus, and the like. For clarity of illustration in the embodiments of the present invention, the various buses are illustrated in FIG. 12 as system bus 63.
An embodiment of the present invention further provides a system for ensuring application consistency, including: a first node having any of the features of the embodiments described above, and at least one second node having any of the features of the embodiments described above. Embodiments of the present invention also provide a software product including computer instructions for implementing a method for ensuring application consistency. The computer instructions may be stored on a readable storage medium; from which a processor may read and execute computer instructions causing the processor to implement a method of ensuring application consistency.
It will be clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to perform all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present invention may be implemented in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only an embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions within the technical scope of the present invention are intended to be covered by the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (15)
1. A method for ensuring application consistency, comprising:
a first node receives data protection information, wherein the data protection information is used for requesting to protect data of a first application, and the first application is any one of at least one application using a container;
the first node sends data synchronization information to a second node according to the data protection information, wherein the data synchronization information is used for indicating the second node to store the data of the first application in a data volume of a container used by the first application;
the first node sends snapshot execution information to the second node, wherein the snapshot execution information is used for indicating the second node to execute snapshot on the data volume of the container used by the first application so as to obtain a first snapshot; or the first node performs a snapshot on the data volume of the container used by the first application to obtain a first snapshot.
2. The method for guaranteeing application consistency according to claim 1, wherein before the first node receives the data protection information, the method further comprises:
and the first node receives the first corresponding relation sent by the second node.
3. The method for guaranteeing application consistency according to claim 1 or 2, wherein after the first node sends the execution snapshot information to the second node, the method further comprises:
and the first node receives data recovery information and sends the data recovery information to the second node, wherein the data recovery information is used for requesting to recover the data of the first application according to the first snapshot.
4. The method for guaranteeing application consistency according to claim 1 or 2, wherein after the first node performs snapshot on the data volume of the container used by the first application to obtain a first snapshot, the method further comprises:
the first node receives data recovery information;
and the first node restores the data of the first application through the first snapshot according to the data restoration information.
5. A method for ensuring application consistency, comprising:
the second node receives data synchronization information sent by the first node;
the second node stores the data of the first application in a data volume of a container used by the first application according to the data synchronization information;
the second node receives execution snapshot information sent by the first node;
and the second node executes snapshot on the data volume of the container used by the first application according to the snapshot execution information to obtain a first snapshot.
6. The method for guaranteeing application consistency according to claim 5, wherein before the second node receives the data synchronization information sent by the first node, the method further comprises:
the second node sends the first correspondence to the first node.
7. The method according to claim 5 or 6, wherein after the second node performs snapshot on the data volume of the container used by the first application according to the snapshot execution information to obtain a first snapshot, the method further comprises:
the second node receives data recovery information sent by the first node;
and the second node restores the data of the first application through the first snapshot according to the data restoration information.
8. A node is characterized in that the node is a first node and comprises a receiving module, a sending module and an executing module;
the receiving module is configured to receive data protection information, where the data protection information is used to request protection of data of a first application, and the first application is any one of at least one application that uses a container;
the sending module is configured to send data synchronization information to a second node according to the data protection information received by the receiving module, where the data synchronization information is used to instruct the second node to store the data of the first application in a data volume of a container used by the first application; sending snapshot execution information to the second node, wherein the snapshot execution information is used for indicating the second node to execute snapshot on the data volume of the container used by the first application so as to obtain a first snapshot;
and the execution module is used for executing snapshot on the data volume of the container used by the first application after the sending module sends the data synchronization information to the second node so as to obtain a first snapshot.
9. The node of claim 8,
the receiving module is further configured to receive the first corresponding relationship sent by the second node before the receiving module receives the data protection information.
10. The node according to claim 8 or 9,
the receiving module is further configured to receive data recovery information after the sending module sends the snapshot execution information to the second node, where the data recovery information is used to request to recover the data of the first application according to the first snapshot;
the sending module is further configured to send the data recovery information received by the receiving module to the second node.
11. The node according to claim 8 or 9,
the receiving module is further configured to receive data recovery information after the executing module executes a snapshot on the data volume of the container used by the first application to obtain a first snapshot;
the execution module is further configured to restore the data of the first application through the first snapshot according to the data restoration information received by the receiving module.
12. A node, wherein the node is a second node, and wherein the node comprises a receiving module and an executing module;
the receiving module is used for receiving data synchronization information sent by a first node;
the execution module is configured to store data of a first application in a data volume of a container used by the first application according to the data synchronization information received by the receiving module;
the receiving module is further configured to receive execution snapshot information sent by the first node after the executing module stores the data of the first application in the data volume of the container used by the first application through the first corresponding relationship;
the executing module is further configured to execute a snapshot on the data volume of the container used by the first application according to the snapshot executing information received by the receiving module, so as to obtain a first snapshot.
13. The node of claim 12, wherein the node further comprises a sending module;
the sending module is configured to send the first corresponding relationship to the first node before the receiving module receives the data synchronization information sent by the first node.
14. The node according to claim 12 or 13,
the receiving module is further configured to receive data recovery information sent by the first node after the executing module executes a snapshot on the data volume of the container used by the first application to obtain a first snapshot;
the executing module is further configured to restore the data of the first application through the first snapshot according to the data restoration information received by the receiving module.
15. A system for ensuring application consistency, comprising a node according to any one of claims 8-11, and at least one node according to any one of claims 12-14.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910872267.2A CN110704249A (en) | 2016-12-30 | 2016-12-30 | Method, device and system for ensuring application consistency |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611269985.3A CN106681866B (en) | 2016-12-30 | 2016-12-30 | A kind of method, apparatus and system for guaranteeing to apply consistency |
| CN201910872267.2A CN110704249A (en) | 2016-12-30 | 2016-12-30 | Method, device and system for ensuring application consistency |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611269985.3A Division CN106681866B (en) | 2016-12-30 | 2016-12-30 | A kind of method, apparatus and system for guaranteeing to apply consistency |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110704249A true CN110704249A (en) | 2020-01-17 |
Family
ID=58849697
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910872267.2A Pending CN110704249A (en) | 2016-12-30 | 2016-12-30 | Method, device and system for ensuring application consistency |
| CN201611269985.3A Active CN106681866B (en) | 2016-12-30 | 2016-12-30 | A kind of method, apparatus and system for guaranteeing to apply consistency |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611269985.3A Active CN106681866B (en) | 2016-12-30 | 2016-12-30 | A kind of method, apparatus and system for guaranteeing to apply consistency |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN110704249A (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108052373A (en) * | 2017-12-22 | 2018-05-18 | 福建星网智慧科技股份有限公司 | Method of the container generation with recovering with network is realized based on runC |
| CN108718333A (en) * | 2018-05-09 | 2018-10-30 | 北京顺丰同城科技有限公司 | Synchronous method, device and computer readable storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101218583A (en) * | 2005-04-29 | 2008-07-09 | 网络装置公司 | Storage system architecture for striping data container content across volumes of a cluster |
| CN101351760A (en) * | 2005-12-30 | 2009-01-21 | 科潘系统公司 | Method and system for accessing auxiliary data in power-efficient high-capacity scalable storage |
| CN102591744A (en) * | 2010-12-17 | 2012-07-18 | 微软公司 | Backup and restore of data from any cluster node |
| CN105302862A (en) * | 2009-10-07 | 2016-02-03 | 亚马逊技术股份有限公司 | Self-service configuration for data environment |
| CN105389230A (en) * | 2015-10-21 | 2016-03-09 | 上海爱数信息技术股份有限公司 | Continuous data protection system and method combining with snapshot technology |
| CN105786642A (en) * | 2014-12-22 | 2016-07-20 | 华为技术有限公司 | Production site, disaster backup site, and remote disaster recovery method based on snapshot |
| CN105843704A (en) * | 2016-03-15 | 2016-08-10 | 上海爱数信息技术股份有限公司 | Data protection method and system capable of combining with snapshot function based on distributed block storage |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8516210B2 (en) * | 2011-12-21 | 2013-08-20 | Microsoft Corporation | Application consistent snapshots of a shared volume |
| US9569310B2 (en) * | 2013-02-27 | 2017-02-14 | Netapp, Inc. | System and method for a scalable crash-consistent snapshot operation |
| US9430333B2 (en) * | 2013-03-14 | 2016-08-30 | Microsoft Technology Licensing, Llc | Recovery of application from snapshot |
| US20160139996A1 (en) * | 2014-11-13 | 2016-05-19 | Netapp, Inc. | Methods for providing unified storage for backup and disaster recovery and devices thereof |
| CN105511943B (en) * | 2015-12-03 | 2019-04-12 | 华为技术有限公司 | A kind of Docker container operation method and device |
-
2016
- 2016-12-30 CN CN201910872267.2A patent/CN110704249A/en active Pending
- 2016-12-30 CN CN201611269985.3A patent/CN106681866B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101218583A (en) * | 2005-04-29 | 2008-07-09 | 网络装置公司 | Storage system architecture for striping data container content across volumes of a cluster |
| CN101351760A (en) * | 2005-12-30 | 2009-01-21 | 科潘系统公司 | Method and system for accessing auxiliary data in power-efficient high-capacity scalable storage |
| CN105302862A (en) * | 2009-10-07 | 2016-02-03 | 亚马逊技术股份有限公司 | Self-service configuration for data environment |
| CN102591744A (en) * | 2010-12-17 | 2012-07-18 | 微软公司 | Backup and restore of data from any cluster node |
| CN105786642A (en) * | 2014-12-22 | 2016-07-20 | 华为技术有限公司 | Production site, disaster backup site, and remote disaster recovery method based on snapshot |
| CN105389230A (en) * | 2015-10-21 | 2016-03-09 | 上海爱数信息技术股份有限公司 | Continuous data protection system and method combining with snapshot technology |
| CN105843704A (en) * | 2016-03-15 | 2016-08-10 | 上海爱数信息技术股份有限公司 | Data protection method and system capable of combining with snapshot function based on distributed block storage |
Non-Patent Citations (1)
| Title |
|---|
| 张雅彬等: "基于虚拟化技术的云仿真资源迁移技术研究", 《系统仿真学报》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106681866B (en) | 2019-10-18 |
| CN106681866A (en) | 2017-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9823877B2 (en) | Virtual machine backup from storage snapshot | |
| US10776215B2 (en) | Snapshot generating method, system, and apparatus | |
| CN111338854B (en) | Kubernetes cluster-based method and system for quickly recovering data | |
| US9507672B2 (en) | Method, apparatus, and system for generating and recovering memory snapshot of virtual machine | |
| CN102594849B (en) | Data backup and recovery method and device, virtual machine snapshot deleting and rollback method and device | |
| CN108469986B (en) | Data migration method and device | |
| US9678680B1 (en) | Forming a protection domain in a storage architecture | |
| CN109710317B (en) | System starting method and device, electronic equipment and storage medium | |
| CN108733311B (en) | Method and apparatus for managing storage system | |
| CN107423301B (en) | Data processing method, related equipment and storage system | |
| CN110704161B (en) | Virtual machine creation method and device and computer equipment | |
| US20190108243A1 (en) | Highly available cluster agent for backup and restore operations | |
| WO2017045491A1 (en) | Method and system for upgrading sqlite3 embedded database | |
| CN108073352B (en) | Virtual disk processing method and device | |
| US20190114076A1 (en) | Method and Apparatus for Storing Data in Distributed Block Storage System, and Computer Readable Storage Medium | |
| CN111881476A (en) | Object storage control method and device, computer equipment and storage medium | |
| CN110780889A (en) | Cloud mobile phone data cloning method and cloud mobile phone data restoring method | |
| CN104517067A (en) | Method, device and system for data access | |
| CN110704249A (en) | Method, device and system for ensuring application consistency | |
| CN103019847A (en) | Method and system for migrating data of virtual machine | |
| US9965357B1 (en) | Virtual backup and restore of virtual machines | |
| US9971532B2 (en) | GUID partition table based hidden data store system | |
| CN111026452B (en) | Method and system for remote 32-bit process injection of 64-bit process | |
| CN105516274A (en) | Method and system for realizing SAN (Storage Network Area)-generic-provider based on cloud platform | |
| CN111208947A (en) | Data migration method and device, physical machine, cloud platform and computer storage medium |
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: 20200117 |