TWI486759B - Subversion configuration library backup method and device - Google Patents

Description

Subversion configuration library backup method and device

The present application relates to the field of computer application technologies, and in particular, to a backup method and apparatus for a Subversion configuration library.

Subversion, or SVN for short, is a code version management software developed in recent years. Compared with traditional version control software, SVN has many advantages. At present, more and more developers have begun to use SVN for code management and control.

For code version management software, backup of the configuration library is a necessary requirement. In the prior art, the most common and simple backup method is to copy the configuration library directory to the backup directory by directly using the copy command. However, because the amount of data in the configuration repository is often very large, it takes a long time for each full backup.

Another way of the prior art is to use the sync command to synchronize the configuration library. Each time the synchronization operation is performed, the backup configuration library only backs up the content updated in the source configuration database relative to the previous synchronization, so the backup speed is significantly improved. However, the problem with this method is that once an error occurs during a certain synchronization process, subsequent versions will not be able to continue to update synchronously, and the correct data that has been backed up cannot be used. And even if you redeploy a new backup configuration repository from scratch, there is no guarantee that errors will not occur in subsequent synchronization operations, that is, configuration library synchronization operations may not be sustainable in practice.

To solve the above technical problem, the embodiment of the present application provides a backup method and device for a Subversion configuration library, so as to implement a synchronization error of the configuration library, and ensure that the synchronization operation of the configuration library can be continued. The technical solution is as follows: a Subversion configuration library The backup method, in advance, sets a version attribute for the backup configuration library, where the version attribute is used to record the identifier of the last version in the backup configuration repository; the backup method includes: performing a configuration library synchronization operation according to the version attribute of the backup configuration library; If successful, the version attribute value of the backup configuration repository is updated to the version identifier of the successful synchronization; if the synchronization operation fails, after determining that the current version is an unsynchronized version, the source configuration library is backed up by full copy mode, and The version property value of the backup configuration repository is updated to the identity of the non-synchronizable version.

A backup device of the Subversion configuration library, comprising: a synchronization unit, configured to perform a configuration library synchronization operation according to a version attribute of the backup configuration library; and a synchronization success processing unit, configured to: when the synchronization operation is successful, the preset backup configuration database is The version attribute value is updated to the version identifier of the successful synchronization; wherein the pre-set version attribute is used to record the identifier of the last version in the backup configuration repository; the synchronization failure processing unit is configured to determine the current when the synchronization operation fails After the version is not synchronizable, the source configuration repository is backed up by full copy and the version attribute value of the backup configuration repository is updated to the identity of the non-synchronizable version.

In the prior art, before the first synchronization of the configuration library, an empty backup configuration library needs to be created and initialized. Once an error occurs in a certain synchronization process, the correct data that has been backed up before is not used, and Synchronous operations are also difficult to continue. The application of the technical solution of the present application does not need to initialize the backup configuration library. By setting the version attribute directly for the backup configuration library, the backup operation can be performed by copying when the synchronization operation cannot be performed correctly, and then the version attribute of the backup configuration library is modified. This allows the synchronization operation to continue on the basis of the current copy backup.

In addition, the present application also provides a corresponding automatic processing method for some specific reasons for synchronization failure. If the synchronization process can be directly continued after the automatic processing, the full copy mode can be avoided, thereby further improving the backup efficiency of the configuration library.

The existing configuration library synchronization scheme needs to create an empty backup configuration library and initialize it with the svnsync init command before the first synchronization of the configuration database. Once an error occurs during a synchronization, it will be backed up before. The correct data is not available, and even if a new backup configuration repository is redeployed, it is still difficult to ensure that subsequent synchronization operations are performed correctly.

To solve the above technical problem, the technical solution provided by the present application is: pre-set a version attribute for the backup configuration library, and the role of the version attribute is to record the identifier of the last version in the backup configuration library, wherein, under normal circumstances, "final A version" is the last successful synchronization version, and when the synchronization fails, the attribute value can be modified to make the synchronization operation continue.

The Subversion configuration library backup method provided by the embodiment of the present application includes the following basic steps: performing a configuration library synchronization operation according to the version attribute of the backup configuration library; if the synchronization operation is successful, updating the version attribute value of the backup configuration database to the success Synchronized version identifier; if the synchronization operation fails, after determining that the current version is an unsynchronizable version, the source configuration repository is backed up by full copy mode, and the version attribute value of the backup configuration repository is updated to the identifier of the non-synchronizable version.

