Upgrading Subversion server from 1.5.5 to 1.6.5 - dump/upgrade/reload, exact steps?

tags:

svn
upgrade

views:

974

answers:

+1 Q:

Upgrading Subversion server from 1.5.5 to 1.6.5 - dump/upgrade/reload, exact steps?

Hi all,

I'm about to upgrade a SVN server from version 1.5.5 to 1.6.5 - all is fine with the actual upgrade, but I'm a little confused about upgrading the actual repositories.

I've read in a few places (here, here), that it's better to dump and reload the repositories rather than using svnadmin upgrade. I assume that I should dump, upgrade the server and then load the dumps back in - however, should I clear the old files out of the repository before loading? If so, what's the best way to do this?

If, before I thoroughly screw up my version control system, someone could give me a quick step-by-step, it would be really helpful!

Cheers, Mark

+1 A:

If you're going to do it that way then you probably want to dump, upgrade, delete and recreate the repo then load it back in again.

I can't say I've ever had any issues just using upgrade though, although you may end up with a less optimal repo structure.

Steven Robbins 2009-10-04 11:22:28

So, would you suggest that I may as well just use upgrade?

Mark B 2009-10-04 11:24:50

Unless it's a particularly big or complicated repo that's what I'd do. Dump and load can take a long time.

Steven Robbins 2009-10-04 11:30:29

I agree. However, you should nevertheless make sure you have a backup before you upgrade. Making a dump is one way to create a backup.

sbi 2009-10-04 11:48:21

Of course, but I would hope his svn is already being backed up regularly :-)

Steven Robbins 2009-10-04 11:51:51

Yep, every half-hour :)

Mark B 2009-10-04 12:12:25

+3 A:

there is a quick step-by-step in the Subversion FAQ:

Shut down svnserve, Apache, and anything else that might be accessing the repository.

svnadmin dump /path/to/repository > dumpfile.txt , using version X of svnadmin.

mv /path/to/repository /path/to/saved-old-repository

Now upgrade to Subversion Y (i.e., build and install Y, replacing X).

svnadmin create /path/to/repository, using version Y of svnadmin.

svnadmin load /path/to/repository < dumpfile.txt , again using version Y of svnadmin.

Copy over hook scripts, etc, from the old repository to the new one.

Restart svnserve, Apache, etc.

more details on dumping and loading in the Subversion book. i assume you studied the subversion 1.6 release notes.

ax 2009-10-04 11:36:48

Yep, I've checked the release notes - thanks though, that was exactly what I was looking for.

Mark B 2009-10-04 11:39:35

Beware, those dumps are big. You *could* use the --deltas option with svn dump, which will somewhat reduce your dump file size. It is slower though, and alternatively you could gzip the dumps on the fly (without --deltas) which will be even more efficient.

RedGlyph 2009-10-04 12:17:32

Noted - thanks!

Mark B 2009-10-09 17:03:09

+2 A:

No, you do not need to dump/load to upgrade, 1.6 was specifically designed to be an easy upgrade using just svnadmin upgrade. I've done it, it worked, I am happy.

The release notes explicitly say there is no need to dump/load the repo.

I would make a backup anyway (just in case), and then do the recommended upgrade. I'd then pack the repo files (svadmin pack) to make future backups quicker and SVN perform faster.

gbjbaanb 2009-10-09 13:23:55

the release notes also say (http://subversion.tigris.org/svn_1.6_releasenotes.html#bdb-forward-deltas): "If you want to achieve the most optimized state of an older [BDB] repository, you still need to perform dump and load of the repository." also see the links in the question.

ax 2009-10-09 17:27:36

Nobody should use a BDB repo. If you do, you still need to dump and load the repo.... into a FSFS one :)

gbjbaanb 2009-10-10 14:08:12

ansaurus

tags:

views:

answers:

Upgrading Subversion server from 1.5.5 to 1.6.5 - dump/upgrade/reload, exact steps?

related questions