CN114238255A

CN114238255A - Method and device for synchronizing files, electronic equipment and computer readable storage medium

Info

Publication number: CN114238255A
Application number: CN202111447731.7A
Authority: CN
Inventors: 申骜; 方孝鹏; 徐翔
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2021-11-30
Filing date: 2021-11-30
Publication date: 2022-03-25

Abstract

The invention discloses a method and a device for synchronizing files, electronic equipment and a computer readable storage medium. Relating to the technical field of financial science and technology, the method comprises the following steps: acquiring a file to be synchronized in a source server; determining at least one target server from a plurality of servers; and controlling the remote calling program in the at least one target server to start so that the remote calling program synchronizes the file to be synchronized to the at least one target server. Through the method and the device, the technical problem of low synchronization efficiency caused by manual one-by-one synchronization operation in the prior art is solved.

Description

Method and device for synchronizing files, electronic equipment and computer readable storage medium

Technical Field

The invention relates to the technical field of financial science and technology, in particular to a method and a device for synchronizing files, electronic equipment and a computer readable storage medium.

Background

At present, in a medium-large enterprise, in order to adapt to business development, the number of servers is often rapidly increased along with the increase of business volume; when a cluster server needs to deploy a file or synchronize a file in batch, an operator is often required to manually operate the cluster server one by one, and as the number of servers increases, the manual operation demand on the servers also increases exponentially. Therefore, when the number of servers reaches a certain number, the following problems occur:

(1) and is time consuming. For a single server or a plurality of servers, when meeting the requirements of file deployment or synchronization, the servers can log in one by one to transmit files one by one; however, when the number of servers increases to several tens or even hundreds, the modification of each file will have to take a lot of time for the operator to process one by one.

(2) And labor is consumed. When the number of the servers is large, a lot of manpower is consumed for synchronously deploying a large number of files in the cluster; if some of the changes are required to be completed in a limited amount of time, the enterprise will have to increase the manpower required to handle the transaction.

In view of the above problems, no effective solution has been proposed.

Disclosure of Invention

The embodiment of the invention provides a method and a device for synchronizing files, electronic equipment and a computer readable storage medium, which at least solve the technical problem of low synchronization efficiency caused by manual one-by-one synchronization operation in the prior art.

According to an aspect of an embodiment of the present invention, there is provided a method of synchronizing files, including: acquiring a file to be synchronized in a source server; determining at least one target server from a plurality of servers; and controlling the remote calling program in the at least one target server to start so that the remote calling program synchronizes the file to be synchronized to the at least one target server.

Optionally, the method for synchronizing files further includes: and synchronizing the file to be synchronized to the shared file system before controlling the remote calling program in the at least one target server to start.

Optionally, the method for synchronizing files further includes: after the remote calling program in the at least one target server is controlled to be started, the remote calling program is controlled to acquire the file to be synchronized from the shared file system, and the file to be synchronized is synchronized to the at least one target server.

Optionally, the method for synchronizing files further includes: before determining at least one target server from a plurality of servers, grouping the plurality of servers to obtain at least one group; and storing grouping information of the at least one group into a configuration file, wherein the grouping information at least comprises a server identification and a server address corresponding to the server in the at least one group.

Optionally, the method for synchronizing files further includes: receiving a selection instruction; determining target grouping information corresponding to the target grouping from the configuration file according to the selection instruction; at least one target server corresponding to the target group is determined from the plurality of servers based on the target group information.

Optionally, the method for synchronizing files further includes: before determining at least one target server from a plurality of servers, detecting whether a backup file of a file to be synchronized is a file to be cleaned; when the backup file of the file to be synchronized is the file to be cleaned, cleaning the backup file of the file to be synchronized, and detecting whether a configuration file exists in a source server; when detecting that a configuration file exists in a source server, detecting whether grouping information exists in the configuration file or not; when detecting that the grouping information exists in the configuration file, detecting whether a first log file corresponding to the source server exists or not; and when detecting that the first log file exists in the source server, determining that the source server is in a normal operation state.

Optionally, the method for synchronizing files further includes: acquiring first synchronous operation information of a source server and a first detection result for detecting the source server; storing the first synchronous operation information and the first detection result into a first log file, wherein the first log file is stored in the source server; acquiring second synchronous operation information of at least one target server and a second detection result for detecting the at least one target server; and storing the second synchronous operation information and the detection result into a second log file, wherein the second log file is stored in at least one target server.

According to another aspect of the embodiments of the present invention, there is also provided an apparatus for synchronizing files, including: the receiving module is used for acquiring a file to be synchronized in the source server; a first processing module for determining at least one target server from a plurality of servers; and the second processing module is used for controlling the starting of a remote calling program in at least one target server so as to enable the remote calling program to synchronize the file to be synchronized to the target server.

According to another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the above-mentioned method for synchronizing files when running.

According to another aspect of the embodiments of the present invention, there is also provided an electronic device, including one or more processors; memory for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to carry out a method for running the programs, wherein the programs are arranged such that when run they perform the above-mentioned method of synchronizing files.

According to another aspect of the embodiments of the present invention, there is also provided a computer program product including a computer program/instructions, which when executed by a processor, implement the method for synchronizing files described above.

