VISUALSVN Server Library Migration (RPM)

Transferred from: http://blog.csdn.net/yuhuijun_1/article/details/9762683

First, VISUALSVN server Manager, contains two paths, one is the installation path, such as native: C:\Program files\visualsvn Server, one is the library path, such as native: C:\Repositories, where Repositories includes project files and project information files, important project information files are Authz and Htpasswd,authz are Directory access control files, htpasswd is VisualSVN Server The manager user and password log files are now migrated to VISUALSVN Server Manager in the following ways:
For example:
Original server A,VISUALSVN Server Manager
Current server B,VISUALSVN Server Manager
Steps:
1. Copy the repositories folder on a to B
2. Open VisualSVN Server Manager on B
3. Right-click Repositories, select Import existing in All Tasks repository
4. Select the project folder in step 1 to import until all projects have been imported to completion
5. Replace the Authz and htpasswd files so that the user and user rights in VISUALSVN Server Manager are consistent with the previous

The first time the migration, did not find the user and user rights of the file, and then add users and assign permissions, wasted a lot of time, later, the server changed again, forced to make a second migration, at this time, do not want to add a user and assign permissions, also feel that there is no other way, so, First view and record the size of all files, and then add users to see which file found the change, and later learned the role of Authz and htpasswd files, hehe

VISUALSVN Server repository migrated to Linux (contains all versions, permissions, user information)

Windows Server deep poisoning, from windows to CentOS, so to transfer the original services to Linux, SVN transfer encountered some problems, took three days to go a lot of detours, now finally solved the SVN migration problem, recorded:
On Windows we use VISUALSVN Server as the SVN service, and Linux is a compiled and installed Subversion 1.7.7.
Windows SVN repository at E:\svnrepositories,linux in/data/svnrepos
1th step, Export VISUALSVN Warehouse: svnadmin dump E:\SVNREPOSITORIES\REPO1 E:\repo1.dump
2nd step, create the same name on the Linux side of the warehouse: Svnadmin CREATE/DATA/SVNREPOS/REPO1
3rd step, load Windows Export library on Linux side:
Cd/data/svnrepos
Svnadmin Load REPO1 < Repo1.dump
So far, the REPO1 library has been imported into the subversion of Linux, but the user information and permissions information has not been imported (this is also a problem I have been tossing for a long time), continue:
4th step, upload E:\SVNRepositories\authz to/data/svnrepos
Copy E:\SVNRepositories\htpasswd to passwd and upload to/data/svnrepos after modification
The modified passwd format is as follows (in fact, user name = password):
[Users]
User1 = 123
User2 = 456
5th, modify the/conf/svnserve.conf of the warehouse so that it points to the two files uploaded in step 4th:
[General]
Anon-access = None
auth-access = Write
Password-db =.. /.. /passwd
Authz-db =.. /.. /authz
This is done here, with the command svnserve-d-r/data/svnrepos/to start the Subversion service.
There is also a problem is passwd file original password information is lost, due to the use of the Apache password file under Windows, the password used by the MD5 encryption, and under the Linux svn passwd file password is in clear form saved. So the original MD5 password will not be used.
I only used REPO1 this warehouse, if there are multiple warehouses like steps, export the import separately, and modify the warehouse/conf/svnserve.conf
If you follow the above method or not, start svnserve with--log-file./log.txt parameter to view error messages

VISUALSVN Server Library Migration (RPM)