System data conversion methods, devices, equipment, storage media, and program products

By synchronizing data to the disaster recovery database in real time during system operation, and performing heterogeneous synchronization and data playback, the problem of business interruption caused by downtime during system upgrades was solved, achieving seamless upgrades and highly reliable data conversion.

CN117573652BActive Publication Date: 2026-11-17CHINA CONSTRUCTION BANK +1
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202311616393.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-11-29
Publication Date
2026-11-17
Estimated Expiration
2043-11-29

AI Technical Summary

Technical Problem

Existing technologies require system downtime for data conversion during system upgrades, leading to business processing interruptions and impacting system availability.

Method used

During the operation of the original system, data is synchronized to the disaster recovery database in real time and heterogeneous synchronization is performed. Data backup is paused, cross-sectional data of the disaster recovery database is extracted, converted to the target system, and data is replayed based on database change information.

Benefits of technology

It enables data conversion to be completed without downtime, avoiding business processing interruptions and improving the reliability of data conversion and the seamlessness of system upgrades.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117573652B_ABST
    Figure CN117573652B_ABST
Patent Text Reader

Abstract

This invention discloses a method, apparatus, device, storage medium, and program product for system data conversion, relating to the field of data migration technology. The method includes: during the operation of the original system, real-time disaster recovery synchronization of the original system's data to a disaster recovery database; heterogeneous synchronization of database change information of the original system; wherein the database change information includes the changed data and the change method; pausing the disaster recovery synchronization of the original system's data and extracting cross-sectional data from the disaster recovery database; converting the cross-sectional data to a target system; and replaying the original system's data to the target system based on the database change information. The technical solution of this invention enables data conversion without system downtime, avoiding business processing interruptions and improving the reliability of data conversion.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of data migration technology, and in particular to a system data conversion method, apparatus, device, storage medium and program product. Background Technology

[0002] With the continuous development of computer technology, software systems are being updated and replaced more frequently. Due to technological updates and ongoing business development, a system may require a comprehensive upgrade after a period of operation. During the upgrade process, the database and table structures used by the upgraded system will change to accommodate the latest computer technologies and consider future business development. To ensure that the data in the original system can continue to be used after the upgrade, data transformation (hereinafter referred to as data conversion) is essential. However, current data conversion solutions require downtime, and the downtime is directly proportional to the system's data capacity and complexity. Downtime will impact the original system's business operations. Summary of the Invention

[0003] This invention provides a system data conversion method, apparatus, device, storage medium, and program product, which ensures that the original system can convert data to the target system without downtime, reducing the impact on the original system's business and improving the reliability of data conversion.

[0004] In a first aspect, embodiments of the present invention provide a method for converting system data, including:

[0005] During the operation of the original system, the data of the original system is synchronized to the disaster recovery database in real time.

[0006] Heterogeneous synchronization of database change information in the original system; wherein, the database change information includes the changed data and the change method;

[0007] Suspend the disaster recovery synchronization of the original system's data and extract the cross-sectional data of the disaster recovery database;

[0008] The cross-sectional data is then transferred to the target system.

[0009] Based on the database change information, the data from the original system is replayed to the target system.

[0010] Secondly, embodiments of the present invention also provide a system data conversion apparatus, the apparatus comprising:

[0011] The data synchronization module is used to synchronize the data of the original system to the disaster recovery database in real time during the operation of the original system.

[0012] A heterogeneous synchronization module is used to perform heterogeneous synchronization of database change information of the original system; wherein, the database change information includes the changed data and the change method;

[0013] The cross-sectional data extraction module is used to pause the disaster recovery synchronization of the original system's data and extract cross-sectional data from the disaster recovery database.

[0014] The data conversion module is used to convert the cross-sectional data to the target system;

[0015] The data playback module is used to play back the data from the original system to the target system based on the database change information.

[0016] Thirdly, embodiments of the present invention also provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the system data conversion method as described in the embodiments of the present invention.

[0017] Fourthly, embodiments of the present invention also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the system data conversion method as described in the embodiments of the present invention.

[0018] Fifthly, embodiments of the present invention also provide a computer program product, including a computer program that, when executed by a processor, implements the system data conversion method as described in the embodiments of the present invention.