In the embodiment of the invention, a mode of controlling a remote calling program to synchronize files is adopted, a file to be synchronized in a source server is obtained firstly, at least one target server is determined from a plurality of servers, and finally the remote calling program in the at least one target server is controlled to start, so that the remote calling program synchronizes the file to be synchronized to the at least one target server.

In the process, the remote calling program can automatically synchronize the file to be synchronized to the target server, so that operations such as clicking and copying required by operators during manual synchronization can be effectively replaced, and the synchronization efficiency is improved. Meanwhile, when files need to be synchronized in batch, the source server or other equipment only needs to acquire the files to be synchronized and determine the target server, and then the starting of the remote calling program in each target server can be automatically controlled, so that operations such as clicking and the like required by operators during batch synchronization can be effectively replaced, time wasted by the operators when waiting for synchronization of each server is avoided, and the synchronization efficiency is further improved.

Therefore, the scheme provided by the application achieves the aim of controlling the remote calling program to synchronize the files, achieves the technical effect of improving the synchronization efficiency, and further solves the technical problem of low synchronization efficiency caused by manual one-by-one synchronization operation in the prior art.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

FIG. 1 is a flow diagram of an alternative method of synchronizing files in accordance with an embodiment of the present invention;

FIG. 2 is a schematic diagram of an alternative method of synchronizing files according to an embodiment of the invention;

FIG. 3 is a program directory structure diagram of an alternative method of synchronizing files in accordance with embodiments of the present invention;

FIG. 4 is a logic diagram of an alternative method of synchronizing files in accordance with embodiments of the present invention;

FIG. 5 is a block diagram of an alternative apparatus for synchronizing files in accordance with an embodiment of the present invention;

FIG. 6 is a schematic diagram of an alternative electronic device according to an embodiment of the invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It should be noted that, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for presentation, analyzed data, etc.) referred to in the present disclosure are information and data authorized by the user or sufficiently authorized by each party.

Example 1

In accordance with an embodiment of the present invention, there is provided an embodiment of a method of synchronizing files, it should be noted that the steps illustrated in the flowchart of the figure may be performed in a computer system such as a set of computer-executable instructions and that, although a logical order is illustrated in the flowchart, in some cases, the steps illustrated or described may be performed in an order different than that presented herein.

Fig. 1 is a method of synchronizing files according to an embodiment of the present invention, as shown in fig. 1, the method including the steps of:

step S101, acquiring a file to be synchronized in a source server.

In step S101, a to-be-synchronized file in the source server may be obtained through a device such as the source server, a third-party application system, or a third-party computing device, and preferably, the to-be-synchronized file is obtained through the source server. Optionally, the source server may obtain the file to be synchronized through an absolute path of the file to be synchronized, may also obtain the file to be synchronized through a relative path of the file to be synchronized, and may also obtain the file to be synchronized according to a name of the file to be synchronized or other information having a corresponding relationship with the file to be synchronized.

In this embodiment, as shown in fig. 2 and fig. 3, when a file needs to be synchronized with another server, a source server is manually logged in (e.g., user 1, user 2, and user 3 in fig. 2), the source server receives an instruction manually input to call a file synchronization program servcp.sh in the source server, and the source server receives an absolute path of a file to be synchronized manually input based on the file synchronization program servcp.sh to obtain the file to be synchronized. The source server is any server in the server cluster having a file to be synchronized, and the type of the file to be synchronized includes, but is not limited to, a picture, a video, a document, software, a configuration file, and the like.

It should be noted that, by acquiring the file to be synchronized in the source server, an effective file to be synchronized can be provided for the subsequent file synchronization operation, thereby ensuring the normal operation of the synchronization operation.

Step S102, at least one target server is determined from a plurality of servers.

In step S102, the plurality of servers and the source server may be servers of the same cluster or servers of different clusters, and the operating system of each server may be Linux, Windows, NetWare, or other operating systems. Further, the target servers are servers to be synchronized, such as target server 1, target server 2, target server 3, target server 4, target server N in fig. 2.

Specifically, the source server may determine the at least one target server in a direct or indirect manner by obtaining information input by the operator, for example, when the information input by the operator is a selection instruction (i.e., may be a click from a plurality of servers), the target server may be directly determined; for another example, when the information input by the operator is demand information (that is, information related to a service corresponding to each server and a server type), the target server may be determined by setting a pairing relationship between the demand information and the server in advance in the source server and indirectly determining the target server based on the correspondence relationship. The source server can acquire input information of an operator through the human-computer interaction interface.

It should be noted that, by determining at least one target server from the plurality of servers, an effective synchronization destination can be provided for the file to be synchronized during the subsequent file synchronization operation, thereby ensuring the normal operation of the synchronization operation. In addition, in the application, the target server is selectively determined, so that the method can be more suitable for practical application and has higher applicability.

Step S103, controlling the remote calling program in at least one target server to start, so that the remote calling program synchronizes the file to be synchronized to the at least one target server.

In step S103, a remote calling program remote is set in each target server, and the source server can control the start of the remote calling program.

