A file synchronization method, system and storage medium

Abstract

Embodiments of the present invention relate to the technical field of data synchronization, and in particular, to a file synchronization method, system, and storage medium. The method includes: when a public cloud test server deployed in a public cloud environment detects a file to be synchronized, synchronizing the file to be synchronized to a public cloud synchronization server deployed in both the public cloud environment and the cloud desktop environment; after receiving the file to be synchronized, the public cloud synchronization server synchronizes the file to be synchronized to a cloud desktop file server deployed in the cloud desktop environment; after receiving the file to be synchronized, the cloud desktop file server synchronizes the file to be synchronized to a private cloud synchronization server deployed in both the cloud desktop environment and the private cloud environment; after receiving the file to be synchronized, the private cloud synchronization server synchronizes the file to be synchronized to a private cloud test server deployed in the private cloud environment. The technical solution of the embodiments of the present invention can achieve automatic synchronization of files to be synchronized in different network environments.

Description

Technical Field

[0001] Embodiments of the present invention relate to the technical field of data synchronization, and in particular, to a file synchronization method, system, and storage medium. Background Art

[0002] Confidentiality and security are very important for banks. Therefore, the control of the test environment within the bank is relatively strict, and the network environments under each test environment are isolated from each other.

[0003] Currently, when developers and testers update files in one of the network environments, they need to manually switch to different network environments to manually upload and / or download files, so as to ensure file synchronization in different network environments.

[0004] However, the existing solutions for file synchronization in each network environment have problems of low efficiency and high error rate. Summary of the Invention

[0005] Embodiments of the present invention provide a file synchronization method, system, and storage medium to achieve the effect of automatic file synchronization in different network environments.

[0006] In a first aspect, embodiments of the present invention provide a file synchronization method, which may include:

[0007] When the public cloud test server deployed in the public cloud environment detects a file to be synchronized, it synchronizes the file to be synchronized to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment;

[0008] After receiving the file to be synchronized, the public cloud synchronization server synchronizes the file to be synchronized to the cloud desktop file server deployed in the cloud desktop environment;

[0009] After receiving the file to be synchronized, the cloud desktop file server synchronizes the file to be synchronized to the private cloud synchronization server deployed in the cloud desktop environment and the private cloud environment;

[0010] After receiving the file to be synchronized, the private cloud synchronization server synchronizes the file to be synchronized to the private cloud test server deployed in the private cloud environment.

[0011] In a second aspect, embodiments of the present invention further provide a file synchronization system, which may include: a public cloud test server deployed in the public cloud environment, a public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment, a cloud desktop file server deployed in the cloud desktop environment, a private cloud synchronization server deployed in the cloud desktop environment and the private cloud environment, and a private cloud test server deployed in the private cloud environment; wherein,

[0012] The public cloud test server is used to synchronize the file to be synchronized to the public cloud synchronization server when the file to be synchronized is detected; the public cloud synchronization server is used to synchronize the file to be synchronized to the cloud desktop file server after receiving the file to be synchronized; the cloud desktop file server is used to synchronize the file to be synchronized to the private cloud synchronization server after receiving the file to be synchronized; the private cloud synchronization server is used to synchronize the file to be synchronized to the private cloud test server after receiving the file to be synchronized.

[0013] Thirdly, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the file synchronization method provided by any embodiment of the present invention is implemented.

[0014] Fourthly, an embodiment of the present invention further provides a computer program product, on which a computer program is stored, and when the computer program is executed by a processor, the file synchronization method provided by any embodiment of the present invention is implemented.

[0015] In the technical solution of the embodiment of the present invention, when the public cloud test server deployed in the public cloud environment detects the file to be synchronized, the file to be synchronized is synchronized to the public cloud synchronization server that can communicate with itself and is deployed in the public cloud environment and the cloud desktop environment; the public cloud synchronization server synchronizes the received file to be synchronized to the cloud desktop file server that can communicate with itself and is deployed in the cloud desktop environment; the cloud desktop file server synchronizes the received file to be synchronized to the private cloud synchronization server that can communicate with itself and is deployed in the cloud desktop environment and the private cloud environment; the private cloud synchronization server synchronizes the received file to be synchronized to the private cloud test server that can communicate with itself and is deployed in the private cloud environment, thereby automatically synchronizing the file to be synchronized in the public cloud environment to the private cloud environment. The above technical solution solves the problems of low efficiency and high error rate caused by manually synchronizing the files to be synchronized in different network environments, and can automatically synchronize the files to be synchronized in multiple non-connected network environments, thereby achieving the effect of automatically synchronizing the files to be synchronized in the remaining network environments after the files to be synchronized are updated in one network environment, effectively ensuring the high consistency of the files to be synchronized in each network environment. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 is a flowchart of a file synchronization method in Embodiment 1 of the present invention;

[0017] Figure 2 is a flowchart of a file synchronization method in Embodiment 2 of the present invention;

[0018] Figure 3 is a schematic diagram of an optional example in the file synchronization method in Embodiment 2 of the present invention;

[0019] Figure 4 It is a flowchart of a file synchronization method in Embodiment 3 of the present invention;

[0020] Figure 5 It is a structural block diagram of a file synchronization system in Embodiment 4 of the present invention. Detailed implementation manners

[0021] The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It can be understood that the specific embodiments described herein are only used to explain the present invention, rather than limiting the present invention. In addition, it should be noted that for the sake of description, only parts related to the present invention rather than all structures are shown in the accompanying drawings.

[0022] Embodiment 1

[0023] Figure 1 It is a flowchart of a file synchronization method provided in Embodiment 1 of the present invention. This embodiment is applicable to the situation of automatically synchronizing files in different network environments. This method can be executed by the file synchronization system provided by the embodiments of the present invention, and the system can be implemented in a software and / or hardware manner.

[0024] See Figure 1 , the method of the embodiment of the present invention specifically includes the following steps:

[0025] S110. When the public cloud test server deployed in the public cloud environment detects a file to be synchronized, it synchronizes the file to be synchronized to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment.

