Data exchange method, program product, storage medium and equipment

Abstract

The invention provides a data exchange method, a program product, a storage medium and equipment, in the method, basic configuration information for database synchronization is configured at a source end and a destination end, a field containing a file path and a file name in a to-be-synchronized data table is indicated, and when data of the to-be-synchronized database is synchronized, the file path and the file name of the to-be-synchronized data table are synchronized. Collecting a plurality of records of the field, extracting all folder paths according to a collection result, generating a monitoring directory required by a file synchronization strategy according to the folder paths, splitting original single data according to the extracted folder paths, and taking residual paths and file names after splitting as cache information of the to-be-synchronized file; and carrying out file synchronization based on the monitoring directory and the cache information of the file to be synchronized. Therefore, the database field information is associated with the synchronization file, so that files which do not belong to the file path of database form field storage are prevented from being synchronized, and the number of the synchronization files is reduced.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a data exchange method, program product, storage medium, and device. Background Technology

[0002] Data exchange refers to the process of sharing and transmitting data between different systems, devices, or organizations according to rules and protocols. Data exchange in secure isolation devices mainly includes two functions: database synchronization and file synchronization. Database synchronization is used to synchronize form data between the source and destination database servers, while file synchronization is used to synchronize files and folders between the source and destination file servers. However, on secure isolation devices, the database synchronization and file synchronization functions lack coordination. During file synchronization, files located in file paths not belonging to database form fields are also synchronized, creating redundant files. Summary of the Invention

[0003] The purpose of this application is to provide a data exchange method, program product, storage medium, and device, which aims to solve the problem of redundant files occurring during data exchange in the data exchange process of security isolation devices in related technologies.

[0004] Firstly, this application provides a data exchange method applied to a secure isolation device; the method includes: configuring basic configuration information for database synchronization at the source and destination ends, and specifying that the data table to be synchronized contains fields for file paths and file names; activating a database synchronization strategy, summarizing multiple records of the specified fields, extracting all folder paths based on the summarization results, generating a target monitoring directory based on the folder paths, splitting the records based on the folder paths, and obtaining source-end file cache information to be synchronized based on the remaining paths and file names after splitting; and performing a file synchronization operation to synchronize the corresponding files to the destination end based on the target monitoring directory and the source-end file cache information to be synchronized.

[0005] In the above implementation process, a data exchange method for secure isolation devices is provided. Basic configuration information for database synchronization is configured at both the source and destination ends, specifying fields in the data table to be synchronized that contain file paths and filenames. While the data in the database to be synchronized is being synchronized, multiple records for this field are aggregated. Based on the aggregation results, all folder paths are extracted. A monitoring directory required for the file synchronization strategy is generated based on these folder paths. The original single data entries are split based on the extracted folder paths. The remaining paths and filenames after splitting are used as cache information for the files to be synchronized. File synchronization is then performed based on this monitoring directory and the cache information for the files to be synchronized. In this way, database field information is associated with synchronized files, thus avoiding the synchronization of files located at file paths not belonging to the database form field storage, reducing the number of synchronized files.

[0006] Furthermore, in some examples, the basic configuration information for database synchronization includes the configuration information of the database server, the configuration information of the database synchronization strategy, and the synchronization configuration information; the synchronization configuration information includes the table name of the data table to be synchronized and the names of the fields to be synchronized under the table.

[0007] The above implementation process provides specific details on the basic configuration information for database synchronization.

[0008] Furthermore, in some examples, the database synchronization strategy includes: activating the database synchronization strategy when a pre-set full synchronization time is reached, or when the field data in the data table to be synchronized changes.

[0009] In the above implementation process, the database synchronization function supports incremental synchronization and full synchronization. When the field data in the data table to be synchronized changes, it indicates that the source server has performed add, modify, or delete operations on a single record or a single file. At this time, the incremental synchronization operation is started. When the preset full synchronization time is reached, the full synchronization operation is automatically triggered.

