SVN requirements: Move to an offsite cloud environment and the migration process minimizes the time it takes to impact users.
Several common scenarios for SVN migration:
First: The entire SVN Library directory package Migration, the original library size 17G, packaging and migration time estimate time of about 5 hours, the interruption does not meet the requirements.
The second kind: svnadmin dump export Load Import Mode migration: All version export size exceeds the disk remaining space (not less than 40G), the interruption does not meet the requirements.
The Third Kind: The first full-volume synchronization by Svnsync Hook script synchronization, incremental synchronization during migration (estimated the fastest time 10 minutes or so).
Using the Svnsync synchronization process:
1. The original SVN server and the target SVN server
Open account for synchronization on both sides (best account password consistent)
2. On the target SVN server:
Use the SVN-brought hook script to change the following:
Path: D:\svn_repository\hooks\pre-revprop-change.tmpl
Change the last three lines to exit 0 as follows:
Repos= "$"
rev= "$"
User= "$"
Propname= "$4"
Action= "$"
#if ["$ACTION" = "M"-a "$PROPNAME" = "Svn:log"]; Then exit 0; Fi
#echo "Changing revision properties other than Svn:log is prohibited" >&2
Exit 0
Create a new Pre-revprop-change.bat file, copy the last two lines of Pre-revprop-change, or enter exit 0 directly.
Exit 0
Restart the SVN service.
The next initialization before synchronization, format svnsync init target library path Source Library path
Svnsync Init svn://127.0.0.1/svn://61.174.30.194/
If error: Repository have not been enabled to accept revision Propchanges;ask the administrator to create a pre-revprop-change ho Ok.
Pre-revprop-change.bat checks if this script file exists, such as whether the file is properly formatted. My side. After creating the Pre-revprop-change.bat file with a text document under Windows server2008, it is not an executable file, but a TXT file type. This troubleshooting has wasted a lot of time and has been initialized unsuccessfully. Create a new executable file format from your Win7 machine pre-revprop-change.bat to the server side test OK.
Start syncing:
Svnsync Sync svn://127.0.0.1/
3.SVN After migration change the domain name point to test svn update times wrong:
Repository UUID ' 60f49f27-8aaa-164f-9098-701db8904462 ' doesn ' t match expected
The reasons are:
The UUID of the original repository creator is the former, and the UUID of the latter is now being manipulated. Therefore, the current workaround is to update the UUID of the repository with the relevant commands.
To view the UUID of the original svn:
D:\svnrepository>svnlook UUID D:\svnrepository
1024ede3-db12-4f4b-a8b4-28f755881912
To view the new SVN uuid:
C:\users\administrator>svnlook UUID D:\svn_repository
60f49f27-8aaa-164f-9098-701db8904462
Change the new SVN uuid to the same as the original SVN:
C:\users\administrator>svnadmin setuuid D:\svn_repository 1024ede3-db12-4f4b-a8b 4-28f755881912
Again, SVN update test OK.
See if the version numbers on both sides are consistent after synchronizing Svnlook youngest D:\svnrepository
This article is from the "E-space" blog, please be sure to keep this source http://iceeggplant.blog.51cto.com/1446843/1595591
Windows SVN Repository Migration Summary