hotbackup inconsistencies (bdb4.0, bdb4.1, debian)

as debian delivers svn with db4.1 compiled in, we have to recompile svn with db4.0 on every
upgrade to make it working for heavlily used repositories.

the following occurred:

1. compile svn for use db40
2. install it
3. hotbackup got called during the night, it uses:
   db_recover
   db_arch
   which is db4.1_recover, db4.1_arch in debian.

--> hotbackukp rendered all the repositories unusable, they got automatically
    upgraded to db4.1. db_arch did that when cleaning unnecessary logfiles i suppose?

--> but luckily hotbackup copies away the repository BEFORE doing that,
    so we had a working backup.

it would be very nice, if hotbackup and svn are more integrated, so it is not possible to use
commands of different bdb-versions.

i.e. use svnadmin recover, and add something for db_arch? or add the db-version to the repository
configuration, and all svn-related commands check the version before doing something, so e.g.
hotbackup.py bails out before running db4.1_arch?

if svn should support other databases too, it would be anyway necessary (in this case clearly post-1.0).

__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 10 11:35:45 2003