[0010] Furthermore, in some examples, the step of performing the file synchronization operation to synchronize the corresponding file to the destination based on the target monitoring directory and the cache information of the file to be synchronized includes: configuring the configuration information of the configuration server on the source end and the destination end, creating a file synchronization policy according to the configuration information and the target monitoring directory; starting the file synchronization policy, and creating cache information of the file to be synchronized at the destination end according to the target monitoring directory; comparing the cache information of the file to be synchronized at the source end and the cache information of the file to be synchronized at the destination end, and performing file synchronization according to the comparison result.

[0011] In the above implementation process, after converting the target monitoring directory and the source-side file cache information to be synchronized, the configuration file synchronization server information is configured, and then a file synchronization policy is created in conjunction with the target monitoring directory. Next, this file synchronization policy is activated, and destination-side file cache information to be synchronized is created based on the target monitoring directory. The source-side and destination-side file cache information to be synchronized are compared to determine the files that need to be updated, and then the file synchronization operation is performed. This effectively solves the problem of overly complex file synchronization corresponding to database storage paths.

[0012] Furthermore, in some examples, the file synchronization based on the comparison result includes: when the source-end file cache information to be synchronized and the destination-end file cache information to be synchronized are inconsistent, marking a synchronizable data identifier in the destination-end file cache information to be synchronized based on the comparison result; the synchronizable data identifier is used to indicate the file that needs to be updated; and file synchronization is performed based on the synchronizable data identifier.

[0013] In the above implementation process, files that need to be updated are identified by difference comparison, and precise synchronization is achieved through tag-driven synchronization, thereby improving synchronization efficiency.

[0014] Furthermore, in some examples, the file synchronization based on the synchronizable data identifier includes: generating a target number of threads based on the synchronizable data identifier; the target number is the minimum of the number of synchronizable data identifiers and the preset number of threads for the file synchronization service; and synchronizing the files corresponding to the synchronizable data identifiers based on the generated threads.

[0015] In the above implementation, during file synchronization, the number of syncable data identifiers is compared with the preset number of threads. If the number of syncable data identifiers is greater than or equal to the preset number of threads, threads are generated according to the preset number of threads; otherwise, threads are generated according to the number of syncable data identifiers. This ensures that the file synchronization threads are independent of the database synchronization business, avoiding the problem of slow form data synchronization progress due to excessively large files to be synchronized on large storage servers.

[0016] Furthermore, in some examples, the process also includes: obtaining the file synchronization result; if the file synchronization result is successful and there are still synchronizable data identifiers in the cache information of the file to be synchronized on the destination end, generating a new thread and synchronizing a new file based on the new thread; if the file synchronization result is unsuccessful, generating a new thread and trying again; when the number of synchronization failures for any file is greater than or equal to the target number, marking the file as a file synchronization failure.

[0017] In the above implementation process, if file synchronization is successful, the current thread resources are immediately released and a new thread is generated to synchronize the new file, thereby improving synchronization efficiency. If synchronization fails, a new thread is generated to try multiple times to increase synchronization reliability. If it still fails after multiple attempts, a file synchronization failure is marked, which makes it easier for the administrator to quickly locate the problem.

[0018] Secondly, this application provides a data exchange device applied to a secure isolation device; the device includes: a configuration module, used to configure basic configuration information for database synchronization at the source and destination ends, and specifying fields in the data table to be synchronized that contain file paths and file names; a generation module, used to initiate a database synchronization strategy, summarize multiple records in the specified fields, extract all folder paths based on the summary results, generate a target monitoring directory based on the folder paths, split the records based on the folder paths, and obtain source-end file cache information to be synchronized based on the remaining paths and file names after splitting; and a synchronization module, used to perform a file synchronization operation to synchronize the corresponding files to the destination end based on the target monitoring directory and the source-end file cache information to be synchronized.

[0019] Thirdly, this application provides an electronic device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the steps of the method described in any of the first aspects.

[0020] Fourthly, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method described in any of the first aspects.