Specifically, when synchronizing files in batches, if a target server that needs to synchronize files is: the server a, the server B and the server C … … S control the remote calling program in the server a of the target server to start first, and at this time, the remote calling program in the server a is remote. After the synchronization of the server a is finished, the source server may obtain the synchronization finished information of the server a by receiving a synchronization finished signal fed back by the server a, may also obtain the synchronization finished information of the server a by sending an inquiry to the server a, and may also obtain the synchronization finished information of the server a by performing a monitoring operation on the server a in advance to obtain a real-time work progress of the server a or in other manners. And when the source server receives the information of the synchronization end of the server A, the source server controls the remote calling program in the server B in the target server to start, and at the moment, the remote calling program in the server B is remote. After the synchronization of the server B is completed, the server C is started with reference to the operation after the synchronization of the server a is completed. Thus, the above process is repeatedly performed until the S-server completes synchronization. The remote calling program can synchronize the file to be synchronized to the target server through copying.

Optionally, in this embodiment, the remote calling program remote is started through the file synchronization program servcp.sh, and other operations performed in the source server in the method may also be realized through the file synchronization program servcp.sh.

It should be noted that, the files to be synchronized are automatically copied through the remote calling program, so that manual operation can be effectively saved, labor cost is reduced, and synchronization efficiency is improved. Meanwhile, when the synchronous operation of a large number of servers is manually executed, the problem of synchronization missing or synchronization error often occurs, and the remote calling program is automatically called, and the remote calling program is automatically synchronized, so that careless omission caused by the problems of fatigue of operators, unconsciousness and the like can be effectively avoided, and the accuracy of synchronization is ensured.

Based on the schemes defined in steps S101 to S103, it can be known that, in the embodiment of the present invention, a manner of controlling a remote invocation program to perform file synchronization is adopted, and a file to be synchronized in a source server is obtained first, then at least one target server is determined from a plurality of servers, and finally the remote invocation program in the at least one target server is controlled to start, so that the remote invocation program synchronizes the file to be synchronized to the at least one target server.

It is easy to notice that, in the above process, the remote calling program can automatically synchronize the file to be synchronized to the target server, so that operations such as clicking and copying required by an operator during manual synchronization can be effectively replaced, and the synchronization efficiency is improved. Meanwhile, when files need to be synchronized in batch, the source server or other equipment only needs to acquire the files to be synchronized and determine the target server, and then the starting of the remote calling program in each target server can be automatically controlled, so that operations such as clicking and the like required by operators during batch synchronization can be effectively replaced, time wasted by the operators when waiting for synchronization of each server is avoided, and the synchronization efficiency is further improved.

In an alternative embodiment, the source server synchronizes the file to be synchronized to the shared file system before controlling the remote caller in the at least one target server to start.

Optionally, the shared File System performs File sharing between different types of systems through a Network based on a Network File System (NFS).

It should be noted that by using a shared file system, users and programs can access files on a remote system as if they had access to local files, so that the nodes of each computer can conveniently use resources on the network as if they had access to local resources.

In this embodiment, the shared file system is established under the source server, and the shared file system under the source server is mounted to the other servers, and then the file to be synchronized is copied to the designated path in the shared file system in the source server, so that the file sharing between the source server and the target server can be realized. Wherein, the designated path is configured in the configuration file servcp. It should be noted that the file sharing between the source server and the target server may also be implemented by establishing the shared file system in another server, and then mounting the shared file system in the other server to the source server and the other servers.

It should be noted that, based on the characteristics of the network file system, when the source server copies the file to be synchronized to the specified path of the shared file system, it can copy the file to be synchronized by executing the "CP" instruction, thereby avoiding the problem that the user affiliation group and authority of the file to be synchronized are easily changed due to the execution of the "SCP" instruction when the synchronization operation is directly performed between the source server and the target server, and further improving the accuracy of the present application in synchronization.

In an alternative embodiment, the source server may log into the at least one target server before controlling the remote caller in the at least one target server to start. Specifically, the source server may find the target servers according to the acquired server addresses corresponding to the target servers and log in the target servers in batch. In the login process, the source server can log in each target server without secret based on the ssh-keygen function of the Linux operating system. Optionally, the encryption algorithm may be an RSA algorithm, and the RSA public key cryptosystem is a cryptosystem in which different encryption keys and decryption keys are used, and it is computationally infeasible to derive the decryption key from a known encryption key.

By logging in each target server, the source server can normally control the start of the remote calling program in the target server.

In an alternative embodiment, after controlling the remote caller in the at least one target server to start, the source server controls the remote caller to acquire the file to be synchronized from the shared file system and synchronize the file to be synchronized to the at least one target server.

Optionally, in this embodiment, each target server is internally hung with a shared file system that is the same as that in the source server, so that after the source server synchronizes the file to be synchronized to the shared file system, the target server can read the updated content in the shared file system, thereby successfully synchronizing the file to be synchronized to the target server.

It should be noted that, based on the characteristics of the network file system, the target server can also effectively avoid the problem that the user affiliation group and the authority of the file to be synchronized change when the file to be synchronized is copied to the local, thereby ensuring that the user affiliation group and the authority of the file to be synchronized can be kept consistent before and after the file to be synchronized is synchronized to the target server from the source server, and further ensuring the accuracy of the application in synchronization.