[0026] Among them, the public cloud environment is a type of test environment. The public cloud test server where the public cloud test server is located can be a server deployed in the public cloud environment, such as a server deployed in the development test environment (System Integration Test Case, SIT), a server deployed in the user acceptance test environment (User Acceptance Test, UAT), etc. It is the starting point in the file synchronization system.

[0027] The cloud desktop environment is a development environment. It and the public cloud environment are different network environments. The public cloud synchronization server that can perform file synchronization deployed at the junction of the public cloud environment and the cloud desktop environment can communicate (i.e., file transfer) with the servers deployed in these two network environments respectively.

[0028] After detecting a file to be synchronized in itself, the public cloud test server can synchronize the file to be synchronized to a public cloud synchronization server that can communicate with itself. The file to be synchronized can be a file to be synchronized from the public cloud environment to the private cloud environment, and it can be various types of files, such as script files, character files, picture files, etc., which are not specifically limited here. In practical applications, optionally, development and test personnel can upload the file to be synchronized to the public cloud test server through a bastion host (i.e., the public cloud operation console), so that the public cloud test server can detect the file to be synchronized in itself; further optionally, the file to be synchronized can be synchronized to the public cloud synchronization server through the Secure File Transfer Protocol (SFTP). At this time, the public cloud synchronization server can be an SFTP server; further optionally, an sh script can be deployed on the public cloud test server, so that the public cloud test server can periodically execute a file detection operation based on the sh script to detect whether there is a file to be synchronized.

[0029] S120. After receiving the file to be synchronized, the public cloud synchronization server synchronizes the file to be synchronized to the cloud desktop file server deployed in the cloud desktop environment.

[0030] Among them, the cloud desktop file server can be a server deployed in the cloud desktop environment that can receive and forward files. The cloud desktop file server where it is located is the transfer point of the file synchronization system. In practical applications, optionally, the cloud desktop file server can be a File Transfer Protocol (FTP) server that provides file storage and access services on the Internet.

[0031] After receiving the file to be synchronized, the public cloud synchronization server can synchronize the file to be synchronized to the cloud desktop file server that can communicate with itself. In practical applications, optionally, this synchronization process can be a periodic synchronization process. For example, the public cloud synchronization server synchronizes files at regular preset time intervals.

[0032] S130. After receiving the file to be synchronized, the cloud desktop file server synchronizes the file to be synchronized to the private cloud synchronization server deployed in the cloud desktop environment and the private cloud environment.

[0033] Among them, the private cloud environment is a type of test environment, which is a different environment from the cloud desktop environment. The private cloud synchronization server that can perform file synchronization deployed at the junction of the cloud desktop environment and the private cloud environment can communicate (i.e., file transfer) with the servers deployed in these two network environments respectively.

[0034] On this basis, after receiving the file to be synchronized, the cloud desktop file server can synchronize the file to be synchronized to the private cloud synchronization server. In practical applications, optionally, this synchronization process can be a timed synchronization process. For example, the cloud desktop file server automatically performs a file synchronization every preset time interval.

[0035] S140. After receiving the file to be synchronized, the private cloud synchronization server synchronizes the file to be synchronized to the private cloud test server deployed in the private cloud environment.

[0036] Among them, the private cloud test server can be a server deployed in the private cloud environment, that is, the private cloud test server where it is located can be a server deployed in the private cloud environment, such as a server deployed under SIT, a server deployed under UAT, a server deployed under the Virtualization Technology (VT), etc. It is the end point in the file synchronization system.

[0037] Since communication can be carried out between the private cloud test server and the private cloud synchronization server, after the private cloud synchronization server receives the file to be synchronized, it can synchronize the file to be synchronized to the private cloud test server. In practical applications, optionally, an optional implementation solution for the above synchronization process is: there is a sh script on the private cloud test server for periodically detecting whether there are newly added files to be synchronized on the private cloud synchronization server. Thus, after detecting that there are newly added files to be synchronized on the private cloud synchronization server based on the sh script, it can send a file acquisition request to the private cloud synchronization server to download the newly added files to be synchronized from the private cloud synchronization server.

[0038] It should be noted that taking the private cloud environment as an example, it can include at least one network environment, such as SIT, UAT, VT, etc. The above text is only elaborated in units of a certain network environment in the private cloud environment. In other words, the file to be synchronized can be synchronized to any network environment in the private cloud environment through the above solution. In addition, one set, two sets or multiple sets of independent private cloud test servers can be deployed under each network environment, and sh scripts can be deployed on each set of private cloud test servers respectively, which means that each set of private cloud test servers can independently execute the above solution to obtain the file to be synchronized. The situation of the public cloud environment is similar and will not be elaborated here.

[0039] In the technical solution of the embodiment of the present invention, when the public cloud test server deployed in the public cloud environment detects a file to be synchronized, the file to be synchronized is synchronized to the public cloud synchronization server that is deployed in the public cloud environment and the cloud desktop environment and can communicate with itself; the public cloud synchronization server synchronizes the received file to be synchronized to the cloud desktop file server that is deployed in the cloud desktop environment and can communicate with itself; the cloud desktop file server synchronizes the received file to be synchronized to the private cloud synchronization server that is deployed in the cloud desktop environment and the private cloud environment and can communicate with itself; the private cloud synchronization server synchronizes the received file to be synchronized to the private cloud test server that is deployed in the private cloud environment and can communicate with itself, thereby automatically synchronizing the file to be synchronized in the public cloud environment to the private cloud environment. The above technical solution solves the problems of low efficiency and high error rate caused by manually synchronizing files to be synchronized in different network environments, and can automatically synchronize files to be synchronized in multiple non-connected network environments, thereby achieving the effect of automatically synchronizing files to be synchronized in the remaining network environments after the file to be synchronized is updated in one network environment, effectively ensuring a high degree of consistency of the files to be synchronized in each network environment.