[0021] Fifthly, this application provides a computer program product that, when run on a computer, causes the computer to perform the method described in any of the first aspects.

[0022] Other features and advantages disclosed in this application will be set forth in the following description, or some features and advantages may be inferred from the description or determined without doubt, or may be learned by practicing the above-described technology disclosed in this application.

[0023] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

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

[0025] Figure 1 A flowchart illustrating a data exchange method provided in an embodiment of this application; Figure 2 A schematic diagram of the system architecture involved in a server storage file data exchange scheme provided in an embodiment of this application; Figure 3 A block diagram of a data exchange apparatus provided in an embodiment of this application; Figure 4 This is a structural block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0026] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[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 application, terms such as "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0028] Server-based file storage uses a dedicated server to centrally store and manage files, allowing multiple users to access these files over a network. The mainstream approach is to store file paths on a database server, while the file content itself is stored in a file system or dedicated storage service, such as NAS (Network Attached Storage) or object storage. Data exchange refers to the process of sharing and transmitting data between different systems, devices, or organizations according to rules and protocols. Data exchange in secure isolation devices primarily includes two functions: database synchronization and file synchronization. Database synchronization synchronizes form data between the source and destination database servers, while file synchronization synchronizes files and folders between the source and destination file servers. However, on secure isolation devices, the database and file synchronization functions lack coordination. During file synchronization, files located in file paths not belonging to database form fields are also synchronized, resulting in redundant files.

[0029] To address the aforementioned issues, this application provides a data exchange method for secure isolation devices. While synchronizing data in the database to be synchronized, multiple records in the data table containing file path and filename fields are aggregated. Based on the aggregation results, all folder paths are extracted. A monitoring directory required for the file synchronization strategy is generated based on these folder paths. The original single data entries are then split based on the extracted folder paths, and the remaining paths and filenames are used as cache information for the files to be synchronized. In this way, database field information is correlated with synchronized files, thereby reducing the number of synchronized files.

[0030] The embodiments of this application will be described below: like Figure 1 As shown, Figure 1 This is a flowchart illustrating a data exchange method provided in an embodiment of this application. The method can be applied to a security isolation device. A security isolation device is a network security product designed to achieve physical isolation and secure data exchange between networks of different security levels. It can effectively isolate internal and external networks, protecting the internal network from external threats. In implementation, the security isolation device can be a one-way isolation gateway, a two-way isolation gateway, or an optical gateway, etc. It connects two servers at both ends through two devices, and then configures data synchronization through device policies. The two databases establish database synchronization policies and file synchronization policies for the security isolation device, respectively, achieving synchronization of different data content through different policy configurations.

[0031] The method includes: Step 101: Configure the basic configuration information for database synchronization on the source and destination ends, and specify the fields containing file path and file name in the data table to be synchronized; In this step, the "source" refers to the party initiating the data exchange, which pushes data to the secure isolation device, hoping the data can cross the isolation barrier and reach the destination. Correspondingly, the "destination" refers to the party receiving the data exchange. Taking a server in an enterprise's internal network as an example, when one of the enterprise's servers shares some business data with an external partner, the enterprise's server is the source, and the partner's server is the destination, receiving data transmitted from the enterprise's internal network through the secure isolation device. In this embodiment, basic configuration information for database synchronization is configured at both the source and destination ends, specifying which field in the data table to be synchronized is used to store file paths and filenames.

[0032] In some embodiments, the basic configuration information for database synchronization mentioned in this step may include the configuration information of the database server, the configuration information of the database synchronization strategy, and the synchronization configuration information; the synchronization configuration information includes the table name of the data table to be synchronized and the names of the fields under the table to be synchronized. That is, when implementing the database synchronization function, first configure the relevant information of the database server, including but not limited to the server address, port, username, password, etc.; then create a database synchronization strategy based on the database server configuration information, that is, configure the strategy ID, direction, synchronization method, synchronization action, synchronization type, effective time, primary key modification strategy, etc.; then continue to add synchronization configuration, which needs to specify the table name of the data table to be synchronized and the names of the fields under the table to be synchronized.

[0033] Step 102: Start the database synchronization strategy, summarize multiple records of the field, extract all folder paths according to the summary results, generate the target monitoring directory according to the folder paths, split the records according to the folder paths, and obtain the source-end file cache information to be synchronized according to the remaining paths and file names after splitting. This step refers to: initiating a database synchronization strategy; while synchronizing data in the database to be synchronized, aggregating specified field data from multiple records of the data to be synchronized, extracting common folder paths, and generating the monitoring directory required by the file synchronization strategy; then, splitting the original single data record based on the extracted folder paths, and using the remaining paths and filenames as cache information for the files to be synchronized. For example, if the source database server uploads a file and adds two database entries containing file paths and filenames, namely "a / aa / aaa / a.text" and "a / aa / bbb / b.text", the extracted monitoring directory would be "a / aa", and the source file cache information would be "path: / aaa / , filename: a.text" and "path: / bbb / , filename: b.text". In this way, by aggregating the core elements in the storage path information and generating a file synchronization monitoring directory, the field information in the database is correlated with the actual file synchronization.

[0034] In some embodiments, the database synchronization strategy mentioned in this step may include: activating the database synchronization strategy when a pre-set full synchronization time is reached, or when the field data in the data table to be synchronized changes. That is, the database synchronization function of the security isolation device in this application can support incremental synchronization and full synchronization. Incremental synchronization occurs when the source server performs add, modify, or delete operations on a single record or file, and the field data in the data table to be synchronized changes; at this time, the destination server automatically performs the same operation. Full synchronization, on the other hand, is generated on the destination server after all the field data of the synchronization table or all files on the source server have been read and written. In implementation, a full synchronization time can be preset, and when this full synchronization time is reached, the full synchronization operation is automatically triggered.

[0035] Step 103: Based on the target monitoring directory and the source end file cache information to be synchronized, perform a file synchronization operation to synchronize the corresponding file to the destination end.

[0036] In this embodiment, the stored file paths and file names are summarized, extracted, and split to generate target monitoring directories and source-end file cache information to be synchronized. This links the database service and file service, preventing files that do not belong to the path corresponding to the database form fields from being synchronized during the file synchronization process, thereby simplifying the database files.

[0037] In some embodiments, this step may include: configuring the configuration information of the configuration synchronization server on the source and destination ends; creating a file synchronization policy based on the configuration information and the target monitoring directory; starting the file synchronization policy and creating destination-side file cache information to be synchronized based on the target monitoring directory; comparing the source-side file cache information to be synchronized with the destination-side file cache information to be synchronized, and performing file synchronization based on the comparison result. That is, after completing the conversion of the target monitoring directory and the source-side file cache information to be synchronized, configuration synchronization server-related information can be configured, including but not limited to server address, port, username, and password, and then a file synchronization policy can be created in conjunction with the target monitoring directory, such as configuring policy ID, direction, synchronization method, synchronization type, effective time, and other advanced configurations; then, the file synchronization policy is started, and specific files and folders are searched on the destination server based on the target monitoring directory to obtain specific file attribute information, thereby creating destination-side file cache information to be synchronized; the source-side file cache information to be synchronized with the destination-side file cache information to determine the files that need to be updated, and then performing the file synchronization operation. This effectively solves the problem of overly complex file synchronization corresponding to database storage paths.

[0038] In some embodiments, the aforementioned file synchronization based on comparison results may include: when the source-end file cache information and the destination-end file cache information are inconsistent, marking the destination-end file cache information with a synchronizeable data identifier based on the comparison result; the synchronizeable data identifier is used to indicate the file that needs to be updated; and file synchronization is performed based on the synchronizeable data identifier. That is, by comparing the source and destination file cache information, if they are consistent, it indicates that the source file server and the destination file server have maintained consistent file content, and file synchronization is unnecessary. Conversely, if they are inconsistent, a synchronizeable data identifier is marked for the inconsistent cache information in the destination-end file cache information, indicating that the file corresponding to the cache information needs to be updated, and then file synchronization is performed based on the synchronizeable data identifier. In this way, files that need to be updated are identified through difference comparison, and precise synchronization is driven by marking, thereby improving synchronization efficiency.

[0039] Furthermore, in some embodiments, the aforementioned file synchronization based on the synchronizable data identifier may include: generating a target number of threads based on the synchronizable data identifier; the target number being the minimum of the number of synchronizable data identifiers and a preset number of threads for the file synchronization service; and synchronizing the files corresponding to the synchronizable data identifiers based on the generated threads. In other words, multiple threads can be pre-set for the file synchronization service. During file synchronization, the number of synchronizable data identifiers is compared with the preset number of threads. If the number of synchronizable data identifiers is greater than or equal to the preset number of threads, threads are generated according to the preset number of threads; if the number of synchronizable data identifiers is less than the preset number of threads, threads are generated according to the number of synchronizable data identifiers. This ensures that the file synchronization threads are independent of the database synchronization service, avoiding the problem of slow form data synchronization progress due to excessively large files to be synchronized on large storage servers.

[0040] Furthermore, in some embodiments, the process may also include: obtaining the file synchronization result; if the file synchronization result is successful and the cached information of the file to be synchronized on the destination end still contains synchronizeable data identifiers, generating a new thread and synchronizing the new file based on the new thread; if the file synchronization result fails, generating a new thread and attempting again; when the number of synchronization failures for any file is greater than or equal to the target number, marking the file as having failed synchronization. In other words, during file synchronization, if file synchronization is successful, the current thread resources are immediately released, and a new thread is generated to synchronize the new file, thereby improving synchronization efficiency. If synchronization fails, a new thread is generated to attempt multiple times to increase synchronization reliability. If it still fails after multiple attempts, a file synchronization failure is marked, thus facilitating rapid problem identification by the administrator.

[0041] This application provides a data exchange method for secure isolation devices. Basic configuration information for database synchronization is configured at both the source and destination ends, specifying fields in the data table to be synchronized that contain file paths and filenames. While the data in the database to be synchronized is being synchronized, multiple records for this field are aggregated. Based on the aggregation results, all folder paths are extracted. A monitoring directory required for the file synchronization strategy is generated based on these folder paths. The original single data entries are split based on the extracted folder paths. The remaining paths and filenames after splitting are used as cache information for the files to be synchronized. File synchronization is then performed based on this monitoring directory and the cache information. In this way, database field information is associated with synchronized files, thereby avoiding the synchronization of files located at file paths not belonging to the database form field storage, thus reducing the number of synchronized files.

[0042] To provide a more detailed explanation of the solution in this application, a specific embodiment is described below: This embodiment provides a server storage file data exchange scheme. This scheme can be applied to the design of file simplification during data exchange between large storage servers in secure isolation devices. The system architecture involved in this scheme is as follows: Figure 2 As shown, the security isolation device 21 connects the source server 24 and the destination server 25 via two devices (numbered 22 and 23 in the diagram). Source server 24 includes a source database server 26 and a source file server 27, while destination server 25 includes a destination database server 28 and a destination file server 29. For ease of discussion, the subsystem responsible for data exchange in the security isolation device 21 will be referred to as the "system" below. The system is communicable with the database servers and file servers at both the source and destination ends. The workflow of this solution includes: S201. System startup. Configure database synchronization basic information and synchronization configuration information on both the source and destination ends, specifying that field a in the synchronization fields is the path storage field. S202: Basic configuration required for synchronizing configuration files on both the source and destination ends, excluding the monitoring directory; S203. The source database server system first uploads the file, and then adds two database entries. The entry information includes the file path and file name, for example, "a / aa / aaa / a.text" and "a / aa / bbb / b.text" respectively. S204. When new data is detected, the system enables the database synchronization strategy and records the cache information of the files to be synchronized. This cache information includes, but is not limited to, file path, file name, operation, file update time and other file attributes. S205. The system process splits the cache information of the file to be synchronized into path and file name attributes, converts the path into the monitoring directory required by the file synchronization strategy, and converts the file name attribute into the cache information of the file to be synchronized on the source end; specifically, according to the example, the extracted monitoring directory is "a / aa", and the cache information of the file to be synchronized on the source end is "path: / aaa / , file name: a.text" and "path: / bbb / , file name: b.text"; S206. Create a file synchronization strategy based on the monitoring directory obtained from the transformation, and then start the file synchronization strategy to obtain the cache information of the files to be synchronized on the destination based on the monitoring directory. S207. Compare the source-end file cache information and the destination-end file cache information, and update the synchronizeable data identifier according to the comparison result. The synchronizeable data identifier is used to indicate the file that needs to be updated. Specifically, the source-end file cache information and the destination-end file cache information will be updated in real time according to the synchronization progress. When the file changes during the database synchronization process, the comparison between the two will be inconsistent, and the synchronizeable data identifier needs to be updated. S208. Generate a thread based on the synchronizeable data identifier to perform file synchronization; S209. Log the synchronization status. If the file synchronization is successful, a new thread is generated to synchronize the new file. If the synchronization fails, a new thread is generated to try multiple times. If it continues to fail, a file synchronization failure is marked.

[0043] This embodiment of the solution can invoke file synchronization through database storage fields in a secure isolation device, thereby linking database services and file services, simplifying operations, refining synchronization configuration information, and reducing the number of files to be synchronized.

[0044] Corresponding to the embodiments of the aforementioned methods, this application also provides embodiments of a data exchange apparatus and a terminal for its application: like Figure 3 As shown, Figure 3 This is a block diagram of a data exchange device provided in an embodiment of this application. The device is applied to a secure isolation device; the device includes: Configuration module 31 is used to configure basic configuration information for database synchronization at the source and destination ends, and to specify the fields containing file path and file name in the data table to be synchronized; The generation module 32 is used to start the database synchronization strategy, summarize multiple records of the field, extract all folder paths according to the summary results, generate the target monitoring directory according to the folder paths, split the records according to the folder paths, and obtain the source end file cache information to be synchronized according to the remaining paths and file names after splitting. Synchronization module 33 is used to perform a file synchronization operation to synchronize the corresponding file to the destination based on the target monitoring directory and the source end file cache information to be synchronized.

[0045] The specific implementation process of the functions and roles of each module in the above device can be found in the implementation process of the corresponding steps of the above method, and will not be repeated here.

[0046] This application also provides an electronic device, please refer to [link to application]. Figure 4 , Figure 4 This is a structural block diagram of an electronic device provided in an embodiment of this application. The electronic device may include a processor 410, a communication interface 420, a memory 430, and at least one communication bus 440. The communication bus 440 is used to enable direct communication between these components. In this embodiment, the communication interface 420 of the electronic device is used for signaling or data communication with other node devices. The processor 410 may be an integrated circuit chip with signal processing capabilities.

[0047] The processor 410 described above 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), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor, or the processor 410 can be any conventional processor.

