CN117591341A - Data backup method and device, electronic equipment and readable storage medium - Google Patents

Data backup method and device, electronic equipment and readable storage medium Download PDF

Info

Publication number
CN117591341A
CN117591341A CN202311614374.8A CN202311614374A CN117591341A CN 117591341 A CN117591341 A CN 117591341A CN 202311614374 A CN202311614374 A CN 202311614374A CN 117591341 A CN117591341 A CN 117591341A
Authority
CN
China
Prior art keywords
data
backed
backup
target
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
Application number
CN202311614374.8A
Other languages
Chinese (zh)
Inventor
李静
张美庆
叶松杰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Merchants Bank Co Ltd
Original Assignee
China Merchants Bank Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by China Merchants Bank Co Ltd filed Critical China Merchants Bank Co Ltd
Priority to CN202311614374.8A priority Critical patent/CN117591341A/en
Publication of CN117591341A publication Critical patent/CN117591341A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1469—Backup restoration techniques
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application is applied to the technical field of databases, and discloses a data backup method, a device, electronic equipment and a readable storage medium, wherein the data backup method comprises the following steps: acquiring form information to be backed up and a target data node cluster; configuring backup interfaces for all target data nodes in the target data node cluster, and configuring access HDFS for all the backup interfaces to obtain the access configuration data node cluster, wherein the HDFS is used for storing data to be backed up; and backing up the data to be backed up corresponding to the form information to be backed up to a backup database through the access configuration data node cluster. The data backup recovery method and device aim to solve the technical problem of low data backup recovery efficiency of HBase.

Description

