Re: hotbackup & FSFS repos

>>>>> "Jacob" == Jacob Atzen <jacob@aub.dk> writes:

 Jacob> On Wed, Jan 18, 2006 at 02:19:08PM -0500, Paul Koning wrote:
>> >>>>> "Jacob" == Jacob Atzen <jacob@aub.dk> writes:
 Jacob> Your wish has been granted:
>>
 Jacob> <http://svn.collab.net/repos/svn/trunk/notes/fsfs>
>> Thanks, that's helpful. It doesn't answer the specific question
>> I mentioned, though it answers several others.
>> ...

 Jacob> The final paragraph of the forementioned text describes what
 Jacob> exactly is needed to perform a coldbackup:

Not quite; it describes how to do a hotcopy without using the
"svnadmin hotcopy" command.

 Jacob> So, if you are using standard backup tools to make backups of
 Jacob> a FSFS repository, configure the software to copy the
 Jacob> "current" file before the numbered revision files, if
 Jacob> possible, and configure it not to copy the "transactions"
 Jacob> directory.

Thanks. I must have overlooked that, perhaps because it wasn't clear.

 Jacob> An example of how to do this with rsync is available at:

 Jacob> <http://snarfed.org/space/backup+subversion+fsfs+with+rsync>

That should be clearer...

 Jacob> I hope this answers your question.

I still know of no way to quiesce Subversion. It appears that
svnserve doesn't pay any attention to any signals, and it runs until
killed. So I can turn off write access, and I can force an abrupt
termination of any that might be in progress, but I don't see a way to
do a clean closedown.

I suppose I could add a signal handler to svnserve: upon receipt of,
say, SIGHUP, set the -X flag, causing the daemon to exit when the
current operation is done. Would that work?

        paul

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 19 18:35:34 2006