[0048] The memory 430 may be, but is not limited to, random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), etc. The memory 430 stores computer-readable instructions. When these computer-readable instructions are executed by the processor 410, the electronic device can perform the aforementioned operations. Figure 1 The various steps involved in the method implementation examples.

[0049] Alternatively, the electronic device may also include a storage controller and an input / output unit.

[0050] The memory 430, storage controller, processor 410, peripheral interface, and input / output unit are electrically connected directly or indirectly to achieve data transmission or interaction. For example, these components can be electrically connected to each other through one or more communication buses 440. The processor 410 is used to execute executable modules stored in the memory 430, such as software function modules or computer programs included in electronic devices.

[0051] The input / output unit is used to provide users with the ability to create tasks and to set optional start periods or preset execution times for those tasks, thereby enabling user-server interaction. The input / output unit may be, but is not limited to, a mouse and keyboard.

[0052] Understandable. Figure 4 The structure shown is for illustrative purposes only; the electronic device may also include components that are more advanced than those shown. Figure 4 The more or fewer components shown, or having the same Figure 4 The different configurations shown. Figure 4 The components shown can be implemented using hardware, software, or a combination thereof.

[0053] This application also provides a storage medium storing instructions. When the instructions are run on a computer, the computer program is executed by a processor to implement the method described in the method embodiment. To avoid repetition, the method will not be described again here.

