On 7/6/06, Thomas Hemmer <themmer@go-engineering.de> wrote:
> 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.
There's no such statement because 'dump' uses the normal repository
access methods - in contrast with the 'raw file copy' from hotcopy -
making it just as safe as concurrent checkouts.
HTH,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 8 00:42:40 2006