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

Re: a "proper" backup tool

From: Andy Whitcroft <apw_at_shadowen.org>
Date: 2004-07-06 18:11:34 CEST

--On 02 July 2004 17:36 +0200 Michael <tigris@zzZZzz.net> wrote:

> I've been reading a discussion about a "proper" backup tool and now I'm
> wondering if I misunderstand something in the nature of svn... Can
> someone explain what is wrong with this backup policy... Say, I want to
> keep a copy of repository. To make it harder -- remote one. Isn't it
> achieved with something like
>
> RREV="`ssh user@host "svnlook youngest /repo"`"
> REV="`svnlook youngest /repo`"
> if [ "${REV}" != "${RREV}" ] ; then
> REV="`expr ${REV} + 1`"
> ssh user@host "svnadmin dump /repo -r ${REV}:HEAD --incremental" \
> | svnadmin load /repo
> fi
>
> Well, of course, one can add conditional creation of the local repo,
> more error checking would make sense, maybe, setting umasks if needed,
> and even compression filter, but those are unnecessary details.
>
> Wouldn't this pattern get you a proper copy of the repository?

If you want a valid and accessible copy, what about svn-push
(contrib/client-side/svn-push). That does the same thing essentially?

-apw

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 6 20:54:51 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.