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

Re: hotbackup & FSFS repos

From: Paul Koning <pkoning_at_equallogic.com>
Date: 2006-01-18 19:31:56 CET

>>>>> "Ryan" == Ryan Schmidt <subversion-2006Q1@ryandesign.com> writes:

 Ryan> On Jan 18, 2006, at 15:47, Paul Koning wrote:
>>> i dont need to bother with hotbackups with FSFS repos, correct?
>>> only use that with berkeley db-based repos?
>> I wonder. The doc doesn't say that, and hotcopy certainly works
>> just fine with FSFS.
>>
>> It sure would be nice to have a supported "cold copy" procedure.
>> So far I have a lot of rumor on how to construct one but no
>> guidance from the most knowledgeable people...

 Ryan> I thought I had heard on this list that doing a regular
 Ryan> filesystem copy of a live FSFS repository is perfectly fine,
 Ryan> and that though the hotcopy procedure would work too, it was
 Ryan> unnecessary.

I can easily believe that. But the book (the V1.2 online edition that
I copied about 2 months ago) doesn't say that. Instead, it says (in
"Repository Backup"):

   A full backup of the repository is quite literally a duplication of
   the entire repository directory (which includes either Berkeley
   database or FSFS environment). Now, unless you temporarily disable
   all other access to your repository, simply doing a recursive
   directory copy runs the risk of generating a faulty backup, since
   someone might be currently writing to the database.

The warning against plain old file copy is NOT qualified, so as
written it applies to either repository format.

        paul

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 18 22:23:17 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.