Data backup method and device, electronic equipment and readable storage medium
Technical Field
The application belongs to the technical field of databases, and relates to a data backup method, a data backup device, electronic equipment and a readable storage medium.
Background
With the advent of the big data age, data information is increasingly important, data protection problems are increasingly prominent, and various catastrophic events alert users to a lot of vigilance. Data protection and disaster recovery of data are very important topics. The HBase Database is built on a distributed file system HDFS (Hadoop Distributed File System, distributed file system), and if an irresistible factor is encountered, the data stored in the HDFS may not be accessed or lost, so it is very important to backup and restore the data in the HBase Database.
At present, data in an HBase database is usually backed up and restored in a snapshot mode, but the snapshot mode is usually that the data in the whole database is backed up and restored, the backed up data volume occupies a large amount of storage space, and longer time is required in data restoration, and in practical application, the data in the whole database is not necessarily backed up and restored at times, so that the efficiency of data backup and restoration is lower for the HBase database at present.
The foregoing is provided merely for the purpose of facilitating an understanding of the technical solutions of the present application and is not intended to represent an admission that the foregoing is prior art.
Disclosure of Invention
The main purpose of the application is to provide a data backup method, a device, an electronic device and a readable storage medium, which aim to solve the technical problem of low data backup and recovery efficiency of HBase.
In order to achieve the above object, the present application provides a data backup method, including:
acquiring form information to be backed up and a target data node cluster;
configuring backup interfaces for all target data nodes in the target data node cluster, and configuring access HDFS for all the backup interfaces to obtain the access configuration data node cluster, wherein the HDFS is used for storing data to be backed up;
And backing up the data to be backed up corresponding to the form information to be backed up to a backup database through the access configuration data node cluster.
To achieve the above object, the present application provides a data backup apparatus, including:
the acquisition module is used for acquiring the form information to be backed up and the target data node cluster;
the node determining module is used for configuring backup interfaces for all target data nodes in the target data node cluster, and configuring access HDFS for all the backup interfaces to obtain the access configuration data node cluster, wherein the HDFS is used for storing data to be backed up;
and the backup module is used for backing up the data to be backed up corresponding to the form information to be backed up to a backup database through the access configuration data node cluster.
The application also provides an electronic device comprising: the computer-readable storage medium comprises a memory, a processor and a program of the data backup method stored in the memory and capable of running on the processor, wherein the program of the data backup method can realize the steps of the data backup method when being executed by the processor.
The present application also provides a readable storage medium having stored thereon a program for implementing a data backup method, which when executed by a processor implements the steps of the data backup method as described above.
The present application also provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of a data backup method as described above.
The application provides a data backup method, a device, electronic equipment and a readable storage medium, wherein a backup interface is configured for each target data node in the target data node cluster by acquiring the target data node cluster of form information to be backed up, and each backup interface is configured to allow access to an HDFS (Hadoop distributed file system) to obtain the access configuration data node cluster, so that each access configuration data node in the access configuration data node cluster can access the HDFS, and the data to be backed up corresponding to the form information to be backed up can be accessed through the access configuration data node cluster, so that the data to be backed up can be backed up for storage in a backup database; therefore, the method and the device can realize the backup of the data of the single form without the need of the backup of the HBase database corresponding to the HDFS, reduce the calculation power of the computer when the data is backed up, and improve the data backup efficiency of the single form.
Furthermore, the data of the single form can be backed up, so that the data of the single form can be obtained, the data of the single form can be recovered without recovering the HBase database corresponding to the HDFS, and the data recovery efficiency is improved. In summary, the method and the device overcome the defect that the HBase database in the prior art cannot backup and restore a single form, and improve the efficiency of data backup and restoration.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the description of the embodiments or the prior art will be briefly described below, and it will be obvious to those skilled in the art that other drawings can be obtained from these drawings without inventive effort.
FIG. 1 is a flowchart of a first embodiment of a data backup method according to the present application;
FIG. 2 is a schematic flow chart of single table data backup in the data backup method of the present application;
FIG. 3 is a flowchart of a second embodiment of a data backup method according to the present application;
FIG. 4 is a schematic flow chart of single table data recovery in the data backup method of the present application;
FIG. 5 is a schematic diagram of an apparatus according to an embodiment of a data backup method of the present application;
fig. 6 is a schematic device structure diagram of a hardware operating environment related to a data backup method in an embodiment of the present application.
The implementation, functional features and advantages of the present application will be further described with reference to the accompanying drawings in conjunction with the embodiments.
Detailed Description
In order to make the above objects, features and advantages of the present application more comprehensible, the following description will make the technical solutions of the embodiments of the present application clear and complete with reference to the accompanying drawings of the embodiments of the present application. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, based on the embodiments herein, which are within the scope of the protection of the present application, will be within the purview of one of ordinary skill in the art without the exercise of inventive faculty.
HBase and Phoenix do not provide official backup and restore functions by themselves, but can only be backed up and restored by snapshot, which has the following problems that Phoenix is an open source SQL (Structured Query Language, database language) middle layer of HBase: (1) the amount of backup data is large, and the performance may be limited: backing up the entire table of data may take up a lot of memory space and the performance of the backup and restore may be affected. Especially for large tables and high concurrent written tables, backup and restore may take longer; (2) Additional tools and procedures may be required to manage and maintain the backup data, including storage management of the backup data, backup policy and version control considerations.
However, table-level backup of HBase and Phoenix can only achieve backup and restore effects by using an import and export method, but the following problems also occur: (1) Single Table backup and recovery: in practice, it is sometimes only necessary to backup and restore a single table, not the entire database. However, conventional backup schemes may not provide backup and restore functionality for a single table; (2) backup data storage and management: storage and management of backup data is a challenge, particularly for large-scale data and backups that require long-term retention. Traditional backup schemes may require additional storage devices and backup management systems; (3) backup recovery speed: when a recovery table is required, the recovery speed of the backup data is an important consideration. Traditional backup schemes may take a long time to restore the entire table of data, especially for large tables.
According to the method and the device, the backup recovery is carried out on the single table, and the parallel backup recovery is carried out through the plurality of access configuration data nodes, so that the data of the whole database is not required to be backed up, the data of the whole database is not required to be recovered, the data backup and recovery efficiency is further improved, the overlarge data backup pressure is not generated, and the backup cost is reduced.
Example 1
Referring to fig. 1, an embodiment of the present application provides a data backup method, where in a first embodiment of the data backup method of the present application, the data backup method includes:
step S10, form information to be backed up and a target data node cluster are obtained;
it should be noted that, the embodiment of the present application is applied to a scenario of HBase database and Phoenix, and performs backup and recovery on data corresponding to the HBase database and Phoenix. Phoenix is an HBase open source SQL engine. The form information to be backed up is characterized by parameter information of data to be backed up, and comprises a form name to be backed up, a first directory address and a form data quantity to be backed up. The form information to be backed up may be parameter information corresponding to a single form. The target data node cluster comprises at least one target data node, and the target data node can be used for backing up data. Each target data node in the target data node cluster can be used for backing up the data corresponding to the form information to be backed up.
The method for obtaining the form information to be backed up may be obtained in response to a data backup instruction, or the form information to be backed up may be preset, or default form information to be backed up in the HBase database. The target data node cluster may be obtained in response to a data backup instruction, or may be each target data node configured by default in the HBase database, etc.
As an example, step S10 includes: and responding to a data backup instruction, acquiring a form name to be backed up and a first directory address from the data backup instruction, and acquiring a target data node cluster.
It should be noted that, the data backup instruction is used for indicating to backup data, and the name of the form to be backed up and the first directory address may be obtained from the data backup instruction. The names of the forms to be backed up are names of the forms needing to be backed up, and the first directory address is a directory address of the data to be backed up stored on the HDFS, which corresponds to the names of the forms to be backed up. Each target data node in the target data node cluster may be each data node that is backed up and restored by a user that is pre-arranged in the HBase.
As another example, the step of obtaining the target data node cluster in step S10 may further include: based on the node number requirement of the user, acquiring each target data node with the number matched with the node number requirement in the HBase based on the node number requirement to obtain a target data node cluster. The node number requirement is the number of target data nodes that the user can provide. And a plurality of target data nodes can be selected in the HBase at will, and the plurality of target data nodes can be configured.
According to the method and the device for the data backup, the target data node cluster is determined based on the data quantity corresponding to the form information to be backed up or calculated by the user, so that the user requirement can be met on one hand, the number of the nodes is determined based on the data quantity on the other hand, and therefore parallel backup can be performed based on a plurality of target data nodes when the data quantity is large, and the data backup efficiency is improved.
Step S20, configuring backup interfaces for all target data nodes in the target data node cluster, and configuring access HDFS for all the backup interfaces to obtain the access configuration data node cluster, wherein the HDFS is used for storing data to be backed up;
it should be noted that, the backup interface is used for backing up data corresponding to the HDFS, the HDFS is used for storing data to be backed up, the specific HDFS has a corresponding HDFS directory, the corresponding data to be backed up can be found on the HDFS directory, the backup interface is CV software (common server), and the target data node can be considered as a server. Accessing the HDFS means that the data node may access data in a database corresponding to the HDFS. The access configuration data node cluster comprises at least one access configuration data node, each access configuration data node in the access configuration data node cluster is a data node configured with CV software, and the CV software is configured with access HDFS. The access configuration data node can access the database corresponding to the HDFS and can be used for backing up data.
Illustratively, the access configuration data node may be considered as a server, and CV software and backup interfaces may be installed on each target data node, and then the configuration of the access HDFS may be performed in each CV software, to obtain each access configuration data node. As another example, CV software configured with access HDFS may also be installed directly on the target data node to obtain access configuration data nodes.
In a possible embodiment, step S20 includes:
step S21, a first HDFS authentication file and a protocol configuration file corresponding to the HBase are obtained;
step S22, configuring preset protocol information in the first HDFS authentication file to obtain a second HDFS authentication file;
step S23, configuring the second HDFS authentication file and the protocol configuration file in the backup interfaces of the target data nodes, to obtain an access configuration data node cluster.
It should be noted that, the first HDFS authentication file and the protocol configuration file are two files corresponding to a Kerberos protocol (computer network authorization protocol), the first HDFS authentication file is an HDFS authentication file before configuration modification, and the first HDFS authentication file may be a default authentication file in the Kerberos protocol. The protocol configuration file is krb (Kerberos 5, network authentication security protocol) configuration file, the protocol configuration file comprises a default domain name, and when the protocol configuration file is configured on the backup interface, a forwarding request of the domain name can be received by the HDFS in the HBase, so that an access configuration data node where the backup interface is located can access the HDFS directory to backup data in the HDFS directory. The preset protocol information is characterized as configuration information of the first HDFS authentication file, the preset protocol information may be determined based on a Kerberos protocol, and if the Kerberos protocol is to be used, the preset protocol information needs to be configured in the first HDFS authentication file. The second HDFS authentication file is a modified HDFS file, and the second HDFS authentication configuration file is used for distributing service ticket to a CV server in CV software, so that a request (request) sent by a Comm server (a master server of CV software) can be authenticated by accessing a configuration data node, thereby enabling access to data in the HDFS.
The first HDFS authentication file and the protocol configuration file may be determined based on a Kerberos protocol, or the first HDFS authentication file and the protocol configuration file sent by the user may be received. The preset protocol information may be added to a subfile in the first HDFS authentication file to obtain a second HDFS authentication file, where the subfile of the first HDFS authentication file may be an hfs-site.xml file, and the preset protocol information may be content configured. And configuring the second HDFS authentication file and the protocol configuration file in the backup interfaces of the target data nodes to obtain access configuration data node clusters, so that the HDFS in the HDFS can be accessed through each access configuration data node.
According to the embodiment of the application, the CV software is configured on each target data node, and the access configuration data nodes are obtained by configuring the access HDFS of the CV software, so that the access of the HDFS directory corresponding to the HDFS through each access configuration data node is realized, backup data can be backed up based on each access configuration data node, and therefore, backup of a single table can be realized.
Step S30, backing up the data to be backed up corresponding to the form information to be backed up to a backup database through the access configuration data node cluster;
it should be noted that, the backup database is used for storing data to be backed up, and the data to be backed up is characterized as the form content to be backed up. The to-be-backed-up form information is parameter information corresponding to the to-be-backed-up data, the to-be-backed-up form information comprises a directory address of the to-be-backed-up data stored in the HDFS directory, and the to-be-backed-up data corresponding to the to-be-backed-up form information is obtained based on the directory address, and then the to-be-backed-up data is stored in a backup database.
The method comprises the steps of obtaining data to be backed up corresponding to form information to be backed up, carrying out parallel backup on the data to be backed up through each access configuration data node, and writing the data into a backup database to realize backup storage of the data to be backed up. By parallel backup, the backup speed of the data to be backed up is improved, and the backup efficiency is improved.
In a possible embodiment, step S30 further includes:
step S31, obtaining form information to be backed up from a first directory address of an HDFS through each access configuration data node in the access configuration data node cluster, wherein the form information to be backed up corresponds to each area block to be backed up;
And step S32, parallelly backing up each region block to be backed up to the backup database, and storing backup log information and metadata information corresponding to the form information to be backed up to the backup database.
It should be noted that, the form information to be backed up includes a first directory address. The first directory address is a directory address of the data to be backed up stored in the HDFS of the HBase; the data to be backed up comprises at least one region block to be backed up, each region block to be backed up of the same data to be backed up is generally stored in the same directory, the region block to be backed up is characterized as a data block, and the region block to be backed up is data corresponding to a region. One form data may be assigned to one or more regions to keep the load on access balanced. The backup log information is each log generated in the backup process of the data to be backed up, the metadata information is each metadata corresponding to the form of the data to be backed up, and the table structure can be obtained from the metadata information by way of example. The backup Log information may be a WAL (Write Ahead Log) file.
Exemplary, according to the first directory address, accessing the first directory address in the HDFS through each access configuration data node, and obtaining each region block to be backed up corresponding to the form information to be backed up from the first directory address; and carrying out parallel backup on each area block to be backed up through each access configuration data node, storing the area blocks to be backed up into a backup database, and jointly storing backup log information and metadata information corresponding to the data to be backed up into the backup database, wherein the backup log information and the metadata information can be stored in association with the data to be backed up.
As another example, the step of backing up the data to be backed up to the backup database may further be to obtain a backup time limit of the data to be backed up, start timing when the data to be backed up is backed up to the backup database, obtain a backup storage time of the data to be backed up, and if the backup storage time of the data to be backed up reaches the backup time limit, perform cold storage on the data to be backed up. The cold storage mode of the data to be backed up may be that the data to be backed up is compressed and stored again so as to reduce the storage space of the data to be backed up. Thereby enabling more data to be backed up in the backup database.
The embodiment of the application can provide assistance for the data recovery stage by storing the backup log information and the metadata information corresponding to the data to be backed up, and can determine whether the data is stored in the backup database or not based on the backup log during the data recovery stage. And the user can check whether the backup data is wrong, thereby improving the accuracy of data backup.
In a possible embodiment, the step of backing up each of the to-be-backed up area blocks in parallel in step S32 includes:
Step S321, for any region block to be backed up, performing hash calculation on the region block to be backed up to obtain a region hash value of the region block to be backed up;
step S322, searching whether the region hash value exists in the backup database;
step S323, if not, storing the region block to be backed up to the backup database, and storing the region block to be backed up to a storage position of the backup database;
and step S324, if yes, storing the storage position of the region hash value in the backup database.
It should be noted that, the region block to be backed up is a region block to be backed up which is segmented from the data to be backed up; the region hash value is the hash value of the region block to be backed up. The storage location is a location where data is stored in the backup database, and in this embodiment, the storage location is a location where the area block to be backed up is stored in the backup database. If the region blocks to be backed up exist in the backup database, the region blocks to be backed up can be not stored any more, so that the waste of storage resources in the backup database is avoided, and the repeated storage of the region blocks to be backed up can be avoided. Each access configuration data node performs hash calculation on the region blocks to be backed up before backing up the region blocks to be backed up to obtain region hash values, so that whether the region blocks to be backed up have repeated backup conditions can be judged, and repeated backup is avoided.
Illustratively, steps S321 through S324 include: carrying out hash calculation on each region block to be backed up to obtain a region hash value of the region block to be backed up; searching whether the region hash value exists in the backup database; if the region hash value does not exist in the backup database, the fact that the data block to be backed up does not exist in the backup database is indicated, the region block to be backed up is stored in the backup database, and the region block to be backed up is stored in a storage position of the backup database; the storage position of the area block to be backed up in the backup database can be recorded, and the index of the area block to be backed up in the backup database can be created so as to search the data block to be backed up in the backup database. If the regional hash value exists in the backup database, the fact that the data block to be backed up exists in the backup database is indicated, repeated backup of the data block to be backed up can be omitted, but a storage position of the regional hash value in the backup database is needed to be stored, and accordingly the corresponding data block to be backed up can be found based on the storage position.
For a better understanding of the embodiments of the present application, reference is made to fig. 2, and fig. 2 is a schematic flow chart of single table data backup in the embodiments of the present application; configuring CV on the target data node means configuring a backup interface on the target data node, the configuring backup interface can be regarded as installing CV software on the target data node, after installing CV software, adding a second HDFS authentication file and a protocol configuration file to complete the configuration of accessing HDFS, realizing the arrangement of an HDFS backup environment, then backing up the data to be backed up, and the data to be backed up can be divided into two parts, wherein one part is the form content in the data to be backed up, and the other part is the form content in the data to be backed up, including the deduplication and position record of the data to be backed up, the storage of the data to be backed up and the period management of the data to be backed up; and when the other part is used for backing up the rest data of the data to be backed up, wherein the rest data comprises backup log information and metadata information. The data deduplication and position record to be backed up refers to that when the region block to be backed up corresponding to the data to be backed up is stored in the backup database, the region hash value of the region block to be backed up is calculated first, then the region hash value exists in the backup database, the region block to be backed up corresponding to the region hash value is not stored, the duplicate storage is avoided, the data to be backed up is deduplicated, the position record refers to the position of the region block to be backed up stored in the backup database, and the position of the region hash value in the backup database is recorded when the region hash value of the region block to be backed up exists in the backup database before the region block to be backed up is stored. The location stamp may also be called an index. Storing data to be backed up refers to storing the data to be backed up to a backup database. The period management of the data to be backed up refers to that if the data to be backed up is stored in the backup database and carries a backup time limit, when the storage time of the data to be backed up reaches the backup time limit, the data to be backed up is cold stored, for example, further compressed and stored, or set as the unusual backup data to reduce the storage pressure of the backup database.
The application provides a data backup method, a device, electronic equipment and a readable storage medium, wherein a backup interface is configured for each target data node in the target data node cluster by acquiring the target data node cluster of form information to be backed up, and each backup interface is configured to allow access to an HDFS (Hadoop distributed file system) to obtain the access configuration data node cluster, so that each access configuration data node in the access configuration data node cluster can access the HDFS, and the data to be backed up corresponding to the form information to be backed up can be accessed through the access configuration data node cluster, so that the data to be backed up can be backed up for storage in a backup database; therefore, the method and the device can realize the backup of the data of the single form without the need of the backup of the HBase database corresponding to the HDFS, reduce the calculation power of the computer when the data is backed up, and improve the data backup efficiency of the single form.
Furthermore, the data of the single form can be backed up, so that the data of the single form can be obtained, the data of the single form can be recovered without recovering the HBase database corresponding to the HDFS, and the data recovery efficiency is improved. In summary, the method and the device overcome the defect that the HBase database in the prior art cannot backup and restore a single form, and improve the efficiency of data backup and restoration.
Example two
Further, referring to fig. 3, in another embodiment of the present application, the same or similar content as the above embodiment may be referred to the above description, and will not be repeated. On the basis, after the step of backing up the data to be backed up corresponding to the form information to be backed up to the backup database through the access configuration data node cluster, the method further comprises the following steps:
step A10, responding to a data recovery instruction, and acquiring form information to be recovered;
and step A20, matching target recovery data corresponding to the form information to be recovered from the backup database through the access configuration data node cluster, and recovering the data to be recovered corresponding to the form information to be recovered based on the target recovery data.
It should be noted that, in this embodiment of the present application, a single form may also be restored, a data restoration instruction is used to indicate that data is restored, and, illustratively, in response to the data restoration instruction, a directory corresponding to an HDFS corresponding to a to-be-restored form name may be obtained, an original form structure, an original form area name, original form area segmentation information, and a second directory address may also be directly searched from a backup database, and may be searched based on information such as a backup log and metadata information stored in the backup database, by using the to-be-restored form name, so as to obtain the original form structure, the original form area name, the original form area segmentation information, and so on.
The form information to be recovered is characterized as parameter information corresponding to the form data to be recovered, and the form information to be recovered can comprise the form name to be recovered, or can be a directory address corresponding to the data, and the form name corresponding to the data to be recovered is obtained based on the directory address. The form information to be restored further includes an original form structure, a second directory address, original form area name information, and original form area division information.
The original table structure is an original table structure corresponding to the data to be recovered, and can be considered as a corresponding table structure when the data is stored in the HDFS directory before the data is not lost or damaged, and the table structure refers to the column name of the table, the field type of each data column, and the like by way of example. The second directory address refers to a reply address of the data to be recovered, and may be considered as a storage address of the original data corresponding to the data to be recovered on the HDFS directory. The original data may be considered as data to which the data to be recovered corresponds before it is not lost or corrupted.
The original table region name information is the name of each region block corresponding to the original data, the data is stored in each region block, and the original table region division information is the division unit corresponding to each region block. When the original data is stored on the HDFS, the original data is distributed to one or more regions so that the load balance is kept when the original data is accessed, the original data is required to be segmented before the original data is distributed to one or more regions, region blocks are obtained, each region block is distributed to each region, and the original data is generally segmented through split; split refers to the split rowkey of the parent region. For example, a parent region may have a rowKey in the range of 1-10 and a split of 5, and the parent region may be divided into two child regions in units of split.
The form name to be recovered refers to the name corresponding to the form data to be recovered, and the data to be recovered is the form data to be recovered. And under the condition that the form name to be restored exists in the backup database, the data which is backed up in the backup database before the data to be restored exists in the backup database is explained. In data recovery, it is also necessary to recover data by accessing the configuration data node.
The data recovery instruction may be a data recovery instruction triggered under a preset condition, where the preset condition may be that data is lost, and the data recovery instruction may also be a request initiated by a CVserver on CV software, where the request may carry a to-be-recovered form name, an original form structure, a second directory address, original form area name information, original form area segmentation information, and the like. And matching target recovery data corresponding to the form information to be recovered from the backup database through the access configuration data node cluster, and recovering the data to be recovered corresponding to the form information to be recovered based on the target recovery data. Therefore, the recovery of single form data can be realized, and the data recovery efficiency is improved.
In a possible embodiment, a20 further comprises:
step A21, determining the form name to be restored, the original form structure, the second directory address, the original form area name information and the original form area segmentation information from the form information to be restored;
step A22, searching target recovery data corresponding to the form name to be recovered in the backup database through the access configuration data node cluster, and recovering the target recovery data to the HDFS based on the second directory address;
and step A23, dividing and recovering the target recovery data to each target recovery area corresponding to the original table structure based on the original table structure, the original table area name information and the original table area dividing information, and verifying the area blocks to be recovered of each target recovery area.
It should be noted that, the data to be restored includes target restoration data and at least one area block to be restored, where the target restoration data may be considered as all data contents of the data to be restored, but does not include information such as an area name corresponding to the data to be restored, and the area block to be restored is to restore the data corresponding to the area to be restored in the data to be restored, restore the area block to be restored to the target restoration area, and verify the area block to be restored, which is to complete restoration of the data to be restored. The target recovery data may be an HFile file. The target recovery area is an area corresponding to the original data.
Illustratively, based on the second directory address and the access configuration data node cluster corresponding to the data to be restored, an address of the target restoration data on the HDFS is determined, so as to restore the target restoration data to the HDFS based on the address. Determining each target recovery area based on the original table area name information; dividing target recovery data based on original table area name information and original table area dividing information to obtain an area block to be recovered, recovering the area block to be recovered to a target recovery area, and verifying the area block to be recovered in the target recovery area.
According to the embodiment of the application, the corresponding data to be backed up is searched in the backup database, so that the data to be backed up is restored to the HDFS, the restoration of single form data is realized, and the data restoration efficiency is improved.
In a possible embodiment, the step of dividing and restoring the target restoration data to each target restoration area corresponding to the original table structure in the step a23 based on the original table structure, the original table area name information, and the original table area division information further includes:
step A231, generating a recovery form composed of each target recovery area based on the original table structure and the original table area segmentation information;
Step A232, obtaining a segmentation unit corresponding to each target recovery area from the original table area segmentation information;
step A233, performing region segmentation on the target recovery data based on the original table region name information and the segmentation units by a preset importing tool to obtain to-be-recovered region blocks corresponding to the original table region names respectively;
step A234, searching target recovery areas respectively matched with the target original table area names in the recovery form based on the target original table area names respectively corresponding to the to-be-recovered area blocks;
and step A235, restoring each region block to be restored to the corresponding target restoring region.
The recovery form is characterized as a reconstructed form, and the form structure, the region segmentation condition and the like of the recovery form are the same as those of the form structure and the region segmentation condition corresponding to the original data. The original table region division information includes division information corresponding to each original table region, and the division information may include division units. Therefore, the original table area division information can specify the division unit of the target restoration data, the division unit being used to divide the target restoration data. The preset importing tool is used for supporting the segmentation of the target recovery data and importing the segmented data into the HDFS directory. The target restoration areas may be divided into areas corresponding to the same division units or different division units, and the area division means that the target restoration data is divided into areas corresponding to the respective division units. When the target recovery data is segmented, the original table area name corresponding to the area block to be recovered is determined. The preset import tool may be a Bulkload tool (data loading tool). For example, the target original table area name information may be represented as a list.
As an example, steps a231 to a235 include: generating a recovery form composed of each target recovery area based on the original table structure and the division units of each target recovery area in the original table area division information, and determining the division units corresponding to the target recovery areas from the original table area division information; and performing region segmentation on the target recovery data based on the original table region name information and each segmentation unit by a preset importing tool. Specifically, the original table area names of each target can be determined based on the original table area name information, when the target recovery data is subjected to area segmentation for any target original table area name, a segmentation unit corresponding to the original table area name can be acquired first, and then the target recovery data is segmented based on the original table area name and the segmentation unit to obtain an area block to be recovered corresponding to the original table area name. Searching target recovery areas which are respectively matched with the target original table area names in the recovery form based on the target original table area names respectively corresponding to the to-be-recovered area blocks; and restoring each region block to be restored to the corresponding target restoring region.
According to the embodiment of the application, the complete recovery of the data to be recovered is realized by recovering the blocks of the region to be recovered and the target recovery regions corresponding to the data to be recovered, and the data is stored in the sub-regions under the HDFS directory before the data is not lost or damaged, so that the accuracy of the data can be ensured due to the regional recovery during recovery. Further, the embodiment of the application can be considered as reconstructing a reconstruction table which is the same as the original table corresponding to the original data, so that the data in the table are restored to the reconstruction table, and the recovery of the data in the table is realized.
In a possible embodiment, the verifying the to-be-restored area block of each target restoration area in step a23 further includes:
step X10, acquiring recovery verification data, and inquiring whether the recovery verification data exists in each target recovery area through a preset inquiry tool;
and step X20, if yes, determining that the data to be restored corresponding to the form name to be restored is restored without errors.
It should be noted that, the recovery verification data may be data of any area block corresponding to the data to be recovered stored in the backup database, the recovery verification data is used for verifying whether the data recovery is correct, the preset query tool is used for performing data query in each target recovery area, the preset query tool may be an Sqlline tool, and the Sqlline tool may use sql statement to perform operations such as query insertion on the HDFS directory in hbase. It can be determined whether the data to be restored is restored accurately by querying whether restoration verification data exists in each of the target restoration areas through an SQL (structured query language) tool. And further, the accuracy of data recovery is ensured.
Illustratively, obtaining recovery verification data, and querying whether the recovery verification data exists in each target recovery area through a preset query tool; if the recovery verification data are inquired in each target recovery area, the recovery of the data to be recovered corresponding to the form names to be recovered is described as error-free; if the recovery verification data are not found in the target recovery areas, the recovery errors of the data to be recovered are indicated, and recovery error prompt information can be output to prompt a user that the data to be recovered is in error.
For a better understanding of the embodiments of the present application, reference is made to fig. 4, and fig. 4 is a schematic flow chart of single table data recovery in the embodiments of the present application; the single table recovery process may be that the original table structure, the original table area name information and the original table area segmentation information corresponding to the data to be recovered are obtained first, restore is performed, the data to be recovered is recovered to the HDFS directory, and the data to be recovered is not segmented at this time; recovering through bulk load, that is, recovering each region block to be recovered to each target Recovery region, wherein the recovering of each region block to be recovered to each target Recovery region may comprise three steps, namely, firstly dividing the data to be recovered to obtain each region block to be recovered, then importing each region block to be recovered to each target Recovery region of the Recovery form, and finally, verifying through sqlline to detect whether the recovered data is wrong.
Example III
Referring to fig. 5, an embodiment of the present application further provides a data backup device, where the data backup device includes:
the acquisition module 10 is used for acquiring the form information to be backed up and the target data node cluster;
the node determining module 20 is configured to configure a backup interface for each target data node in the target data node cluster, and perform configuration of accessing an HDFS for each backup interface to obtain an access configuration data node cluster, where the HDFS is used to store data to be backed up;
and the backup module 30 is configured to backup the data to be backed up corresponding to the form information to be backed up to a backup database through the access configuration data node cluster.
Optionally, the node determining module 20 is further configured to:
acquiring a first HDFS authentication file and a protocol configuration file;
configuring preset protocol information in the first HDFS authentication file to obtain a second HDFS authentication file;
and configuring the second HDFS authentication file and the protocol configuration file in the backup interfaces of the target data nodes to obtain an access configuration data node cluster.
Optionally, the backup module 30 is further configured to:
acquiring form information to be backed up from a first directory address of an HDFS (Hadoop distributed file system) corresponding to each region block to be backed up through each access configuration data node in the access configuration data node cluster;
And parallelly backing up each region block to be backed up to the backup database, and storing backup log information and metadata information corresponding to the form information to be backed up to the backup database.
Optionally, the backup module 30 is further configured to:
carrying out hash calculation on any region block to be backed up to obtain a region hash value of the region block to be backed up;
searching whether the region hash value exists in the backup database;
if not, storing the region block to be backed up to the backup database, and storing the position of the region block to be backed up to the backup database;
and if so, storing the position of the region hash value in the backup database.
Optionally, the backup module 30 is further configured to:
responding to a data recovery instruction, and acquiring form information to be recovered;
and matching target recovery data corresponding to the form information to be recovered from the backup database through the access configuration data node cluster, and recovering the data to be recovered corresponding to the form information to be recovered based on the target recovery data.
Optionally, the backup module 30 is further configured to:
Determining the name, original table structure, second directory address, original table area name information and original table area segmentation information of the to-be-restored form from the to-be-restored form information;
searching target recovery data corresponding to the form name to be recovered in the backup database through the access configuration data node cluster, and recovering the target recovery data to an HDFS (Hadoop distributed File System) based on the second directory address;
and dividing and recovering the target recovery data to each target recovery area corresponding to the original table structure based on the original table structure, the original table area name information and the original table area dividing information, and verifying the area blocks to be recovered of each target recovery area.
Optionally, the backup module 30 is further configured to:
generating a recovery form composed of each target recovery area based on the original table structure and the original table area segmentation information;
obtaining a segmentation unit corresponding to each target recovery area from the original table area segmentation information;
performing region segmentation on the target recovery data based on the original table region name information and the segmentation units through a preset importing tool to obtain to-be-recovered region blocks corresponding to the original table region names respectively;
Searching target recovery areas which are respectively matched with the target original table area names in the recovery form based on the target original table area names respectively corresponding to the to-be-recovered area blocks;
and restoring each region block to be restored to the corresponding target restoring region.
Optionally, the backup module 30 is further configured to:
obtaining recovery verification data, and inquiring whether the recovery verification data exists in each target recovery area through a preset inquiring tool;
if yes, determining that the data to be restored corresponding to the form names to be restored is restored without errors.
The data backup device provided by the application adopts the data backup method in the embodiment, and aims to solve the technical problem of low data backup and recovery efficiency of HBase. Compared with the prior art, the data backup method provided in the embodiment of the present application has the same beneficial effects as the data backup method provided in the foregoing embodiment, and other technical features in the data backup device are the same as the features disclosed in the foregoing embodiment method, which are not described herein in detail.
Example IV
The embodiment of the application provides an electronic device, which may be a playing device, including: at least one processor; and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the data backup method of the above embodiment.
Referring now to fig. 6, a schematic diagram of an electronic device suitable for use in implementing embodiments of the present disclosure is shown. The electronic devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistant, personal digital assistants), PADs (portable Android device, tablet computers), PMPs (Portable Media Player, portable multimedia players), vehicle terminals (e.g., car navigation terminals), and the like, and stationary terminals such as digital TVs, desktop computers, and the like. The electronic device shown in fig. 6 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.
As shown in fig. 6, the electronic apparatus may include a processing device (e.g., a central processing unit, a graphics processor, etc.) that may perform various appropriate actions and processes according to a program stored in a ROM (Read-Only Memory) or a program loaded from a storage device into a RAM (Random Access Memory ). In the RAM, various programs and data required for the operation of the electronic device are also stored. The processing device, ROM and RAM are connected to each other via a bus. An input/output (I/O) interface is also connected to the bus.
In general, the following systems may be connected to the I/O interface: input devices including, for example, touch screens, touch pads, keyboards, mice, image sensors, microphones, tachometers, gyroscopes, etc.; output devices including, for example, LCDs (Liquid Crystal Display, liquid crystal displays), speakers, vibrators, and the like; storage devices including, for example, magnetic tape, hard disk, etc.; a communication device. The communication means may allow the electronic device to communicate with other devices wirelessly or by wire to exchange data. While electronic devices having various systems are shown in the figures, it should be understood that not all of the illustrated systems are required to be implemented or provided. More or fewer systems may alternatively be implemented or provided.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network through a communication system, or installed from a storage system, or installed from ROM. The above-described functions defined in the methods of the embodiments of the present disclosure are performed when the computer program is executed by a processing system.
The electronic device provided by the application adopts the data backup method in the first embodiment to solve the technical problem of low data backup and recovery efficiency of the HBase. Compared with the prior art, the beneficial effects of the product flow data distribution provided by the embodiment of the present application are the same as those of the data backup method provided by the above embodiment, and other technical features in the data backup device are the same as those disclosed by the method of the above embodiment, which are not described herein in detail.
It should be understood that portions of the present disclosure may be implemented in hardware, software, firmware, or a combination thereof. In the description of the above embodiments, particular features, structures, materials, or characteristics may be combined in any suitable manner in any one or more embodiments or examples.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Example five
The present embodiment provides a readable storage medium having computer readable program instructions stored thereon for performing the data backup method of the first embodiment.
The readable storage medium provided in the embodiments of the present application may be, for example, a usb disk, but is not limited to, an apparatus, a device or a device of electric, magnetic, optical, electromagnetic, infrared, or semiconductor, or a combination of any of the above. More specific examples of the readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable EPROM (Electrical Programmable Read Only Memory, read-only memory) or flash memory, an optical fiber, a portable compact disc CD-ROM (compact disc read-only memory), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this embodiment, the readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution apparatus, device, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, fiber optic cables, RF (radio frequency), and the like, or any suitable combination of the foregoing.
The readable storage medium may be contained in an electronic device; or may exist alone without being assembled into an electronic device.
The readable storage medium carries one or more programs which, when executed by an electronic device, cause the electronic device to: acquiring form information to be backed up and a target data node cluster; configuring backup interfaces for all target data nodes in the target data node cluster, and configuring access HDFS for all the backup interfaces to obtain the access configuration data node cluster, wherein the HDFS is used for storing data to be backed up; and backing up the data to be backed up corresponding to the form information to be backed up to a backup database through the access configuration data node cluster.
Computer program code for carrying out operations of the present disclosure may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a LAN (local area network ) or WAN (Wide Area Network, wide area network), or it may be connected to an external computer (for example, through the Internet using an Internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of devices, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based devices which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present disclosure may be implemented in software or hardware. Wherein the name of the module does not constitute a limitation of the unit itself in some cases.
The readable storage medium provided by the application stores computer readable program instructions for executing the data backup method, and aims to solve the technical problem of low data backup and recovery efficiency of HBase. Compared with the prior art, the beneficial effects of the readable storage medium provided by the embodiment of the present application are the same as those of the data backup method provided by the above embodiment, and are not described herein.
Example six
The present application also provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of a data backup method as described above.
The computer program product provided by the application aims to solve the technical problem of low data backup and recovery efficiency of HBase. Compared with the prior art, the beneficial effects of the computer program product provided by the embodiment of the present application are the same as those of the data backup method provided by the above embodiment, and are not described herein.
The foregoing description is only of the preferred embodiments of the present application and is not intended to limit the scope of the claims, and all equivalent structures or equivalent processes using the descriptions and drawings of the present application, or direct or indirect application in other related technical fields are included in the scope of the claims.

Claims (10)

1. A data backup method, the data backup method comprising:
acquiring form information to be backed up and a target data node cluster;
configuring backup interfaces for all target data nodes in the target data node cluster, and configuring access HDFS for all the backup interfaces to obtain the access configuration data node cluster, wherein the HDFS is used for storing data to be backed up;
and backing up the data to be backed up corresponding to the form information to be backed up to a backup database through the access configuration data node cluster.
2. The data backup method as claimed in claim 1, wherein the step of configuring backup interfaces for each target data node in the target data node cluster and performing configuration of access HDFS for each backup interface to obtain access configuration data node cluster includes:
acquiring a first HDFS authentication file and a protocol configuration file;
configuring preset protocol information in the first HDFS authentication file to obtain a second HDFS authentication file;
and configuring the second HDFS authentication file and the protocol configuration file in the backup interfaces of the target data nodes to obtain an access configuration data node cluster.
3. The data backup method as claimed in claim 1, wherein the data to be backed up includes area blocks to be backed up; the form information to be backed up comprises a first directory address;
the step of backing up the data to be backed up corresponding to the form information to be backed up to a backup database through the access configuration data node cluster comprises the following steps:
acquiring form information to be backed up from a first directory address of an HDFS (Hadoop distributed file system) corresponding to each region block to be backed up through each access configuration data node in the access configuration data node cluster;
and parallelly backing up each region block to be backed up to the backup database, and storing backup log information and metadata information corresponding to the form information to be backed up to the backup database.
4. The data backup method as claimed in claim 3, wherein the step of backing up each of the region blocks to be backed up to the backup database in parallel comprises:
carrying out hash calculation on any region block to be backed up to obtain a region hash value of the region block to be backed up;
searching whether the region hash value exists in the backup database;
if not, storing the region block to be backed up to the backup database, and storing the position of the region block to be backed up to the backup database;
And if so, storing the position of the region hash value in the backup database.
5. The data backup method as claimed in claim 1, further comprising, after the step of backing up the data to be backed up corresponding to the form information to be backed up to a backup database through the access configuration data node cluster:
responding to a data recovery instruction, and acquiring form information to be recovered;
and matching target recovery data corresponding to the form information to be recovered from the backup database through the access configuration data node cluster, and recovering the data to be recovered corresponding to the form information to be recovered based on the target recovery data.
6. The data backup method of claim 5, wherein the data to be restored comprises target restoration data and a region block to be restored; the form information to be recovered comprises a form name to be recovered;
the step of matching the target recovery data corresponding to the form information to be recovered from the backup database through the access configuration data node cluster and recovering the data to be recovered corresponding to the form information to be recovered based on the target recovery data comprises the following steps:
Determining the name, original table structure, second directory address, original table area name information and original table area segmentation information of the to-be-restored form from the to-be-restored form information;
searching target recovery data corresponding to the form name to be recovered in the backup database through the access configuration data node cluster, and recovering the target recovery data to an HDFS (Hadoop distributed File System) based on the second directory address;
and dividing and recovering the target recovery data to each target recovery area corresponding to the original table structure based on the original table structure, the original table area name information and the original table area dividing information, and verifying the area blocks to be recovered of each target recovery area.
7. The data backup method of claim 6 wherein the primary table area name information includes a target primary table area name;
the step of dividing and restoring the target restoration data to each target restoration area corresponding to the original table structure based on the original table structure, the original table area name information and the original table area dividing information comprises the following steps:
generating a recovery form composed of each target recovery area based on the original table structure and the original table area segmentation information;
Obtaining a segmentation unit corresponding to each target recovery area from the original table area segmentation information;
performing region segmentation on the target recovery data based on the original table region name information and the segmentation units through a preset importing tool to obtain to-be-recovered region blocks corresponding to the original table region names respectively;
searching target recovery areas which are respectively matched with the target original table area names in the recovery form based on the target original table area names respectively corresponding to the to-be-recovered area blocks;
and restoring each region block to be restored to the corresponding target restoring region.
8. The data backup method as claimed in claim 6, wherein said verifying the to-be-restored area blocks of each of the target restoration areas includes:
obtaining recovery verification data, and inquiring whether the recovery verification data exists in each target recovery area through a preset inquiring tool;
if yes, determining that the data to be restored corresponding to the form names to be restored is restored without errors.
9. An electronic device, the electronic device comprising:
at least one processor;
And a memory communicatively coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the steps of the data backup method of any one of claims 1 to 7.
10. A readable storage medium, characterized in that the readable storage medium is a computer readable storage medium, on which a program implementing a data backup method is stored, the program implementing the data backup method being executed by a processor to implement the steps of the data backup method according to any one of claims 1 to 7.
CN202311614374.8A 2023-11-29 2023-11-29 Data backup method and device, electronic equipment and readable storage medium Pending CN117591341A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311614374.8A CN117591341A (en) 2023-11-29 2023-11-29 Data backup method and device, electronic equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311614374.8A CN117591341A (en) 2023-11-29 2023-11-29 Data backup method and device, electronic equipment and readable storage medium

Publications (1)

Publication Number Publication Date
CN117591341A true CN117591341A (en) 2024-02-23

Family

ID=89919743

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311614374.8A Pending CN117591341A (en) 2023-11-29 2023-11-29 Data backup method and device, electronic equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN117591341A (en)

Similar Documents

Publication Publication Date Title
US11068501B2 (en) Single phase transaction commits for distributed database transactions
US10387673B2 (en) Fully managed account level blob data encryption in a distributed storage environment
EP3477914B1 (en) Data recovery method and device, and cloud storage system
JP6495568B2 (en) Method, computer readable storage medium and system for performing incremental SQL server database backup
US9348827B1 (en) File-based snapshots for block-based backups
KR101780340B1 (en) Method, system, and computer-readable storage medium for creating validated database snapshots for provisioning virtual databases
US11093387B1 (en) Garbage collection based on transmission object models
US11010401B2 (en) Efficient snapshot generation of data tables
JP2020502626A (en) Formation and operation of test data in a database system
US10572470B2 (en) Enhanced FSCK mechanism for improved consistency in case of erasure coded object storage architecture built using clustered file system
US11977532B2 (en) Log record identification using aggregated log indexes
US10409691B1 (en) Linking backup files based on data partitions
CN111984465A (en) Database remote backup method, device, medium and electronic equipment
US10318330B2 (en) Data-persisting temporary virtual machine environments
US20210034468A1 (en) Method and system for redundant distribution and reconstruction of storage metadata
US11853165B2 (en) Using file system extended attributes to update databases in hierarchical file systems
US8595271B1 (en) Systems and methods for performing file system checks
AU2021268828B2 (en) Secure data replication in distributed data storage environments
CN117591341A (en) Data backup method and device, electronic equipment and readable storage medium
CN113419896B (en) Data recovery method, device, electronic equipment and computer readable medium
CN115658391A (en) Backup recovery method of WAL mechanism based on QianBase MPP database
US10795588B1 (en) Check point recovery based on identifying used blocks for block-based backup files
US11645333B1 (en) Garbage collection integrated with physical file verification
US11593498B2 (en) Distribution of user specific data elements in a replication environment
US11204845B2 (en) Workload coordination on disaster recovery site

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