[0040] An optional technical solution for synchronizing the file to be synchronized to the private cloud synchronization server deployed in the cloud desktop environment and the private cloud environment may include: storing the file to be synchronized in the long-term cloud desktop path created under the first database user, and downloading the file to be synchronized stored in the long-term cloud desktop path to the temporary cloud desktop path; logging in to the second database user, where a short-term cloud desktop path is created under the second database user, and the file synchronization interval of the short-term cloud desktop path is shorter than that of the long-term cloud desktop path; synchronizing the file to be synchronized stored on the temporary cloud desktop path to the short-term cloud desktop path through the logged-in second database user; where the temporary cloud desktop path is a path created on the cloud desktop file server where the cloud desktop file server is located, and both the first database user and the second database user are database users on the cloud desktop file server.

[0041] Among them, when the cloud desktop file server is a database server, the first database user is a database user on the cloud desktop file server, which may be a super system user, and the long-term cloud desktop path may be a path created under the first database user. The second database user is also a database user on the cloud desktop file server, and the short-term cloud desktop path may be a path created under the second database user. The paths set on the cloud desktop file server each have their own file synchronization interval duration, which can indicate how often the file to be synchronized stored in the corresponding path is synchronized.

[0042] It should be noted that the files to be synchronized to the private cloud synchronization server are stored in the long-term path of the cloud desktop, and the file synchronization interval of the long-term path of the cloud desktop is longer than that of the short-term path of the cloud desktop. On this basis, in order to speed up the file synchronization speed, the files to be synchronized stored in the long-term path of the cloud desktop can be copied to the short-term path of the cloud desktop. However, these two paths are created under different database users, which makes the files to be synchronized stored under them unable to be directly copied. Accordingly, a temporary path for the cloud desktop is created on the cloud desktop file server, and the files to be synchronized downloaded from the long-term path of the cloud desktop are stored in the temporary path for the cloud desktop; furthermore, log in to the second database user so that the files to be synchronized stored on the temporary path for the cloud desktop can be synchronized to the short-term path of the cloud desktop that can only be used by the second database user through the logged-in second database user, thereby enabling the synchronization of the files to be synchronized through the short-term path of the cloud desktop and speeding up the file synchronization speed. In practical applications, optionally, the above first database user can be khsit, and the temporary path for the cloud desktop can be the BJ-CP path.

[0043] An optional technical solution for synchronizing the files to be synchronized to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment may include: for the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment, sending a file deletion instruction to the public cloud synchronization server so that the public cloud synchronization server deletes the historical synchronization files stored in the public cloud target path according to the received file deletion instruction, where the public cloud target path is a path created on the public cloud synchronization server where the public cloud synchronization server is located; synchronizing the files to be synchronized to the public cloud target path. Among them, the file deletion instruction can be an instruction for deleting the historical synchronization files created under the public cloud target path on the public cloud synchronization server, and the historical synchronization files can be the files to be synchronized synchronized to the public cloud synchronization server at a historical time point. To ensure the correctness during file synchronization, that is, the files to be synchronized being synchronized are the files to be synchronized that need to be synchronized this time, rather than the files to be synchronized that have been synchronized previously, the public cloud test server can first send the file deletion instruction to the public cloud synchronization server to delete the historical synchronization files, and then synchronize the files to be synchronized to the public cloud target path. On this basis, optionally, if the public cloud target path is not created on the public cloud synchronization server, then the public cloud test server can first send a file creation instruction for creating the public cloud target path to the public cloud synchronization server to create the public cloud target path.

[0044] An alternative technical solution, the above file synchronization method may further include: when the cloud desktop file server detects a pre-synchronized file, synchronize the pre-synchronized file to the public cloud synchronization server, so that the public cloud synchronization server synchronizes the received pre-synchronized file to the public cloud test server; the cloud desktop file server synchronizes the pre-synchronized file to the private cloud synchronization server, so that the private cloud synchronization server synchronizes the received pre-synchronized file to the private cloud test server. Among them, the pre-synchronized file may be a file uploaded by developers and testers to the cloud desktop file server and to be synchronized to the public cloud environment and the private cloud environment. Since there is a two-way synchronization function between the cloud desktop environment and the public cloud environment, and the cloud desktop environment has a one-way synchronization function to the private cloud environment, when the cloud desktop file server detects a pre-synchronized file, it can synchronize the pre-synchronized file to the public cloud test server through the public cloud synchronization server, and synchronize the pre-synchronized file to the private cloud test server through the private cloud synchronization server, thereby achieving the effect of high consistency of the pre-synchronized file uploaded by the cloud desktop file server in the public cloud environment and the private cloud environment.

[0045] Embodiment 2

[0046] Figure 2 It is a flowchart of a file synchronization method provided in Embodiment 2 of the present invention. This embodiment is optimized based on the above technical solutions. In this embodiment, optionally, when the public cloud test server deployed in the public cloud environment detects a file to be synchronized, it may include: the public cloud test server deployed in the public cloud environment detects a file to be synchronized in the original path, where the original path is a path created on the public cloud test server where the public cloud test server is located; after synchronizing the file to be synchronized to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment, the above file synchronization method may further include: the public cloud test server deletes the file to be synchronized stored in the original path. Among them, the explanations of the same or corresponding terms as those in the above embodiments will not be repeated here.

[0047] See Figure 2 , the method of this embodiment may specifically include the following steps:

[0048] S210. When the public cloud test server deployed in the public cloud environment detects a file to be synchronized in the original path, synchronize the file to be synchronized stored in the original path to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment, and delete the file to be synchronized stored in the original path, where the original path is a path created on the public cloud test server where the public cloud test server is located.

[0049] Among them, after the file to be synchronized is uploaded to the original path created on the public cloud test server, the public cloud test server can detect the file to be synchronized under the original path. To ensure the accuracy of file synchronization, after synchronizing the file to be synchronized stored under the original path to the public cloud synchronization server, the file to be synchronized stored under the original path can be deleted, thereby avoiding the situation of synchronizing the already synchronized file to be synchronized again next time.

[0050] On this basis, optionally, before the public cloud test server deployed in the public cloud environment detects the file to be synchronized, the above file synchronization method may further include: when the public cloud test server receives a file detection instruction, it detects whether there is a file to be synchronized stored under the original path according to the file detection instruction, where the file detection instruction is an instruction triggered when the current time point is a preset detection time point. Optionally, the detection time point can be determined according to a preset start time point and detection time interval, thereby achieving the effect of detecting the file to be synchronized regularly.