In an alternative embodiment, before determining at least one target server from the plurality of servers, the source server groups the plurality of servers to obtain at least one group, and then stores group information of the at least one group into the configuration file, wherein the group information at least includes a server identifier and a server address corresponding to the server in the at least one group.

Optionally, the source server may group a plurality of servers to obtain at least one group. In this embodiment, the servers may be grouped according to the service requirement information, for example, the servers may be grouped according to different platforms, or the servers may be grouped according to other factors or requirements in actual applications, so as to determine the target server subsequently.

Optionally, after the source server may group the plurality of servers to obtain at least one group, the source server may further store the grouping information of the at least one group in the configuration file. The grouping and grouping information can be customized by an operator, and the grouping information at least comprises a server identification and a server address corresponding to the server in at least one group. Profile is stored in the source server, and the server identifiers in the grouping information correspond to the server addresses one to one. The server id may be an alphabet, a number, or other form to characterize the corresponding server, and the server address is used to find the target server in the subsequent synchronization process.

It should be noted that, by grouping a plurality of servers and storing grouping information corresponding to the grouping into a configuration file, an operator can conveniently and quickly select a large number of servers, and meanwhile, the operator can conveniently modify and synchronize related files of the same service, so that labor is saved and synchronization speed is increased.

In an alternative embodiment, the source server may determine at least one target server from a plurality of servers. Specifically, the source server may receive a selection instruction, determine target grouping information corresponding to the target grouping from the configuration file according to the selection instruction, and then determine at least one target server corresponding to the target grouping from the plurality of servers based on the target grouping information.

Optionally, after the file to be synchronized in the source server is acquired, the source server may read the configuration file to acquire the grouping information, and then display the grouping corresponding to the grouping information through a manual interaction interface for an operator to select. The operator can select the packet to be synchronized by manually clicking the packet, can select the packet to be synchronized by inputting the packet sequence number, and can select the packet to be synchronized by voice or other methods. And then, the source server receives the selection instruction input by the operator through a human-computer interaction interface. The selection instruction is characterized in that the information which can represent the selection content and is input by the operator can include the server identification corresponding to the server in the group selected by the operator.

It should be noted that, after receiving the selection instruction, the source server may check the validity of the selection instruction, for example, when the operator selects a packet by inputting a packet serial number, the source server searches for the packet serial number input by the operator, and if a corresponding packet can be found, the selection instruction is an effective instruction; if the corresponding group cannot be found, the selection instruction is an invalid instruction, so that the content input by the operator can be ensured to be valid content.

Optionally, after receiving the selection instruction, the source server may find, in the configuration file, the target group information corresponding to the group in the selection instruction according to the server identifier or other identifiers included in the operation instruction.

Further, after acquiring the target grouping information corresponding to the target grouping, the source server determines at least one target server corresponding to the target grouping from the plurality of servers based on the target grouping information. Specifically, the source server may determine the target server based on the server identifier included in the target group information, and then based on the server address included in the target group information, the source server may successfully find the target server and control the remote calling program corresponding to the target server.

It should be noted that, by determining the target server according to the operation instruction, that is, selectively determining the target server, the method can be more suitable for practical application and has higher applicability.

In an alternative embodiment, as shown in fig. 4, before determining at least one target server from the plurality of servers, the source server detects whether the backup file of the file to be synchronized is the file to be cleaned, and thereafter, when the backup file of the file to be synchronized is the file to be cleaned, the source server cleans the backup file of the file to be synchronized, and detecting whether the source server has a configuration file, and when detecting that the source server has the configuration file, the source server detects whether the configuration file has grouping information, and then, when detecting that the grouping information exists in the configuration file, the source server detects whether a first log file corresponding to the source server exists, and finally, upon detecting that the source server exists in the first log file, it is determined that the source server is in a normal operation state, wherein the first log may be servcp.

Optionally, after the file to be synchronized is acquired, the source server determines whether a backup file of the file exists in the source server, further determines a backup date of the backup file if the backup file exists, determines whether the backup file is a unique backup if the backup date of the backup file is more than 30 days, and determines that the backup file of the file to be synchronized exists as the backup file of the file to be cleaned if the backup file is not the unique backup. Further, when the backup files with the backup date less than 30 days exist, the backup files with the backup date more than 30 days are all files to be cleaned; and when the backup files with the backup date less than 30 days do not exist, the backup files with the backup date more than 30 days are the files which are not to be cleaned, and the rest of the backup files are the files to be cleaned. Wherein the backup files are stored in the origin server or in the shared file system. In the above process, the setting of the backup date of the backup file may be different according to different actual situations.

Further, when the backup file of the file to be synchronized is the file to be cleaned, the source server may clean the backup file of the file to be synchronized and detect whether the source server has the configuration file. In this embodiment, when the cleaning of the backup file is completed or no backup file needs to be cleaned, the source server detects whether the configuration file exists in the source server. The source server can determine whether the configuration file exists or not by inquiring the name of the configuration file, and when the configuration file does not exist in the source server, fault prompt information can be output to prompt an operator.