[0019] This invention discloses a system data conversion method, apparatus, device, storage medium, and program product, comprising: during the operation of the original system, real-time disaster recovery synchronization of the original system's data to a disaster recovery database; heterogeneous synchronization of database change information of the original system; wherein, the database change information includes the changed data and the change method; pausing the disaster recovery synchronization of the original system's data and extracting cross-sectional data from the disaster recovery database; converting the cross-sectional data to the target system; and replaying the original system's data to the target system based on the database change information. The system data conversion method provided by this invention, by real-time disaster recovery synchronization of the original system's data to a disaster recovery database, heterogeneous synchronization of database change information of the original system, extraction of cross-sectional data from the disaster recovery database, conversion of the cross-sectional data to the target system, and replaying the original system's data to the target system, can ensure that data is converted to the target system without system downtime, avoiding interruption of business processing, reducing the impact on the original system's business, and improving the reliability of data conversion. Attached Figure Description

[0020] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 A flowchart of a system data conversion method provided in an embodiment of the present invention;

[0022] Figure 2 A flowchart of a system data conversion method provided in an embodiment of the present invention;

[0023] Figure 3 An example diagram illustrating a system data conversion method provided in an embodiment of the present invention;

[0024] Figure 4 This is a schematic diagram of the structure of a system data conversion device provided in an embodiment of the present invention;

[0025] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0026] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, and not all of the structures.

[0027] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this invention, terms such as "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0028] The acquisition, storage, use, and processing of data in this application all comply with the relevant provisions of national laws and regulations.

[0029] As software systems are continuously updated, a comprehensive upgrade is required after a period of operation. However, the structure of the database and tables used by the upgraded system will change. To ensure that the original system's data can continue to be used after the upgrade, data conversion is necessary. However, current data conversion solutions require system downtime; a medium-sized system might require 4-5 hours of downtime to complete the conversion process, leading to interruptions in the original system's operations. This invention proposes a data conversion solution that allows for system-wide downtime during upgrades, enabling seamless system upgrades, avoiding business interruptions, and improving the reliability of data conversion.

[0030] Figure 1 This is a flowchart illustrating a system data conversion method provided in an embodiment of the present invention. This embodiment is applicable to situations involving system data conversion. The method can be executed by a system data conversion device, which can be implemented in software and / or hardware, optionally through an electronic device, such as a mobile terminal, PC, or server. Specifically, it includes the following steps:

[0031] S110. During the operation of the original system, the data of the original system is synchronized to the disaster recovery database in real time.

[0032] In this context, the data in the original system can be understood as the data in the corresponding database. During operation, the original system needs to access and process data from this database, and the structure of this data can be recognized and parsed by the original system. Disaster recovery synchronization can be understood as backing up the data from the original system to its disaster recovery database. The original system's database and the disaster recovery database are identical.

[0033] S120. Perform heterogeneous synchronization of database change information in the original system.

[0034] The database change information includes the changed data and the method of change. The method of change can include operations such as adding, deleting, or modifying data in the original system's database.

[0035] One way to perform heterogeneous synchronization of database change information in the original system is to synchronize the database change information generated by the original system to the heterogeneous synchronization system, so that the heterogeneous synchronization system can perform structural transformation on the synchronized data at an appropriate time.

[0036] For example, suppose the data in the original system's database before the change is A. Then, operations such as adding, deleting, and modifying are performed on the original system's database to obtain the data after the change, A'. The data after the change, A', and the change method are then synchronized heterogeneously to the heterogeneous synchronization system.

[0037] S130. Suspend the disaster recovery synchronization of the original system's data and extract the cross-sectional data of the disaster recovery database.

[0038] Cross-sectional data can be understood as a snapshot of the original system at a certain point in time.

[0039] In this embodiment, after heterogeneously synchronizing the database change information of the original system, the operation of backing up the data of the original system to the disaster recovery database is paused, so that the disaster recovery database of the original system is in a static state. At this time, the cross-sectional data in the disaster recovery database is extracted.

[0040] S140. Convert the cross-sectional data to the target system.

[0041] Data transformation can be understood as the transformation of data structure.

[0042] In this embodiment, the cross-sectional data of the disaster recovery database is converted into a structure that the target system can recognize. During the cross-sectional data conversion process, the conversion result of the cross-sectional data is simultaneously transmitted to the database corresponding to the target system.