[0051] S220. After receiving the file to be synchronized, the public cloud synchronization server synchronizes the file to be synchronized to the cloud desktop file server deployed in the cloud desktop environment.

[0052] S230. After receiving the file to be synchronized, the cloud desktop file server synchronizes the file to be synchronized to the private cloud synchronization server deployed in the cloud desktop environment and the private cloud environment.

[0053] S240. After receiving the file to be synchronized, the private cloud synchronization server synchronizes the file to be synchronized to the private cloud test server deployed in the private cloud environment.

[0054] In the technical solution of the embodiment of the present invention, after the public cloud test server detects the file to be synchronized under the original path, the file to be synchronized stored under the original path can be synchronized to the public cloud synchronization server and the file to be synchronized stored under the original path can be deleted, thereby avoiding the situation of repeatedly synchronizing the same file to be synchronized.

[0055] On this basis, an optional technical solution for synchronizing the file to be synchronized to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment may include: copying the file to be synchronized from the original path to the created backup path, where the backup path is a path created on the public cloud test server; synchronizing the file to be synchronized stored in the backup path or the original path to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment. When the public cloud synchronization server detects the file to be synchronized on the original path, it can copy the file to be synchronized stored in the original path to the backup path pre-created on the public cloud synchronization server. In this way, even if the file to be synchronized in the original path is deleted subsequently, the file to be synchronized can still be found from the backup path, thus ensuring the traceability of the file to be synchronized.

[0056] On this basis, optionally, the above file synchronization method may further include: the public cloud test server obtains the current timestamp and creates a backup path named based on the current timestamp; synchronizing the file to be synchronized stored in the backup path to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment may include: obtaining the folder to be synchronized storing the file to be synchronized corresponding to the backup path; synchronizing the folder to be synchronized to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment. Creating a backup path named based on the current timestamp means creating a folder to be synchronized whose name includes the current timestamp. Thus, the file to be synchronized copied to the backup path can be understood as the file to be synchronized copied to the folder to be synchronized, and then the folder to be synchronized with the current timestamp can be directly synchronized to the public cloud synchronization server, thereby achieving the effect of being able to clearly determine when the file to be synchronized stored in the folder to be synchronized was synchronized according to the folder to be synchronized. In practical applications, optionally, the current timestamp can be represented in the form of YYYYMMDDHHMI. Further optionally, if the public cloud test server synchronizes the folder to be synchronized to the public cloud synchronization server, then when several subsequent servers perform file synchronization, they can also synchronize the folder to be synchronized, that is, the public cloud synchronization server synchronizes the received folder to be synchronized to the cloud desktop file server, the cloud desktop file server synchronizes the received folder to be synchronized to the private cloud synchronization server, and then the private cloud synchronization server synchronizes the received folder to be synchronized to the private cloud test server, thus ensuring a high degree of consistency of the folder to be synchronized in the public cloud environment and the private cloud environment.

[0057] On this basis, optionally, the above file synchronization method may further include: the public cloud test server obtains a timestamp registration file, adds the current timestamp to the timestamp registration file, and updates the timestamp registration file according to the addition result; synchronizing the folder to be synchronized to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment may include: synchronizing the folder to be synchronized and the timestamp registration file to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment. Among them, the timestamp registration file is a file stored in the public cloud test server and registered with historical timestamps associated with historical synchronized files, and the historical timestamp may be the current timestamp when the historical synchronized file was synchronized. Adding the current timestamp to the timestamp registration file and updating the timestamp registration file according to the addition result ensures the integrity of each timestamp recorded in the timestamp registration file. Furthermore, synchronizing the folder to be synchronized and the timestamp registration file to the public cloud synchronization server together enables the public cloud synchronization server to determine the accurate synchronization time of each folder to be synchronized. In practical applications, optionally, the public cloud test server synchronizes the folder to be synchronized and the timestamp registration file to the public cloud synchronization server. Then, when the subsequent several servers perform file synchronization, they can still synchronize the folder to be synchronized and the timestamp registration file. That is, the public cloud synchronization server synchronizes the received folder to be synchronized and the timestamp registration file to the cloud desktop file server, the cloud desktop file server synchronizes the received folder to be synchronized and the timestamp registration file to the private cloud synchronization server, and then the private cloud synchronization server synchronizes the received folder to be synchronized and the timestamp registration file to the private cloud test server, thereby ensuring a high degree of consistency of the folder to be synchronized and the timestamp registration file in the public cloud environment and the private cloud environment.

[0058] On this basis, optionally, after receiving the file to be synchronized, the private cloud synchronization server synchronizes the file to be synchronized to the private cloud test server deployed in the private cloud environment, which may include: after receiving the folder to be synchronized and the timestamp registration file, the private cloud synchronization server stores the folder to be synchronized and the timestamp registration file in the private cloud temporary path; obtains the timestamp comparison file, and determines whether the target timestamp newly added in the timestamp comparison file is consistent with the current timestamp in the timestamp registration file; if not, synchronizes the folder to be synchronized stored in the private cloud temporary path to the private cloud target path, adds the current timestamp to the timestamp comparison file, and updates the timestamp comparison file according to the addition result; wherein, both the private cloud temporary path and the private cloud target path are paths created on the private cloud synchronization server where the private cloud synchronization server is located. The timestamp comparison file is a file stored on the private cloud synchronization server and recording the historical timestamps of each previously synchronized historical synchronization file. The target timestamp may be the historical timestamp newly added to the timestamp comparison file. Thus, it can be determined whether the file to be synchronized has been synchronized previously by comparing whether the target timestamp is consistent with the target timestamp recorded in the timestamp registration file. Furthermore, when the target timestamp is inconsistent with the current timestamp, it indicates that the file to be synchronized has not been synchronized previously. Thus, the folder to be synchronized stored in the private cloud temporary path can be synchronized to the private cloud target path created on the private cloud synchronization server, so that the private cloud synchronization server can synchronize the folder to be synchronized that has not been synchronized previously and stored under the private cloud target path to the private cloud test server, thereby ensuring the effective synchronization of the folder to be synchronized that has not been synchronized previously. At the same time, the current timestamp can also be added to the timestamp comparison file, thereby ensuring the accuracy of timestamp comparison during subsequent file synchronization.

