[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

BDB4.3 conversion

From: Simon Large <slarge_at_slarge.plus.com>
Date: 2005-05-25 22:18:16 CEST

Hi folks,

Your FAQ gives the following method of upgrading to BDB4.3

* Make sure no process is accessing the repository (stop Apache,
  svnserve, restrict access via file://, svnlook, svnadmin, etc.)

* Using an older svnadmin binary (that is, linked to an older
BerkeleyDB):
     1. Recover the repository: 'svnadmin recover /path/to/repository'
     2. Make a backup of the repository.
     3. Delete all unused log files. You can see them by running
        'svnadmin list-unused-dblogs /path/to/repeository'
     4. Delete the shared-memory files. These are files in the
        repository's db/ directory, of the form __db.00*

Steps 3 & 4 sound potentially scary for inexperienced users, and I was
wondering if you could achieve the same thing more easily using these
steps:

1. svnadmin hotcopy /path/to/repos /path/to/repos43
2. mv /path/to/repos /path/to/backup
3. mv /path/to/repos43 /path/to/repos

Simon

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 25 22:18:39 2005

This is an archived mail posted to the Subversion Dev mailing list.