[0054] This application also provides a computer program product that, when run on a computer, causes the computer to perform the method described in the method embodiment.

[0055] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can also be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram and / or flowchart, and combinations of blocks in block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0056] In addition, the functional modules in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0057] If the aforementioned functions are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0058] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application. 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.

[0059] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0060] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

Claims

1. A data exchange method, characterized in that, Applied to security isolation equipment; the method includes: Configure the basic configuration information for database synchronization on both the source and destination ends, and specify the fields containing file path and file name in the data table to be synchronized; Start the database synchronization strategy, summarize multiple records of the field, extract all folder paths based on the summary results, generate the target monitoring directory based on the folder paths, split the records based on the folder paths, and obtain the source-end file cache information to be synchronized based on the remaining paths and file names after splitting. Based on the target monitoring directory and the source end file cache information to be synchronized, a file synchronization operation is performed to synchronize the corresponding file to the destination end.

2. The method according to claim 1, characterized in that, The basic configuration information for database synchronization includes the configuration information of the database server, the configuration information of the database synchronization strategy, and the synchronization configuration information; the synchronization configuration information includes the table name of the data table to be synchronized and the names of the fields to be synchronized under the table.

3. The method according to claim 1, characterized in that, The database synchronization strategy includes: When the preset full synchronization time is reached, or when the field data in the data table to be synchronized changes, the database synchronization strategy is activated.