[0059] To better understand the specific implementation process of the above technical solutions, the following is an exemplary description with specific examples. Taking the above servers as database servers as an example, such as Figure 3As shown, Database A is equivalent to the public cloud test server 1, and Database B is equivalent to the public cloud test server 2. Both are public cloud test servers deployed in the public cloud environment; the public cloud synchronization file server is equivalent to the public cloud synchronization server, the model parameter server is equivalent to the cloud desktop file server, and the private cloud synchronization file server is equivalent to the private cloud synchronization server; Database C is equivalent to the private cloud test server 1, and Database B is equivalent to the private cloud test server 2. Both are private cloud test servers deployed in the private cloud environment. On this basis, a cloud desktop environment can be used to centrally manage the process of files to be synchronized in multiple network environments (such as public cloud environment, private cloud environment, etc.). The newly added files to be synchronized can be periodically synchronized through the synchronization servers in each network environment, and the network environment receives the files to be synchronized at regular intervals, thereby achieving the effect of synchronously downloading the files to be synchronized after a certain delay.

[0060] Embodiment III

[0061] Taking the private cloud test server as a certain database server and the file to be synchronized as a script file for operating on the database on the database server (i.e., the database operation script file) as an example, at least one database server can be deployed in the private cloud environment, and there can be multiple database users under each database server. After synchronizing the database operation script file to each database server, for each database user under a certain database server, it is necessary to log in to the database user before the database operation script file can be executed to synchronously update the database parameters and / or database models in the database associated with the database user. When the above process is manually executed by development and testing personnel, when the number of database servers and / or database users is too large, it is necessary to manually record which database operation script file has been executed by which database user on which database server to ensure consistency. Then, when the synchronization update operation is relatively frequent, it is very easy to make operation mistakes.

[0062] Figure 4It is a flowchart of a file synchronization method provided in Embodiment 3 of the present invention. This embodiment is optimized based on the above technical solutions. In this embodiment, optionally, the file to be synchronized may include a database operation script file. The above file synchronization method may further include: after detecting the database operation script file, the private cloud test server obtains the database username according to the file name of the database operation script file, and obtains the database user password matching the database username in the preset ciphertext; the private cloud test server logs in to the target database user matching the database username and the database user password, and executes the database operation script file through the logged-in target database user to synchronously update the database parameters and / or database model in the target database where the target database user is located. Among them, the explanations of the same or corresponding terms as those in the above embodiments will not be repeated here.

[0063] See Figure 4 , the method of this embodiment may specifically include the following steps:

[0064] S310. When the public cloud test server deployed in the public cloud environment detects the database operation script file, it synchronizes the database operation script file to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment.

[0065] S320. After receiving the database operation script file, the public cloud synchronization server synchronizes the database operation script file to the cloud desktop file server deployed in the cloud desktop environment.

[0066] S330. After receiving the database operation script file, the cloud desktop file server synchronizes the database operation script file to the private cloud synchronization server deployed in the cloud desktop environment and the private cloud environment.

[0067] S340. After receiving the database operation script file, the private cloud synchronization server synchronizes the database operation script file to the private cloud test server deployed in the private cloud environment.

[0068] S350. After detecting the database operation script file, the private cloud test server obtains the database username according to the file name of the database operation script file, and obtains the database user password matching the database username in the preset ciphertext.

[0069] Among them, there is a corresponding relationship between the database operation script file and the database user. The database username can be recorded in the file name of the database operation script file, so the database username can be obtained according to the file name. The preset ciphertext is stored in the private cloud test server, which records the database username and the database user password of each database user, so the database user password matching the database username can be obtained in the preset ciphertext.

[0070] The S360 and the private cloud test server log in to the target database user that matches the database user name and the database user password, and execute the database operation script file through the logged-in target database user to synchronously update the database parameters and / or the database model in the target database where the target database user is located.

[0071] Among them, after obtaining the database user name and the database user password, the private cloud test server can log in to the target database user based on the two, and the target database user can be the database user that matches the above database user name and the database user password among each database user. Furthermore, the database operation script file can be executed through the logged-in target database user, so as to synchronously update the database parameters and / or the database model in the target database where the target database user is located, where the database model can be the Data Definition Language (DDL), and the database parameters can be the Data Manipulation Language (DML).

[0072] It should be noted that for each database user on the private cloud test server, the above steps can be adopted to complete the automatic login of the database user and the automatic execution of the database operation script file.

[0073] In the technical solution of the embodiment of the present invention, when the file to be synchronized is a database operation script file, after detecting the database operation script file, the private cloud test server can obtain the database user name according to the file name of the database operation script file, and then obtain the database user password that matches the database user name in the preset ciphertext, thereby achieving the effect of automatically identifying the database user name of the target database user corresponding to the database operation script file and automatically obtaining the database user password of the target database user; furthermore, log in to the target database user that matches the database user name and the database user password, and execute the database operation script file through the logged-in target database user to synchronously update the database parameters and / or the database model in the target database where the target database user is located, thereby achieving the effect of the automatic login of the target database user and the automatic execution of the database operation script file, and further achieving the effect of the automatic synchronous update of the database parameters and / or the database model.

[0074] On this basis, an alternative technical solution for the above file synchronization method may further include: the private cloud test server determines whether the database operation script file is executed successfully; if so, a preset suffix is added to the file name, and the file name is updated according to the addition result, otherwise the database parameters and / or the database model are rolled back. Among them, when the database operation script file is executed successfully, the fact that the database operation script file has been executed can be identified by adding a preset suffix to the file name, thereby avoiding the situation of repeatedly executing the already executed database operation script file; otherwise, the database parameters and / or the database model can be rolled back, that is, the modified database parameters and / or the database model are restored to the data state before modification. On this basis, optionally, an alarm message can also be sent to prompt the development and test personnel to check.

