CN113220638B - Method and system for establishing database snapshot by using container technology - Google Patents
Method and system for establishing database snapshot by using container technology Download PDFInfo
- Publication number
- CN113220638B CN113220638B CN202110770470.6A CN202110770470A CN113220638B CN 113220638 B CN113220638 B CN 113220638B CN 202110770470 A CN202110770470 A CN 202110770470A CN 113220638 B CN113220638 B CN 113220638B
- Authority
- CN
- China
- Prior art keywords
- database
- container
- mirror image
- snapshot
- creating
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/128—Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computer Security & Cryptography (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method and a system for establishing database snapshots by using a container technology, wherein the method comprises the following steps: manufacturing a database container mirror image, and installing preset database application software and a three-party component in the database container mirror image; creating a container for providing database service to the outside by using the database container mirror image, and storing a preset data file in the container; quitting the database process and keeping all data files in the database consistent; executing a commit save operation on the container, saving the whole container as a new mirror image and saving the mirror image as a snapshot; and according to file import or pulling a corresponding mirror image from a mirror image warehouse, and restarting a new container by using the mirror image to realize recovery of the database snapshot version. Has the advantages that: the invention saves and restores the database snapshot by using the container technology, has the advantages of simple realization, low cost, small data volume and the like, and has obvious advantages in specific application scenes.
Description
Technical Field
The invention relates to the technical field of telecom operator DevOps, in particular to a method and a system for establishing database snapshot by using container technology.
Background
With the continuous Development of the digital transformation of telecommunication operators, the business agility increasingly depends on the quick iteration of the application, and the enterprise is helped to build a continuous delivery pipeline by introducing the concept of DevOps (the combination words of Development and Operations are the general names of a group of processes, methods and systems), so as to realize quick value delivery. The automatic test in the continuous delivery process is a core link, and the quality of version release can be guaranteed only by establishing a set of perfect automatic test. Enterprise applications are often very complex, and many historical applications exist, so that the testability is poor, and test cases often need to rely on relevant test case data. In the process of automatic testing, maintaining the test case data is a complex task, such as cleaning the data after testing, storing and recovering the test case data, and the like. These data are usually stored in a database, and therefore, the version management work of the database is particularly important.
At present, a certain version of a database can be saved by taking a snapshot of the database, and the version can be quickly switched by switching to the snapshot when needed, but many databases do not support the snapshot, and the implementation modes of the databases supporting the snapshot function have many differences, which makes the docking management more complicated. One solution in the industry is to perform a database snapshot by taking a snapshot in the storage layer, but such solutions all require a specific storage device or software, and are relatively expensive to implement and manage.
An effective solution to the problems in the related art has not been proposed yet.
Disclosure of Invention
The present invention provides a method and system for creating a database snapshot using a container technique, so as to overcome the above technical problems in the related art.
Therefore, the invention adopts the following specific technical scheme:
according to one aspect of the present invention, there is provided a method for creating a database snapshot using container technology, the method comprising the steps of:
s1, making a database container mirror image, and installing preset database application software and a three-party component in the database container mirror image;
s2, creating a container for providing database service to the outside by using the database container mirror image, and storing a preset data file in the container;
s3, quitting the database process and keeping the data files in the database consistent;
s4, performing a commit save operation on the container, saving the whole container as a new mirror image and saving the mirror image as a snapshot;
and S5, pulling the corresponding mirror image from the mirror image warehouse according to the file import or the mirror image warehouse, and restarting a new container by using the mirror image to realize the recovery of the database snapshot version.
Further, the step of making a database container mirror image in S1, and installing preset database application software and a three-party component in the database container mirror image includes the following steps:
s101, manufacturing a database container mirror image through a pre-written Dockerfile;
and S102, installing preset database application software and a three-party component in the database container mirror image.
Further, the database container image in S101 may also be downloaded from an official repository and modified.
Further, the creating a container for providing database services to the outside by using the database container image in S2, and storing a preset data file inside the container includes the following steps:
s201, creating a container for providing database service to the outside by using the database container mirror image;
s202, using the container to realize the operation of the database;
s203, storing the database application program and the database file into the container.
Further, the storage drives of the container include devicemopper and Thin provisioning.
Further, the database comprises MySQL, MariaDB, PostgreSQL and FileMaker.
Further, the exiting the database process in S3 and keeping the data files in the database consistent includes the following steps:
and when the snapshot needs to be made, stopping the service of the container and the database, waiting for the exit of the database process, and keeping the consistency of all data files in the database.
Further, the snapshot saving includes saving locally, saving the mirror export as an independent file, or pushing to a mirror repository.
According to another aspect of the present invention, there is provided a system for creating a database snapshot using container technology, the system comprising:
the system comprises a mirror image making module, a database storage module and a mirror image processing module, wherein the mirror image making module is used for making a database storage mirror image and installing preset database application software and a three-party component in the database storage mirror image;
the container creating module is used for creating a container which provides database service to the outside by using the database container mirror image and storing a preset data file in the container;
the database quitting module is used for quitting the database process and keeping all data files in the database consistent;
the container submitting module is used for executing submitting and saving operation on the container, saving the whole container as a new mirror image and saving the mirror image as a snapshot;
and the database recovery module is used for importing or pulling the corresponding mirror image from the mirror image warehouse according to the file, and restarting a new container by using the mirror image to realize the recovery of the database snapshot version.
Further, the steps of manufacturing a database container mirror image, and installing preset database application software and a three-party component in the database container mirror image comprise:
the method comprises the following steps of realizing the manufacture of a database container mirror image through a pre-written Dockerfile;
and installing preset database application software and a three-party component in the database container mirror image.
The invention has the beneficial effects that:
1) the invention provides a method for establishing database snapshot based on a container, which fully utilizes the advantage that the container packs application, data and environment together, can support the snapshot function of various databases, and has the advantages of mature container technology and related ecology and lower learning and use cost for users. The invention can realize the unified management of the test data versions by utilizing the database snapshot technology aiming at various test environments.
2) The snapshot of the invention is realized at the level of container software and does not depend on the support of database software. At present, many databases do not support the snapshot function, and the method of the present invention can be used for realizing the snapshot for the databases with data stored in files. Furthermore, the snapshot capability of the present invention does not need to rely on a special storage device. Many independent storage devices such as disk arrays have snapshot capability, and the snapshot of the database can be realized by using the professional devices, but the invention only uses container technology to realize the same function, so the scheme is simpler and the cost is lower.
3) In the invention, the database software program and the data are snapshots which are made together, and can be recovered together when the snapshots are recovered, so that the consistency of the database version and the data can be maintained. In addition, compared with a mode of taking snapshots by using a virtual machine, the mirror image of the container provides a mechanism of hierarchical storage, so that only the file part of incremental change is generated in each snapshot, meanwhile, the virtual machine contains a large amount of extra storage such as system logs which are not related to database data, and the container only contains database applications, so that the snapshot is smaller.
4) The invention realizes the unified snapshot by using the container technology without different realization of butt joint of various databases, and can more conveniently realize the storage, export, import, rollback and version management work of the unified snapshot. The container technology is used for saving and restoring the database snapshot, the advantages of simple implementation, low cost, small data volume and the like are achieved, and the method has obvious advantages in a specific application scene.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
FIG. 1 is a flow diagram illustrating a method for creating a database snapshot using container technology, in accordance with an embodiment of the present invention;
FIG. 2 is a diagram illustrating a database snapshot implemented by a container in a method for creating a database snapshot using container technology according to an embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating snapshot saving by DeviceMapper and Thin Provision in a method for creating database snapshots by using container technology according to an embodiment of the present invention;
FIG. 4 is a functional block diagram of a system for creating database snapshots using container technology, according to an embodiment of the invention.
Detailed Description
For further explanation of the various embodiments, the drawings which form a part of the disclosure and which are incorporated in and constitute a part of this specification, illustrate embodiments and, together with the description, serve to explain the principles of operation of the embodiments, and to enable others of ordinary skill in the art to understand the various embodiments and advantages of the invention, and, by reference to these figures, reference is made to the accompanying drawings, which are not to scale and wherein like reference numerals generally refer to like elements.
According to the embodiment of the invention, a method and a system for establishing a database snapshot by using a container technology are provided.
Referring now to the drawings and the detailed description, in accordance with an embodiment of the present invention, a method for creating a database snapshot using container technology, as shown in fig. 1-3, includes the following steps:
s1, making a database container mirror image, and installing preset database application software and a three-party component in the database container mirror image;
the step of making a database container mirror image in S1, and installing preset database application software and a three-party component in the database container mirror image includes the following steps:
s101, manufacturing a database container mirror image through a pre-written Dockerfile;
specifically, the database container mirror image in S101 may also be implemented by downloading a corresponding database container mirror image from an official repository and modifying the database container mirror image. Preferably, the database application itself and all data files used by the database operation are placed inside the container, and mapping to the outside in a VOLUME mounting mode and the like is avoided.
And S102, installing preset database application software and a three-party component in the database container mirror image.
S2, creating a container for providing database service to the outside by using the database container mirror image, and storing a preset data file in the container;
wherein, the creating a container for providing database services to the outside by using the database container mirror image in S2, and storing a preset data file inside the container includes the following steps:
s201, creating a container for providing database service to the outside by using the database container mirror image;
specifically, in this embodiment, DeviceMapper and Thin provisioning are used as container storage drivers, so that resource occupation is reduced, access performance is improved, and practicability of the scheme is ensured.
S202, using the container to realize the operation of the database;
specifically, the database comprises MySQL, MariaDB, PostgreSQL and FileMaker.
S203, storing the database application program and the database file into the container.
S3, quitting the database process and keeping the data files in the database consistent;
the exiting of the database process in S3 and the keeping of consistency of each data file in the database include the following steps:
and when the snapshot needs to be made, stopping the service of the container and the database, waiting for the exit of the database process, and keeping the consistency of all data files in the database.
S4, performing a commit save operation on the container, saving the whole container as a new mirror image and saving the mirror image as a snapshot, thereby completing the generation and the saving of the database snapshot;
wherein the snapshot saving comprises local saving, exporting and saving the mirror image as an independent file or pushing the mirror image to a mirror image warehouse.
And S5, pulling the corresponding mirror image from the mirror image warehouse according to the file import or the mirror image warehouse, and restarting a new container by using the mirror image to realize the recovery of the database snapshot version, wherein the new container is the recovered database, thereby finishing the rollback of the database snapshot.
In order to better understand the above technical solution of the present invention, an example of implementing a database snapshot by a container in the present invention is described in detail below.
As shown in fig. 2-3, the container 1 is started by mirroring on the basis of the database, and the changes to the data by various operations of the database are recorded in the data directory/database _ data (note: in the figure, database _ app is the database application directory, database _ data is the database data directory, these two directory names are only examples, and systemd/kswap/bios/rsyslog and so on are name examples of the system application). After executing the save commit command for container 1, the/database _ data and/database _ data directory file will be saved to the new container image: in the database snapshot 1, the database application and the database data are included in the database snapshot 1. Preferably, when the container is executed with the save command, the container must be stopped first, so as to avoid data inconsistency caused by that part of data in the database is not written from the memory to the file in time. Container 2 starts with database snapshot 1, i.e., container 2 restores the snapshot of container 1 at the point in time it was saved. The same container 2 may also be selected to be saved at a certain point in time, forming a database snapshot 2 of the container 2. The stored container mirror images can be transmitted to a mirror image warehouse to realize off-site storage, so that the snapshot can be restored on another machine.
Preferably, the Device mapper and Thin provisioning mechanisms of the Linux kernel are used to store container and mirrored data (note: Device mapper is a mapping framework mechanism from a logical Device to a physical Device provided by the Linux kernel, and Thin provisioning is a storage mechanism provided by the Linux kernel to implement Thin provisioning). Since the data files of the database are very large and database operations tend to write data files randomly, using DeviceMapper and Thin provisioning, the database snapshot can only save incrementally modified file portions (allocated on demand in units of minimum blocks, with a default of 64K per block) without copying the entire data file. The principle of the method is shown in fig. 3, where the gray shaded portion represents the content of the incremental change, and the diagonal portion represents data introduced from the next layer of data in a snapshot manner, this figure is only a schematic diagram, for example, the writing positions of data are actually scattered, and the illustration is not continuous.
In addition, the database of this embodiment adopts the currently mainstream MySQL database, and for further explanation, a specific implementation method of the present invention is described below with MySQL as a specific embodiment:
1) downloading MySQL database container mirror image from an official, setting a/var/lib/MySQL directory as VOLUME by the official mirror image, mounting the directory on a host by default, which is inconsistent with our requirements, modifying the official mirror image by using a docker-copyedt. The new mirror name is assumed to be mysql:5.7. novol.
2) The deployment Docker is installed on the host, and the DeviceMapper mode is used by the storage drive.
3) Executing docker run-d-name db 1-e MYSQL _ ROOT _ PASSWORD =123456 MYSQL:5.7. nomol on the host, starting the container, and starting the database db1, wherein some database operations can be performed on db1, such as adding a library, adding a table, and the like.
4) When creating the snapshot, executing the docker stop db1 in the first step, stopping the container, then executing the docker commit db1 db _ snap _1, and saving the snapshot as the mirror db _ snap _1, at which point the snapshot creation is completed.
5) When the snapshot is restored, the database db2 is started by executing docker run-d-name db 2-e MYSQL _ ROOT _ PASSWORD =123456 db _ snap _1, and the database db2 restores the db _ snap _1 snapshot.
According to another embodiment of the present invention, as shown in fig. 4, there is provided a system for creating a database snapshot using a container technique, the system including:
the system comprises a mirror image making module 1, a database storage module and a mirror image processing module, wherein the mirror image making module is used for making a database storage mirror image and installing preset database application software and a three-party component in the database storage mirror image;
the container creating module 2 is configured to create a container that provides a database service to the outside by using the database container mirror image, and store a preset data file in the container;
the database quitting module 3 is used for quitting the database process and keeping all the data files in the database consistent;
the container submitting module 4 is used for performing submitting and saving operations on the container, saving the whole container as a new mirror image and saving the mirror image as a snapshot;
and the database recovery module 5 is used for pulling the corresponding mirror image from the mirror image warehouse according to the file import or the mirror image warehouse, and restarting a new container by using the mirror image to realize the recovery of the database snapshot version.
In one embodiment, the steps of manufacturing a database container mirror image, and installing preset database application software and a three-party component in the database container mirror image comprise:
the method comprises the following steps of realizing the manufacture of a database container mirror image through a pre-written Dockerfile;
and installing preset database application software and a three-party component in the database container mirror image.
In summary, with the aid of the above technical solutions of the present invention, the present invention provides a method and a system for creating database snapshots based on containers, which fully utilize the advantage that the containers pack applications, data, and environments together, and can support snapshot functions of various databases, and meanwhile, the container technology and related ecology are very mature, and the learning and use costs of users are low. The invention can realize the unified management of the test data versions by utilizing the database snapshot technology aiming at various test environments.
In addition, the snapshot of the invention is realized at the level of container software, and does not depend on the support of database software. At present, many databases do not support the snapshot function, and the method of the present invention can be used for realizing the snapshot for the databases with data stored in files. Furthermore, the snapshot capability of the present invention does not need to rely on a special storage device. Many independent storage devices such as disk arrays have snapshot capability, and the snapshot of the database can be realized by using the professional devices, but the invention only uses container technology to realize the same function, so the scheme is simpler and the cost is lower.
In addition, in the invention, the database software program and the data are snapshots which are made together, and can be recovered together when the snapshots are recovered, so that the consistency of the database version and the data can be maintained. In addition, compared with a mode of taking snapshots by using a virtual machine, the mirror image of the container provides a mechanism of hierarchical storage, so that only the file part of incremental change is generated in each snapshot, meanwhile, the virtual machine contains a large amount of extra storage such as system logs which are not related to database data, and the container only contains database applications, so that the snapshot is smaller.
In addition, the invention realizes the unified snapshot by using the container technology without different realization of butt joint of various databases, and can more conveniently realize the storage, export, import, rollback and version management work of the unified snapshot. The container technology is used for saving and restoring the database snapshot, the advantages of simple implementation, low cost, small data volume and the like are achieved, and the method has obvious advantages in a specific application scene.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (7)
1. A method for creating a database snapshot using container technology, the method comprising the steps of:
s1, making a database container mirror image, and installing preset database application software and a three-party component in the database container mirror image;
s2, creating a container for providing database service to the outside by using the database container mirror image, and storing a preset data file in the container;
s3, quitting the database process and keeping the data files in the database consistent;
s4, performing a commit save operation on the container, saving the whole container as a new mirror image and saving the mirror image as a snapshot;
s5, pulling a corresponding mirror image from the mirror image warehouse according to file import or file pull, and restarting a new container by using the mirror image to realize recovery of the database snapshot version;
the step of making a database container mirror image in S1, and installing preset database application software and a three-party component in the database container mirror image includes the following steps:
s101, manufacturing a database container mirror image through a pre-compiled Dockerfile or downloading and transforming the database container mirror image from an official warehouse;
s102, installing preset database application software and a three-party component in the database container mirror image;
creating a container for providing database services to the outside by using the database container mirror image in S2, and storing a preset data file in the container, including the following steps:
s201, creating a container for providing database service to the outside by using the database container mirror image;
s202, using the container to realize the operation of the database;
s203, storing the database application program and the database file into the container.
2. The method of claim 1, wherein the storage drives of the container comprise DeviceMapper and Thin provisioning.
3. The method of claim 1, wherein the database comprises MySQL, MariaDB, PostgreSQL, and FileMaker.
4. The method for creating a database snapshot using container technology as claimed in claim 1, wherein said exiting the database process in S3 and keeping the data files in the database consistent comprises the following steps:
and when the snapshot needs to be made, stopping the service of the container and the database, waiting for the exit of the database process, and keeping the consistency of all data files in the database.
5. The method for creating a database snapshot using container technology as claimed in claim 1, wherein the saving of the snapshot includes saving the snapshot locally, saving the mirror export as a separate file, or pushing the mirror export to a mirror repository.
6. A system for creating a database snapshot by using container technology, which is used for implementing the steps of the method for creating a database snapshot by using container technology in any one of claims 1-5, and is characterized in that the system comprises:
the system comprises a mirror image making module, a database storage module and a mirror image processing module, wherein the mirror image making module is used for making a database storage mirror image and installing preset database application software and a three-party component in the database storage mirror image;
the container creating module is used for creating a container which provides database service to the outside by using the database container mirror image and storing a preset data file in the container;
the database quitting module is used for quitting the database process and keeping all data files in the database consistent;
the container submitting module is used for executing submitting and saving operation on the container, saving the whole container as a new mirror image and saving the mirror image as a snapshot;
and the database recovery module is used for importing or pulling the corresponding mirror image from the mirror image warehouse according to the file, and restarting a new container by using the mirror image to realize the recovery of the database snapshot version.
7. The system for creating a database snapshot by using a container technology as claimed in claim 6, wherein the step of making a database container mirror image and installing preset database application software and a three-party component in the database container mirror image comprises the following steps:
the method comprises the following steps of realizing the manufacture of a database container mirror image through a pre-written Dockerfile;
and installing preset database application software and a three-party component in the database container mirror image.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110770470.6A CN113220638B (en) | 2021-07-08 | 2021-07-08 | Method and system for establishing database snapshot by using container technology |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110770470.6A CN113220638B (en) | 2021-07-08 | 2021-07-08 | Method and system for establishing database snapshot by using container technology |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113220638A CN113220638A (en) | 2021-08-06 |
| CN113220638B true CN113220638B (en) | 2021-10-08 |
Family
ID=77081208
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110770470.6A Active CN113220638B (en) | 2021-07-08 | 2021-07-08 | Method and system for establishing database snapshot by using container technology |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113220638B (en) |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10884869B2 (en) * | 2015-04-16 | 2021-01-05 | Nuodb, Inc. | Backup and restore in a distributed database utilizing consistent database snapshots |
| CN105681420A (en) * | 2016-01-18 | 2016-06-15 | 浪潮集团有限公司 | Method for realizing backup of switch operating system based on Docker |
| CN108958976A (en) * | 2018-07-02 | 2018-12-07 | 山东汇贸电子口岸有限公司 | A kind of PV snapshot restores distributed data base data method and system |
| CN110109779A (en) * | 2019-07-02 | 2019-08-09 | 南京云信达科技有限公司 | A method of data, which are carried out, based on micro services restores rehearsal environmental structure |
| CN111290767B (en) * | 2020-01-20 | 2021-06-08 | 中国科学院计算技术研究所 | Container group updating method and system with service quick recovery function |
-
2021
- 2021-07-08 CN CN202110770470.6A patent/CN113220638B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN113220638A (en) | 2021-08-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7370164B1 (en) | Backup of virtual machines from the base machine | |
| CN111338854B (en) | Kubernetes cluster-based method and system for quickly recovering data | |
| US6618736B1 (en) | Template-based creation and archival of file systems | |
| US6785693B2 (en) | Management of multiple links to a file in a file system | |
| EP1706822B1 (en) | Maintaining consistency for remote copy using virtualization | |
| US20070277012A1 (en) | Method and apparatus for managing backup data and journal | |
| CN103780638A (en) | Data synchronization method and system | |
| US8667238B2 (en) | Selecting an input/output tape volume cache | |
| CN107016016B (en) | Data processing method and device | |
| CN109902034A (en) | Snapshot creation method, device, electronic equipment and machine readable storage medium | |
| US9207966B2 (en) | Method and system for providing a high-availability application | |
| US11500738B2 (en) | Tagging application resources for snapshot capability-aware discovery | |
| US9251189B2 (en) | Update of data structure configured to store metadata associated with a database system | |
| US9798483B2 (en) | Object storage power consumption optimization | |
| CN111367856A (en) | Data copying method and device, electronic equipment and machine-readable storage medium | |
| US20210326271A1 (en) | Stale data recovery using virtual storage metadata | |
| CN113220638B (en) | Method and system for establishing database snapshot by using container technology | |
| US20210334165A1 (en) | Snapshot capability-aware discovery of tagged application resources | |
| CN113835625B (en) | Data storage method, device, equipment and storage medium based on sub-path | |
| CN115562590A (en) | Method, system, equipment and storage medium for using cloud hard disk by cloud host | |
| EP3769225A1 (en) | Free space pass-through | |
| CN109117167A (en) | A kind of starting Oftware updating method based on ZYNQ chip | |
| CN112486517B (en) | Application program installation method and system, electronic equipment and storage medium | |
| US11675931B2 (en) | Creating vendor-neutral data protection operations for vendors' application resources | |
| CN114138560A (en) | Backup restoration method and system for 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 |