CN118193290A - Code processing method, device and storage medium - Google Patents
Code processing method, device and storage medium Download PDFInfo
- Publication number
- CN118193290A CN118193290A CN202410338398.3A CN202410338398A CN118193290A CN 118193290 A CN118193290 A CN 118193290A CN 202410338398 A CN202410338398 A CN 202410338398A CN 118193290 A CN118193290 A CN 118193290A
- Authority
- CN
- China
- Prior art keywords
- backup
- server
- code
- file
- main server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 31
- 238000000034 method Methods 0.000 claims abstract description 54
- 238000004891 communication Methods 0.000 claims abstract description 15
- 238000012795 verification Methods 0.000 claims description 43
- 230000000694 effects Effects 0.000 claims description 24
- 238000012545 processing Methods 0.000 claims description 23
- 238000004422 calculation algorithm Methods 0.000 claims description 7
- 238000012216 screening Methods 0.000 claims description 7
- 230000002596 correlated effect Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 15
- 230000008569 process Effects 0.000 description 13
- 230000001360 synchronised effect Effects 0.000 description 13
- 238000004590 computer program Methods 0.000 description 12
- 238000011084 recovery Methods 0.000 description 10
- 230000000875 corresponding effect Effects 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 7
- 238000011161 development Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 7
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 238000012544 monitoring process Methods 0.000 description 6
- 238000012806 monitoring device Methods 0.000 description 5
- 230000008859 change Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000001514 detection method Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000000605 extraction Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 238000012163 sequencing technique Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/178—Techniques for file synchronisation in file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1873—Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a code processing method, a device and a storage medium, wherein the method relates to the technical field of computers, and comprises the following steps: receiving target codes pushed by a client through a main server, wherein a version control system is arranged in the main server; determining a changed code file according to the code file and the target code in the version control system; and synchronizing the changed code files to a plurality of backup servers through the main server, wherein the plurality of backup servers are all provided with a version control system, and the main server is in communication connection with the plurality of backup servers. According to the method and the device, the problem that in the related art, when codes are locally pushed to a plurality of remote target code libraries, the codes are inconsistent among the plurality of remote target code libraries due to pushing failure, and the working efficiency of developers is reduced is solved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a code processing method, a code processing device, and a storage medium.
Background
With the continuous development of informatization, the security problem of enterprise data is increasingly serious, and the code is one of important assets of an internet enterprise, and the security of the code is also greatly threatened. Therefore, code backup management becomes an important ring of enterprise data security management, and it is necessary to ensure the security and integrity of codes through backup technology. On the other hand, considering the complexity of the business and the flexibility of code development, the code branch volume of the company is generally large, and particularly in the case of multi-deployment servers, the efficient synchronous management of multiple warehouses is considered. Therefore, the method is different from the traditional periodic incremental and full-quantity backup, can be suitable for a large environment of multi-warehouse management, and is particularly important to complete, flexible, convenient and safe code backup management. For the application scenario of multi-warehouse management, a distributed version control system (hereinafter referred to as Git) is used for code version management, and a configuration of a plurality of remote warehouse addresses needs to be added on a local client to realize the function of pushing codes to a plurality of remote warehouses simultaneously when the codes are submitted locally. When a user submits codes from a local warehouse, the local script searches a code management configuration file stored locally, reads the configuration file, determines configuration information of a plurality of remote target Git code warehouses arranged in the configuration file, and uploads the codes needing to be uploaded to the plurality of remote target Git code warehouses in parallel. But the local pushing codes to a plurality of remote target code libraries has higher requirements on the performance of the local network, the success rate of the code pushing is reduced, if the pushing fails, the problem of inconsistent codes among the plurality of remote target code libraries is caused, and therefore, a user is required to adjust or process the inconsistent codes, the workload of the user is increased, and the problem of lower working efficiency is caused.
Disclosure of Invention
The application mainly aims to provide a code processing method, a code processing device and a storage medium.
In order to achieve the above object, according to one aspect of the present application, there is provided a code processing method. The method comprises the following steps: receiving target codes pushed by a client through a main server, wherein a version control system is arranged in the main server; determining a changed code file according to the code file in the version control system and the target code; and synchronizing the changed code files to a plurality of backup servers through the main server, wherein the plurality of backup servers are all deployed with the version control system, and the main server is in communication connection with the plurality of backup servers.
Further, the method further comprises: determining a changed target file under the condition that the client side is detected to execute target operation on the target file in the version control system, wherein the target file comprises the following components: database files and/or configuration files; and synchronizing the changed target file to the plurality of backup servers through the main server.
Further, before synchronizing the altered code file to a plurality of backup servers by the primary server, the method further comprises: sending a public key of a key pair of the main server to each backup server and a storage server through the main server so as to realize that the main server is authorized to access each backup server and each storage server; wherein the storage server is configured to store a backup file from the primary server, where the backup file includes at least one of: code files, database files, and configuration files; the synchronizing, by the primary server, the altered code file to a plurality of backup servers, comprising: synchronizing the changed code files to a plurality of backup servers according to the configuration information of the main server; the configuration information at least comprises server information of each standby server and server information of the storage server.
Further, the method further comprises: receiving a public key in a key pair of each backup server and a public key in a key pair of a storage server through the main server to obtain a public key set; transmitting the public key set and the configuration information to each backup server and the storage server through the main server; after the target backup server in the plurality of backup servers is switched to the main server, the public key set and the configuration information are used for the target backup server to synchronize the changed files to other backup servers and the storage servers in the plurality of backup servers.
Further, the method further comprises: according to a preset period, carrying out full backup on the data in the version control system through the main server, and generating a backup file; after the backup file is generated, the backup file is sent to a storage server.
Further, after sending the backup file to the storage server, the method further comprises: the storage server adopts a message digest algorithm to carry out integrity check on the backup file received by the storage server, so as to obtain a check result; under the condition that the verification result indicates that the verification is successful, determining that the backup file received by the storage server is complete; and under the condition that the verification result indicates that verification fails, determining that the backup file received by the storage server is not complete.
Further, after sending the backup file to the storage server, the method further comprises: extracting the project information of the version control system from the backup file received by the storage server every time a preset time length passes; determining the activity of each branch in N items of the item information, wherein N is a positive integer greater than or equal to 1, and the activity of each branch is positively correlated with the submission times of the branch; for each item, screening branches with the maximum activity from branches contained in the item to obtain M target branches, wherein M is greater than or equal to N; compiling the M target branches, and if the target files are successfully compiled, determining that the backup files received by the storage server are successfully checked; and if the target file is not successfully compiled, determining that the backup file received by the storage server fails to verify.
In order to achieve the above object, according to another aspect of the present application, there is provided a code processing apparatus. The device comprises: the first receiving unit is used for receiving target codes pushed by the client through a main server, wherein a version control system is arranged in the main server; a first determining unit, configured to determine a changed code file according to the code file and the object code in the version control system; and the first synchronization unit is used for synchronizing the changed code files to a plurality of backup servers through the main server, wherein the plurality of backup servers are all provided with the version control system, and the main server is in communication connection with the plurality of backup servers.
Further, the apparatus further comprises: a second determining unit, configured to determine, when it is detected that the client performs a target operation on a target file in the version control system, a changed target file, where the target file includes: database files and/or configuration files; and the second synchronization unit is used for synchronizing the changed target files to the plurality of backup servers through the main server.
Further, the apparatus further comprises: a first sending unit, configured to send, by the primary server, a public key of a key pair of the primary server to each backup server and a storage server before synchronizing, by the primary server, the changed code file to a plurality of backup servers, so as to realize that the primary server is authorized to access each backup server and the storage server; wherein the storage server is configured to store a backup file from the primary server, where the backup file includes at least one of: code files, database files, and configuration files; the first synchronization unit includes: a first synchronization subunit, configured to synchronize the changed code file to a plurality of backup servers according to the configuration information of the primary server; wherein the configuration information includes at least server information of each backup server and server information of the storage server.
Further, the apparatus further comprises: the second receiving unit is used for receiving the public key of the key pair of each backup server and the public key of the key pair of the storage server through the main server to obtain a public key set; the second sending unit is used for sending the public key set and the configuration information to each backup server and the storage server through the main server; after the target backup server in the plurality of backup servers is switched to the main server, the public key set and the configuration information are used for the target backup server to synchronize the changed files to other backup servers and the storage servers in the plurality of backup servers.
Further, the apparatus further comprises: the backup unit is used for carrying out full-scale backup on the data in the version control system through the main server according to a preset period and generating a backup file; and the third sending unit is used for sending the backup file to a storage server after the backup file is generated.
Further, the apparatus further comprises: the verification unit is used for carrying out integrity verification on the backup file received by the storage server by adopting a message digest algorithm through the storage server after the backup file is sent to the storage server, so as to obtain a verification result; a third determining unit, configured to determine that the backup file received by the storage server is complete if the verification result indicates that the verification is successful; and the fourth determining unit is used for determining that the backup file received by the storage server is not complete under the condition that the verification result indicates that the verification fails.
Further, the apparatus further comprises: the extraction unit is used for extracting the project information of the version control system from the backup files received by the storage server every time a preset time length passes after the backup files are sent to the storage server; a fifth determining unit, configured to determine an activity level of each branch in N items of the item information, where N is a positive integer greater than or equal to 1, and the activity level of the branch is positively related to a number of submissions of the branch; the screening unit is used for screening branches with the maximum activity from branches contained in each item to obtain M target branches, wherein M is greater than or equal to N; the compiling unit is used for compiling the M target branches, and if the target files are successfully compiled, the backup files received by the storage server are determined to be successfully checked; and if the target file is not successfully compiled, determining that the backup file received by the storage server fails to verify.
To achieve the above object, according to one aspect of the present application, there is provided a computer program product comprising a computer program which, when executed by a processor, implements the code processing method of any one of the above, and which, when executed by the processor, implements the steps of the code processing method of the various embodiments of the application.
In order to achieve the above object, according to an aspect of the present application, there is provided an electronic device including one or more processors and a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the code processing method of any of the above.
According to the application, the following steps are adopted: receiving target codes pushed by a client through a main server, wherein a version control system is arranged in the main server; determining a changed code file according to the code file in the version control system and the target code; and synchronizing the changed code files to a plurality of backup servers through the main server, wherein the plurality of backup servers are all provided with the version control system, and the main server is in communication connection with the plurality of backup servers, so that the problem that in the related art, when codes are locally pushed to a plurality of remote target code libraries, the codes are inconsistent due to push failure, and the working efficiency of developers is reduced is solved. According to the application, the target codes pushed by the client are received by the main server, the changed code files are determined according to the target codes, and the changed code files can be synchronized to the plurality of backup servers, so that the purpose of code consistency in the main server and each backup server is realized, the instantaneity of the backup codes to the plurality of backup servers is ensured, meanwhile, the problem that the service of the version control system is required to be stopped when the main server updates the codes to a plurality of remote target warehouses in real time at the same time is avoided, the development efficiency is reduced, and the effect of improving the working efficiency of developers is achieved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application. In the drawings:
FIG. 1 is a flow chart of a code processing method provided according to an embodiment of the present application;
FIG. 2 is a schematic diagram I of an alternative code processing method provided in accordance with an embodiment of the present application;
FIG. 3 is a schematic diagram II of an alternative code processing method provided in accordance with an embodiment of the present application;
FIG. 4 is a schematic diagram III of an alternative code processing method provided in accordance with an embodiment of the present application;
FIG. 5 is a schematic diagram IV of an alternative code processing method provided in accordance with an embodiment of the application;
FIG. 6 is a schematic diagram five of an alternative code processing method provided in accordance with an embodiment of the present application;
FIG. 7 is a diagram six of an alternative code processing method provided in accordance with an embodiment of the present application;
FIG. 8 is a schematic diagram of a code processing apparatus provided in accordance with an embodiment of the present application;
fig. 9 is a schematic diagram of a code processing electronic device provided according to an embodiment of the present application.
Detailed Description
It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other. The application will be described in detail below with reference to the drawings in connection with embodiments.
In order that those skilled in the art will better understand the present application, a technical solution in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, shall fall within the scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate in order to describe the embodiments of the application 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.
The embodiments or examples of the present disclosure are not intended to be exhaustive, but rather are merely illustrative of some of the embodiments or examples, and are not intended to limit the scope of the disclosure in any way. Each step in a certain implementation manner or embodiment may be implemented as an independent embodiment, and the steps may be arbitrarily combined, for example, a scheme after removing part of the steps in a certain implementation manner or embodiment may be implemented as an independent embodiment, and the order of the steps in a certain implementation manner or embodiment may be arbitrarily exchanged, and further, an optional manner or optional embodiment in a certain implementation manner or embodiment may be arbitrarily combined; furthermore, various embodiments or examples may be arbitrarily combined, for example, some or all steps of different embodiments or examples may be arbitrarily combined, and a certain embodiment or example may be arbitrarily combined with alternative modes or alternative examples of other embodiments or examples.
For convenience of description, the following will describe some terms or terminology involved in the embodiments of the present application:
Gitlab is a widely used, git-based open source code management platform that can manage code and documents generated during software development. Many companies build their own multiple Gitlab platforms for code management and version maintenance of in-house development projects. Meanwhile, as Web (World Wide Web) service software, the abundant visual operation interface also enables the platform manager to work more conveniently and intuitively in aspects of warehouse maintenance, project management and the like. By carrying out code backup management based on Gitlab, the data security can be well protected, the collaboration efficiency is improved, the development efficiency is improved, and the version management is convenient.
The present application will be described with reference to preferred implementation steps, and fig. 1 is a flowchart of a code processing method according to an embodiment of the present application, as shown in fig. 1, and the method includes the following steps:
Step S101, receiving target codes pushed by a client through a main server, wherein a version control system is deployed in the main server.
The execution main body of the code processing method provided by the embodiment of the application is a main server, the main server is suitable for a distributed version control system (Git), and the main server is also suitable for a centralized version control System (SVN).
In this embodiment, the version control system refers to a system for tracking and managing the modification history of code, for example, git, SVN. The user pushes the object code to the version control system on the primary server through the local client. Specifically, the object code may be pushed to a version control system deployed on the primary server using a "gitpush" command. The primary server and the backup server support disaster recovery switching, i.e., the primary server may be automatically or manually switched to the backup server when the primary server encounters a failure or disaster.
Step S102, according to the code file and the target code in the version control system, determining the changed code file.
In this embodiment, in order to synchronize the changed code to the backup server in time, it is necessary to compare the code file in the version control system with the target code uploaded by the user, and analyze the difference between the two code files, so as to generate the changed code file.
Step S103, the changed code files are synchronized to a plurality of backup servers through the main server, wherein the plurality of backup servers are all provided with a version control system, and the main server is in communication connection with the plurality of backup servers.
In this embodiment, in order to ensure code consistency between the primary server and the backup server, multiple threads need to be established, and the changed code files are transmitted to the multiple backup servers, so as to synchronize the codes after user change in the multiple backup servers in real time.
In the code processing method provided by the embodiment of the application, the target code pushed by the client is received through the main server, wherein the main server is provided with a version control system; determining a changed code file according to the code file and the target code in the version control system; the changed code files are synchronized to a plurality of backup servers through the main server, wherein version control systems are deployed in the plurality of backup servers, and the main server is in communication connection with the plurality of backup servers, so that the problem that in the related art, when codes are locally pushed to a plurality of remote target code libraries, the codes are inconsistent among the plurality of remote target code libraries due to pushing failure is solved, and the working efficiency of developers is reduced. The target codes pushed by the client are received by the main server, changed code files are determined according to the target codes, and the changed code files can be synchronized to a plurality of backup servers, so that the purpose of code consistency in the main server and each backup server is achieved, the instantaneity of the backup codes to the plurality of backup servers is ensured, meanwhile, the problem that relevant services of a version control system need to be stopped when the main server updates the codes to a plurality of remote target warehouses in real time at the same time is avoided, the development efficiency is reduced, and the effect of improving the working efficiency of developers is achieved.
Optionally, in the code processing method provided by the embodiment of the present application, the method further includes: and under the condition that the client side is detected to execute target operation on the target file in the version control system, determining the changed target file, wherein the target file comprises the following components: database files and/or configuration files; and synchronizing the changed target file to a plurality of backup servers through the main server.
In this embodiment, in order to ensure the consistency of the codes of the main server and the backup server, the target operation performed on the version control system by the user at the client may be monitored in real time, so that after the target operation is performed, the modification of the version control system by the user is synchronized to other backup servers, thereby realizing the effect of ensuring the consistency of the data in the main server and the data in the backup server, avoiding the problem of inconsistent data stored in other backup servers by the main server due to different configuration of the database, improving the accuracy of the data in the main server and the backup server, and further achieving the effect of improving the reliability of the main server and the backup server.
In an alternative embodiment, the target operation may be: modifying the operation of the information of the database, including host name, port, protocol, storage warehouse location, file location, type of the database, connection information, backup strategy, mail information, etc.; adding a database, editing the database, deleting the database and the like.
Optionally, in the code processing method provided by the embodiment of the present application, before the changed code file is synchronized to the plurality of backup servers by the main server, the method further includes: the public key in the key pair of the main server is sent to each backup server and each storage server through the main server, so that the main server is authorized to access each backup server and each storage server; the storage server is used for storing backup files from the main server, wherein the backup files comprise at least one of the following: code files, database files, and configuration files; synchronizing, by the primary server, the changed code file to a plurality of backup servers, comprising: synchronizing the changed code files to a plurality of backup servers according to the configuration information of the main server; the configuration information at least comprises server information of each backup server and server information of a storage server.
Here, the primary server is authorized to access the backup server, which is understood to be accessible by the primary server without providing an access password to the backup server. Here, the primary server is authorized to access the storage server, which is understood to be accessible by the primary server without providing an access password to the backup server.
In this embodiment, in order to improve the code transmission security, before synchronizing the changed code files, the main server may send the public key in its own key pair to each backup server and storage server, so that the main server and each backup server, the main server and the storage server perform data transmission, and in the case that the main server or the backup server receives data, only the public key in the corresponding key pair is allowed to access the data owned by the other party, thereby preventing unauthorized access and attack, improving the security of the main server and the backup server, and achieving the effect of protecting the security of the main server, the backup server and the data.
Optionally, in the code processing method provided by the embodiment of the present application, the method further includes: receiving a public key in a key pair of each backup server and a public key in a key pair of a storage server through a main server to obtain a public key set; sending the public key set and the configuration information to each backup server and the storage server through the main server; after the target backup server in the plurality of backup servers is switched to the main server, the public key set and the configuration information are used for synchronizing the changed files to other backup servers and storage servers in the plurality of backup servers by the target backup server.
Here, the changed file includes at least one of: code files, database files, and configuration files.
In an alternative embodiment, a key pair of each backup server and a key pair of the storage server may be generated, a public key list (i.e., the public key set described above) is obtained according to the public key in the key pair of each backup server and the public key in the key pair of the storage server, and the public key set is sent to the primary server, so as to enable the primary server to be authorized to access each backup server and storage server.
In an alternative embodiment, the process of encrypting a transmission between a primary server and a backup server may be as shown in FIG. 2. First, the backup servers 1 to n generate respective key pairs, the storage server generates a key pair, and the public key pair of the keys of the backup servers 1 to n and the public key of the storage server are sent to the main server, so as to obtain a public key list (i.e. the public key set). Then, the main server modifies the configuration information of the main server according to the user operation so as to realize that the main server synchronizes the changed files to the backup servers according to the configuration information, wherein the configuration information at least comprises information such as IP addresses of the backup servers.
In an alternative embodiment, the server information and the backup failure threshold value of each backup server can be input in the backup management system of the main server by a developer to obtain the backup library configuration information, so that the main server can automatically start the data synchronization service according to the public key set and the backup library configuration information, and send the backup library configuration information to all the backup servers, and the backup servers store the backup library configuration information so as to modify the database configuration information when the backup servers are switched to the main server.
In this embodiment, in order to ensure the data consistency of the primary server and the backup server, the backup monitoring module may determine whether the changed code files are successfully synchronized, so as to take corresponding measures to ensure that the data stored in the primary server and the backup server are the same.
In an alternative embodiment, whether the synchronization of the changed code file is successful or not may be determined, and in the case that the synchronization of the changed code file is successful, the server information of each backup server and the database information corresponding to each backup server are sent to each backup server, so as to perform the code synchronization; in the case of the synchronization failure of the changed code file, a synchronization failure log is generated according to the synchronization process and the synchronization condition of the changed code file, so that the target object (for example, a developer, an operation and maintenance person, a project manager and the like) locates the reason of the synchronization failure of the changed code file according to the synchronization failure log, thereby solving the problem of the synchronization failure. In addition, the backup management system of the main server is controlled to continuously execute the synchronization operation on the premise of synchronization failure until the synchronization is successful. In the synchronization process, if the number of times of failure of the backup management system to perform the synchronization operation reaches a backup failure threshold (for example, 10, 50 and other values), the master server is controlled to stop performing the synchronization operation, and a mail notification is sent to the target object to remind the target object of timely solving the problem of failure of the synchronization of the changed code file.
In an alternative embodiment, each backup server may automatically update and synchronize the changed code file to the databases of the plurality of backup servers according to the received server information of each backup server and the received database information corresponding to each backup server.
Optionally, in the code processing method provided by the embodiment of the present application, the method further includes: according to a preset period, carrying out full-quantity backup on data in the version control system through a main server, and generating a backup file; after the backup file is generated, the backup file is sent to the storage server.
In this embodiment, in order to avoid the influence caused by data loss, in addition to timely synchronizing incremental data in the main server to the backup server, the data in the main server may be backed up in full at intervals of the preset period (for example, 7 days, 15 days, etc.), so as to obtain the backup file (the backup file includes at least one of the following files: a code file, a database file and a configuration file), and in the case that the backup file is successfully generated, the backup file is compressed and sent to the storage server, so that the data security of the main server is improved.
In an alternative embodiment, the generated backup file may be detected in real time, and when the backup fails, the backup monitoring module records the data synchronization failure information and forms a backup failure log, and the backup management system continues to execute the backup operation until the failure number reaches the set backup failure number threshold. When the backup times reach the failure threshold value, the main server stops the backup operation and sends a backup failure mail to the backup manager through the mail module so as to remind the backup manager to properly process the backup failure condition.
Optionally, in the code processing method provided by the embodiment of the present application, after sending the backup file to the storage server, the method further includes: the storage server adopts a message digest algorithm to carry out integrity check on the backup file received by the storage server, so as to obtain a check result; under the condition that the verification result indicates that the verification is successful, determining that the backup file received by the storage server is complete; and in the case that the verification result indicates that the verification fails, determining that the backup file received by the storage server is not complete.
In an alternative embodiment, after the backup file is sent to the storage server, the backup file received by the storage server may be checked by using a message digest algorithm to obtain a check result; if the verification result indicates that the verification is successful, determining that the backup file received by the storage server is complete; if the verification result indicates that the verification fails, determining that the backup file received by the storage server has a defect, and needing the main server to resend the backup file to the storage server again.
Optionally, in the code processing method provided by the embodiment of the present application, after sending the backup file to the storage server, the method further includes: extracting project information of a version control system from a backup file received by a storage server every time a preset time length passes; determining the liveness of each branch in N items of item information, wherein N is a positive integer greater than or equal to 1, and the liveness of the branch is positively correlated with the submission times of the branch; aiming at each project, screening branches with the maximum activity from branches contained in the project to obtain M target branches, wherein M is greater than or equal to N; compiling the M target branches, and if the target files are successfully compiled, determining that the backup files received by the storage server are successfully checked; if the target file is not successfully compiled, determining that the backup file received by the storage server fails to verify.
In this embodiment, since the backup files in the storage server are more, the code with the most number of modifications in the code file, that is, the code of the target branch with higher activity, may be verified, so as to ensure that the backup files are intact.
In an alternative embodiment, the process of verifying the backup code file may be as shown in FIG. 3. The number (n) of product lines is calculated according to item information in a version control system (Gitlab in fig. 3), the activity (Ai) of each code branch (Br) in each product line is determined according to the code compiling times of the branches, and each product line selects two branches with the highest activity to carry out compiling verification, so that 2n code branches are required to be compiled in total. If the code branch is compiled to obtain an image file (namely the target file), the verification is considered to be successful; if the image file is not generated after compiling the code branches, the verification is regarded as failure.
In an alternative embodiment, the number of branches of the project information in the version control system may be determined, the compiling times of each branch may be counted, and the liveness of each code branch in each product line may be determined according to the compiling times of the codes of the branches. For example, if the number of compilations of the code branch A1 is 10, the liveness of the code branch A1 may be determined to be 10, and if the number of compilations of the code branch A2 is 5, the liveness of the code branch A2 may be determined to be 5.
In an alternative embodiment, it is assumed that product lines P1, P2 … Pn are obtained according to item information in Git, where P1 is the 1 st product line (the product line is "item" in the foregoing embodiment), pn is the nth product line, each product line has a different code branch, and Ai represents the activity of the code branch. For example, pn.brn.ai is the liveness Ai of the nth branch Brn of the Pn product line. Calculating the branch liveness of each product line, and sequencing from high to low to obtain: the branch liveness sequence of the P1 product line, P1.Brx.ai > P1.Bry.ai > P1.Brz.ai > … > P1.Brn.ai; until the Pn product line branches to liveness sequence, pn.Brx.ai > Pn.Bry.ai > Pn.Brz.ai > … > Pn.Brn.ai. The two code branches with highest liveness in each product line are compiled and checked, for example, the P1 product line selects branches P1.Brx and P1.Bry to be compiled and checked, and the Pn product line selects branches Pn.Brx and Pn.Bry to be compiled and checked. Assuming that the number n of product lines of a certain company is 17, the total compiling branch number 34 is required for recovery verification, each branch is compiled for about 1.5-2 hours, if a single server can compile at most 3 branches in parallel at the same time, at most 36 branches can be compiled in one day, and if the number n of product lines of the certain company is greater than the required compiling branch number 34, the main server can complete verification in one day.
By checking the code branches with higher liveness in each product line, the code branches with more verification coverage and modification can be checked, the time required by compiling and checking is greatly reduced, and meanwhile, the occupation of hardware resources is reduced.
Alternatively, in this embodiment, the method for performing code backup and recovery verification on the code in the main server according to the present embodiment may be applied to a code backup and recovery verification system, where the code backup and recovery verification system may be as shown in fig. 4. The first configuration module, namely a communication configuration module, performs communication configuration among the main server, the plurality of backup servers and the storage server, and realizes that the main server is authorized to access other servers in the backup management system; the second configuration module, namely a backup parameter configuration module, performs data synchronization configuration and backup detection information configuration, and realizes the functions of performing data synchronization backup operation on a plurality of backup servers by the main server, performing data cold backup operation on a storage server by the main server and triggering the backup monitoring module; the backup data migration module is used for initializing the backup server data; the real-time increment synchronization module comprises a file change monitoring device and is used for performing real-time increment synchronization of the version control system code warehouse; the timing increment synchronization module comprises a file changing and timing monitoring device and is used for timing increment synchronization of information such as a database, a configuration file and the like of the version control system; the timing full-capacity cold standby module comprises a timing monitoring device and is used for carrying out full-capacity backup on application data of the version control system; the backup monitoring module is used for detecting and managing the real-time incremental synchronous backup and the timing full backup of the data; the mail module is called by the backup monitoring module to carry out important backup information notification operation; and the recovery verification module comprises a timing monitoring device and is used for carrying out backup file verification of the storage server and code recovery verification of the main server.
Alternatively, in this embodiment, the process of performing code backup and recovery verification on the code in the primary server according to this embodiment may be as shown in fig. 5. The communication configuration among the main server, the plurality of backup servers and the storage server is carried out through the first configuration module (namely the communication configuration module), and the data synchronization configuration and the backup detection information configuration are carried out through the second configuration module. The method comprises the steps of monitoring codes pushed by a client and target operation configured by the client on a version control system in real time through a file change monitoring device, pushing code files changed by the client to backup libraries of a plurality of backup servers in real time through a data backup device, synchronizing the integrated changes of information such as databases and configuration files of the version control system to the plurality of backup servers, generating a full-volume backup file in a regular manner, compressing the full-volume backup file and sending the full-volume backup file to a storage server for storing the backup file. The backup detection device monitors backup events in real time, controls the backup flow to continue or stop according to the configured error threshold value, and sends important notification mails. The recovery checking device checks the accuracy of the real-time file and automatically performs code recovery checking at regular intervals so as to ensure the integrity of the backup data. And under the condition that the file backup is successful, checking the backup file by adopting a message digest algorithm, and selecting code branches with higher liveness in each product line to perform compiling check (for example, compiling image check). If the synchronization fails or the backup file generation fails, a corresponding failure log is generated, and under the condition that the failure times reach the preset times, a failure mail is sent to a backup manager or other staff through a mail module so as to remind the backup manager or other staff of taking corresponding measures.
Alternatively, in this embodiment, the access rights of the warehouses of the version control systems of the primary server and the backup server in this solution may be as shown in fig. 6. The clients (e.g., client 1 through client n in fig. 6) pull (e.g., pull) the code from the backup servers (e.g., backup server 1 through backup server n in fig. 6) and the primary server, and push the code to the primary server as in fig. 6. By modifying Customerhooks configuration of the version control system, the master server version control system code warehouse is used as a read-write library, and the version control system code warehouses of a plurality of backup servers are used as authority division of a read-only library. The remote warehouse of the local client configured push code is a version control system code warehouse of the main server, and when the substitution code is cloned or pulled locally, the version control system code warehouse of the proper backup server can be selected.
Alternatively, in this embodiment, a flow chart of switching the standby database to the primary server in this embodiment may be shown in fig. 7, where a dotted line indicates data transmission of the old primary server and a solid line indicates data transmission of the new primary server. When the main server goes wrong, the backup management system of one backup server in the plurality of backup servers is started to convert the backup server into the main server. The client modifies the remote warehouse address of the local push code to be the remote warehouse address of the new main server, so that the client adjusts the push code to the old main server from the push code to the new main server, adjusts the real-time/timing increment synchronous data to each backup server from the old main server to the real-time/timing increment synchronous data to each backup server from the new main server, and adjusts the backup data to the storage server from the old main server to the new main server to the backup data to the storage server. By the method for switching the main server and the backup server, the effects that the version control system service is not required to be stopped when the codes are hot standby, and the main library and the backup library can be normally used when the data are synchronized are achieved, and the working efficiency of developers is improved.
It should be noted that the steps illustrated in the flowcharts of the figures 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 flowcharts, in some cases the steps illustrated or described may be performed in an order other than that illustrated herein.
The embodiment of the application also provides a code processing device, and the code processing device of the embodiment of the application can be used for executing the code processing method provided by the embodiment of the application. The following describes a code processing apparatus provided in an embodiment of the present application.
Fig. 8 is a schematic diagram of a code processing apparatus according to an embodiment of the present application. As shown in fig. 8, the apparatus includes:
The first receiving unit 801 is configured to receive, by using a main server, an object code pushed by a client, where the main server is deployed with a version control system.
A first determining unit 802, configured to determine a modified code file according to the code file and the object code in the version control system.
And a first synchronization unit 803, configured to synchronize the changed code file to a plurality of backup servers through the main server, where the plurality of backup servers are all deployed with a version control system, and the main server is communicatively connected to the plurality of backup servers.
The code processing device provided by the embodiment of the application is used for receiving the target code pushed by the client through the first receiving unit 801, wherein a version control system is arranged in the main server; a first determining unit 802, configured to determine a modified code file according to the code file and the object code in the version control system; the first synchronization unit 803 is configured to synchronize the changed code file to a plurality of backup servers through the main server, where the plurality of backup servers are all deployed with a version control system, and the main server is in communication connection with the plurality of backup servers, so as to solve the problem that in the related art, when locally pushing codes to a plurality of remote target code libraries, due to a pushing failure, there is a code inconsistency between the plurality of remote target code libraries, and the working efficiency of developers is reduced. The target codes pushed by the client are received by the main server, changed code files are determined according to the target codes, and the changed code files can be synchronized to a plurality of backup servers, so that the purpose of code consistency in the main server and each backup server is achieved, the instantaneity of the backup codes to the plurality of backup servers is ensured, meanwhile, the problem that relevant services of a version control system need to be stopped when the main server updates the codes to a plurality of remote target warehouses in real time at the same time is avoided, the development efficiency is reduced, and the effect of improving the working efficiency of developers is achieved.
Optionally, in the code processing apparatus provided in the embodiment of the present application, the apparatus further includes: a second determining unit, configured to determine, when it is detected that the client performs a target operation on a target file in the version control system, a changed target file, where the target file includes: database files and/or configuration files; and the second synchronization unit is used for synchronizing the changed target file to a plurality of backup servers through the main server.
Optionally, in the code processing apparatus provided in the embodiment of the present application, the apparatus further includes: a first transmitting unit, configured to transmit, by the primary server, a public key of a key pair of the primary server to each of the backup servers and the storage servers before synchronizing, by the primary server, the changed code file to the plurality of backup servers, so as to realize that the primary server is authorized to access each of the backup servers and the storage servers; the storage server is used for storing backup files from the main server, wherein the backup files comprise at least one of the following: code files, database files, and configuration files; the first synchronization unit includes: a first synchronization subunit, configured to synchronize the changed code file to a plurality of backup servers according to the configuration information of the primary server; the configuration information at least comprises server information of each backup server and server information of a storage server.
Optionally, in the code processing apparatus provided in the embodiment of the present application, the apparatus further includes: the second receiving unit is used for receiving the public key of the key pair of each backup server and the public key of the key pair of the storage server through the main server to obtain a public key set; the second sending unit is used for sending the public key set and the configuration information to each backup server and each storage server through the main server; after the target backup server in the plurality of backup servers is switched to the main server, the public key set and the configuration information are used for synchronizing the changed files to other backup servers and storage servers in the plurality of backup servers by the target backup server.
Optionally, in the code processing apparatus provided in the embodiment of the present application, the apparatus further includes: the backup unit is used for carrying out full backup on the data in the version control system through the main server according to a preset period and generating backup files; and the third sending unit is used for sending the backup file to the storage server after the backup file is generated.
Optionally, in the code processing apparatus provided in the embodiment of the present application, the apparatus further includes: the verification unit is used for carrying out integrity verification on the backup file received by the storage server by adopting a message digest algorithm through the storage server after the backup file is sent to the storage server, so as to obtain a verification result; the third determining unit is used for determining that the backup file received by the storage server is complete under the condition that the verification result indicates that the verification is successful; and the fourth determining unit is used for determining that the backup file received by the storage server is not complete under the condition that the verification result indicates that the verification fails.
Optionally, in the code processing apparatus provided in the embodiment of the present application, the apparatus further includes: the extraction unit is used for extracting the project information of the version control system from the backup files received by the storage server every time a preset time length passes after the backup files are sent to the storage server; a fifth determining unit, configured to determine an activity level of each branch in N items of the item information, where N is a positive integer greater than or equal to 1, and the activity level of the branch is positively related to a number of submissions of the branch; the screening unit is used for screening branches with the maximum activity from branches contained in each item to obtain M target branches, wherein M is greater than or equal to N; the compiling unit is used for compiling the M target branches, and if the target files are successfully compiled, the backup files received by the storage server are determined to be successfully checked; if the target file is not successfully compiled, determining that the backup file received by the storage server fails to verify.
The code processing apparatus includes a processor and a memory, the first receiving unit 801, the first determining unit 802, the first synchronizing unit 803, and the like are stored as program units in the memory, and the processor executes the program units stored in the memory to realize the corresponding functions.
The processor includes a kernel, and the kernel fetches the corresponding program unit from the memory. The kernel can be provided with one or more than one kernel, and the working efficiency of the developer is improved by adjusting the kernel parameters.
The memory may include volatile memory, random Access Memory (RAM), and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM), among other forms in computer readable media, the memory including at least one memory chip.
The embodiment of the invention provides a storage medium on which a program is stored, which when executed by a processor, implements the code processing method.
The embodiment of the invention provides a processor which is used for running a program, wherein the code processing method is executed when the program runs.
As shown in fig. 9, an embodiment of the present invention provides an electronic device, where the device includes a processor, a memory, and a program stored in the memory and executable on the processor, and the processor implements the following steps when executing the program: receiving target codes pushed by a client through a main server, wherein a version control system is arranged in the main server; determining a changed code file according to the code file and the target code in the version control system; and synchronizing the changed code files to a plurality of backup servers through the main server, wherein the plurality of backup servers are all provided with a version control system, and the main server is in communication connection with the plurality of backup servers.
The device herein may be a server, PC, PAD, cell phone, etc.
The application also provides a computer program product adapted to perform, when executed on a data processing device, a program initialized with the method steps of: receiving target codes pushed by a client through a main server, wherein a version control system is arranged in the main server; determining a changed code file according to the code file and the target code in the version control system; and synchronizing the changed code files to a plurality of backup servers through the main server, wherein the plurality of backup servers are all provided with a version control system, and the main server is in communication connection with the plurality of backup servers.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, etc., such as Read Only Memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.
Claims (10)
1.A code processing method, comprising:
Receiving target codes pushed by a client through a main server, wherein a version control system is arranged in the main server;
Determining a changed code file according to the code file in the version control system and the target code;
And synchronizing the changed code files to a plurality of backup servers through the main server, wherein the plurality of backup servers are all deployed with the version control system, and the main server is in communication connection with the plurality of backup servers.
2. The method according to claim 1, wherein the method further comprises:
Determining a changed target file under the condition that the client side is detected to execute target operation on the target file in the version control system, wherein the target file comprises the following components: database files and/or configuration files;
and synchronizing the changed target file to the plurality of backup servers through the main server.
3. The method of claim 1, wherein prior to synchronizing the altered code file to a plurality of backup servers by the primary server, the method further comprises:
Sending a public key of a key pair of the main server to each backup server and a storage server through the main server so as to realize that the main server is authorized to access each backup server and each storage server; wherein the storage server is configured to store a backup file from the primary server, where the backup file includes at least one of: code files, database files, and configuration files;
The synchronizing, by the primary server, the altered code file to a plurality of backup servers, comprising:
synchronizing the changed code files to a plurality of backup servers according to the configuration information of the main server; wherein the configuration information includes at least server information of each backup server and server information of the storage server.
4. A method according to claim 3, characterized in that the method further comprises:
receiving a public key in a key pair of each backup server and a public key in a key pair of a storage server through the main server to obtain a public key set;
Transmitting the public key set and the configuration information to each backup server and the storage server through the main server; after the target backup server in the plurality of backup servers is switched to the main server, the public key set and the configuration information are used for the target backup server to synchronize the changed files to other backup servers and the storage servers in the plurality of backup servers.
5. The method according to any one of claims 1 to 4, further comprising:
According to a preset period, carrying out full backup on the data in the version control system through the main server, and generating a backup file;
After the backup file is generated, the backup file is sent to a storage server.
6. The method of claim 5, wherein after sending the backup file to a storage server, the method further comprises:
the storage server adopts a message digest algorithm to carry out integrity check on the backup file received by the storage server, so as to obtain a check result;
Under the condition that the verification result indicates that the verification is successful, determining that the backup file received by the storage server is complete;
And under the condition that the verification result indicates that verification fails, determining that the backup file received by the storage server is not complete.
7. The method of claim 5, wherein after sending the backup file to a storage server, the method further comprises:
extracting the project information of the version control system from the backup file received by the storage server every time a preset time length passes;
Determining the activity of each branch in N items of the item information, wherein N is a positive integer greater than or equal to 1, and the activity of each branch is positively correlated with the submission times of the branch;
for each item, screening branches with the maximum activity from branches contained in the item to obtain M target branches, wherein M is greater than or equal to N;
compiling the M target branches, and if the target files are successfully compiled, determining that the backup files received by the storage server are successfully checked; and if the target file is not successfully compiled, determining that the backup file received by the storage server fails to verify.
8. A code processing apparatus, comprising:
the first receiving unit is used for receiving target codes pushed by the client through a main server, wherein a version control system is arranged in the main server;
A first determining unit, configured to determine a changed code file according to the code file and the object code in the version control system;
And the first synchronization unit is used for synchronizing the changed code files to a plurality of backup servers through the main server, wherein the plurality of backup servers are all provided with the version control system, and the main server is in communication connection with the plurality of backup servers.
9. An electronic device comprising one or more processors and memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the code processing method of any of claims 1-7.
10. A computer-readable storage medium storing a program, wherein the program, when run, controls a device in which the computer-readable storage medium is located to execute the code processing method according to any one of claims 1 to 7.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202410338398.3A CN118193290A (en) | 2024-03-22 | 2024-03-22 | Code processing method, device and storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202410338398.3A CN118193290A (en) | 2024-03-22 | 2024-03-22 | Code processing method, device and storage medium |
Publications (1)
Publication Number | Publication Date |
---|---|
CN118193290A true CN118193290A (en) | 2024-06-14 |
Family
ID=91408357
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202410338398.3A Pending CN118193290A (en) | 2024-03-22 | 2024-03-22 | Code processing method, device and storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN118193290A (en) |
-
2024
- 2024-03-22 CN CN202410338398.3A patent/CN118193290A/en active Pending
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110825420B (en) | Method, device, equipment and storage medium for updating configuration parameters of distributed cluster | |
US8667096B2 (en) | Automatically generating system restoration order for network recovery | |
US9940208B2 (en) | Generating reverse installation file for network restoration | |
US8990368B2 (en) | Discovery of network software relationships | |
US10922303B1 (en) | Early detection of corrupt data partition exports | |
WO2019147732A1 (en) | Trusted verification of cybersecurity remediation | |
US11550677B2 (en) | Client-less database system recovery | |
CN102609281B (en) | Distributed software patch update method and system | |
CN103597463A (en) | Automatic configuration of a recovery service | |
CN103608781A (en) | Recovery service location for a service | |
US11144405B2 (en) | Optimizing database migration in high availability and disaster recovery computing environments | |
CN112817791A (en) | Mobile terminal monitoring method for mining state of working face cluster | |
KR20140025503A (en) | Replaying jobs at a secondary location of a service | |
US20200125449A1 (en) | Database backup from standby db | |
CN111581285B (en) | Data information synchronization method, device, electronic equipment and medium | |
Kumar T et al. | Intelligent Fault‐Tolerant Mechanism for Data Centers of Cloud Infrastructure | |
KR102294048B1 (en) | Method and system for replicating blockchain application service | |
US20240289109A1 (en) | Updating application hosts in a cluster | |
US20240289228A1 (en) | Restoring configuration files to rollback agent updates when cluster updates fail | |
CN118193290A (en) | Code processing method, device and storage medium | |
Wagdy et al. | Network function virtualization over Cloud-Cloud computing as business continuity solution | |
US12164390B2 (en) | Agent lifecycle management for backup and restore applications | |
US12367104B2 (en) | Generating installation software that rolls back agent updates when cluster updates fail | |
US12124838B2 (en) | Automatically updating agents from backup and restore applications | |
US20240289230A1 (en) | Generating installation software that rolls back agent updates when cluster updates fail |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination |