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

hotcopy --incremental auto-upgrade Re: Backup strategy sanity check

From: Daniel Shahaf <danielsh_at_elego.de>
Date: Sun, 11 Aug 2013 01:25:24 +0300

Thomas Harold wrote on Sat, Aug 10, 2013 at 10:53:43 -0400:
> With the 'svnadmin hotcopy --incremental' backups, we have to do extra
> checking in the script (comparing reponame/db/format versions) in order
> to make sure that the hotcopy runs correctly.

If you have to do that, please do it correctly:

- Check reponame/format
- Check reponame/db/fs-type
- Check reponame/db/format

(And 1.9 will have 'svnadmin info' which will give you the same information)

> It would have been nice if --incremental would automatically upgrade the
> target repository (and fallback to a full backup) if the versions
> mismatch.

Hmm. Interesting idea, but replacing failure modes with automagical
behaviour is generally looked at with skepticism (is this error _really_
always safe to not tell the admin about?). For the sake of argument,
why shouldn't admins who want this behaviour opt-in to it by having
their scripts do

    svnadmin upgrade $dest
    svnadmin hotcopy --incremental $src $dest

? (Note that 'upgrade' is idempotent, and will exit without error for
already-most-recent-format repositories.)


Received on 2013-08-11 00:26:20 CEST

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.