Data Migration in the Subversion Database

The Subversion database data migration company's Subversion server often shuts down automatically due to computer hardware reasons. You need to reinstall a server. The original Subversion Server was deployed on Windows XP using the VisualSVN Server. Now, we take this opportunity to migrate it to the Linux system. Therefore, you need to migrate the original version Library to the new server. The method for installing the Subversion server on www.2cto.com Linux is described in the previous article. This article only describes how to migrate version database data on the previously configured Subversion server. After the following two simple steps, the version library is migrated. 1. on the old server, export the version Library to the dump file on the Windows installed in the original Subversion. > Svnadmin dump myrepos> myrepos. after a long time, dump obtains a large file named myrepos. dump: this file is much larger than the original version library itself, because in the file, each version of each file is saved in the form of complete text. Svnadmin dump reads the revision tree from the version library and performs the same process as other "readers" (such as svn checkout). Therefore, you can run this command safely at any time. Www.2cto.com 2. On the new server, import the version library to copy the myrepos. dump file to the new server, create a new version library, and import the dump file. $ Svnadmin create/home/svn/repos/myrepos $ svnadmin load/home/svn/repos/myrepos <myrepos. dump
It takes a long time for the svnadmin load command to import each revision in the dump file in sequence. This process is the same as the operation that uses the common Subversion client to directly submit to the version library, therefore, a new version library that is identical to the original version library is obtained.