Upgrading from 1.1.x to 1.2.0 on window servers

Hi,

Heads-up from buildnotes.txt: (didn't see this in any emails)

***** IMPORTANT *** Upgrading from 1.1.x to 1.2.x *** IMPORTANT *****

In this release, we've upgraded BerkeleyDB from version 4.2.52 to
4.3.27. If you are currently using Subversion 1.1.x as a server on
Windows with BerkeleyDB, use the following steps to upgrade your
repositories:

  -- Make sure nobody is using the repository (stop Apache/svnserve,
     restrict access via file://).
  -- For each repository, using the old (1.1.x) binaries:
     -- Run "svnadmin recover <repos-dir>";
     -- Create a backup of the repository;
     -- Run "svnadmin list-unused-dblogs <repos-dir>"
        and remove the listed files;
     -- Delete all the "<repos-dir>\db\__db.00?" files.
  -- Upgrade Subversion.

Once again, this is only necessary for repositories based on BDB.
You do NOT have to dump/reload your repositories.

*********************************************************************

We still have over 2 dozen bdb repositories so I've written a NAnt
script to perform this upgrade process ('tis part of a suite of NAnt
scripts aiding Subversion administration when you have lots of repos)
and it's working okay on test repos and hotcopies of production,
however for the life of me I can't seem to get any output from:

svnadmin list-unused-dblogs <repos-dir>

I assume it's because there are no unused-dblogs to list :)

Paranoia warrants testing this before running on production, since
hotcopies clean the logs right? I've tried creating test repos with
svnadmin --bdb-log-keep on v1.1.4 and then importing and adding,
but I can't seem to make any dblogs unused. Any clues how?

Also, what are these "<repos-dir>\db\__db.00?" files we're deleting?

cheers
si

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 24 10:24:53 2005