Multi-system data unified backup method, system, equipment and medium
By adopting a single backup file format in the internal bank system, the error risk and operation and maintenance difficulties in the multi-file backup process are solved, and the problem positioning efficiency and management simplicity are improved.
Patent Information
- Application Number
- CN202410987527.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-23
- Publication Date
- 2024-11-19
AI Technical Summary
In the prior art, there is a risk of errors in the backup and uploading process of multiple files, and multiple files need to be checked when troubleshooting problems, resulting in difficulty in operation and maintenance.
The single backup file format is adopted, including the export format, export data and export results. It is generated and uploaded to the back-end system through the front-end system. The back-end system judges the export results for file processing and archive, reducing the number of files and network transmission.
It reduces the risk of errors in file reading and writing and network transmission, improves problem positioning efficiency, simplifies backup management process, and reduces operation and maintenance difficulties.
Smart Images

Figure CN118981394A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of data processing technology. Specifically, the present invention is applied to the field of self-service terminal systems, and in particular to a method, system, device and medium for unified backup of multi-system data. Background Art
[0002] At present, there are many systems within the bank (ATM monitoring and management system, self-service terminal management system, transaction monitoring system, safe management system, etc.). It is necessary to back up the data of key tables in the database of all systems, and there must be a supervision mechanism for all backup data; the current common solution in the industry is that each system (front-end system) regularly exports DAT data files and DDL of database tables (because each system uses different databases, such as oracle, sqlserver, mysql and db2, so it is necessary to use a common or custom file format to export data and table structure) and upload them to the designated directory of the backup management system, and notify the backup management system (back-end system) by sending a communication message or a successful upload notification file (the file content only indicates that the data of a certain table has been uploaded successfully).
[0003] The above existing methods involve many types of files (DAT, DDL, success notification files), and add multiple file read and write operations and network transmission operations in each stage of front-end system file generation, file upload, and back-end system file processing, which involves technical links such as network status, storage device status, and file operation permissions. Therefore, it can be seen that the solution of multiple files has a considerable risk of error, and when a problem occurs, multiple files must be checked to locate the problem, which also causes difficulties in operation and maintenance. Summary of the invention
[0004] The object of the present invention is to provide a method, system, device and medium for unified backup of multi-system data, thereby solving all or one of the above-mentioned problems existing in the prior art.
[0005] In order to solve the above technical problems, the specific technical solutions of the present invention are as follows: In one aspect, the present invention provides a method for unified backup of multi-system data, comprising the following steps: Configuration backup file format: The file name format and file content format required for backup are configured respectively, and the file content format includes: export format, export data and export result; Backup file processing: Based on the backup file format, a single backup file is used to perform backup processing on a single data table of the system.
[0006] As an improved solution, the configuration of the export format includes: Format description configuration, field description configuration, and data quantity configuration.
[0007] As an improved solution, the field description configuration includes: The field names in the export format are the corresponding field names in the database table; The data type of the export format is a standard SQL data type name; The length of the export format is the data type length or precision, which can be left blank or filled with 0; When the export format type is decimal, fill in the decimal length; The primary key format of the export format is Y or N.
[0008] As an improved solution, the configuration of the exported data includes: Setting each record of the exported data to be exported based on the format description configuration and the field description of the export format; Each record of the exported data is set to be separated by a line break using the format description configuration of the export format.
[0009] As an improved solution, the backup process of a single data table of the system using a single backup file based on the backup file format includes: The front-end system periodically generates backup files and uploads them to the back-end system; The back-end system determines the export result of the backup file.
[0010] As an improved solution, the derived result judgment includes: The back-end system determines whether the export result of generating the backup file is Y; If it is Y, the back-end system analyzes the export format and export data of the backup file; and archives the file according to the analysis result; If it is N, the backup file is deleted and the operation log is recorded.
[0011] As an improved solution, the file archiving according to the parsing situation includes: In response to the success of the back-end system parsing, archiving the backup file or performing an operation of entering the backup library; In response to the backend system parsing failure, the backup file is deleted and an operation log is recorded.
[0012] On the other hand, the present invention also provides a multi-system data unified backup system, comprising: The backup file format configuration module is used to configure the file name format and file content format required for backup, and the file content format includes export format, export data and export result; The backup file processing module is used to: based on the backup file format, use a single backup file to perform backup processing on a single data table of the system.
[0013] On the other hand, the present invention further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the multi-system data unified backup method are implemented.
[0014] On the other hand, the present invention further provides a computer device, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; wherein: The memory is used to store computer programs; The processor is used to execute the steps of the multi-system data unified backup method by running the program stored in the memory.
[0015] The beneficial effects of the technical solution of the present invention are: 1. The multi-system data unified backup method described in the present invention can realize the backup process with only one file, reduce the number of files in the backup process, and reduce the risk of errors in file reading and writing and network transmission. When a backup task fails, it is only necessary to check the generation and transmission process of one file, thereby improving the efficiency of problem locating, thereby solving the problem of easy errors and difficult maintenance in the unified backup management of data of key tables in databases of various systems within the bank, making up for the defects of the existing technology and having high application value.
[0016] 2. The multi-system data unified backup system described in the present invention can realize the multi-system data unified backup method described in the present invention through the mutual cooperation of system modules.
[0017] 3. The computer-readable storage medium described in the present invention can realize the cooperation of the guiding system module, thereby realizing the multi-system data unified backup method described in the present invention, and the computer-readable storage medium described in the present invention also effectively improves the operability of the multi-system data unified backup method.
[0018] 4. The computer device described in the present invention can store and execute the computer-readable storage medium, thereby realizing the multi-system data unified backup method described in the present invention. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0020] Figure 1 It is a flowchart of the method for unified backup of multi-system data according to Embodiment 1 of the present invention; Figure 2 It is a logical flow diagram of the method for unified backup of multi-system data according to Embodiment 1 of the present invention; Figure 3 Schematic diagram of the architecture of the multi-system data unified backup system according to Embodiment 2 of the present invention; Figure 4 is a schematic diagram of the structure of the computer device described in Example 4 of the present invention; The symbols in the accompanying drawings are explained as follows: 1501, processor; 1502, communication interface; 1503, memory; 1504, communication bus. DETAILED DESCRIPTION
[0021] The preferred embodiments of the present invention are described in detail below in conjunction with the accompanying drawings so that the advantages and features of the present invention can be more easily understood by those skilled in the art, thereby making a clearer and more definite definition of the protection scope of the present invention.
[0022] In the description of the present invention, it should be noted that the embodiments described in the present invention are only part of the embodiments of the present invention, rather than all of the embodiments; based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present invention.
[0023] The terms "first", "second", etc. in the specification and claims of this article and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of this article described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment. Example 1
[0024] This embodiment provides a method for unified backup of multi-system data. Figure 1 and Figure 2 As shown, the following steps are included: The core function of the present invention is to summarize all the relevant information required for a single backup task of a database table into one file, reduce the number of files to be processed, greatly reduce the probability of error, and ensure the normal and effective operation of the backup work. Because only a single file needs to be checked, the efficiency of locating the problem when a fault occurs is improved. The specific steps are as follows: S100, Configuration backup file format: In this step, the file name format and file content format required for backup are configured respectively, wherein the file content format includes: export format, export data and export result; Specifically, the configuration backup file name format is: front-end system name_table name_backup date_backup method (incremental / full).DBD; Specifically, the format of export configuration, export data, and export results is described in the following table: Export Format Format description: character set; field separator; line separator; field description: field description 1: field description 2: ... (see notes for specific definitions); data quantity; Exporting Data Each record is exported according to the field description and field separator defined in the "Export Format". Each record is separated by the line break character defined in the "Export Format". Export Results Export result: Y (success) / N (failure); export data verification (optional) Specifically, the annotation configuration of the field description is as follows: the field name is the corresponding field name in the database table; the data type is the standard SQL data type name; the length is the data type length or precision, leave it blank or fill in 0; the decimal is the decimal length when the type is decimal, and leave it blank for other types; whether it is the primary key is Y (yes) or N (no); S200, backup file processing: In this step, based on the above format, a single backup file is used to perform backup processing on a single data table of the system; Specifically, the front-end system periodically generates a “backup file” and uploads it to the back-end system; Specifically, the back-end system determines whether the "export result" of the generated "backup file" is Y; if it is Y, the back-end system parses the "export format" and "export data" of the "backup file"; if it is N, the "backup file" is deleted and the operation log is recorded; Specifically, when the back-end system parses successfully, the back-end system archives the "backup file" or performs an operation into the backup library; when the back-end system parses unsuccessfully, the "backup file" is deleted and an operation log is recorded.
[0025] It should be noted that the above examples are only for explaining the present invention and cannot limit the protection scope of the present invention. Example 2
[0026] This embodiment is based on the same inventive concept as the multi-system data unified backup method described in Embodiment 1, and provides a multi-system data unified backup system, such as Figure 3As shown, including: The backup file format configuration module is used to configure the file name format and file content format required for backup, wherein the file content format includes: export format, export data and export result; Specifically, the configured backup file name format is: front-end system name_table name_backup date_backup method (incremental / full).DBD; Specifically, the formats of the configured backup export format, export data, and export results are described in the following table: Export Format Format description: character set; field separator; line separator; field description: field description 1: field description 2: ... (see notes for specific definitions); data quantity; Exporting Data Each record is exported according to the field description and field separator defined in the "Export Format". Each record is separated by the line break character defined in the "Export Format". Export Results Export result: Y (success) / N (failure); export data verification (optional) Specifically, the field description format is configured as follows: field name is the corresponding field name in the database table; data type is the standard SQL data type name; length is the data type length or precision, leave it blank or fill in 0; decimal is the decimal length when the type is decimal, and leave it blank for other types; whether it is a primary key is Y (yes) or N (no); The backup file processing module is used to: based on the above format, use a single backup file to perform backup processing of a single data table of the system; Specifically, the front-end system periodically generates a “backup file” and uploads it to the back-end system; Specifically, the back-end system determines whether the "export result" of the generated "backup file" is Y; if it is Y, the back-end system parses the "export format" and "export data" of the "backup file"; if it is N, the "backup file" is deleted and the operation log is recorded; Specifically, when the back-end system parses successfully, the back-end system archives the "backup file" or performs an operation into the backup library; when the back-end system parses unsuccessfully, the "backup file" is deleted and an operation log is recorded.
[0027] It should be noted that the above examples are only for explaining the present invention and cannot limit the protection scope of the present invention. Example 3
[0028] This embodiment provides a computer-readable storage medium, including: The storage medium is used to store computer software instructions used to implement the multi-system data unified backup method described in the above-mentioned Example 1, which includes a program for executing the above-mentioned program set for the multi-system data unified backup method; specifically, the executable program can be built into the multi-system data unified backup system described in Example 2, so that the multi-system data unified backup system can implement the multi-system data unified backup method described in Example 1 by executing the built-in executable program.
[0029] In addition, the computer-readable storage medium of this embodiment may adopt any combination of one or more computer-readable storage media, wherein the computer-readable storage medium includes electrical, optical, electromagnetic, infrared or semiconductor systems, devices or components, or any combination thereof. Example 4
[0030] This embodiment provides an electronic device, such as Figure 4 As shown, the electronic device may include: a processor 1501 , a communication interface 1502 , a memory 1503 and a communication bus 1504 , wherein the processor 1501 , the communication interface 1502 , and the memory 1503 communicate with each other via the communication bus 1504 .
[0031] Memory 1503, used for storing computer programs; The processor 1501 is used to implement the steps of the method described in the above-mentioned embodiment 1 when executing the computer program stored in the memory 1503.
[0032] As an embodiment of the present invention, the communication bus mentioned in the above terminal can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.
[0033] As an implementation mode of the present invention, the communication interface is used for communication between the above-mentioned terminal and other devices.
[0034] As an embodiment of the present invention, the memory may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.
[0035] As an embodiment of the present invention, the above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
[0036] Different from the prior art, the present application provides a method, system, device and medium for unified backup of multi-system data, which can implement the backup process with only one file, reduce the number of files in the backup process, and reduce the risk of errors in file reading and writing and network transmission. When a backup task fails, it is only necessary to check the generation and transmission process of one file, thereby improving the efficiency of problem locating, and further solving the problem of easy errors and difficult maintenance in the unified backup management of data of key tables in databases of various systems within the bank, making up for the defects of the prior art and having high application value.
[0037] It should be understood that in the various embodiments of this document, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this document.
[0038] It should also be understood that in the embodiments of this document, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects before and after are in an "or" relationship.
[0039] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this article.
[0040] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0041] In the several embodiments provided herein, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.
[0042] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of this article.
[0043] In addition, each functional unit in each embodiment of this invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of software functional unit.
[0044] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this article is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of this article. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.
[0045] The above descriptions are merely embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.
Claims
1. A method for unified backup of multi-system data. It is characterized in that The following steps are involved: Configuration backup file format: The file name format and file content format required for backup are configured respectively, and the file content format includes: export format, export data and export result; Backup file processing: Based on the backup file format, a single backup file is used to perform backup processing on a single data table of the system.
2. The method for unified backup of multi-system data according to claim 1, Features: The configuration of the export format includes: Format description configuration, field description configuration, and data quantity configuration.
3. The method for unified backup of multi-system data according to claim 2, Features: The field description configuration includes: The field names in the export format are the corresponding field names in the database table; The data type of the export format is a standard SQL data type name; The length of the export format is the data type length or precision, which can be left blank or filled with 0; When the export format type is decimal, fill in the decimal length; The primary key format of the export format is Y or N.
4. The method for unified backup of multi-system data according to claim 2, Features: The configuration of the exported data includes: Setting each record of the exported data to be exported based on the format description configuration and the field description of the export format; Each record of the exported data is set to be separated by line breaks using the format description configuration of the export format.
5. The method for unified backup of multi-system data according to claim 1, Features: The backup process of a single data table of the system using a single backup file based on the backup file format includes: The front-end system periodically generates backup files and uploads them to the back-end system; The back-end system determines the export result of the backup file.
6. The method for unified backup of multi-system data according to claim 5, Features: The derivation result judgment includes: The back-end system determines whether the export result of generating the backup file is Y; If it is Y, the back-end system analyzes the export format and export data of the backup file; and archives the file according to the analysis result; If it is N, the backup file is deleted and the operation log is recorded.
7. The method for unified backup of multi-system data according to claim 6, Features: The file archiving according to the parsing situation includes: In response to the success of the back-end system parsing, archiving the backup file or performing an operation of entering the backup library; In response to the backend system parsing failure, the backup file is deleted and an operation log is recorded.
8. A unified backup system for multi-system data, It is characterized in that include: The backup file format configuration module is used to configure the file name format and file content format required for backup, and the file content format includes export format, export data and export result; The backup file processing module is used to: based on the backup file format, use a single backup file to perform backup processing on a single data table of the system.
9. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the multi-system data unified backup method described in any one of claims 1 to 7 are implemented.
10. A computer device, It is characterized in that It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; wherein: The memory is used to store computer programs; The processor is used to execute the steps of the multi-system data unified backup method according to any one of claims 1 to 7 by running the program stored in the memory.
