Wendy,
> -----Original Message-----
> From: Wendy Smoak [mailto:wsmoak@gmail.com]
> Sent: Wednesday, July 05, 2006 5:30 PM
> To: users@subversion.tigris.org
> Subject: Re: backing up fsfs repo
>
> On 7/5/06, Thomas Hemmer <themmer@go-engineering.de> wrote:
>
> > as long as you make sure that no svn server (svnserve or apache) is
> > accessing (and thus potentially modifying) your repository
> while you
> > are backing up the simple method of "tar"ing or similar
> should do the
> > job perfectly well.
> > If you can't tell exactly, "svnadmin dump" is safer.
>
> Does this mean it's _not_ necessary to prevent access to the
> repository during 'svnadmin dump'?
>
> On a similar topic, I've heard advice to "take the repository offline"
> before backing up.
You are right.
I confused the "dump" and "hotcopy" subcommands, sorry (excuse me, I'm almost 50
;-) ). "svnadmin hotcopy" _really_ works regardless of whether the repository is
currently accessed by a server process (according to the SVN book).
Unlike that there is no statement about "dump"s behaviour with respect to
concurrent access situations, so it should be considered rather unsafe.
> This may be some basic unix admin thing I just don't know,
> but having started svnserve...
> $ svnserve -d -r /path/to/repos
> .... how do I _stop_ it? I looked at svnserve --help, and a
> quick search only turned up advice to kill the process.
> http://svn.haxx.se/users/archive-2005-09/0800.shtml
I personally don't know about any other method.
But if you check out other systems' fancy "blablactl start|stop|restart"
front-ends you will notice that they neither do anything else in most cases.
>
> Is that really the best way?
Don't know for sure, but maybe the _only_ one ;-)
HTH, Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 6 09:59:13 2006