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

Re: backing up fsfs repo

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: 2006-07-05 17:23:45 CEST

On Wed, 2006-07-05 at 09:24 -0400, Nico Kadel-Garcia wrote:

> >> Can anybody tell me what the implications of just doing a normal backup
> >> (unix dump or tar of flat file structure) of an fsfs repo might be? Is it
> >> safe, or should I still be using "svnadmin dump"?
> >
> > IMHO, yes, because it is The Documented Way(tm) to make backups.
> It's a slight bit risky, because if files are being written while being
> tarballed, you may wind up with an incomplete change recorded on the last
> last commit operation. FSFS seems much better about this than BDB, though.

What would happen if the server crashed with that incomplete change
in progress? Is there a way to recover, and if so would it also
work to fix a backup snapshot that happened to hit that state?

> I'd personally suggest using hot-packup-py to make a clean backup, and
> backing up that. In case anyone uses the system while you're in the midst of
> doing the backup, it's handy to have a good clean snapshot like that. You
> might not have the last commit recorded, but it seems much safer.

When you run many applications on a server it is kind of annoying to
have to dedicate special operations and duplicate space for each one
just to back it up. Shouldn't it be able to recover from any state
that you happen to copy?

  Les Mikesell
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 5 17:26:15 2006

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.