Applying the above solution, you do not need to initialize the backup configuration repository. By setting the version attribute directly for the backup configuration repository, you can back up by copying when the synchronization operation cannot be performed correctly, and then modify the version attribute of the backup configuration repository to make the synchronization. The operation can continue on the basis of the current copy backup.

The technical solutions in the embodiments of the present application are clearly and completely described in the following, in which the technical solutions in the embodiments of the present application are clearly and completely described. The embodiments are only a part of the embodiments of the present application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments in the present application should fall within the scope of the present application.

1 is a flowchart of a backup method of a Subversion configuration library provided by an embodiment of the present application, where repo1 is a source configuration library and repo2 is a backup configuration library, and the method includes the following steps: S101, according to a version attribute of a backup configuration library To perform the configuration library synchronization operation; before performing the configuration library synchronization operation, you need to set the property of the backup configuration library. The necessary attribute settings include the version attribute of the backup configuration library: svn:sync-last-merged-rev The record is the identifier of the last version in the backup configuration repository, that is, the version number recorded in repo2/db/current. If the current configuration library is empty, the version number can be taken as 0. On the next synchronization, by reading this property, you can continue the synchronization of subsequent versions.

In addition, the backup configuration repository properties that need to be set include: the identity of the source configuration repository:

Svn:sync-from-uuid

This attribute records the identifier of the configuration repository that is read during the synchronization operation. The uuid is the identifier of the configuration repository. In this embodiment, the attribute value set is the uuid of repo1.

Source configuration library address:

Svn:sync-from-url

This attribute records the storage path of the source configuration repository. In this embodiment, the set attribute value is the storage path of repo1.

The above attributes are all global attributes of repo2. After the attribute is set, a synchronization link is established for the source configuration repository and the backup configuration repository. The svnsync sync http://localhost/repo2 is executed for synchronization, according to the version attribute of repo2 sync- Last-merged-rev, you can back up the updated version after this version in the source configuration repository to repo2.

Among them, further configuration can be made to achieve automatic synchronization when repo1 has a new revision commit, thereby establishing instant synchronization of repo1 and repo2. For example, you can script the repo1 post-commit file so that repo1 automatically triggers the synchronization operation when a new revision is submitted.

S102. If the synchronization operation succeeds, the version attribute value of the backup configuration repository is updated to the version identifier of the successful synchronization; under normal circumstances, after each synchronization operation succeeds, the version attribute of the repo2 is automatically updated to just successfully synchronized. The version identifier. At the next synchronization, content updates will be made directly based on the content of the version.

S103. If the synchronization operation fails, after determining that the current version is an unsynchronized version, the source configuration library is backed up by the full copy mode, and the version attribute value of the backup configuration library is updated to the identifier of the non-synchronizable version.

If the synchronization operation is unsuccessful, you can directly determine that the current version is an unsynchronized version. The unsynchronized version described here is still a version that can run correctly, and its own code is not a problem, but for some reason, it cannot be properly synchronized to the backup configuration repository. At this point, all versions (including non-backupable versions of the source configuration repository) in the source configuration repository can be backed up to the backup configuration repository by full copy.

In the prior art, the synchronization operation must be performed after the initialization of the empty backup configuration library. If the previous version uses the copy mode for backup, the synchronization operation cannot be performed on this basis. In the embodiment of the present invention, after the source configuration library is backed up by copying, the version attribute of the backup configuration library is further modified to the version number of the non-synchronizable version. That is to say, by modifying the version attribute, the system recognizes the version backed up by the copy mode as the version backed up by the synchronous method, thereby skipping the version that cannot be synchronized, and ensuring that the synchronization continues.

Of course, in actual applications, the synchronization failure caused by some specific reasons can be quickly processed by a certain method. Therefore, the embodiment of the present application further provides the following automatic synchronization failure processing method: when the synchronization operation fails, the corresponding error information is first obtained, and the common error information includes: backup configuration database locking, backup of a certain file lock of the configuration library, The last version of the backup configuration repository is incorrect, etc., which will be explained separately below.

a) Backup configuration repository lock: The error information of this type of error is similar to the form of "Failed to get lock on destination repos, currently held by 'alicode: 1b27a4fd-fb0e-42a0-a13f-9091cc87b9ac'", where "alicode" is the machine name .

During the synchronization process, the sync program may be aborted due to network disconnection or other factors, and then the next synchronization will fail. In this case, you need to clear the lock protection of the backup configuration repository, that is, delete the backup configuration database by the following command. Sync-lock attribute:

