CN112269679A - Database persistence method, system, equipment and storage medium of cloud platform - Google Patents
Database persistence method, system, equipment and storage medium of cloud platform Download PDFInfo
- Publication number
- CN112269679A CN112269679A CN202011110438.7A CN202011110438A CN112269679A CN 112269679 A CN112269679 A CN 112269679A CN 202011110438 A CN202011110438 A CN 202011110438A CN 112269679 A CN112269679 A CN 112269679A
- Authority
- CN
- China
- Prior art keywords
- database
- cloud platform
- service data
- external storage
- unit
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 230000002688 persistence Effects 0.000 title claims abstract description 49
- 238000000034 method Methods 0.000 title claims abstract description 38
- 210000001503 joint Anatomy 0.000 claims abstract description 9
- 238000003032 molecular docking Methods 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 11
- 230000004048 modification Effects 0.000 claims description 8
- 238000012986 modification Methods 0.000 claims description 8
- 230000001960 triggered effect Effects 0.000 claims description 3
- 230000000694 effects Effects 0.000 abstract 1
- 238000010586 diagram Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000011010 flushing procedure Methods 0.000 description 1
- 230000000717 retained effect Effects 0.000 description 1
- 238000012800 visualization Methods 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/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1471—Saving, restoring, recovering or retrying involving logging of persistent data for recovery
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1456—Hardware arrangements for backup
Abstract
The application discloses a database persistence method of a cloud platform, which comprises the following steps: deleting original database components of the cloud platform cluster; the cloud platform cluster is in butt joint with a preset external storage device; modifying the file configuration to modify the default storage type of the database set in the file configuration into a storage type conforming to the external storage equipment; the new database is deployed in the external storage device. By applying the scheme of the application, the database persistence is effectively realized. The application also discloses a database persistence system, equipment and a storage medium of the cloud platform, and the system, the equipment and the storage medium have corresponding technical effects.
Description
Technical Field
The invention relates to the technical field of databases, in particular to a database persistence method, a database persistence system, a database persistence device and a storage medium of a cloud platform.
Background
As kubernets communities become active, heterogeneous cloud platform products based on kubernets are continuously moving to cloud markets. The heterogeneous cloud platform mainly completes virtualization or containerization of an underlying physical resource pool, and then the underlying physical resource pool is provided for customers to use in a visualization service mode. The database belongs to an indispensable service component of the heterogeneous cloud platform and provides writing and retrieval of cloud platform service data.
The heterogeneous cloud platform deployment environment is a physical server or a virtual machine, and the storage relied on when the database is deployed is a local disk. In a conventional scheme, a certain protection is usually performed on a database, for example, two copies of data stored in a local disk are stored to implement redundancy, and for example, some mechanisms for reading and writing data are provided to implement data protection. However, if the host or disk fails seriously, the database is difficult to recover, which directly affects the business application.
In summary, how to effectively implement the persistence of the database and further ensure the security of the data is a technical problem that needs to be solved urgently by those skilled in the art.
Disclosure of Invention
The invention aims to provide a database persistence method, a database persistence system, a database persistence device and a storage medium of a cloud platform, so that the database persistence is effectively realized, and the data security is further ensured.
In order to solve the technical problems, the invention provides the following technical scheme:
a database persistence method of a cloud platform includes:
deleting original database components of the cloud platform cluster;
the cloud platform cluster is in butt joint with a preset external storage device;
modifying the file configuration to modify the default storage type of the database set in the file configuration to be in accordance with the storage type of the external storage equipment;
and deploying the new database in the external storage equipment.
Preferably, the method further comprises the following steps:
judging whether a preset service data backup condition is satisfied;
if not, executing the operation of deleting the original database component of the cloud platform cluster;
if the service data in the original database of the cloud platform cluster is the original database component, the service data in the original database of the cloud platform cluster is backed up before the original database component of the cloud platform cluster is deleted, and the backed-up service data is written into the new database in a flashing mode after the new database is deployed in the external storage device.
Preferably, the preset service data backup conditions are as follows: the original database of the cloud platform cluster at least comprises one service data.
Preferably, the preset service data backup conditions are as follows: the original database of the cloud platform cluster at least comprises one item of service data, and the type of at least one item of service data meets the preset type requirement.
Preferably, the method further comprises the following steps:
when the cloud platform cluster is judged to be not deployed and K8S is deployed, the cloud platform cluster is in butt joint with a preset external storage device;
modifying the file configuration to modify the default storage type of the database set in the file configuration to be in accordance with the storage type of the external storage equipment;
and deploying the new database in the external storage equipment.
A database persistence system of a cloud platform, comprising:
the database component deleting unit is used for deleting the original database component of the cloud platform cluster;
the docking unit is used for docking the cloud platform cluster with a preset external storage device;
the storage type modification unit is used for modifying the file configuration so as to modify the default storage type of the database set in the file configuration into the storage type which accords with the external storage equipment;
and the new database deployment unit is used for deploying the new database in the external storage equipment.
Preferably, the method further comprises the following steps:
the service data backup condition judging unit is used for judging whether a preset service data backup condition is established or not;
if not, triggering the database component deleting unit;
if yes, triggering a backup unit before triggering the database component deleting unit, and triggering a backup executing unit after triggering a new database deploying unit;
the backup unit is used for backing up the service data in the original database of the cloud platform cluster,
and the backup execution unit is used for flashing the backup service data into a new database.
Preferably, the method further comprises the following steps:
a second docking unit to: and when the cloud platform cluster is judged not to be deployed and K8S is deployed, the cloud platform cluster is in butt joint with a preset external storage device, and the storage type modification unit and the new database deployment unit are sequentially triggered.
A database persistence device of a cloud platform, comprising:
a memory for storing a computer program;
a processor for executing the computer program to implement the steps of the database persistence method of the cloud platform of any of the above.
A computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the database persistence method of the cloud platform of any of the above.
By applying the technical scheme provided by the embodiment of the invention, the data in the database is stored in the local disk in consideration of the traditional scheme, and even if some data protection mechanisms are arranged, once physical equipment or the local disk fails, the database may lose the read-write capability and cannot be recovered. Therefore, in the scheme of the application, in order to improve the reliability of data and realize the persistence of the database of the cloud platform, the database of the cloud platform cluster is moved to an external storage device, specifically, an original database component of the cloud platform cluster is firstly deleted, the cloud platform cluster is then butted with a preset external storage device, and the file configuration is modified so as to modify the default storage type of the database set in the file configuration into the storage type conforming to the external storage device, so that the new database can be deployed in the external storage device. The database of the scheme is deployed in the external storage device, so that the recoverability of the data is greatly improved, the reliability of the data is improved, and the persistence of the database is effectively realized.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flowchart illustrating an embodiment of a database persistence method of a cloud platform according to the present invention;
FIG. 2 is a schematic structural diagram of a database persistence system of a cloud platform according to the present invention;
fig. 3 is a schematic structural diagram of a database persistence device of a cloud platform according to the present invention.
Detailed Description
The core of the invention is to provide a database persistence method of a cloud platform, which effectively realizes the persistence of the database.
In order that those skilled in the art will better understand the disclosure, the invention will be described in further detail with reference to the accompanying drawings and specific embodiments. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, fig. 1 is a flowchart illustrating an implementation of a database persistence method of a cloud platform according to the present invention, where the database persistence method of the cloud platform may include the following steps:
step S101: and deleting the original database component of the cloud platform cluster.
In practical applications, such an embodiment of the present application is generally directed to a newly deployed cloud platform, that is, no business data or important business data is temporarily stored in a database of the cloud platform.
The database component can establish a corresponding relation between the upper-layer application and the database, and the original database component of the cloud platform cluster needs to be deleted because the new database needs to be deployed in the external storage device according to the scheme of the application.
Step S102: and butting the cloud platform cluster with a preset external storage device.
Generally, the docking of the cloud platform cluster and a preset external storage device can be realized by using a docking script. The specific type of the preset external storage device can be selected according to actual needs.
In addition, it should be noted that the cloud platform cluster is docked with a preset external storage device. The deployment of the kubernets is usually performed after the cloud platform is deployed, or when the cloud platform is not completely deployed but at least the kubernets deployment is completed, that is, at least the K8S deployment is completed. After the cloud platform deployment is completed, or the kubernets deployment is completed, the plug-ins or services required for docking are deployed and completed in the cluster, so that the docking of the cloud platform cluster and the preset external storage device can be performed.
Step S103: and modifying the file configuration to modify the default storage type of the database set in the file configuration to be in accordance with the storage type of the external storage device.
After the cloud platform cluster is connected with the preset external storage device, a storage type conforming to the external storage device can be created, and then the file configuration is modified, namely the file configuration of the database component yml is modified, so that the default storage type of the database set in the file configuration is modified into the storage type conforming to the external storage device.
Typically, for a particular external storage device, there will be a particular storage type that conforms to the external storage device. Of course, if a certain external storage device supports two or more storage types, the implementation of the present invention is not affected, and only one storage type corresponding to the external storage device needs to be selected as needed to implement the scheme of the present application.
The new database can be deployed in the external storage device by modifying the file configuration.
Step S104: the new database is deployed in the external storage device.
The new database is deployed in the external storage device, so that the movement of the database is completed, namely, the database originally deployed in the local disk is changed to be deployed in the external storage device, thereby being beneficial to realizing the database persistence of the cloud platform and ensuring the data security.
In an embodiment of the present invention, the method may further include:
judging whether a preset service data backup condition is satisfied;
if not, executing the operation of deleting the original database component of the cloud platform cluster;
if yes, before deleting the original database component of the cloud platform cluster, backing up the service data in the original database of the cloud platform cluster, and after deploying the new database in the external storage device, flushing the backed-up service data into the new database.
The implementation mode is generally applied to the occasions that the cloud platform is deployed and the service is already operated.
When the preset service data backup condition is judged to be established, the cloud platform is completely deployed, the service is already operated, and it is required to ensure that the existing service data is not lost after the scheme of the application is executed. Therefore, in this embodiment, after the preset service data backup condition is determined to be satisfied, before deleting the original database component of the cloud platform cluster, the service data in the original database of the cloud platform cluster is backed up. Specifically, sql script backup may be performed.
After the new database is deployed in the external storage device, the backup business data can be written into the new database in a flashing manner, so that the integrity of the data is guaranteed.
Correspondingly, when the preset service data backup condition is not met, it indicates that the service data is not the service data currently, or the service data in the original database may not need to be retained. Of course, the specific content of the preset service data backup condition may be set and adjusted according to actual needs.
For example, in a specific embodiment of the present invention, the preset service data backup conditions are: the original database of the cloud platform cluster at least comprises one service data.
The setting of the implementation mode is simple and convenient, and the backup of the service data can be carried out as long as at least one item of service data is included in the original database of the cloud platform cluster, so that after the application mobile database is connected to the external storage device, all original existing service data cannot be lost.
In a specific embodiment of the present invention, the preset service data backup conditions are: the original database of the cloud platform cluster at least comprises one item of service data, and the type of at least one item of service data meets the preset type requirement.
In the embodiment, it is considered that in some occasions, although business data exists in the original database of the cloud platform cluster, if the business data is not particularly important, the business data does not need to be reserved, and the time consumption of implementation of the scheme is shortened. Therefore, in this embodiment, it is also required that the type of at least one service data meets the preset type requirement, that is, it is indicated that at least one service data is more important data. Of course, the specific type items included in the preset type requirements can be set and selected according to actual needs.
In one embodiment of the present invention, the method further comprises:
when the cloud platform cluster is judged to be not deployed and K8S is deployed, the cloud platform cluster is in butt joint with a preset external storage device;
modifying the file configuration to modify the default storage type of the database set in the file configuration into a storage type conforming to the external storage equipment;
the new database is deployed in the external storage device.
As described above, the scheme of the present application may be executed in a newly deployed cloud platform, may also be executed in a cloud platform already running a service, and may also be executed in a case that the cloud platform is not yet deployed, but deployment of K8S is completed. The embodiment is directed to the case where the cloud platform cluster is not deployed completely, but the deployment of K8S is completed. Specifically, in this case, the original database is not deployed, so that the operation of docking the cloud platform cluster with the preset external storage device can be directly performed, and then the file configuration is modified to modify the default storage type of the database set in the file configuration to the storage type conforming to the external storage device, so that the new database can be deployed in the external storage device.
By applying the technical scheme provided by the embodiment of the invention, the data in the database is stored in the local disk in consideration of the traditional scheme, and even if some data protection mechanisms are arranged, once physical equipment or the local disk fails, the database may lose the read-write capability and cannot be recovered. Therefore, in the scheme of the application, in order to improve the reliability of data and realize the persistence of the database of the cloud platform, the database of the cloud platform cluster is moved to an external storage device, specifically, an original database component of the cloud platform cluster is firstly deleted, the cloud platform cluster is then butted with a preset external storage device, and the file configuration is modified so as to modify the default storage type of the database set in the file configuration into the storage type conforming to the external storage device, so that the new database can be deployed in the external storage device. The database of the scheme is deployed in the external storage device, so that the recoverability of the data is greatly improved, the reliability of the data is improved, and the persistence of the database is effectively realized.
Corresponding to the above method embodiment, the embodiment of the present invention further provides a database persistence system of a cloud platform, and the following description of the database persistence system of the cloud platform and the above description of the database persistence method of the cloud platform may be referred to each other correspondingly.
Referring to fig. 2, a schematic structural diagram of a database persistence system of a cloud platform in the present invention is shown, including:
a database component deleting unit 201, configured to delete an original database component of the cloud platform cluster;
the docking unit 202 is configured to dock the cloud platform cluster with a preset external storage device;
the storage type modification unit 203 is used for modifying the file configuration so as to modify the default storage type of the database set in the file configuration into a storage type conforming to the external storage device;
a new database deployment unit 204, configured to deploy the new database in the external storage device.
In one embodiment of the present invention, the method further comprises:
the service data backup condition judging unit is used for judging whether a preset service data backup condition is established or not;
if not, triggering a database component deleting unit 201;
if yes, triggering a backup unit before triggering the database component deleting unit 201, and triggering a backup executing unit after triggering the new database deploying unit 204;
a backup unit for backing up the service data in the original database of the cloud platform cluster,
and the backup execution unit is used for flashing the backup service data into the new database.
In a specific embodiment of the present invention, the preset service data backup conditions are: the original database of the cloud platform cluster at least comprises one service data.
In a specific embodiment of the present invention, the preset service data backup conditions are: the original database of the cloud platform cluster at least comprises one item of service data, and the type of at least one item of service data meets the preset type requirement.
In one embodiment of the present invention, the method further comprises:
a second docking unit to: and when the cloud platform cluster is judged not to be deployed and K8S is deployed, the cloud platform cluster is in butt joint with a preset external storage device, and then the storage type modification unit and the new database deployment unit are sequentially triggered.
Corresponding to the above method and system embodiments, the present invention further provides a database persistence device of a cloud platform and a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the database persistence method of the cloud platform in any of the above embodiments are implemented. A computer-readable storage medium as referred to herein may include Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
Referring to fig. 3, a schematic structural diagram of a database persistence device of a cloud platform in the present invention is shown, including:
a memory 301 for storing a computer program;
a processor 302 for executing a computer program to implement the steps of the database persistence method of the cloud platform of any of the above.
It is further noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The principle and the implementation of the present invention are explained in the present application by using specific examples, and the above description of the embodiments is only used to help understanding the technical solution and the core idea of the present invention. It should be noted that, for those skilled in the art, it is possible to make various improvements and modifications to the present invention without departing from the principle of the present invention, and those improvements and modifications also fall within the scope of the claims of the present invention.
Claims (10)
1. A database persistence method of a cloud platform is characterized by comprising the following steps:
deleting original database components of the cloud platform cluster;
the cloud platform cluster is in butt joint with a preset external storage device;
modifying the file configuration to modify the default storage type of the database set in the file configuration to be in accordance with the storage type of the external storage equipment;
and deploying the new database in the external storage equipment.
2. The database persistence method of the cloud platform according to claim 1, further comprising:
judging whether a preset service data backup condition is satisfied;
if not, executing the operation of deleting the original database component of the cloud platform cluster;
if the service data in the original database of the cloud platform cluster is the original database component, the service data in the original database of the cloud platform cluster is backed up before the original database component of the cloud platform cluster is deleted, and the backed-up service data is written into the new database in a flashing mode after the new database is deployed in the external storage device.
3. The database persistence method of the cloud platform according to claim 2, wherein the preset service data backup conditions are: the original database of the cloud platform cluster at least comprises one service data.
4. The database persistence method of the cloud platform according to claim 2, wherein the preset service data backup conditions are: the original database of the cloud platform cluster at least comprises one item of service data, and the type of at least one item of service data meets the preset type requirement.
5. The database persistence method of the cloud platform according to claim 1, further comprising:
when the cloud platform cluster is judged to be not deployed and K8S is deployed, the cloud platform cluster is in butt joint with a preset external storage device;
modifying the file configuration to modify the default storage type of the database set in the file configuration to be in accordance with the storage type of the external storage equipment;
and deploying the new database in the external storage equipment.
6. A database persistence system of a cloud platform, comprising:
the database component deleting unit is used for deleting the original database component of the cloud platform cluster;
the docking unit is used for docking the cloud platform cluster with a preset external storage device;
the storage type modification unit is used for modifying the file configuration so as to modify the default storage type of the database set in the file configuration into the storage type which accords with the external storage equipment;
and the new database deployment unit is used for deploying the new database in the external storage equipment.
7. The cloud platform database persistence system of claim 6, further comprising:
the service data backup condition judging unit is used for judging whether a preset service data backup condition is established or not;
if not, triggering the database component deleting unit;
if yes, triggering a backup unit before triggering the database component deleting unit, and triggering a backup executing unit after triggering a new database deploying unit;
the backup unit is used for backing up the service data in the original database of the cloud platform cluster,
and the backup execution unit is used for flashing the backup service data into a new database.
8. The cloud platform database persistence system of claim 6, further comprising:
a second docking unit to: and when the cloud platform cluster is judged not to be deployed and K8S is deployed, the cloud platform cluster is in butt joint with a preset external storage device, and the storage type modification unit and the new database deployment unit are sequentially triggered.
9. A database persistence device of a cloud platform, comprising:
a memory for storing a computer program;
a processor for executing the computer program to implement the steps of the database persistence method of the cloud platform according to any one of claims 1 to 5.
10. A computer-readable storage medium, characterized in that a computer program is stored thereon, which computer program, when being executed by a processor, realizes the steps of the database persistence method of the cloud platform according to one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011110438.7A CN112269679B (en) | 2020-10-16 | 2020-10-16 | Database persistence method, system, equipment and storage medium of cloud platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011110438.7A CN112269679B (en) | 2020-10-16 | 2020-10-16 | Database persistence method, system, equipment and storage medium of cloud platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112269679A true CN112269679A (en) | 2021-01-26 |
| CN112269679B CN112269679B (en) | 2022-11-11 |
Family
ID=74338305
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011110438.7A Active CN112269679B (en) | 2020-10-16 | 2020-10-16 | Database persistence method, system, equipment and storage medium of cloud platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112269679B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113312179A (en) * | 2021-06-01 | 2021-08-27 | 中国民航信息网络股份有限公司 | Data component management method, device and system, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105653719A (en) * | 2016-01-06 | 2016-06-08 | 上海斐讯数据通信技术有限公司 | Method and system for rapidly acquiring files of external storage equipment and router |
| CN108491500A (en) * | 2018-03-20 | 2018-09-04 | 新华三云计算技术有限公司 | Database cut-in method and device |
| US20200050522A1 (en) * | 2018-08-13 | 2020-02-13 | Remote DBA Experts, LLC | Highly available cloud-based database services |
| CN111338854A (en) * | 2020-05-25 | 2020-06-26 | 南京云信达科技有限公司 | Kubernetes cluster-based method and system for quickly recovering data |
-
2020
- 2020-10-16 CN CN202011110438.7A patent/CN112269679B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105653719A (en) * | 2016-01-06 | 2016-06-08 | 上海斐讯数据通信技术有限公司 | Method and system for rapidly acquiring files of external storage equipment and router |
| CN108491500A (en) * | 2018-03-20 | 2018-09-04 | 新华三云计算技术有限公司 | Database cut-in method and device |
| US20200050522A1 (en) * | 2018-08-13 | 2020-02-13 | Remote DBA Experts, LLC | Highly available cloud-based database services |
| CN111338854A (en) * | 2020-05-25 | 2020-06-26 | 南京云信达科技有限公司 | Kubernetes cluster-based method and system for quickly recovering data |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113312179A (en) * | 2021-06-01 | 2021-08-27 | 中国民航信息网络股份有限公司 | Data component management method, device and system, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112269679B (en) | 2022-11-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10310949B1 (en) | Disaster restore of big data application with near zero RTO | |
| US8732121B1 (en) | Method and system for backup to a hidden backup storage | |
| US7606842B2 (en) | Method of merging a clone file system with an original file system | |
| US20060123211A1 (en) | Method for optimizing a snapshot operation on a file basis | |
| EP3750066B1 (en) | Protection of infrastructure-as-a-service workloads in public cloud | |
| US20110093437A1 (en) | Method and system for generating a space-efficient snapshot or snapclone of logical disks | |
| US9823976B2 (en) | Optimization to permit block based incremental backup across system reboot or crash | |
| US8655847B2 (en) | Mirroring data changes in a database system | |
| US20060200500A1 (en) | Method of efficiently recovering database | |
| CN109684298B (en) | Database migration method, device, equipment and storage medium | |
| CN115098299B (en) | Backup method, disaster recovery method, device and equipment of virtual machine | |
| CN113656149A (en) | Application processing method and device and related equipment | |
| JP5665889B2 (en) | Method and apparatus for backing up subversion repository | |
| CN112269679B (en) | Database persistence method, system, equipment and storage medium of cloud platform | |
| CN110597660A (en) | Data backup method, device, equipment and medium for virtual machine | |
| CN108664255B (en) | Software upgrading method and device | |
| CN110879764B (en) | Bitmap setting method, device and equipment and readable storage medium | |
| CN111722800A (en) | Method for realizing ROW snapshot of distributed storage system and related components | |
| US10423494B2 (en) | Trimming unused blocks from a versioned image backup of a source storage that is stored in a sparse storage | |
| US20190026195A1 (en) | System halt event recovery | |
| CN114138563A (en) | Method for backing up and restoring Hyper-V virtual machine | |
| CN114328020A (en) | Data backup method and related device for cluster file system | |
| CN112269677A (en) | Rollback operation device, method, equipment and medium under heterogeneous cloud platform | |
| CN113641298A (en) | Data storage method, device and computer program product | |
| CN113312212B (en) | Method, apparatus, device and readable storage medium for protecting parameters of model member |
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 |