[0043] For example, suppose the structure of the cross-sectional data of the disaster recovery database before the conversion is B. The structure B is converted into structure B', and the converted result is transmitted to the database corresponding to the target system. Here, structure B' is a structure that the target system can recognize.

[0044] S150. Based on the database change information, replay the data from the original system to the target system.

[0045] The data playback process can be understood as the process of structurally transforming the data in the original system and transferring it to the target system.

[0046] In this embodiment, the method of replaying the data of the original system to the target system based on the database change information can be: converting the changed data in the database change information to the target system.

[0047] Specifically, the modified data in the database change information is converted into a structure that the target system can recognize. During the data conversion process, the conversion result of the modified data is simultaneously transmitted to the database corresponding to the target system.

[0048] For example, suppose the changed data structure in the database change information before the conversion is C. Convert structure C to structure C' and transmit the converted result to the database corresponding to the target system. Here, structure C' is a structure that the target system can recognize.

[0049] The technical solution of this embodiment synchronizes the original system's data to the disaster recovery database in real time during the original system's operation; performs heterogeneous synchronization of database change information of the original system; wherein, the database change information includes the changed data and the change method; pauses the disaster recovery synchronization of the original system's data and extracts cross-sectional data from the disaster recovery database; converts the cross-sectional data to the target system; and replays the data of the original system to the target system based on the database change information. The system data conversion method provided by this embodiment of the invention performs heterogeneous synchronization of database change information of the original system, extracts cross-sectional data from the disaster recovery database, converts the cross-sectional data to the target system, and replays the changed data to the target system, realizing the conversion of data to the target system without system downtime, without causing interruption of business processing, and reducing the impact on the original system's business.

[0050] Figure 2 This is a flowchart illustrating a system data conversion method provided in an embodiment of the present invention. Based on the above embodiment, the concept of time points in the system data conversion method is added, wherein a second time point is greater than a first time point, a third time point is greater than a second time point, and a fourth time point is greater than a third time point. The method includes the following steps:

[0051] S210. Starting from the first point in time, perform heterogeneous synchronization of database change information of the original system.

[0052] The first time point can be any point in time during the process of synchronizing the data from the original system to the disaster recovery database; no limitation is made here. In this embodiment, starting from the first time point, the changed data and change methods of the original system are heterogeneously synchronized to the heterogeneous synchronization system. That is, starting from the first time point, as long as the original system is running, the database change information generated by the original system is heterogeneously synchronized.

[0053] S220. At the second time point, pause the disaster recovery synchronization of the original system's data and extract the cross-sectional data of the disaster recovery database at the second time point.

[0054] The second time point being greater than the first time point can be understood as the second time point being later than the first time point, meaning that the operation of suspending the disaster recovery synchronization of the original system's data is later than the heterogeneous synchronization of the database change information of the original system.

[0055] In this embodiment, the backup of the original system's data to the disaster recovery database is paused at the second time point. That is, starting from the second time point, the disaster recovery database is in a static state. At this time, the cross-sectional data corresponding to the second time point in the disaster recovery database is extracted.

[0056] S230. At the third time point, the cross-sectional data is transferred to the target system.

[0057] The third time point can be understood as either the point in time when the cross-sectional data is completely extracted from the disaster recovery database, or any point in time after the cross-sectional data has been completely extracted from the disaster recovery database. In other words, the operation of transferring the cross-sectional data to the target system can only be performed if the cross-sectional data has been completely extracted from the disaster recovery database.

[0058] In this embodiment, at the third time point, the cross-sectional data of the disaster recovery database is transformed into a data structure, and the transformed result is transmitted to the database corresponding to the target system. At the same time, at the third time point, the data of the original system is continuously synchronized to the disaster recovery database in real time.

[0059] S240. At the fourth time point, the data from the original system is replayed to the target system based on the database change information.

[0060] The fourth time point can be either the time point when the cross-sectional data is completely converted to the target system, or any time point after the cross-sectional data has been completely converted to the target system. In other words, the operation of replaying the data from the original system to the target system based on the database change information can only be performed if the cross-sectional data has been completely converted to the target system.

[0061] In this embodiment, the method of replaying the data of the original system to the target system based on the database change information at the fourth time point can be: filtering the database change information based on the second time point, and replaying the data of the original system to the target system based on the filtered database change information.