Svn propdel svn:sync-lock--revprop-r 0 http://localhost/repo2

b) Back up a file lock of the configuration repository:

The error information for this type of error is:

Svnsync: Server sent unexpected return value(423 Locked)

Subversion can use the lock function on the user side to lock a directory or file. Only the locker can modify the file or directory. When the synchronization is performed, if the backup library has such a version, the synchronization will be performed without permission. The synchronization fails. In this case, you need to clear the corresponding file in the backup library to continue synchronization. The specific method is as follows:

Svnadmin rmlocks repo2/xxxx

Among them, xxxx represents the path and file name of the locked file.

c) The last version of the backup configuration repository is incorrect:

The error information for this type of error is:

Svnsync: Missing node-id in node-rev

During the synchronization process, the latest version of the backup library may be incomplete due to problems such as the network or configuration library response speed, that is, the version information of the last synchronization is incomplete. At this time, the backup configuration library is unavailable and cannot continue to be synchronized. . Applying the technical solution provided in this application, you can delete the last version of the backup configuration repository, that is, delete the latest version under the repo2/db/revs and repo2/db/reprops paths, and the version number recorded in repo2/db/current - 1. At the same time, the version attribute value of the backup configuration repository is also modified to the identifier of the previous version of the last version, so that the next version is not backed up before the full backup.

The above describes the fast processing method of the synchronization failure caused by three typical reasons. If the synchronization process can be directly continued after the above method is automatically processed, the full copy mode can be avoided, thereby further improving the backup efficiency of the configuration library. If the synchronization operation still fails after the corresponding error processing, it can be determined that the current version is an unsynchronizable version, and further execution of S103 is required.

Of course, the reasons for the failure of the synchronization may be various. On the one hand, the errors that can be quickly processed are not limited to the above three categories, and those skilled in the art may add other fast error handling mechanisms according to actual conditions; Quickly processing errors, even errors that are unclear, can also directly determine the current version as an unsynchronizable version based on the error information, and then further execute S103.

Corresponding to the above method embodiment, the application further provides a backup device of the Subversion configuration library. As shown in FIG. 2, the method includes: a synchronization unit 210, configured to perform a configuration library synchronization operation according to a version attribute of the backup configuration library; The processing unit 220 is configured to: when the synchronization operation succeeds, update the version attribute value of the preset backup configuration repository to the version identifier of the successful synchronization; wherein the preset version attribute is used to record the last one in the backup configuration database. The identifier of the version; the synchronization failure processing unit 230 is configured to: when the synchronization operation fails, after the current version is determined to be an unsynchronizable version, the source configuration library is backed up by the full copy mode, and the version attribute value of the backup configuration library is updated to The identifier of the non-synchronizable version.

Applying the Subversion configuration repository backup device provided above does not require initializing the backup configuration repository. By directly setting the version attribute for the backup configuration repository, you can back up by copying when the synchronization operation cannot be performed correctly, and then modify the backup configuration repository. The version attribute allows the synchronization operation to continue on the basis of the current copy backup.

As shown in FIG. 3, the Subversion configuration repository backup device provided by the present application may further include: a non-synchronized version determining unit 240, where the unit may specifically include: an error information obtaining subunit, configured to obtain error information that the synchronization operation fails; a first determining subunit, configured to determine, according to the error information, that the current version is an unsynchronized version; an error processing subunit, configured to perform corresponding error processing according to the error information; and a second determining subunit, configured to perform error processing When the synchronization operation fails, it is determined that the current version is an unsynchronized version.

Wherein, when the error information is: backup configuration library lock, the error processing sub-unit deletes the synchronization lock attribute of the backup configuration library.

When the error message is: a file lock of the backup configuration library, the error handling subunit deletes the lock attribute of the file.

When the error message is: The last version of the backup configuration repository is incorrect, the error handling subunit deletes the last version in the backup configuration repository and modifies the version attribute value of the backup configuration repository to the identity of the previous version of the last version.

The non-synchronized version determining unit 240 in the foregoing apparatus may perform a corresponding automatic processing method for some specific synchronization failure reasons. If the synchronization processing can be directly continued after the automatic processing, the full copy mode may be avoided, thereby further improving the configuration. Library backup efficiency.

For the convenience of description, the above devices are described separately by function into various units. Of course, the functions of each unit can be implemented in the same software or software and/or hardware in the implementation of the present application.