Optionally, when detecting that the configuration file exists in the source server, the source server may detect whether the grouping information exists in the configuration file. The source server can judge whether the grouping information exists in the configuration file by reading the configuration content of the configuration file and identifying a server identifier or a server address or other methods related to the grouping information, and can output fault prompt information to prompt an operator when detecting that the grouping information does not exist in the configuration file.

Optionally, when detecting that the grouping information exists in the configuration file, the source server may detect whether a first log file corresponding to the source server exists; when detecting that the first log file exists in the source server, determining that the source server is in a normal operation state; the source server can determine whether the first log file exists by inquiring the name of the first log file, reading the content of the first log file and judging whether the content of the first log file is empty, can output fault prompt information to prompt an operator when detecting that the first log file does not exist, and can determine that the source server is in a normal operation state and execute the next operation when detecting that the first log file exists.

Before at least one target server is determined from a plurality of servers, the backup files are checked and cleaned, so that the adverse effect of the application on the hard disk space in the server or the shared file system can be prevented; the configuration file and the grouping information are checked to ensure that an operator can normally select server groups; by checking the first log file, the synchronization operation record in the source server and the checking and judging result in the synchronization operation process are all recorded in detail, and further the tracing in the later period is ensured. From this, guaranteed the security, stability and the traceability of this application.

In an optional embodiment, after determining at least one target server from a plurality of servers, detecting whether an input format of a file to be synchronized is correct, then detecting whether a file to be synchronized exists in a source server when the input format of the file to be synchronized is correct, then detecting whether a shared file system exists when the file to be synchronized exists in the source server, and finally determining that the source server is in a normal operation state when the shared file system exists.

Optionally, after determining at least one target server from the plurality of servers, the source server may detect whether the input format of the file to be synchronized is correct. In this embodiment, the source server acquires the file to be synchronized by receiving the manually input absolute path of the file to be synchronized, and thus, checks the input format of the file to be synchronized to check whether the first character of the manually input content is "/". It should be noted that, in the Linux operating system, the initial character of the absolute path is "/". Specifically, the partial codes for judging the input format of the file to be synchronized are as follows:

when the input format of the file to be synchronized is detected to be incorrect, the source server can output fault prompt information to prompt an operator. In this embodiment, the failure information is "the file path or the file name is incorrect, please check". Meanwhile, it should be noted that, when the manner of acquiring the file to be synchronized is changed, the above-mentioned specific determination method for the input format of the file to be synchronized is also changed.

Optionally, when detecting that the input format of the file to be synchronized is correct, the source server may detect whether the file to be synchronized exists inside the source server; in this embodiment, the source server may determine whether the source server has the file to be synchronized by querying the name of the file to be synchronized under the corresponding path, and specifically, based on the shell language, part of codes for detecting whether the source server has the file to be synchronized are as follows:

when detecting that the file to be synchronized does not exist in the source server, the source server can output fault prompt information to prompt an operator. In this embodiment, the failure information is "the required synchronization file is not found, please check".

Optionally, when detecting that the file to be synchronized exists in the source server, the source server may detect whether the shared file system exists. In this embodiment, based on a specified path about a shared file system preset in a configuration file servcp.profile, the shared file system is searched in a source server, and if it is detected that the shared file system does not exist in the source server, the source server automatically creates the specified path about the shared file system preset in the configuration file servcp.profile, specifically, based on a shell language, a part of codes for creating the shared file system are as follows:

it should be noted that, after the source server completes creating the shared file system, the created shared file system may be mounted to the target server, so as to ensure that the target server can normally view the file to be synchronized, which is synchronized to the shared file system by the source server.

Thus, when it is determined that the shared file system exists in the origin server, it is determined that the origin server is in a normal operation state. And after determining that the source server is in a normal operation state based on the detection, synchronizing the file to be synchronized to a specified path of the shared file system.

It should be noted that, after at least one target server is determined from a plurality of servers, by checking the input format of the file to be synchronized, checking whether the file to be synchronized exists in the source server, and checking whether the shared file system exists, it can be ensured that the file to be synchronized can be successfully synchronized to the shared file system in the subsequent synchronization operation, thereby ensuring the normal execution of the method.

In an optional embodiment, after synchronizing the file to be synchronized to the shared file system, the source server may detect whether the file to be synchronized exists in the shared file system, and determine that the file to be synchronized is correctly synchronized when detecting that the file to be synchronized exists in the shared file system. The source server can judge whether the file to be synchronized exists in the shared file system by inquiring the name of the file to be synchronized under the specified path in the shared file system. Specifically, based on the shell language, whether a part of codes of a file to be synchronized exists in the shared file system is judged as follows:

it should be noted that, the files to be synchronized in the shared file system are verified, so as to further ensure that the subsequent target servers can be successfully synchronized, thereby ensuring the stability of the method in the synchronization process.

In an optional embodiment, after controlling the remote invocation program in the at least one target server to start, the remote invocation program may detect whether a second log file corresponding to the at least one target server exists, then, when detecting that the second log file exists in the at least one target server, the remote invocation program detects whether a parameter received by the at least one target server is correct, then, when detecting that the parameter received by the at least one target server is correct, the remote invocation program detects whether a file to be synchronized exists in an assigned path of the shared file system, and finally, when detecting the file to be synchronized, it determines that synchronization between the at least one target server and the shared file system is possible. Log, wherein the second log file may be remote.