[0075] On this basis, an alternative technical solution for obtaining the database user name according to the file name of the database operation script file may include: determining whether the file name of the database operation script file contains a preset suffix; if not, the database user name is obtained according to the file name. That is, it is determined whether the database operation script file has been successfully executed by whether the preset suffix is included in the file name, and the database user name is obtained according to the file name when it has not been successfully executed, thereby avoiding the situation of executing the already successfully executed database operation script file again.

[0076] Embodiment 4

[0077] Figure 5 The block diagram of the file synchronization system provided in Embodiment 4 of the present invention is used to execute the file synchronization method provided in any of the above embodiments. This system and the file synchronization method in the above embodiments belong to the same inventive concept. For the details not described in detail in the embodiment of the file synchronization system, reference can be made to the embodiment of the above file synchronization method. See Figure 5, the system may specifically include: a public cloud test server 410 deployed in a public cloud environment, a public cloud synchronization server 420 deployed in a public cloud environment and a cloud desktop environment, a cloud desktop file server 430 deployed in a cloud desktop environment, a private cloud synchronization server 440 deployed in a cloud desktop environment and a private cloud environment, and a private cloud test server 450 deployed in a private cloud environment; among them, the public cloud test server 410 is used to synchronize the file to be synchronized to the public cloud synchronization server 420 when detecting the file to be synchronized; the public cloud synchronization server 420 is used to synchronize the file to be synchronized to the cloud desktop file server 430 after receiving the file to be synchronized; the cloud desktop file server 430 is used to synchronize the file to be synchronized to the private cloud synchronization server 440 after receiving the file to be synchronized; the private cloud synchronization server 440 is used to synchronize the file to be synchronized to the private cloud test server 450 after receiving the file to be synchronized.

[0078] On this basis, in an optional technical solution, the public cloud test server 410 is specifically used for:

[0079] When detecting the file to be synchronized in the original path, synchronize the file to be synchronized stored in the original path to the public cloud synchronization server 420, and delete the file to be synchronized stored in the original path, where the original path is a path created on the public cloud test server where the public cloud test server 410 is located.

[0080] On this basis, optionally, the public cloud test server 410 is specifically used for:

[0081] When detecting the file to be synchronized in the original path, copy the file to be synchronized from the original path to the created backup path, synchronize the file to be synchronized stored in the backup path or the original path to the public cloud synchronization server 420, and delete the file to be synchronized stored in the original path, where the backup path is a path created on the public cloud test server.

[0082] On this basis, optionally, the public cloud test server 410 is further used for:

[0083] Obtain the current timestamp and create a backup path named based on the current timestamp;

[0084] Correspondingly, the public cloud test server 410 is specifically used for:

[0085] When detecting the file to be synchronized in the original path, copy the file to be synchronized from the original path to the created backup path, obtain the folder to be synchronized storing the file to be synchronized corresponding to the backup path, and synchronize the folder to be synchronized to the public cloud synchronization server 420, and delete the file to be synchronized stored in the original path.

[0086] On this basis, optionally, the public cloud test server 410 is further configured to:

[0087] Obtain a timestamp registration file, add the current timestamp to the timestamp registration file, and update the timestamp registration file according to the addition result;

[0088] Correspondingly, the public cloud test server 410 is specifically configured to:

[0089] When a file to be synchronized is detected in the original path, copy the file to be synchronized from the original path to the created backup path, obtain the folder to be synchronized storing the file to be synchronized corresponding to the backup path, and synchronize the folder to be synchronized and the timestamp registration file to the public cloud synchronization server 420, and delete the file to be synchronized stored in the original path.

[0090] On this basis, optionally, the private cloud synchronization server 440 is specifically configured to:

[0091] After receiving the folder to be synchronized and the timestamp registration file, store the folder to be synchronized and the timestamp registration file in the private cloud temporary path; obtain a timestamp comparison file, and determine whether the latest added target timestamp in the timestamp comparison file is consistent with the current timestamp in the timestamp registration file; if not, synchronize the folder to be synchronized stored in the private cloud temporary path to the private cloud target path, and add the current timestamp to the timestamp comparison file, and update the timestamp comparison file according to the addition result; wherein, both the private cloud temporary path and the private cloud target path are paths created on the private cloud synchronization server where the private cloud synchronization server 440 is located.

[0092] Another optional technical solution, the public cloud test server 410 is further configured to:

[0093] Before detecting the file to be synchronized, when receiving a file detection instruction, detect whether there is a file to be synchronized stored in the original path according to the file detection instruction, where the file detection instruction is an instruction triggered when the current time point is a preset detection time point.

[0094] Optionally, the cloud desktop file server 430 is specifically configured to:

[0095] After receiving the file to be synchronized, store the file to be synchronized in the long-term path of the cloud desktop created under the first database user, and download the file to be synchronized stored in the long-term path of the cloud desktop to the temporary path of the cloud desktop; log in to the second database user, where a short-term path of the cloud desktop is created under the second database user, and the file synchronization interval of the short-term path of the cloud desktop is shorter than that of the long-term path of the cloud desktop; synchronize the file to be synchronized stored in the temporary path of the cloud desktop to the short-term path of the cloud desktop through the logged-in second database user; where the temporary path of the cloud desktop is a path created on the cloud desktop file server where the cloud desktop file server 430 is located, and both the first database user and the second database user are database users on the cloud desktop file server.

[0096] Optionally, the public cloud test server 410 is specifically used for:

[0097] When detecting the file to be synchronized, send a file deletion instruction to the public cloud synchronization server 420, so that the public cloud synchronization server 420 deletes the historical synchronized file stored in the public cloud target path according to the received file deletion instruction, where the public cloud target path is a path created on the public cloud synchronization server where the public cloud synchronization server 420 is located; synchronize the file to be synchronized to the public cloud target path.

[0098] Optionally, the public cloud test server 410 is specifically used for:

[0099] When detecting the file to be synchronized, synchronize the file to be synchronized to the public cloud synchronization server 420 deployed in the public cloud environment and the cloud desktop environment through the secure file transfer protocol.

[0100] Optionally, the cloud desktop file server 430 is also used for:

[0101] When detecting the pre-synchronized file, synchronize the pre-synchronized file to the public cloud synchronization server 420, so that the public cloud synchronization server 420 synchronizes the received pre-synchronized file to the public cloud test server 410; synchronize the pre-synchronized file to the private cloud synchronization server 440, so that the private cloud synchronization server 440 synchronizes the received pre-synchronized file to the private cloud test server 450.

[0102] Optionally, the file to be synchronized includes a database operation script file, and the private cloud test server 450 is also used for:

[0103] After detecting the database operation script file, obtain the database username according to the file name of the database operation script file, and obtain the database user password matching the database username from the preset ciphertext; log in to the target database user matching the database username and the database user password, and execute the database operation script file through the logged-in target database user to synchronously update the database parameters and / or the database model in the target database where the target database user is located.

[0104] On this basis, optionally, the private cloud test server 450 is further configured to:

[0105] Determine whether the execution of the database operation script file is successful; if so, add a preset suffix to the file name and update the file name according to the addition result, otherwise roll back the database parameters and / or the database model.

[0106] On this basis, optionally, the private cloud test server 450 is specifically configured to:

[0107] After detecting the database operation script file, determine whether the file name of the database operation script file contains a preset suffix; if not, obtain the database username according to the file name, and obtain the database user password matching the database username from the preset ciphertext; log in to the target database user matching the database username and the database user password, and execute the database operation script file through the logged-in target database user to synchronously update the database parameters and / or the database model in the target database where the target database user is located.

[0108] The file synchronization system provided in the fourth embodiment of the present invention includes a public cloud test server deployed in a public cloud environment, a public cloud synchronization server deployed in a public cloud environment and a cloud desktop environment, a cloud desktop file server deployed in a cloud desktop environment, a private cloud synchronization server deployed in a cloud desktop environment and a private cloud environment, and a private cloud test server deployed in a private cloud environment. Each server cooperates with each other to solve the problems of low efficiency and high error rate caused by manually synchronizing files to be synchronized in different network environments, and can automatically synchronize the files to be synchronized in multiple non-connected network environments, thereby achieving the effect of automatically synchronizing the files to be synchronized in the remaining network environments after the files to be synchronized are updated in one network environment, effectively ensuring a high degree of consistency of the files to be synchronized in each network environment.

[0109] The file synchronization system provided by the embodiments of the present invention can execute the file synchronization method provided by any embodiment of the present invention, and has corresponding functional modules and beneficial effects for executing the method.

[0110] It should be noted that in the embodiments of the above file synchronization system, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of the functional units are only for the convenience of mutual distinction and do not limit the protection scope of the present invention.

[0111] Embodiment Five

[0112] Embodiment Five of the present invention provides a storage medium containing computer-executable instructions, and the computer-executable instructions are used to execute a file synchronization method when executed by a computer processor. The method includes:

[0113] When the public cloud test server deployed in the public cloud environment detects a file to be synchronized, it synchronizes the file to be synchronized to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment;

[0114] After receiving the file to be synchronized, the public cloud synchronization server synchronizes the file to be synchronized to the cloud desktop file server deployed in the cloud desktop environment;

[0115] After receiving the file to be synchronized, the cloud desktop file server synchronizes the file to be synchronized to the private cloud synchronization server deployed in the cloud desktop environment and the private cloud environment;

[0116] After receiving the file to be synchronized, the private cloud synchronization server synchronizes the file to be synchronized to the private cloud test server deployed in the private cloud environment.

[0117] Of course, for a storage medium containing computer-executable instructions provided by the embodiments of the present invention, the computer-executable instructions are not limited to the method operations as described above, and can also execute the relevant operations in the file synchronization methods provided by any embodiments of the present invention.

[0118] From the above description of the embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software and necessary general-purpose hardware. Of course, it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, such as a floppy disk, read-only memory (ROM), random access memory (RAM), flash memory (FLASH), hard disk or optical disc of a computer, etc., including several instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0119] Note that the above is only the preferred embodiment of the present invention and the technical principles applied. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein. Various obvious changes, re-adjustments, and substitutions can be made by those skilled in the art without departing from the protection scope 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. Without departing from the concept of the present invention, more other equivalent embodiments can be included, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A file synchronization method, characterized in that, Including: When the public cloud test server deployed in the public cloud environment detects a file to be synchronized, it synchronizes the file to be synchronized to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment; After receiving the file to be synchronized, the public cloud synchronization server synchronizes the file to be synchronized to the cloud desktop file server deployed in the cloud desktop environment; After receiving the file to be synchronized, the cloud desktop file server synchronizes the file to be synchronized to the private cloud synchronization server deployed in the cloud desktop environment and the private cloud environment; After receiving the file to be synchronized, the private cloud synchronization server synchronizes the file to be synchronized to the private cloud test server deployed in the private cloud environment; Among them, the step of synchronizing the file to be synchronized to the private cloud synchronization server deployed in the cloud desktop environment and the private cloud environment includes: Storing the file to be synchronized in the long-term path of the cloud desktop created under the first database user, and downloading the file to be synchronized stored in the long-term path of the cloud desktop to the temporary path of the cloud desktop; Logging in to the second database user, where a short-term path of the cloud desktop is created under the second database user, and the file synchronization interval of the short-term path of the cloud desktop is shorter than that of the long-term path of the cloud desktop; Synchronizing the file to be synchronized stored on the temporary path of the cloud desktop to the short-term path of the cloud desktop through the logged-in second database user; Among them, the temporary path of the cloud desktop is a path created on the cloud desktop file server where the cloud desktop file server is located, and both the first database user and the second database user are database users on the cloud desktop file server.

