CN111209139A - Disaster recovery method and device based on version control management system - Google Patents
Disaster recovery method and device based on version control management system Download PDFInfo
- Publication number
- CN111209139A CN111209139A CN201911385878.0A CN201911385878A CN111209139A CN 111209139 A CN111209139 A CN 111209139A CN 201911385878 A CN201911385878 A CN 201911385878A CN 111209139 A CN111209139 A CN 111209139A
- Authority
- CN
- China
- Prior art keywords
- svn
- server
- main server
- backup
- slave
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 29
- 238000011084 recovery Methods 0.000 title claims abstract description 29
- 239000000126 substance Substances 0.000 claims description 3
- 230000003362 replicative effect Effects 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 10
- 238000004590 computer program Methods 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 238000000354 decomposition reaction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 241000700605 Viruses Species 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
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
- 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/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention discloses a disaster recovery method and a disaster recovery device based on a version control management SVN system, wherein an SVN resource warehouse operating on a main server is backed up to a slave server according to a first preset backup configuration; backing up SVN management data running on the main server to the slave server according to a second preset backup configuration; when the main server fails, the address of the SVN server is switched to the slave server to provide SVN service; and after the failure of the main server is eliminated, copying the SVN management data and the SVN resource warehouse backed up by the secondary server to the main server to recover the SVN service of the main server. The embodiment of the invention can solve the problem of how to continuously provide the service when the SVN encounters the fault in the prior art.
Description
Technical Field
The present invention relates to the field of disaster recovery technologies, and in particular, to a disaster recovery method and apparatus based on a version control management (SVN) system.
Background
The SVN is the most popular version control system for open source code, and in daily work, many software development departments perform version management of data and code through the SVN. With the increasing wide application of the SVN, the data of the resource library used by the SVN for storing the data and the code also increases continuously, the data volume is larger and larger, and the data security problem is particularly important.
When the SVN server cannot normally operate due to human factors, power failure, virus intrusion, and the like, if data cannot be recovered, great influence is inevitably caused to an enterprise. However, the backup only can backup the database data at a certain moment, which may greatly cause inconsistency of the database data before and after restoration and further cause unavailability of the SVN, and therefore, an SVN disaster recovery technology is urgently needed to solve the problem of how to continue providing services when the SVN encounters a failure.
Disclosure of Invention
The embodiment of the invention provides a disaster recovery method and device based on SVN (singular value decomposition), which are used for solving the problem of how to continue providing service when the SVN encounters a fault in the prior art.
The embodiment of the invention provides a disaster recovery method for managing an SVN system based on version control, which is applied to the SVN system comprising a main server and a slave server, and comprises the following steps:
backing up the SVN resource warehouse operated in the main server to the slave server according to a first preset backup configuration;
backing up SVN management data running on the main server to the slave server according to a second preset backup configuration;
when the main server fails, the address of the SVN server is switched to the slave server to provide SVN service;
and after the failure of the main server is eliminated, copying the SVN management data and the SVN resource warehouse backed up by the secondary server to the main server to recover the SVN service of the main server.
Preferably, the backing up the SVN repository running on the primary server to the secondary server according to the first preset backup configuration includes:
and inserting script instructions into files under the SVN resource warehouse catalogs of the main server and the slave server respectively to configure the real-time backup of the SVN resource warehouse between the main server and the slave server.
Preferably, the backing up the SVN management data running on the master server to the slave server according to the second preset backup configuration includes:
inserting a database backup script instruction in the slave server;
adding the database backup script instruction into a timing task;
and backing up the SVN management data of the main server to the slave server according to the timing period of the timing task.
Preferably, the copying the SVN management data and the SVN resource repository backed up from the server to the primary server to restore the SVN service includes:
and copying the SVN management data backed up by the secondary server to the configuration file of the main server, and copying the SVN resource warehouse backed up by the secondary server to the SVN resource warehouse of the main server to restore the SVN service of the main server.
The SVN management data comprises SVN user names, corresponding user permissions and resource library restoration commands.
The embodiment of the invention also provides a disaster recovery device based on the version control management SVN system, which is applied to the SVN system comprising a main server and a slave server, and comprises: the system comprises a first backup unit, a second backup unit and a recovery unit; wherein the content of the first and second substances,
the first backup unit is used for backing up the SVN resource warehouse operated in the main server to the slave server according to a first preset backup configuration;
the second backup unit is used for backing up the SVN management data running on the main server to the slave server according to a second preset backup configuration;
the recovery unit is used for switching the address of the SVN server to the slave server to provide the SVN service when the main server fails; and after the failure of the main server is eliminated, copying the SVN management data and the SVN resource warehouse backed up by the secondary server to the main server to recover the SVN service of the main server.
Preferably, the first backup unit is configured to backup, according to a first preset backup configuration, the SVN repository running on the master server to the slave server, and specifically configured to:
and inserting script instructions into files under the SVN resource warehouse catalogs of the main server and the slave server respectively to configure the real-time backup of the SVN resource warehouse between the main server and the slave server.
Preferably, the second backup unit is configured to backup, according to a second preset backup configuration, the SVN management data running on the master server to the slave server, and specifically configured to:
inserting a database backup script instruction in the slave server;
adding the database backup script instruction into a timing task;
and backing up the SVN management data of the main server to the slave server according to the timing period of the timing task.
Preferably, the restoring unit is configured to copy the SVN management data and the SVN resource repository backed up by the slave server to the master server to restore the SVN service, and specifically is configured to:
and copying the SVN management data backed up by the secondary server to the configuration file of the main server, and copying the SVN resource warehouse backed up by the secondary server to the SVN resource warehouse of the main server to restore the SVN service of the main server.
The SVN management data comprises SVN user names, corresponding user permissions and resource library restoration commands.
The invention has the following beneficial effects:
according to the disaster recovery method and device based on the version control management SVN system, provided by the embodiment of the invention, an SVN resource warehouse operating in a main server is backed up to a slave server according to a first preset backup configuration; backing up SVN management data running on the main server to the slave server according to a second preset backup configuration; when the main server fails, the address of the SVN server is switched to the slave server to provide SVN service; and after the failure of the main server is eliminated, copying the SVN management data and the SVN resource warehouse backed up by the secondary server to the main server to recover the SVN service of the main server. The invention provides a disaster recovery method based on an SVN system, when a main server of the SVN system fails, SVN management data and an SVN resource warehouse can be backed up from the main server to a slave server respectively, wherein the backup of the SVN resource warehouse can adopt a real-time backup mechanism, so that the SVN resource warehouse is ensured not to be lost, and the usability of the SVN resource warehouse is ensured not to be influenced; different modes are respectively adopted for backing up the SVN management data and the SVN resource warehouse, so that the backup performance can be improved, and the safety of the data can be further ensured; and when the main server fails, the auxiliary server is adopted to provide the SVN service, and after the main server recovers to be normal, the SVN management data and the SVN resource library in the auxiliary server are restored to the main server from the auxiliary server, so that the continuity of the SVN service is ensured.
Drawings
Fig. 1 is a flowchart of a disaster recovery method for managing an SVN system based on version control according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a disaster recovery device for managing an SVN system based on version control according to an embodiment of the present invention.
Detailed Description
Aiming at the problem of how to continuously provide services when an SVN encounters a fault in the prior art, the disaster recovery method based on the version control management SVN system provided by the embodiment of the invention is applied to the SVN system comprising a main server and a slave server, the flow of the method of the invention is shown in fig. 1, and the execution steps are as follows:
102, backing up SVN management data running on the main server to the slave server according to a second preset backup configuration;
103, when the main server fails, switching the address of the SVN server to the slave server to provide SVN service;
here, the method specifically includes: 1. obtaining SVN user and authority data according to the backup SVN management data of the slave server; 2. respectively writing the user and the authority data into a user and authority configuration file of the SVN service; 3. executing the instruction script and starting an SVN (singular value decomposition) resource warehouse of the slave server; 4. the client switches the accessed service address to the SVN service address provided from the server.
And step 104, copying the SVN management data and the SVN resource warehouse backed up by the secondary server to the primary server to recover the SVN service of the primary server after the failure of the primary server is eliminated.
Preferably, the backing up the SVN repository running on the primary server to the secondary server according to the first preset backup configuration includes:
and inserting script instructions into files under the SVN resource warehouse catalogs of the main server and the slave server respectively to configure the real-time backup of the SVN resource warehouse between the main server and the slave server.
Specifically, firstly, a backup SVN resource repository is created from a server, and the following script commands are written in a configuration hooks/start-commit file under the backup SVN resource repository directory:
#！/bin/bash
USER＝"$2"
if["$USER"＝"test"]；then exit 0；fi
echo"Only the testuser may commit new revisions">&2
exit 1
configuring a hooks/pre-revprop-change file, and writing the following script commands:
#！/bin/bash
USER＝"$3"
if["$USER"＝"test"]；then exit 0；fi
echo"Only the testuser may commit new revisions">&2
exit 1
secondly, writing the following script command in the hooks/post-commit file under the SVN resource warehouse directory of the main server:
#！/bin/sh
REPOS＝"$1"
REV＝"$2"
export LC_CTYPE＝zh_CN.UTF-8
/bin/svnsync synchronize--non-interactive http://192.168.15.177/svn/repos--username test--password test
executing a command to initialize the SVN resource repository of the backup server, as follows:
svnsync init--non-interactive--username test--password 123456http://172.19.1.148/svn/repos file:///home/svn/repos/repos
svnsync sync http://172.19.1.148/svn/repos--username test--password123456
the real-time backup command is enabled as follows:
/bin/svnsync synchronize--non-interactive http://172.19.1.148/svn/test--username test--password 123456。
preferably, the backing up the SVN management data running on the master server to the slave server according to the second preset backup configuration includes:
inserting a database backup script instruction in the slave server;
adding the database backup script instruction into a timing task;
and backing up the SVN management data of the main server to the slave server according to the timing period of the timing task.
Specifically, the backup script instructions are as follows:
preferably, the copying the SVN management data and the SVN resource repository backed up from the server to the primary server to restore the SVN service includes:
and copying the SVN management data backed up by the secondary server to the configuration file of the main server, and copying the SVN resource warehouse backed up by the secondary server to the SVN resource warehouse of the main server to restore the SVN service of the main server. Here, the specific implementation procedure is as follows:
firstly, building SVN service;
secondly, copying the authority and the user data from a database of the slave server to an authority and user configuration file respectively;
thirdly, copying the SVN resource warehouse of the slave server to the SVN resource warehouse root directory of the master server;
fourthly, running a script command configured by the SVN resource warehouse of the batch setting main service, and comprising the following steps:
#！/bin/bash
# warehouse name array
repos_arr＝(shareRepos shareRepos2 wyyck tyjs skcp tyjs1 hh hh2 test8normal test10 testaa testbb zhouhonggang)
# walk operation
for repos in${repos_arr[*]}
do
reposFullPath＝$1$repos
reposHttpRootPath＝$2$repos
reposPostCommitPath＝$reposFullPath/hooks/post-commit
echo-e\#\！\/bin\/bash"\n""\n"REPOS\＝\"\$1\""\n"REV\＝\"\$2\""\n"export LC_CTYPE\＝zh_CN.UTF\-8"\n""\n"\/bin\/svnsync synchronize\-\-non\-interactive$reposHttpRootPath\-\-username$3\-\-password$4>$reposPostCommitPath
done
The SVN management data comprises SVN user names, corresponding user permissions and resource library restoration commands.
According to the disaster recovery method based on the version control management SVN system provided by the embodiment of the invention, according to a first preset backup configuration, an SVN resource warehouse operating in a main server is backed up to a slave server; backing up SVN management data running on the main server to the slave server according to a second preset backup configuration; when the main server fails, the address of the SVN server is switched to the slave server to provide SVN service; and after the failure of the main server is eliminated, copying the SVN management data and the SVN resource warehouse backed up by the secondary server to the main server to recover the SVN service of the main server. The invention provides a disaster recovery method based on an SVN system, when a main server of the SVN system fails, SVN management data and an SVN resource warehouse can be backed up from the main server to a slave server respectively, wherein the backup of the SVN resource warehouse can adopt a real-time backup mechanism, so that the SVN resource warehouse is ensured not to be lost, and the usability of the SVN resource warehouse is ensured not to be influenced; different modes are respectively adopted for backing up the SVN management data and the SVN resource warehouse, so that the backup performance can be improved, and the safety of the data can be further ensured; and when the main server fails, the auxiliary server is adopted to provide the SVN service, and after the main server recovers to be normal, the SVN management data and the SVN resource library in the auxiliary server are restored to the main server from the auxiliary server, so that the continuity of the SVN service is ensured.
Based on the same inventive concept, an embodiment of the present invention provides a disaster recovery device for managing an SVN system based on version control, which is applied to an SVN system including a master server and a slave server, and has a structure as shown in fig. 2, including: a first backup unit 21, a second backup unit 22, and a restoration unit 23; wherein the content of the first and second substances,
the first backup unit 21 is configured to backup the SVN repository running on the master server to the slave server according to a first preset backup configuration;
the second backup unit 22 is configured to backup, according to a second preset backup configuration, the SVN management data running on the master server to the slave server;
the recovery unit 23 is configured to, when the master server fails, switch an address of the SVN server to the slave server to provide the SVN service; and after the failure of the main server is eliminated, copying the SVN management data and the SVN resource warehouse backed up by the secondary server to the main server to recover the SVN service of the main server.
Preferably, the first backup unit 21 is configured to backup, according to a first preset backup configuration, the SVN repository running on the master server to the slave server, and specifically configured to:
and inserting script instructions into files under the SVN resource warehouse catalogs of the main server and the slave server respectively to configure the real-time backup of the SVN resource warehouse between the main server and the slave server.
Preferably, the second backup unit 22 is configured to backup, according to a second preset backup configuration, the SVN management data running on the master server to the slave server, and specifically configured to:
inserting a database backup script instruction in the slave server;
adding the database backup script instruction into a timing task;
and backing up the SVN management data of the main server to the slave server according to the timing period of the timing task.
The restoring unit 23 is configured to copy the SVN management data and the SVN resource repository backed up by the slave server to the master server to restore the SVN service, and specifically configured to:
and copying the SVN management data backed up by the secondary server to the configuration file of the main server, and copying the SVN resource warehouse backed up by the secondary server to the SVN resource warehouse of the main server to restore the SVN service of the main server.
The SVN management data comprises SVN user names, corresponding user permissions and resource library restoration commands.
It should be understood that the implementation principle and process of the disaster recovery device based on the version control management SVN system provided in the embodiment of the present invention are similar to those in fig. 1 and the embodiment shown above, and are not described herein again.
According to the disaster recovery method and device based on the version control management SVN system, provided by the embodiment of the invention, an SVN resource warehouse operating in a main server is backed up to a slave server according to a first preset backup configuration; backing up SVN management data running on the main server to the slave server according to a second preset backup configuration; when the main server fails, the address of the SVN server is switched to the slave server to provide SVN service; and after the failure of the main server is eliminated, copying the SVN management data and the SVN resource warehouse backed up by the secondary server to the main server to recover the SVN service of the main server. The invention provides a disaster recovery method based on an SVN system, when a main server of the SVN system fails, SVN management data and an SVN resource warehouse can be backed up from the main server to a slave server respectively, wherein the backup of the SVN resource warehouse can adopt a real-time backup mechanism, so that the SVN resource warehouse is ensured not to be lost, and the usability of the SVN resource warehouse is ensured not to be influenced; different modes are respectively adopted for backing up the SVN management data and the SVN resource warehouse, so that the backup performance can be improved, and the safety of the data can be further ensured; and when the main server fails, the auxiliary server is adopted to provide the SVN service, and after the main server recovers to be normal, the SVN management data and the SVN resource library in the auxiliary server are restored to the main server from the auxiliary server, so that the continuity of the SVN service is ensured.
Those of ordinary skill in the art will understand that: the figures are merely schematic representations of one embodiment, and the blocks or flow diagrams in the figures are not necessarily required to practice the present invention.
From the above description of the embodiments, it is clear to those skilled in the art that the present invention can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which may be stored in a storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for apparatus or system embodiments, since they are substantially similar to method embodiments, they are described in relative terms, as long as they are described in partial descriptions of method embodiments. The above-described embodiments of the apparatus and system are merely illustrative, and the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations are included in a specific order, but it should be clearly understood that the operations may be executed out of the order presented herein or in parallel, and the sequence numbers of the operations, such as 201, 202, 203, etc., are merely used for distinguishing different operations, and the sequence numbers themselves do not represent any execution order. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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.
While alternative embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following appended claims be interpreted as including alternative embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various modifications and variations can be made in the embodiments of the present invention without departing from the spirit or scope of the embodiments of the invention. Thus, if such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to encompass such modifications and variations.
Claims (10)
1. A disaster recovery method for managing an SVN system based on version control is applied to the SVN system comprising a main server and a slave server, and is characterized in that the method comprises the following steps:
backing up the SVN resource warehouse operated in the main server to the slave server according to a first preset backup configuration;
backing up SVN management data running on the main server to the slave server according to a second preset backup configuration;
when the main server fails, the address of the SVN server is switched to the slave server to provide SVN service;
and after the failure of the main server is eliminated, copying the SVN management data and the SVN resource warehouse backed up by the secondary server to the main server to recover the SVN service of the main server.
2. The method according to claim 1, wherein the backing up the SVN repository running on the primary server to the secondary server according to the first preset backup configuration comprises:
and inserting script instructions into files under the SVN resource warehouse catalogs of the main server and the slave server respectively to configure the real-time backup of the SVN resource warehouse between the main server and the slave server.
3. The method according to claim 1, wherein the backing up the SVN management data running on the master server to the slave server according to a second preset backup configuration comprises:
inserting a database backup script instruction in the slave server;
adding the database backup script instruction into a timing task;
and backing up the SVN management data of the main server to the slave server according to the timing period of the timing task.
4. The method of claim 1, wherein the replicating the backup SVN management data and SVN repository of the slave server to a master server to restore SVN services comprises:
and copying the SVN management data backed up by the secondary server to the configuration file of the main server, and copying the SVN resource warehouse backed up by the secondary server to the SVN resource warehouse of the main server to restore the SVN service of the main server.
5. The method of any of claims 1 to 4, wherein the SVN management data comprises SVN user names and corresponding user permissions, and restore repository commands.
6. A disaster recovery device for managing an SVN system based on version control, the device being applied to the SVN system comprising a master server and a slave server, the disaster recovery device comprising: the system comprises a first backup unit, a second backup unit and a recovery unit; wherein the content of the first and second substances,
the first backup unit is used for backing up the SVN resource warehouse operated in the main server to the slave server according to a first preset backup configuration;
the second backup unit is used for backing up the SVN management data running on the main server to the slave server according to a second preset backup configuration;
the recovery unit is used for switching the address of the SVN server to the slave server to provide the SVN service when the main server fails; and after the failure of the main server is eliminated, copying the SVN management data and the SVN resource warehouse backed up by the secondary server to the main server to recover the SVN service of the main server.
7. The apparatus according to claim 6, wherein the first backup unit is configured to backup, according to a first preset backup configuration, the SVN repository running on the master server to the slave server, and is specifically configured to:
and inserting script instructions into files under the SVN resource warehouse catalogs of the main server and the slave server respectively to configure the real-time backup of the SVN resource warehouse between the main server and the slave server.
8. The apparatus according to claim 7, wherein the second backup unit is configured to backup, according to a second preset backup configuration, the SVN management data running on the master server to the slave server, and is specifically configured to:
inserting a database backup script instruction in the slave server;
adding the database backup script instruction into a timing task;
and backing up the SVN management data of the main server to the slave server according to the timing period of the timing task.
9. The apparatus according to claim 6, wherein the restoring unit is configured to copy the SVN management data and the SVN resource repository backed up by the secondary server to the primary server to restore the SVN service, and is specifically configured to:
and copying the SVN management data backed up by the secondary server to the configuration file of the main server, and copying the SVN resource warehouse backed up by the secondary server to the SVN resource warehouse of the main server to restore the SVN service of the main server.
10. The apparatus according to any one of claims 6 to 9, wherein the SVN management data comprises SVN user names and corresponding user permissions, and repository restore commands.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911385878.0A CN111209139B (en) | 2019-12-29 | 2019-12-29 | Disaster recovery method and device based on version control management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911385878.0A CN111209139B (en) | 2019-12-29 | 2019-12-29 | Disaster recovery method and device based on version control management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111209139A true CN111209139A (en) | 2020-05-29 |
| CN111209139B CN111209139B (en) | 2024-06-18 |
Family
ID=70783827
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911385878.0A Active CN111209139B (en) | 2019-12-29 | 2019-12-29 | Disaster recovery method and device based on version control management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111209139B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103618788A (en) * | 2013-11-26 | 2014-03-05 | 曙光信息产业股份有限公司 | System high-availability method supporting B/S structure |
| KR20140050903A (en) * | 2012-10-22 | 2014-04-30 | 주식회사 엔써티 | Real time backup system of database, system of recovering data and method of recovering data |
| CN104679614A (en) * | 2015-03-31 | 2015-06-03 | 成都文武信息技术有限公司 | Database disaster backup system |
| CN105739960A (en) * | 2014-12-11 | 2016-07-06 | 上海尚景信息技术有限公司 | Software development environment framework capable of being continuously integrated |
| CN106293701A (en) * | 2016-07-26 | 2017-01-04 | 浪潮软件股份有限公司 | Multi-tenant version management application engine design method based on cloud server |
| CN107729066A (en) * | 2017-11-08 | 2018-02-23 | 重庆扬讯软件技术股份有限公司 | One kind is based on SVN resources banks automation structure dissemination method and device |
| CN107861838A (en) * | 2017-10-18 | 2018-03-30 | 福建中金在线信息科技有限公司 | Method and device of the automated back-up MySQL database from storehouse |
| CN108011783A (en) * | 2017-12-07 | 2018-05-08 | 郑州云海信息技术有限公司 | The backup method and standby system of a kind of diagnosis server |
| CN109324928A (en) * | 2018-09-13 | 2019-02-12 | 中通国脉物联科技南京有限公司 | A kind of method of automatically backup data file |
| CN110120983A (en) * | 2019-06-14 | 2019-08-13 | 浪潮软件集团有限公司 | The method and system of SVN real-time synchronization backup is realized based on inotify and rsync automation installation and deployment |
-
2019
- 2019-12-29 CN CN201911385878.0A patent/CN111209139B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20140050903A (en) * | 2012-10-22 | 2014-04-30 | 주식회사 엔써티 | Real time backup system of database, system of recovering data and method of recovering data |
| CN103618788A (en) * | 2013-11-26 | 2014-03-05 | 曙光信息产业股份有限公司 | System high-availability method supporting B/S structure |
| CN105739960A (en) * | 2014-12-11 | 2016-07-06 | 上海尚景信息技术有限公司 | Software development environment framework capable of being continuously integrated |
| CN104679614A (en) * | 2015-03-31 | 2015-06-03 | 成都文武信息技术有限公司 | Database disaster backup system |
| CN106293701A (en) * | 2016-07-26 | 2017-01-04 | 浪潮软件股份有限公司 | Multi-tenant version management application engine design method based on cloud server |
| CN107861838A (en) * | 2017-10-18 | 2018-03-30 | 福建中金在线信息科技有限公司 | Method and device of the automated back-up MySQL database from storehouse |
| CN107729066A (en) * | 2017-11-08 | 2018-02-23 | 重庆扬讯软件技术股份有限公司 | One kind is based on SVN resources banks automation structure dissemination method and device |
| CN108011783A (en) * | 2017-12-07 | 2018-05-08 | 郑州云海信息技术有限公司 | The backup method and standby system of a kind of diagnosis server |
| CN109324928A (en) * | 2018-09-13 | 2019-02-12 | 中通国脉物联科技南京有限公司 | A kind of method of automatically backup data file |
| CN110120983A (en) * | 2019-06-14 | 2019-08-13 | 浪潮软件集团有限公司 | The method and system of SVN real-time synchronization backup is realized based on inotify and rsync automation installation and deployment |
Non-Patent Citations (2)
| Title |
|---|
| 张天;颜秀铭;: "基于云计算的网络教育平台构建研究", 科技信息, no. 34 * |
| 张天;颜秀铭;: "基于云计算的网络教育平台构建研究", 科技信息, no. 34, 5 December 2012 (2012-12-05) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111209139B (en) | 2024-06-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106407356B (en) | Data backup method and device | |
| US9519656B2 (en) | System and method for providing a virtualized replication and high availability environment | |
| KR101960993B1 (en) | Efficient application-aware disaster recovery | |
| US9875160B2 (en) | Efficiently providing virtual machine reference points | |
| US9405630B2 (en) | Methods and apparatus to perform site recovery of a virtual data center | |
| US8612799B2 (en) | Method and apparatus of backing up subversion repository | |
| EP3535955B1 (en) | Systems, devices and methods for managing file system replication | |
| CN105843707A (en) | Quick recovery method and equipment of database | |
| CN105518694A (en) | Reverse replication to rollback corrupted files | |
| CN110727547A (en) | System and method for protecting Docker application container | |
| US10387262B1 (en) | Federated restore of single instance databases and availability group database replicas | |
| US10635636B1 (en) | Hyper-V virtual machine synthetic full backup where user and recovery snapshots coexist | |
| US8959061B1 (en) | Rapid restore from a prepared system image | |
| CN111209139B (en) | Disaster recovery method and device based on version control management system | |
| CN115080309A (en) | Data backup system, method, storage medium, and electronic device | |
| US11474707B2 (en) | Data loss recovery in a secondary storage controller from a primary storage controller | |
| US8676761B1 (en) | Preparation of a system image for rapid restore | |
| CN111966532A (en) | Database management method and device, electronic equipment and medium | |
| CN104809033A (en) | Backup method and system | |
| CN117389713B (en) | Storage system application service data migration method, device, equipment and medium | |
| US10545835B2 (en) | Backup appliance replication to provide virtual machine recovery at a remote site | |
| Jin et al. | Baking Disaster-Proof Kubernetes Applications with Efficient Recipes | |
| CN117539678A (en) | Backup data generation method and device, disaster recovery system and electronic equipment | |
| US9268576B1 (en) | Physical replica utilizing replica virtual storage for computer system | |
| US9135258B1 (en) | Redundant backup elimination |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |