Data processing method and device
By creating a homogeneous backup table in the database and importing all the data, the problem of long data recovery time in existing technologies is solved, achieving efficient data backup and recovery and improving business operation efficiency.
Patent Information
- Application Number
- CN202511067566.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-31
- Publication Date
- 2025-11-14
AI Technical Summary
Existing backup and recovery solutions are time-consuming to restore and import data when dealing with large amounts of data or complex table structures, which affects business efficiency. This is especially true in batch scenarios, where existing methods can only restore the data to its state before the overall batch operation when a batch node fails to process, thus increasing the data recovery time.
Create a homogeneous backup table in the database corresponding to the business table to be backed up, and import all the data into the homogeneous backup table. Through concurrent processing and data block contention mechanism, the homogeneous backup of the data is achieved, and the data of the business table to be backed up is directly replaced during recovery.
It reduces data recovery and backup time and improves business operation efficiency, especially in batch scenarios where only the relevant business tables need to be recovered, avoiding the waste of time in full data recovery.
Smart Images
Figure CN120950306A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of financial technology, and in particular to a data processing method and apparatus. Background Technology
[0002] For enterprise applications, data may be lost or corrupted due to various reasons such as hardware failure, software error, and human error. To ensure the normal operation of applications, data backup and recovery are necessary to restore data after it is lost or corrupted, ensuring data availability and integrity, and improving business continuity and stability.
[0003] Existing backup and recovery solutions back up business tables to the database by exporting full or incremental data. Specifically, database logic export tools convert data into backup files for storage. During recovery, the backup files are parsed, and the data is re-imported into the original business tables. However, when the data volume is large or the table structure is complex, the recovery and import process is time-consuming, especially in batch scenarios. When batch node processing anomalies cause data errors, existing backup and recovery methods can only restore the data to its state before the overall batch operation. In other words, current backup and recovery methods increase data recovery time and impact business operation efficiency. Summary of the Invention
[0004] This application provides a data processing method and apparatus to reduce data recovery time and improve business operation efficiency.
[0005] In a first aspect, embodiments of this application provide a data processing method, the method comprising:
[0006] Create a homogeneous backup table in the database corresponding to the business table to be backed up.
[0007] Import the full data of the business table to be backed up into the homogeneous backup table.
[0008] Optionally, before creating a homogeneous backup table corresponding to the business table to be backed up in the database, the method further includes:
[0009] Query the metadata information in the database to obtain the table creation statement of the business table to be backed up;
[0010] Creating a homogeneous backup table corresponding to the business table to be backed up in the database includes:
[0011] Based on the table creation statement, create the isomorphic backup table in the database.
[0012] Optionally, importing the full data of the business table to be backed up into the homogeneous backup table includes:
[0013] The full data of the business table to be backed up is divided into multiple data blocks;
[0014] Determine the backup concurrency level; the backup concurrency level indicates the number of data blocks that are simultaneously imported into the isomorphic backup table;
[0015] Based on the backup concurrency, the multiple data blocks are imported into the homogeneous backup table.
[0016] Optionally, the step of dividing the full data of the business table to be backed up into multiple data blocks includes:
[0017] Based on the amount of the full data and the range of the preset data blocks, the full data is divided into multiple data blocks.
[0018] Optionally, determining the backup concurrency includes:
[0019] The backup concurrency is determined based on the amount of the full data. The backup concurrency is positively correlated with the amount of data; the larger the amount of data, the higher the backup concurrency.
[0020] Optionally, importing the plurality of data blocks into the homogeneous backup table based on the backup concurrency includes:
[0021] Each concurrent backup program imports the multiple data blocks into the homogeneous backup table by competing to process the data blocks.
[0022] Optionally, if there are multiple business tables to be backed up, the step of creating a homogeneous backup table corresponding to the business tables to be backed up in the database includes:
[0023] Create multiple isomorphic backup tables corresponding to each of the business tables to be backed up in the database.
[0024] The step of importing the full data of the business table to be backed up into the homogeneous backup table includes:
[0025] Import the full data of each of the multiple backup business tables into the corresponding isomorphic backup table.
[0026] Optionally, the method further includes:
[0027] When a batch program malfunctions, determine the business table to be recovered corresponding to the malfunctioning batch node;
[0028] The data of the business table to be restored is recovered using data from a homogeneous backup table that matches the business table to be restored.
[0029] Optionally, restoring the data of the business table to be restored using data from a homogeneous backup table that matches the business table to be restored includes:
[0030] Change the name of the table of services to be restored from its original name to a temporary name.
[0031] Change the name of the matching isomorphic backup table from its original name to the original name of the business table to be restored;
[0032] The temporary table name of the business table to be restored is changed to the original table name of the matching isomorphic backup table in order to restore the data of the business table to be restored.
[0033] Secondly, embodiments of this application provide a data processing apparatus, the apparatus comprising:
[0034] Create a unit, used to create a homogeneous backup table corresponding to the business table to be backed up in the database;
[0035] The import unit is used to import the full data of the business table to be backed up into the homogeneous backup table.
[0036] Thirdly, embodiments of this application provide a computer program product, the computer program product comprising: a computer program (also referred to as code or instructions), which, when the computer program is run, causes the computer to perform the method in any of the possible implementations of any of the above aspects.
[0037] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the method in any of the possible implementations of the second aspect described above.
[0038] Fifthly, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the above aspects or possible implementations to be executed. The chip system may be composed of chips or may include chips and other discrete devices.
[0039] This application provides a data processing method and apparatus. The method creates a homogeneous backup table in a database corresponding to the business table to be backed up, and imports all data from the business table to be backed up into the corresponding homogeneous backup table, thus achieving homogeneous backup of only the data in the business table to be backed up. Therefore, when it is necessary to restore the data in the business table to be backed up, the data in the homogeneous backup table can be directly used to replace the data in the business table to be backed up. This method can reduce recovery and backup time when dealing with large amounts of data or complex table structures. Furthermore, in batch scenarios, when batch node processing anomalies cause data errors, this application only needs to restore the relevant business tables. Therefore, this method can reduce data recovery and backup time and improve business operation efficiency. Attached Figure Description
[0040] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0041] Figure 1 A flowchart of a data processing method provided in an embodiment of this application;
[0042] Figure 2 A schematic diagram illustrating the implementation of importing a homogeneous backup table, provided in an embodiment of this application;
[0043] Figure 3 This is a schematic diagram of a backup pipeline provided in an embodiment of this application;
[0044] Figure 4 A flowchart of another data processing method provided in the embodiments of this application;
[0045] Figure 5 This is a schematic diagram of a recovery pipeline provided in an embodiment of this application;
[0046] Figure 6 This is a schematic diagram of the structure of a data processing device provided in an embodiment of this application. Detailed Implementation
[0047] To enable those skilled in the art to better understand the present application, the technical solutions in this embodiment will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0048] As mentioned earlier, existing backup and recovery solutions back up business tables to the database by exporting full or incremental data. Specifically, database logic export tools convert the data into backup files for storage. During the recovery process, the backup files are parsed, and the data is re-imported into the original business tables. However, when the data volume is large or the table structure is complex, the recovery and import process is time-consuming, especially in batch scenarios. When batch node processing anomalies cause data errors, existing backup and recovery methods can only restore the data to the state before the overall batch operation. In other words, current backup and recovery methods increase data recovery time and affect business operation efficiency.
[0049] The inventors have provided a data processing method that creates a homogeneous backup table within the database corresponding to the business table to be backed up. The full data of the business table to be backed up is imported into the corresponding homogeneous backup table, achieving a homogeneous backup of only the data in the business table to be backed up. Thus, when it is necessary to restore the data in the business table to be backed up, the data in the homogeneous backup table can be directly used to replace the data in the business table to be backed up. Therefore, this method can reduce recovery and backup time when dealing with large amounts of data or complex table structures. Furthermore, in batch scenarios, when data errors occur due to processing anomalies in batch nodes, this application only needs to restore the relevant business tables. Therefore, this method can reduce data recovery and backup time and improve business operation efficiency.
[0050] The data processing method provided in the embodiments of this application will be described in detail below.
[0051] First, let's introduce the technical terms used in the embodiments of this application.
[0052] Batch programs consist of multiple batch nodes that automatically execute a series of pre-defined tasks or operations at regular intervals.
[0053] A batch node is an independent unit in a batch program that can execute specific subtasks or suboperations.
[0054] Database metadata information: Data used to describe the structure and attributes of a database, including but not limited to table names, field types, and index information.
[0055] Business tables are a key component in enterprise applications used to store and manage business data. The structure of a business table consists of a series of fields that contain attributes defining data types, such as integers, strings, dates, and timestamps. Business tables include indexing information to help the database quickly locate the business table or the data within it.
[0056] In enterprise-level applications, multiple business tables are involved. These business tables are used to store different business data. For example, in financial applications, business tables include account information, transaction records, invoices, payment vouchers, and other related data.
[0057] These business tables are stored in the database with different table structures, each carrying specific business data, and are linked together through predefined relational models (such as one-to-many and many-to-many relationships) to form a complex but ordered data network. This design allows enterprise applications to perform data query, update, insert, and delete operations efficiently, while also facilitating data analysis and report generation.
[0058] The data processing method provided in this application can be applied to computing devices, such as servers, computers, laptops, and other electronic devices with computing functions. This application does not specifically limit the application.
[0059] The following description uses a computing device as the execution subject to illustrate the data processing method involved in the embodiments of this application.
[0060] Appendix Figure 1 A flowchart of a data processing method provided in this application embodiment is shown. The method includes the following:
[0061] S10, Create a homogeneous backup table corresponding to the business table to be backed up in the database.
[0062] A homogeneous backup table is a backup table with the same structure as the business table to be backed up. By ensuring that the structure of the homogeneous backup table and the business table to be backed up is consistent, accurate data recovery can be achieved by simply swapping the table names during data recovery.
[0063] The business tables to be backed up refer to the business tables stored in the database that need to be backed up. These can be all the business tables in the database or only a portion of them. For example, the database may contain multiple business tables: account information, transaction records, invoices, and payment vouchers. The business tables to be backed up are the account information and invoice tables.
[0064] In this embodiment of the application, if the business table to be backed up includes multiple business tables, a homogeneous backup table needs to be created for each business table. For example, if the business tables to be backed up are an account information business table and an invoice business table, an account information homogeneous backup table is created for the account information business table, and an invoice homogeneous backup table is created for the invoice business table.
[0065] It is understandable that creating homogeneous backup tables for all business tables in advance would cause maintenance difficulties, as the backup tables would need to be synchronized and modified whenever a business table needs to undergo a change in its table structure.
[0066] In view of the above, in this embodiment of the application, the computing device performs data backup at preset intervals (e.g., 1 day). Each time a data backup is performed, the database metadata information is first queried to obtain the table creation statements for the business tables. Then, a backup table is created based on these statements. This method effectively solves the problem of structural consistency between the backup table and the business table. When the structure of the business table to be backed up changes, a corresponding isomorphic backup table is recreated based on the new structure of the business table before backup, thereby strictly ensuring the structural consistency between the business table and the backup table.
[0067] S20. Import the full data of the business table to be backed up into the homogeneous backup table.
[0068] The computing device imports the full data of the business table to be backed up into the corresponding homogeneous backup table to achieve data backup.
[0069] For example, the business tables to be backed up are the account information business table and the invoice business table, and the corresponding isomorphic backup tables are the account information isomorphic backup table and the invoice isomorphic backup table, respectively. The computing device imports the full data of the account information business table into the account information isomorphic backup table, and imports the full data of the invoice business table into the invoice isomorphic backup table, thereby achieving data backup of only the business tables to be backed up.
[0070] In one specific implementation, when importing full data, the computing device can divide the full data into two steps: data blocks and concurrent data block import, and import the full data into the homogeneous backup table. This specifically includes the following steps:
[0071] Step 1: The computing device can divide the full data into multiple data blocks.
[0072] The number of data blocks can be preset to multiple.
[0073] In addition, the computing device can also divide the full data into multiple data blocks based on the data volume and the preset range of data blocks. Assuming the full data is 1TB and the computing device presets the size of each data block to be 10GB, then approximately 100 data blocks are needed to complete the data partitioning.
[0074] By dividing the entire dataset into multiple equal blocks, the processing time of each concurrent program is relatively evenly distributed during backup. This approach makes the backup process more efficient and avoids backup speed bottlenecks caused by uneven data block sizes.
[0075] Specifically, the computing device can pre-scan the business table to be backed up and divide the full data of the business table to be backed up into multiple data blocks evenly according to the data volume.
[0076] Step 2: Calculate the backup concurrency level of the computing device.
[0077] Backup concurrency refers to the number of data blocks processed at the same time. For example, if the backup concurrency is 2, then the number of database blocks processed at the same time is 2.
[0078] It's understandable that a backup concurrency level corresponds to a certain number of concurrent backup operations. For example, a backup concurrency level of 3 corresponds to 3 concurrent backup programs, simultaneously backing up 3 databases.
[0079] The computing device can preset the backup concurrency level.
[0080] Furthermore, computing devices can determine the backup concurrency level based on the total data volume. Backup concurrency is positively correlated with data volume; the larger the data volume, the higher the backup concurrency. This dynamic determination of backup concurrency allows tables with large data volumes to be backed up with higher concurrency, improving backup efficiency, while tables with small data volumes can be backed up with lower concurrency, conserving system resources.
[0081] It should be noted that steps 1 and 2 can be executed simultaneously, or steps 1 can be executed first and then steps 2, or steps 2 can be executed first and then steps 1.
[0082] Step 3: The computing device imports multiple data blocks into the homogeneous backup table based on the backup concurrency.
[0083] For example, if the backup concurrency is 3 and the number of data blocks is 9, the computing device can import multiple data blocks into the homogeneous backup table by performing 3 data block backups at a time.
[0084] For example, appendix Figure 2 The diagram shown is a schematic representation of an implementation of importing a homogeneous backup table according to an embodiment of this application.
[0085] like Figure 2 As shown, the computing device first imports the first three data blocks of the business table into the same location in the isomorphic backup table using backup concurrency 1, backup concurrency 2, and backup concurrency 3. Then, it imports the second three data blocks of the business table into the same location in the isomorphic backup table using backup concurrency 1, backup concurrency 2, and backup concurrency 3. Finally, it imports the third three data blocks of the business table into the same location in the isomorphic backup table using backup concurrency 1, backup concurrency 2, and backup concurrency 3. This process allows multiple data blocks to be imported into the isomorphic backup table.
[0086] In one specific implementation, each concurrent backup program in the computing device can import multiple data blocks into a homogeneous backup table by competing to process the data blocks. That is, each concurrent program will compete to process a data block, insert the data within the data block into the homogeneous backup table, and continue competing for a data block until all data blocks have been processed.
[0087] This backup program processes data blocks through a competition mechanism, ensuring that data blocks can be quickly and efficiently imported into the backup table, while avoiding data conflicts and redundancy, thus significantly improving backup speed.
[0088] The following section introduces another data processing method with a specific implementation example. This method is implemented by creating a backup pipeline. The computing device automatically creates the backup pipeline based on the list of business tables to be backed up. The backup pipeline execution specifically includes the business tables to be backed up and the specific backup process.
[0089] For example, Appendix Figure 3 This is a schematic diagram of a backup pipeline provided in an embodiment of this application. Figure 3 As shown, the processes are executed concurrently in sequence: Upon start, isomorphic backup tables for business table 1, business table 2, ..., and business table n are created simultaneously. Then, data from business table 1 is imported into the corresponding isomorphic backup table, data from business table 2 is imported into the corresponding isomorphic backup table, ..., data from business table n is imported into the corresponding isomorphic backup table. This process continues until the end. Here, n is a positive integer.
[0090] The computing device automatically creates a backup pipeline based on the list of services to be backed up, and schedules the backup pipeline to complete the backup operation daily.
[0091] It should be noted that each business table to be backed up includes two steps, such as step S10 and step S20, which will not be repeated here.
[0092] In summary, this processing method creates a homogeneous backup table corresponding to the business table to be backed up within the database, and imports the full data of the business table to be backed up into the corresponding homogeneous backup table, thus achieving only a homogeneous backup of the data in the business table to be backed up. Therefore, when it is necessary to restore the data in the business table to be backed up, the data in the homogeneous backup table can be directly used to replace the data in the business table to be backed up. Therefore, this method can reduce recovery and backup time when dealing with large amounts of data or complex table structures. Furthermore, in batch scenarios, when batch node processing anomalies cause data errors, this application only needs to restore the affected business tables. Therefore, this method can reduce data recovery and backup time and improve business operation efficiency.
[0093] The data processing method described above is a data backup method. Based on the above data processing method, a data recovery method is also provided below.
[0094] Appendix Figure 4 This is a flowchart illustrating another data processing method provided in an embodiment of this application. The method is explained using a batch processing scenario as an example. Specifically, during execution... Figure 1 In addition to the data backup, the following steps are also included:
[0095] S410. When a batch program malfunctions and data recovery is required, determine the business table to be recovered corresponding to the malfunctioning batch node.
[0096] S420. Create a recovery pipeline based on the business table to be recovered.
[0097] The recovery pipeline instruction executes the process of restoring the data in the business tables to be restored.
[0098] For example, Appendix Figure 5 The diagram shown is a schematic of a recovery pipeline provided in an embodiment of this application. The recovery pipeline includes a table of services to be recovered, a recovery method, and a recovery sequence.
[0099] For example, continue as follows Figure 5As shown, this recovery pipeline includes multiple business tables. The specific recovery order is as follows: first, the data of business table 1, business table 2, ..., business table n is restored; then, the data of business table 1+1, business table 1+2, ..., business table 1+n is restored, and so on, until the data of business table n+1, business table n+2, ..., business table n+n is restored, and so on. The recovery method includes swapping the table names of the business tables with their corresponding isomorphic backup tables. That is, through database table renaming commands, the original business table name is first changed to a temporary table name; then, the isomorphic backup table name is changed to the original business table name; finally, the temporary table name is changed to the isomorphic backup table name, thus swapping the table names of the backup table and the business table. For example, data recovery is achieved by swapping the table names of the isomorphic backup table of business table 1 with business table 1.
[0100] Since database table name swapping is a second-level operation, this recovery device can quickly restore backup data.
[0101] S430. Based on this recovery pipeline, perform business table recovery.
[0102] In summary, in batch scenarios, the recovery device can automatically create a fine-grained recovery pipeline based on the table range affected by abnormal batch nodes, accurately restoring the data to the state before the abnormal nodes ran. After data recovery, subsequent batch nodes can continue running from the point of batch interruption, avoiding the drawback of traditional backup solutions that can only perform coarse-grained full data recovery, requiring the entire batch to be rerun after recovery.
[0103] In addition, this application also provides a data processing apparatus.
[0104] Appendix Figure 6 This application provides a schematic diagram of the structure of a data processing apparatus 600, which includes:
[0105] Create unit 601, which is used to create a homogeneous backup table corresponding to the business table to be backed up in the database;
[0106] Import unit 602 is used to import the full data of the business table to be backed up into the homogeneous backup table.
[0107] Optionally, the device 600 preferably includes an acquisition unit for:
[0108] Query the metadata information in the database to obtain the table creation statement of the business table to be backed up;
[0109] The creation unit 601 is specifically used to: create the isomorphic backup table in the database according to the table creation statement.
[0110] Import unit 602 is specifically used for:
[0111] The full data of the business table to be backed up is divided into multiple data blocks;
[0112] Determine the backup concurrency level; the backup concurrency level indicates the number of data blocks that are simultaneously imported into the isomorphic backup table;
[0113] Based on the backup concurrency, the multiple data blocks are imported into the homogeneous backup table.
[0114] Optionally, the step of dividing the full data of the business table to be backed up into multiple data blocks includes:
[0115] Based on the amount of the full data and the range of the preset data blocks, the full data is divided into multiple data blocks.
[0116] Optionally, determining the backup concurrency includes:
[0117] The backup concurrency is determined based on the amount of the full data. The backup concurrency is positively correlated with the amount of data; the larger the amount of data, the higher the backup concurrency.
[0118] Optionally, importing the plurality of data blocks into the homogeneous backup table based on the backup concurrency includes:
[0119] Each concurrent backup program imports the multiple data blocks into the homogeneous backup table by competing to process the data blocks.
[0120] Optionally, if there are multiple business tables to be backed up, the step of creating a homogeneous backup table corresponding to the business tables to be backed up in the database includes:
[0121] Create multiple isomorphic backup tables corresponding to each of the business tables to be backed up in the database.
[0122] The step of importing the full data of the business table to be backed up into the homogeneous backup table includes:
[0123] Import the full data of each of the multiple backup business tables into the corresponding isomorphic backup table.
[0124] Optionally, the device 600 further includes a recovery unit, configured to: determine the business table to be recovered corresponding to the abnormal batch node when the batch program runs abnormally; and recover the data of the business table to be recovered using data from a homogeneous backup table that matches the business table to be recovered.
[0125] Optionally, restoring the data of the business table to be restored using data from a homogeneous backup table that matches the business table to be restored includes:
[0126] Change the name of the table of services to be restored from its original name to a temporary name.
[0127] Change the name of the matching isomorphic backup table from its original name to the original name of the business table to be restored;
[0128] The temporary table name of the business table to be restored is changed to the original table name of the matching isomorphic backup table in order to restore the data of the business table to be restored.
[0129] This application provides a data processing apparatus that creates a homogeneous backup table corresponding to the business table to be backed up within a database. By importing the full data of the business table to be backed up into the corresponding homogeneous backup table, only the data of the business table to be backed up can be backed up homogeneously. Thus, when it is necessary to restore the data of the business table to be backed up, the data in the homogeneous backup table can be directly used to replace the data in the business table to be backed up. Therefore, this apparatus can reduce recovery and backup times when dealing with large amounts of data or complex table structures. Furthermore, in batch scenarios, when batch node processing anomalies cause data errors, this application only needs to restore the relevant business tables, thereby reducing data recovery and backup times and improving business operation efficiency.
[0130] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.
[0131] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.
[0132] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.
[0133] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.
[0134] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.
[0135] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.
[0136] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.
[0137] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
Claims
1. A data processing method, characterized in that, The method includes: Create a homogeneous backup table in the database corresponding to the business table to be backed up. Import the full data of the business table to be backed up into the homogeneous backup table.
2. The processing method according to claim 1, characterized in that, Before creating a homogeneous backup table corresponding to the business table to be backed up in the database, the method further includes: Query the metadata information in the database to obtain the table creation statement of the business table to be backed up; Creating a homogeneous backup table corresponding to the business table to be backed up in the database includes: Based on the table creation statement, create the isomorphic backup table in the database.
3. The processing method according to claim 1, characterized in that, The step of importing the full data of the business table to be backed up into the homogeneous backup table includes: The full data of the business table to be backed up is divided into multiple data blocks; Determine the backup concurrency level; the backup concurrency level indicates the number of data blocks that are simultaneously imported into the isomorphic backup table; Based on the backup concurrency, the multiple data blocks are imported into the homogeneous backup table.
4. The processing method according to claim 3, characterized in that, The process of dividing the full data of the business table to be backed up into multiple data blocks includes: Based on the amount of the full data and the range of the preset data blocks, the full data is divided into multiple data blocks.
5. The processing method according to claim 3, characterized in that, The determination of backup concurrency includes: The backup concurrency is determined based on the amount of the full data. The backup concurrency is positively correlated with the amount of data; the larger the amount of data, the higher the backup concurrency.
6. The processing method according to claim 3, characterized in that, The step of importing the multiple data blocks into the homogeneous backup table based on the backup concurrency includes: Each concurrent backup program imports the multiple data blocks into the homogeneous backup table by competing to process the data blocks.
7. The processing method according to claim 1, characterized in that, If there are multiple business tables to be backed up, the step of creating a homogeneous backup table corresponding to the business tables to be backed up in the database includes: Create multiple isomorphic backup tables corresponding to each of the business tables to be backed up in the database. The step of importing the full data of the business table to be backed up into the homogeneous backup table includes: Import the full data of each of the multiple backup business tables into the corresponding isomorphic backup table.
8. The processing method according to claim 1, characterized in that, The method further includes: When a batch program malfunctions, determine the business table to be recovered corresponding to the malfunctioning batch node; The data of the business table to be restored is recovered using data from a homogeneous backup table that matches the business table to be restored.
9. The processing method according to claim 8, characterized in that, The step of restoring the data of the business table to be restored using data from a homogeneous backup table that matches the business table to be restored includes: Change the name of the table of services to be restored from its original name to a temporary name. Change the name of the matching isomorphic backup table from its original name to the original name of the business table to be restored; The temporary table name of the business table to be restored is changed to the original table name of the matching isomorphic backup table in order to restore the data of the business table to be restored.
10. A data processing apparatus, characterized in that, The device includes: Create a unit, used to create a homogeneous backup table corresponding to the business table to be backed up in the database; The import unit is used to import the full data of the business table to be backed up into the homogeneous backup table.