AW: AW: Upgrade SVN from 1.0 to 1.3 need help!
From: Markus Karg <markus.karg_at_quipsy.de>
Date: 2006-03-08 09:22:18 CET
André,
Von: Fritsch, Andre (EXT) [mailto:andre.fritsch@siemens.com]
Thanks for your help!
The repositories i look after have a size of about 12 GB seperated in several projects. When i dump and report all projects it will take a lot of time. If i seperate do it per project i will have to run 2 svn instances seperatly, because the dump and import lasts longer than from 5pm to 8 am (the time our developers are at home). For this reason i hoped that there would be possibility to get the upgrad done quicker.
Gruß,
André
___________________________________________________
André Fritsch Telefon +49(5251)8 2 55 96
-----Ursprüngliche Nachricht-----
On Mar 7, 2006, at 14:51, Fritsch, Andre (EXT) wrote:
> I am an admin to a running svn 1.0 installation on red hat enterprise
1.0 is quite old, so you should do this upgrade carefully.
The best idea would be to "dump" your current repository to a textfile with "svnadmin dump" using your current v1.0 svnadmin program. Then "load" that with "svnadmin load" into a new repository created with svnadmin v1.3. See:
http://subversion.tigris.org/faq.html#dumpload
Note that since Subversion 1.1 you have the choice of two different repository backends: BerkeleyDB ("BDB"), which is what you're using now, and the newer "FSFS" storage mechanism which became the default as of Subversion 1.2. I generally recommend FSFS, as it's usually less problematic than BDB, except that there's a problem with FSFS and revisions larger than 2GB until the next version of APR comes out. So if you have such large commits, or expect to have them, you may want to stick with BDB.
http://subversion.tigris.org/issues/show_bug.cgi?id=2453
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.