4. The method according to claim 1, characterized in that, The step of performing a file synchronization operation to synchronize the corresponding files to the destination based on the target monitoring directory and the cache information of the files to be synchronized includes: The configuration information of the configuration server is synchronized between the source end and the destination end, and a file synchronization strategy is created based on the configuration information and the target monitoring directory; Start the file synchronization strategy and create destination-end file cache information to be synchronized based on the target monitoring directory; The source end file cache information to be synchronized and the destination end file cache information to be synchronized are compared, and file synchronization is performed based on the comparison result.

5. The method according to claim 4, characterized in that, The file synchronization based on the comparison results includes: When the source-end file cache information to be synchronized and the destination-end file cache information to be synchronized are inconsistent, a synchronizeable data identifier is marked in the destination-end file cache information to be synchronized according to the comparison result; the synchronizeable data identifier is used to indicate the file that needs to be updated. File synchronization is performed based on the synchronizeable data identifier.

6. The method according to claim 4, characterized in that, The process of synchronizing files based on the synchronizeable data identifier includes: Based on the synchronizable data identifiers, a target number of threads are generated; the target number is the minimum of the number of synchronizable data identifiers and the preset number of threads for the file synchronization service. Based on the generated thread, the file corresponding to the synchronizeable data identifier is synchronized.

7. The method according to claim 6, characterized in that, Also includes: Get the file synchronization results; If the file synchronization result is successful, and there are still syncable data identifiers in the cache information of the file to be synchronized on the destination end, a new thread is generated, and the new file is synchronized based on the new thread; If the file synchronization fails, a new thread is generated and the attempt is repeated. When the number of synchronization failures for any file is greater than or equal to the target number, the file is marked as having failed synchronization.

8. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that, It stores a computer program thereon, which, when executed by a processor, implements the method as described in any one of claims 1 to 7.

10. An electronic device, characterized in that, It includes a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method as described in any one of claims 1 to 7.

Images