
This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
98
|
Chapter 5: Repository Administration
Migrating a Repository
A Subversion filesystem has its data spread throughout various database tables in a
fashion generally understood by (and of interest to) only the Subversion developers
themselves. However, circumstances may arise that call for all, or some subset, of
that data to be collected into a single portable, flat-file format. Subversion provides
such a mechanism, implemented in a pair of
svnadmin subcommands: dump and load.
The most common reason to dump and load a Subversion repository is due to
changes in Subversion itself. As Subversion matures, there are times when certain
changes made to the back-end database schema cause Subversion to be incompati-
ble with previous versions of the repository. The recommended course of action
when you are upgrading across one of those compatibility boundaries is a relatively
simple process:
1. Using your current version of
svnadmin, dump your repositories to dump files.
2. Upgrade to the new version of Subversion.
3. Move your old repositories out of the way, and create new empty ones in their
place using your new
svnadmin.
4. Again using your new
svnadmin, load your dump files into their respective, just-
created repositories.
5. Finally, be sure to copy any customizations from your old repositories ...