Optionally, in this embodiment, the remote calling program may determine whether the second log file exists by querying a name of the second log file, reading content of the second log file, and determining whether the content of the second log file is empty, and when it is detected that the second log file does not exist, the remote calling program may record the fault information to the second log file.

Optionally, when detecting that the second log file exists in the at least one target server, the remote caller may detect whether the parameter received by the at least one target server is correct. In this embodiment, the parameter received by the at least one target server is a parameter passed in the synchronous file command output by the source server, the remote calling program may determine whether the parameter is correct by querying a format or a number of the parameter, and when it is detected that the parameter received by the at least one target server is incorrect, the remote calling program may record the failure information in the second log file. The parameters received by at least one target server at least comprise a designated path of the shared file system and the name of a file to be synchronized.

Optionally, when detecting that the parameter received by the at least one target server is correct, the remote calling program may detect whether a file to be synchronized exists in a specified path of the shared file system. In this embodiment, the remote calling program queries the name of the file to be synchronized under the specified path according to the specified path in the parameters received by the target server and the name of the file to be synchronized, so as to determine whether the file to be synchronized exists in the shared file system, when it is detected that the file to be synchronized does not exist in the shared file system, the remote calling program may record failure information to the second log file, and when it is detected that the file to be synchronized exists in the shared file system, it is determined that the at least one target server and the shared file system can synchronize and execute the next operation.

It should be noted that, by checking the second log file, it is ensured that the synchronization operation record performed in at least one target server at a time and the checking and determining result in the synchronization operation process are recorded in detail, thereby ensuring that the tracing back can be performed in the later period; whether the file to be synchronized exists in the appointed path of the shared file system is detected by detecting the parameters received by the at least one target server and detecting according to the received parameters, so that the remote calling program can successfully find the file to be synchronized in the synchronization process, and the stability of the application in the synchronization process is further ensured.

In an alternative embodiment, after determining that synchronization is enabled between the at least one target server and the shared file system, the remote caller backs up an existing file in the at least one target server to obtain a first backed-up file. The existing file can be characterized as a file to be covered by the file to be synchronized or a file having an association relation with the file to be synchronized. In the backup process, a remote calling program adds a time field into the name of the obtained first backup file, and the content corresponding to the time field is accurate to millisecond, so that the phenomenon of coverage among a plurality of first backups can be avoided when the same existing file is backed up for a plurality of times. Wherein the first backup file may be stored in the target server.

It should be noted that, by backing up an existing file, it is ensured that the file can be traced back later.

In an alternative embodiment, after the existing file in the at least one target server is backed up to obtain the first backup file, the remote caller may synchronize the file to be synchronized from the shared file system to the at least one target server. Specifically, the remote calling program reads a file to be synchronized in a specified path of the shared file system, and then synchronizes the file to be synchronized to the specified path of at least one target server in a copying manner to complete the synchronization operation.

It should be noted that, by synchronizing the shared file system and the at least one target server based on a copy manner, the group and authority of the file can be effectively prevented from changing, and the stability of the application is further ensured.

In an optional embodiment, after synchronizing the file to be synchronized from the shared file system to the at least one target server, the remote caller detects whether the size of the file to be synchronized in the at least one target server is correct, and then the remote caller detects whether the authority of the file to be synchronized in the at least one target server is correct, and finally the remote caller detects whether the affiliation group of the file to be synchronized in the at least one target server is correct, and outputs synchronization end information.

Optionally, in this embodiment, the remote calling program may read the size of the file to be synchronized in the shared file system or the source server, and compare the size of the file to be synchronized in the specified path of the at least one target server with the size of the file to be synchronized in the specified path of the at least one target server to determine whether the size of the file to be synchronized in the at least one target server is correct. Specifically, the partial code for detecting whether the size of the file to be synchronized in the at least one target server is correct is as follows:

when it is detected that the size of the file to be synchronized in the at least one target server is incorrect, the remote caller may record the failure information to a second log file. In this embodiment, the failure information is "please check the file with inconsistent size after copying".

Further, after detecting whether the size of the file to be synchronized in the at least one target server is correct, the remote calling program may detect whether the authority of the file to be synchronized in the at least one target server is correct. In this embodiment, the remote calling program may determine whether the authority of the file to be synchronized in the at least one target server is correct by reading the authority of the file to be synchronized in the shared file system or the source server and comparing the authority with the file authority of the file to be synchronized in the specified path of the at least one target server. Specifically, the partial code for detecting whether the authority of the file to be synchronized in the at least one target server is correct is as follows:

when the authority of the file to be synchronized in at least one target server is detected to be incorrect, the remote calling program can record fault information to a second log file. In this embodiment, the failure information is "please check that the authority after copying the file is inconsistent".

Optionally, after detecting whether the authority of the file to be synchronized in the at least one target server is correct, the remote calling program may detect whether the affiliation group of the file to be synchronized in the at least one target server is correct, and output synchronization end information. In this embodiment, the remote caller may read the affiliation group of the file to be synchronized in the shared file system or the source server, and compare the affiliation group with the file affiliation group of the file to be synchronized in the specified path of the at least one target server to determine whether the affiliation group of the file to be synchronized in the at least one target server is correct. Specifically, the partial code for detecting whether the affiliation group of the file to be synchronized in the at least one target server is correct is as follows:

