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

RE: backing up a repository over a network

From: D.J. Heap <djheap_at_dhiprovo.com>
Date: 2003-06-10 01:49:52 CEST

I don't think the temp tree is created in temporary files -- it uses
space within the repository database. So it has not changed *logically*
after the temp area is discarded. Physically (on disk) it has changed,
though not much for read operations, usually.

Of course, this is just my understanding from some code and docs perusal
and watching the database as I perform operations.


-----Original Message-----
From: Faheem Mitha [mailto:faheem@email.unc.edu]
Sent: Monday, June 09, 2003 5:19 PM
To: SVN Dev List
Subject: Re: backing up a repository over a network

On 9 Jun 2003 cmpilato@collab.net wrote:

> Without seeing exactly what you did and in what order you did those
> things, I'm not able to really poke a guess at what ails you. All I
> say is that the folks at Sleepycat recommend a particular algorithm
> making hot backups of Berkeley DB environments which is guaranteed to
> not screw stuff up, and it is that algorithm which hot-backup.py
> follows.

You misunderstand. This is not a complaint or request for help. I just
wondered why, if the files created are temporary, that the repository
appears to have changed even after the transaction (eg. `svn co ...')
completed. Clearly this is no problem as such.

> If we can agree on two things,
> (1) that the hot-backup.py algorithm is the only one which
> guarantees a usable backup repository, and
> (2) that rsync will faithfully copy byte-for-byte filesystem
> segments across a network,
> then I think we have a recipe for scratching your itch. To use
> another non-Sleepycat-sanctioned backup method on a live repository
> takes us into the realm of academic discussion -- not my favorite
> flavor. :-)

Ok. I quite understand if you don't want to have an academic discussion.
I've guess I've spent too long in universities. :-)


This email and any files transmitted with it are confidential
and intended solely for the use of the individual or entity to
whom they are addressed. If you have received this email
in error please notify the system manager.

This footnote also confirms that this email message has been
swept by MIMEsweeper for the presence of computer viruses.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 10 01:52:06 2003

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.