SVN version library migration in Windows

Two servers for SVN migration:
Windows server 2003
Version Library: test
Source server: 192.168.1.14
Target Server: 192.168.1.2
Path: D: \ SVN \ test of the source svn version Library
Path: E: \ svn \ test
 
Method 1: (recommended)

First, note that SVN on the target server is usable. In this article, only their version libraries are used.
Migration.

1. Stop the http service. apache (source server) (target server) is used in this article)
2. cd C: \ Program Files \ Subversion \ bin (installation directory of Subversion) (source server)
3. Run: svnadmin dumpD: \ svn \ test> D: \ svn \ test. dump (source server)
4. Create a test folder (target server) with the same name in the E drive)
5. cd C: \ Program Files \ Subversion \ bin (target server)
6. svnadmin create E: \ svn \ test (target server)
7. test whether the database of the test version can be used. Perform the following operations (target server)
Copy the test. dump File exported on the source server to the target server
8. Svnadmin load E: \ svn \ test <c: \ svn \ test. dump (target server. This is just to import the version library exported from the source server to the current server .)
9. Modify the http configuration file and permissions, or copy the original permission file directly to the new version library. (Target server)
 
Method 2:
 
1. Stop the http service. I use apache.
2. copy all the files under D: \ svn \ test to E: \ svn \ test of 192.168.1.12.
3. Modify the file path in apache and write the new file path.
4. Open the http service, but the condition for this practice is: the operating environment system of the old version of SVN Library and the operating environment system of the new version are the same, and the SVN version is the same.
5. Right-click the local version library and choose TortoiseSVN> Relocate. In the displayed box, enter the IP address of the version library again.
Author: "tony"