when it is detected that the affiliation of the file to be synchronized in the at least one target server is incorrect, the remote caller may record failure information to a second log file. In this embodiment, the failure information is "the attribute of the user is inconsistent after copying the file, please check" or "the attribute group is inconsistent after copying the file, please check". At this point, the remote calling program completes the detection of one of the target servers and outputs the synchronization completion information to the source server, so that the source server can control the next target server to perform synchronization. Meanwhile, it should be noted that after all the target servers are completed, the synchronization result is output. The synchronization result comprises detection results of all the target servers, and an operator can check whether a problem occurs when the remote calling program of each target server performs the synchronization operation according to the synchronization result.

In an optional embodiment, the source server may further obtain first synchronization operation information on the source server and a first detection result of detecting the source server, and store the first synchronization operation information and the first detection result in a first log file, where the first log file is stored in the source server; the remote calling program can also acquire second synchronous operation information of the target server and a second detection result for detecting the target server, and store the second synchronous operation information and the detection result into a second log file, wherein the second log file is stored in the target server.

Optionally, in this embodiment, the first synchronization operation information includes the above-mentioned synchronization-related operation related to or performed in the source server and related information, for example, "acquiring a file to be synchronized in the source server" is an operation related to or performed in the source server; "storage location or name of file to be synchronized or other relevant information" is relevant information related to the origin server or involved in synchronization in the origin server. The first detection result includes a result corresponding to a detection operation related to the source server or performed in the source server, such as the detection operations of "detecting whether the backup file of the file to be synchronized is the file to be cleaned", "detecting whether the configuration file exists in the source server", and the like.

Further, the source server stores the first synchronization operation information and the first detection result in a first log file. Log is stored in the origin server in the present embodiment, to ensure that all operations in the synchronization process of the present application are traceable.

Optionally, in this embodiment, the second synchronization operation information includes the above-mentioned synchronization-related operation related to or performed in the at least one target server and related information, for example, "backing up an existing file in the at least one target server to obtain a first backup file" is an operation related to or performed in the target server; "backup time or path of the first backup file or other relevant information" is relevant information related to the target server or involved in synchronization in the target server. The first detection result includes a result corresponding to a detection operation related to the target server or performed in the target server, such as "detecting whether the size of the file to be synchronized in the at least one target server is correct", "detecting whether the authority of the file to be synchronized in the at least one target server is correct", "detecting whether the affiliation group of the file to be synchronized in the at least one target server is correct", and the like.

Further, the remote calling program stores the second synchronous operation information and the detection result in a second log file. Log is stored in the target server for use when rollback is required, and all operations in the synchronization process of the present application are ensured to be traceable.

It should be noted that the present application is applicable to the technical field of financial technologies, that is, the present application can be applied to a server related to financial technologies and process related services of financial technologies.

According to the content, the remote calling program can automatically synchronize the file to be synchronized to the target server in the process, so that operations such as clicking and copying required by an operator during manual synchronization can be effectively replaced, and the synchronization efficiency is improved. Meanwhile, when files need to be synchronized in batch, the source server or other equipment only needs to acquire the files to be synchronized and determine the target server, and then the starting of the remote calling program in each target server can be automatically controlled, so that operations such as clicking and the like required by operators during batch synchronization can be effectively replaced, time wasted by the operators when waiting for synchronization of each server is avoided, and the synchronization efficiency is further improved.

Example 2

According to an embodiment of the present invention, an embodiment of an apparatus for synchronizing files is provided, where fig. 5 is a schematic diagram of a synchronization apparatus according to an embodiment of the present invention, and as shown in fig. 5, the apparatus includes:

a receiving module 501, configured to obtain a file to be synchronized in a source server;

a first processing module 502 for determining at least one target server from a plurality of servers;

the second processing module 503 is configured to control the remote caller in the at least one target server to start, so that the remote caller synchronizes the file to be synchronized to the at least one target server.

It should be noted that the receiving module 501, the first processing module 502, and the second processing module 503 correspond to steps S101 to S103 in the above embodiment, and the three modules are the same as the corresponding steps in the implementation example and application scenarios, but are not limited to the disclosure in embodiment 1.

Optionally, the apparatus for synchronizing files further includes: and the first synchronization module is used for synchronizing the file to be synchronized to the shared file system.

Optionally, the apparatus for synchronizing files further includes: and the third processing module is used for controlling the remote calling program to acquire the file to be synchronized from the shared file system and synchronizing the file to be synchronized to at least one target server.

Optionally, the apparatus for synchronizing files further includes: the grouping module is used for grouping the plurality of servers to obtain at least one group; and the fourth processing module is used for storing grouping information of at least one group into the configuration file, wherein the grouping information at least comprises a server identification and a server address corresponding to the server in the at least one group.

Optionally, the first processing module 502 includes: the first receiving module is used for the first processing module; the first query module is used for determining target grouping information corresponding to the target grouping from the configuration file according to the selection instruction; a second query module to determine at least one target server from the plurality of servers corresponding to the target group based on the target group information.