[0062] In this embodiment, since the database change information between the first time point and the second time point can be represented by the cross-sectional data in the disaster recovery database, when revisiting the database change information, in order to avoid duplicate processing of the data, the database change information can be filtered based on the second time point.

[0063] Specifically, one way to filter database change information based on the second time point is to filter out database change information that was synchronized heterogeneously before the second time point.

[0064] In this embodiment, since the scope of the heterogeneous synchronized database change information is the data from the first time point to the fourth time point, which already covers the cross-sectional data from the first time point to the second time point, it is necessary to filter out the heterogeneous synchronized database change information before the second time point. Filtering out the heterogeneous synchronized database change information before the second time point can be understood as deleting the heterogeneous synchronized database change information before the second time point, or not replaying the heterogeneous synchronized database change information before the second time point.

[0065] In this embodiment, the database change information from the first time point to the second time point in the heterogeneous synchronization database change information is first filtered out. Then, the changed data in the database change information from the second time point to the fourth time point undergoes data structure transformation, and the transformed result is transmitted to the database corresponding to the target system. This ensures that the data in the original system is completely transformed to the target system while avoiding redundant data transformation and saving computational load.

[0066] The technical solution of this embodiment performs heterogeneous synchronization of database change information of the original system starting from a first time point; at a second time point, it suspends disaster recovery synchronization of the original system's data and extracts cross-sectional data from the disaster recovery database at the second time point; at a third time point, it converts the cross-sectional data to the target system; and at a fourth time point, it replays the data of the original system to the target system based on the database change information. The system data conversion method provided by this embodiment of the invention performs heterogeneous synchronization of database change information at a first time point, extracts cross-sectional data from the disaster recovery database at a second time point, converts the data structure of the cross-sectional data at a third time point and transmits it to the target system, and replays the changed data to the target system at a fourth time point. This reduces the impact on the original system's business and solves the problem of data transfer downtime caused by system upgrades.

[0067] Figure 3 An example diagram of a system data conversion method provided in an embodiment of the present invention is shown below. Figure 3 As shown, during the operation of the original system, the data of the original system is synchronized to the disaster recovery database in real time. At the first time point, heterogeneous synchronization of the original system is initiated, and the heterogeneous synchronization system begins to receive database change information from the original system. At the second time point, the disaster recovery synchronization of the original system is paused, so that the disaster recovery database of the original system is in a static state, and then the cross-sectional data of the disaster recovery database at the second time point is extracted. At the third time point, the cross-sectional data is transformed on the data transfer system, and the transformed result is transmitted to the database corresponding to the target system. During the data transfer process, the original system can still provide services. At the fourth time point, based on the database change information in the heterogeneous synchronization system, the data of the original system is replayed to the target system. The changed data in the database change information from the second time point to the fourth time point is transformed on the data structure, and then the transformed result is transmitted to the database corresponding to the target system.

[0068] Figure 4 This is a schematic diagram of the structure of a system data conversion device provided in an embodiment of the present invention, as shown below. Figure 4 As shown, the device includes:

[0069] The data synchronization module 310 is used to synchronize the data of the original system to the disaster recovery database in real time during the operation of the original system.

[0070] The heterogeneous synchronization module 320 is used to perform heterogeneous synchronization of database change information of the original system; wherein, the database change information includes the changed data and the change method;

[0071] The cross-sectional data extraction module 330 is used to pause the disaster recovery synchronization of the original system's data and extract cross-sectional data from the disaster recovery database.

[0072] Data conversion module 340 is used to convert cross-sectional data to the target system;

[0073] The data playback module 350 is used to play back the data from the original system to the target system based on database change information.

[0074] Optionally, the heterogeneous synchronization module 320 is also used for:

[0075] Starting from the first point in time, heterogeneous synchronization of database change information in the original system is performed.

[0076] Optionally, the cross-sectional data extraction module 330 is also used for:

[0077] At the second time point, the disaster recovery synchronization of the original system's data was paused, and the cross-sectional data of the disaster recovery database at the second time point was extracted.

[0078] Optionally, the data conversion module 340 is also used for:

[0079] The cross-sectional data is transferred to the target system at the third time point.

[0080] Optionally, the data playback module 350 is also used for:

[0081] At the fourth time point, the data from the original system is replayed to the target system based on the database change information.

[0082] Among them, the second time point is greater than the first time point, the third time point is greater than the second time point, and the fourth time point is greater than the third time point.

[0083] Specifically, at the fourth time point, the data from the original system is replayed to the target system based on the database change information, which includes: filtering the database change information based on the second time point, and replaying the data from the original system to the target system based on the filtered database change information.

[0084] Among them, filtering database change information based on the second time point includes filtering out database change information that was synchronized heterogeneously before the second time point.

[0085] Figure 5A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0086] like Figure 5 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0087] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0088] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as system data transformation methods.

[0089] In some embodiments, the system data conversion method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the system data conversion method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the system data conversion method by any other suitable means (e.g., by means of firmware).

[0090] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0091] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0092] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0093] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0094] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0095] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0096] This invention also provides a computer program product, including a computer program that, when executed by a processor, implements the system data conversion method provided in any embodiment of this application.

[0097] In implementing the computer program product, computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0098] Note that the above description is merely a preferred embodiment of the present invention and the technical principles employed. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, the scope of which is determined by the scope of the appended claims.

Claims

1. A method of converting system data, characterized by, include: During the operation of the original system, the data of the original system is synchronized to the disaster recovery database in real time. Starting from the first point in time, heterogeneous synchronization is performed on the database change information of the original system; wherein, the database change information includes the changed data and the change method; At the second time point, the disaster recovery synchronization of the original system's data is paused so that the disaster recovery database is in a stopped state, and the cross-sectional data of the disaster recovery database at the second time point is extracted. The cross-sectional data is converted to the target system at a third time point; wherein the third time point is the time point corresponding to when the cross-sectional data is completely extracted from the disaster recovery database or any time point after the cross-sectional data is completely extracted from the disaster recovery database; At the fourth time point, based on the database change information, the data from the original system is replayed to the target system; Specifically, at the fourth time point, the data from the original system is replayed to the target system based on the database change information, including: Database change information that was synchronized heterogeneously before the second time point will be filtered out. Based on the filtered database change information, the data from the original system is replayed to the target system.

2. The method of claim 1, wherein, The second time point is greater than the first time point; the third time point is greater than the second time point; the fourth time point is greater than the third time point.

3. The method of claim 1, wherein, Also includes: At the third time point, the data from the original system will continue to be synchronized to the disaster recovery database in real time.

4. The method according to claim 1, characterized in that, Based on the database change information, the data from the original system is replayed to the target system, including: The modified data in the database change information is transferred to the target system.

5. A system data conversion device, characterized in that, include: The data synchronization module is used to synchronize the data of the original system to the disaster recovery database in real time during the operation of the original system. The heterogeneous synchronization module is used to perform heterogeneous synchronization of the database change information of the original system starting from a first time point; wherein, the database change information includes the changed data and the change method; The cross-sectional data extraction module is used to pause the disaster recovery synchronization of the original system's data at a second time point, so that the disaster recovery database is in a stopped state, and to extract the cross-sectional data of the disaster recovery database at the second time point. A data conversion module is used to convert the cross-sectional data to the target system at a third time point; wherein, the third time point is the time point corresponding to when the cross-sectional data is completely extracted from the disaster recovery database or any time point after the cross-sectional data is completely extracted from the disaster recovery database; The data replay module is used to replay the data from the original system to the target system based on the database change information at the fourth time point; Specifically, at the fourth time point, the data from the original system is replayed to the target system based on the database change information, including: Database change information that was synchronized heterogeneously before the second time point will be filtered out. Based on the filtered database change information, the data from the original system is replayed to the target system.

6. The apparatus according to claim 5, characterized in that, The data playback module is also used for: The modified data in the database change information is transferred to the target system.

7. An electronic device, characterized in that, The system includes a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, when the processor executes the computer program, it implements a method for converting system data as described in any one of claims 1-4.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by the processor, the program implements the system data conversion method as described in any one of claims 1-4.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the system data conversion method as described in any one of claims 1-4.

Citation Information

Patent Citations

  • Heterogeneous data conversion method, device and apparatus and storage medium

    CN112328675A

  • Disaster recovery construction method and system of electricity utilization information acquisition system and electronic equipment

    CN115756949A