2. The method according to claim 1, wherein The public cloud test server deployed in the public cloud environment detecting a file to be synchronized includes: The public cloud test server deployed in the public cloud environment detects a file to be synchronized in the original path, where the original path is a path created on the public cloud test server where the public cloud test server is located; After synchronizing the file to be synchronized to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment, it further includes: The public cloud test server deletes the file to be synchronized stored in the original path.

3. The method according to claim 2, wherein The step of synchronizing the file to be synchronized to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment includes: Copying the file to be synchronized from the original path to the created backup path, where the backup path is a path created on the public cloud test server; Synchronizing the file to be synchronized stored in the backup path or the original path to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment.

4. The method according to claim 3, wherein It further includes: The public cloud test server obtains the current timestamp and creates the backup path named based on the current timestamp; The step of synchronizing the file to be synchronized stored in the backup path to the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment includes: Obtain a to-be-synchronized folder storing the to-be-synchronized file corresponding to the backup path; Synchronize the to-be-synchronized folder to a public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment.

5. The method according to claim 4, wherein It further includes: The public cloud test server obtains a timestamp registration file, adds the current timestamp to the timestamp registration file, and updates the timestamp registration file according to the addition result; The step of synchronizing the to-be-synchronized folder to a public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment includes: Synchronize the to-be-synchronized folder and the timestamp registration file to a public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment.

6. The method according to claim 5, characterized in that After receiving the to-be-synchronized file, the private cloud synchronization server synchronizes the to-be-synchronized file to a private cloud test server deployed in the private cloud environment, including: After receiving the to-be-synchronized folder and the timestamp registration file, the private cloud synchronization server stores the to-be-synchronized folder and the timestamp registration file in a private cloud temporary path; Obtain a timestamp comparison file, and determine whether the target timestamp newly added in the timestamp comparison file is consistent with the current timestamp in the timestamp registration file; If not, synchronize the to-be-synchronized folder stored in the private cloud temporary path to a private cloud target path, add the current timestamp to the timestamp comparison file, and update the timestamp comparison file according to the addition result; Wherein, both the private cloud temporary path and the private cloud target path are paths created on the private cloud synchronization server where the private cloud synchronization server is located.

7. The method according to claim 2, wherein Before the public cloud test server deployed in the public cloud environment detects the to-be-synchronized file, it further includes: When receiving a file detection instruction, the public cloud test server detects whether the to-be-synchronized file is stored in the original path according to the file detection instruction, wherein the file detection instruction is an instruction triggered when the current time point is a preset detection time point.

8. The method according to claim 1, characterized in that The step of synchronizing the to-be-synchronized file to a public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment includes: For the public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment, send a file deletion instruction to the public cloud synchronization server, so that the public cloud synchronization server deletes the historical synchronization file stored under the public cloud target path according to the received file deletion instruction, wherein the public cloud target path is a path created on the public cloud synchronization server where the public cloud synchronization server is located; Synchronize the to-be-synchronized file to under the public cloud target path.

9. The method according to claim 1, characterized in that, The step of synchronizing the to-be-synchronized file to a public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment includes: Synchronize the to-be-synchronized file to a public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment through a secure file transfer protocol.

10. The method according to claim 1, wherein It further includes: When the cloud desktop file server detects a pre-synchronized file, it synchronizes the pre-synchronized file to the public cloud synchronization server, so that the public cloud synchronization server synchronizes the received pre-synchronized file to the public cloud test server; The cloud desktop file server synchronizes the pre-synchronized file to the private cloud synchronization server, so that the private cloud synchronization server synchronizes the received pre-synchronized file to the private cloud test server.

11. The method according to claim 1, characterized in that, The file to be synchronized includes a database operation script file, and also includes: After the private cloud test server detects the database operation script file, it obtains the database user name according to the file name of the database operation script file, and obtains the database user password matching the database user name in the preset ciphertext; The private cloud test server logs in to the target database user matching the database user name and the database user password, and executes the database operation script file through the logged-in target database user to synchronously update the database parameters and / or database model in the target database where the target database user is located.

12. The method according to claim 11, wherein It also includes: The private cloud test server determines whether the database operation script file is executed successfully; If so, add a preset suffix to the file name and update the file name according to the addition result, otherwise roll back the database parameters and / or the database model.

13. The method according to claim 12, wherein The obtaining the database user name according to the file name of the database operation script file includes: Determine whether the file name of the database operation script file contains the preset suffix; If not, obtain the database user name according to the file name.

14. A file synchronization system, characterized in that, Includes: A public cloud test server deployed in a public cloud environment, a public cloud synchronization server deployed in the public cloud environment and the cloud desktop environment, a cloud desktop file server deployed in the cloud desktop environment, a private cloud synchronization server deployed in the cloud desktop environment and the private cloud environment, and a private cloud test server deployed in the private cloud environment; where The public cloud test server is used to synchronize the file to be synchronized to the public cloud synchronization server when detecting the file to be synchronized; The public cloud synchronization server is used to synchronize the file to be synchronized to the cloud desktop file server after receiving the file to be synchronized; The cloud desktop file server is used to synchronize the file to be synchronized to the private cloud synchronization server after receiving the file to be synchronized; The private cloud synchronization server is used to synchronize the file to be synchronized to the private cloud test server after receiving the file to be synchronized; Among them, the cloud desktop file server is specifically used for: After receiving the file to be synchronized, store the file to be synchronized in the cloud desktop long-term path created under the first database user, and download the file to be synchronized stored in the cloud desktop long-term path to the cloud desktop temporary path; Log in to the second database user, under which a short-term path for the cloud desktop is created, and the file synchronization interval of the short-term path for the cloud desktop is shorter than that of the long-term path for the cloud desktop; Synchronize the file to be synchronized stored on the temporary path of the cloud desktop to the short-term path of the cloud desktop through the logged-in second database user; Wherein, the temporary path of the cloud desktop is a path created on the cloud desktop file server where the cloud desktop file server is located, and both the first database user and the second database user are database users on the cloud desktop file server.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the file synchronization method according to any one of claims 1-13.

16. A computer program product, including a computer program, which implements the file synchronization method according to any one of claims 1-13 when executed by a processor.

Images