Optionally, the apparatus for synchronizing files further includes: the first detection module is used for detecting whether a backup file of a file to be synchronized is a file to be cleaned; the second detection module is used for cleaning the backup file of the file to be synchronized and detecting whether the source server has a configuration file or not when the backup file of the file to be synchronized is the file to be cleaned; the third detection module is used for detecting whether the configuration file has grouping information or not when the configuration file is detected to exist in the source server; the fourth detection module is used for detecting whether the first log file corresponding to the source server exists or not when the grouping information exists in the configuration file; and the fifth detection module is used for determining that the source server is in a normal operation state when detecting that the first log file exists in the source server.

Optionally, the apparatus for synchronizing files further includes: the first acquisition module is used for acquiring first synchronous operation information of the source server and a first detection result for detecting the source server; the first storage module is used for storing the first synchronous operation information and the first detection result into a first log file, wherein the first log file is stored in the source server; the second acquisition module is used for acquiring second synchronous operation information of the target servers and a second detection result for detecting at least one target server; and the second storage module is used for storing the second synchronous operation information and the detection result into a second log file, wherein the second log file is stored in at least one target server.

Example 3

Example 4

According to another aspect of the embodiments of the present invention, there is also provided an electronic device, wherein fig. 6 is a schematic diagram of an electronic device according to the present invention, as shown in fig. 6, the electronic device includes one or more processors; memory for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to carry out a method for running the programs, wherein the programs are arranged such that when run they perform the above-mentioned method of synchronizing files.

Example 5

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, a division of a unit may be a division of a logic function, and an actual implementation may have another division, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or may not be executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

The foregoing is only a preferred embodiment of the present invention, and it should be noted that it is obvious to those skilled in the art that various modifications and improvements can be made without departing from the principle of the present invention, and these modifications and improvements should also be considered as the protection scope of the present invention.

Claims

1. A method of synchronizing files, comprising:

acquiring a file to be synchronized in a source server;

determining at least one target server from a plurality of servers;

and controlling a remote calling program in the at least one target server to start so that the remote calling program synchronizes the file to be synchronized to the at least one target server.

2. The method of synchronizing files according to claim 1, wherein prior to controlling the initiation of the remote caller in the at least one target server, the method further comprises:

and synchronizing the file to be synchronized to a shared file system.

3. The method of synchronizing files according to claim 2, wherein after controlling the remote caller in the at least one target server to launch, the method further comprises:

and controlling the remote calling program to acquire the file to be synchronized from the shared file system and synchronizing the file to be synchronized to the at least one target server.

4. The method of synchronizing files according to claim 1, wherein prior to determining at least one target server from a plurality of servers, the method further comprises:

grouping the plurality of servers to obtain at least one group;

storing grouping information of the at least one group into a configuration file, wherein the grouping information at least comprises a server identification and a server address corresponding to a server in the at least one group.

5. The method of synchronizing files according to claim 4, wherein determining at least one target server from a plurality of servers comprises:

receiving a selection instruction;

determining target grouping information corresponding to target grouping from the configuration file according to the selection instruction;

determining at least one target server corresponding to the target group from the plurality of servers based on the target group information.

6. The method of synchronizing files according to claim 4, wherein prior to determining at least one target server from the plurality of servers, the method further comprises:

detecting whether the backup file of the file to be synchronized is the file to be cleaned;

when the backup file of the file to be synchronized is the file to be cleaned, cleaning the backup file of the file to be synchronized, and detecting whether the configuration file exists in the source server;

when detecting that the configuration file exists in the source server, detecting whether the grouping information exists in the configuration file;

when the grouping information exists in the configuration file, detecting whether a first log file corresponding to the source server exists or not;

and when detecting that the first log file exists in the source server, determining that the source server is in a normal operation state.

7. The method of synchronizing files according to claim 6, further comprising:

acquiring first synchronous operation information of the source server and a first detection result for detecting the source server;

storing the first synchronization operation information and the first detection result in the first log file, wherein the first log file is stored in the source server;

acquiring second synchronous operation information of the at least one target server and a second detection result for detecting the at least one target server;

and storing the second synchronization operation information and the detection result into a second log file, wherein the second log file is stored in the at least one target server.

8. An apparatus for synchronizing files, comprising:

the receiving module is used for acquiring a file to be synchronized in the source server;

a first processing module for determining at least one target server from a plurality of servers;

and the second processing module is used for controlling the starting of a remote calling program in the at least one target server so as to enable the remote calling program to synchronize the file to be synchronized to the at least one target server.

9. A computer-readable storage medium, in which a computer program is stored, wherein the computer program is arranged to perform the method of synchronizing files of any of claims 1 to 7 when executed.

10. An electronic device, characterized in that the electronic device comprises one or more processors; memory for storing one or more programs which, when executed by the one or more processors, cause the one or more processors to implement a method for running a program, wherein the program is arranged to, when run, perform the method of synchronizing files of any of claims 1 to 7.

11. A computer program product comprising computer programs/instructions, characterized in that the computer programs/instructions, when executed by a processor, implement the method of synchronizing files of any of claims 1 to 7.