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

Re: Backing up - is db/current written last?

From: Daniel Berlin <dberlin_at_dberlin.org>
Date: 2005-07-06 00:20:45 CEST

On Mon, 2005-07-04 at 14:02 +0200, Jacob Atzen wrote:
> On Sat, Jul 02, 2005 at 10:32:37PM -0400, Daniel Berlin wrote:
> > Rsync builds the list of files first, *then* transfers them.
> >
> > Thus, the case to worry about is if it transfers db/current *after*
> > another commit has occurred during the rsync (and the newly created
> > revision file is thus not in rsync's list of files), and then you have a
> > db/current that refers to something that wasn't transferred.
> >
> > Hence the reason to transfer it first.
>
> Why not use svnadmin hotcopy[1] and stop worrying instead?

Because it takes time to copy 6.9 gig around to a temporary directory :)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 6 01:26:22 2005

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