As can be seen from the description of the above embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of a software plus a necessary universal hardware platform. Based on such understanding, the technical solution of the present application can be embodied in the form of a software product in essence or in the form of a software product, which can be stored in a storage medium such as a ROM/RAM, a disk, A disc or the like includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present application or portions of the embodiments.

The various embodiments in the specification are described in a progressive manner, and the same or similar parts between the various embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiment. The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, ie may be located in one Places, or they can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without any creative effort.

This application can be used in a variety of general purpose or special purpose computing system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics devices, network PCs, small computers, Large computers, decentralized computing environments including any of the above systems or devices, and more.

The application can be described in the general context of computer-executable instructions executed by a computer, such as a program module. Generally, a program module includes routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types. The present application can also be practiced in a distributed computing environment where tasks are performed by remote processing devices that are connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media, including storage devices.

The above description is only a specific embodiment of the present application, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present application. It should be considered as the scope of protection of this application.

210. . . Synchronization unit

220. . . Synchronous successful processing unit

230. . . Synchronization failure processing unit

240. . . Non-synchronizable version determination unit

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings to be used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only Some of the embodiments described in the application can be obtained by those skilled in the art from the drawings.

FIG. 1 is a flowchart of a method for backing up a Subversion configuration library according to an embodiment of the present application;

2 is a schematic structural diagram of a Subversion configuration library backup apparatus according to an embodiment of the present application;

FIG. 3 is another schematic structural diagram of a Subversion configuration library backup apparatus according to an embodiment of the present application.

Claims (10)

A backup method of a Subversion configuration library, which is characterized in that a version attribute is set in advance for a backup configuration library, and the version attribute is used to record an identifier of a last version in the backup configuration library; the backup method includes: according to a version attribute of the backup configuration library, Perform a configuration library synchronization operation; if the synchronization operation is successful, update the version attribute value of the backup configuration repository to the version identifier of the successful synchronization; and if the synchronization operation fails, pass the full copy after determining that the current version is an unsynchronized version. The method backs up the source configuration repository and updates the version property value of the backup configuration repository to the identity of the non-synchronizable version. The method of claim 1, wherein the method for determining that the current version is an unsynchronizable version comprises: obtaining error information that the synchronization operation fails; determining, according to the error information, that the current version is an unsynchronized version; or according to the error information. After the corresponding error processing, the synchronization operation still fails, and it is determined that the current version is an unsynchronized version. The method of claim 2, wherein the error processing is performed according to the error information, including: when the error information is a backup configuration library lock, deleting the synchronization lock attribute of the backup configuration library. The method of claim 2, wherein the error processing is performed according to the error information, including: when the error information is a file lock of the backup configuration library, the lock attribute of the file is deleted. According to the method of claim 2, wherein the error processing is performed according to the error information, including: when the error information is the last version of the backup configuration repository, the last version in the backup configuration repository is deleted, and The version attribute value of the backup configuration repository is modified to the identity of the previous version of the last version. A backup device of the Subversion configuration library, comprising: a synchronization unit, configured to perform a configuration library synchronization operation according to a version attribute of the backup configuration library; and a synchronization success processing unit, configured to be preset when the synchronization operation is successful The version attribute value of the backup configuration repository is updated to the version identifier of the successful synchronization; wherein the pre-set version attribute is used to record the identifier of the last version in the backup configuration repository; and the synchronization failure processing unit is used to fail the synchronization operation. After determining that the current version is an unsynchronizable version, the source configuration repository is backed up by full copy mode, and the version attribute value of the backup configuration repository is updated to the identifier of the non-synchronizable version. The device of claim 6, further comprising: a non-synchronized version determining unit, the unit comprising: an error information obtaining subunit, configured to obtain error information that the synchronization operation fails; the first determining subunit, Determining, according to the error information, that the current version is an unsynchronized version; an error processing subunit for performing corresponding error processing according to the error information; and a second determining subunit for determining whether the synchronization operation fails after the error processing is performed. The current version is a non-synchronizable version. The apparatus of claim 7, wherein the error handling sub-unit deletes the synchronization lock attribute of the backup configuration library when the error information is a backup configuration library lock. The apparatus of claim 7, wherein the error handling sub-unit deletes the locking attribute of the file when the error information is a file lock of the backup configuration library. The device according to claim 7, wherein the error processing is performed according to the error information, including: when the error information is the last version error of the backup configuration library, the error processing subunit deletes the last in the backup configuration library. A version, and the version attribute value of the backup configuration repository is modified to the identity of the previous version of the last version.