On Fri, 06 Aug 2004 16:44:41 -0700, Kenneth Porter
<shiva@sewingwitch.com> wrote:
> --On Friday, August 06, 2004 7:05 PM -0400 Bryan Donlan <bdonlan@gmail.com>
> wrote:
>
> > There's a special order in which the files must be copied, to prevent
> > database corruption. svnadmin hotcopy implements this, whereas your
> > backup system likely does not. If automatic logfile removal is
> > enabled, hotcopy may fail in a race with a logfile deletion:
> > http://subversion.tigris.org/issues/show_bug.cgi?id=1817
> > Apart from that it should be safe (just make sure svnadmin hotcopy
> > exits without error)
>
> That makes sense.
>
> My backup system is dump (http://dump.sf.net/), the same one used for as
> long as I can remember on Unix systems, at least back to the late 80's. It
> backs up a system by reading the raw disk structure and copying it to tape
> in inode order. (I actually dump to a group of files on a Samba share.)
>
> So any "safe" backup would need an initial step to take a snapshot of the
> repository. Using a hot backup for this has the risk that someone might
> look at the hot backup as the system dump happens, and merely looking at
> the hot backup will modify it in a potentially unsafe way. That's not true
> of the "svnadmin dump" backup, which is in a single immutable file.
It'd only be dangerous if someone runs a svn operation on a hot-backup
while it's being made (or copied by dump) - and there's no reason to
be doing anything with a backup other than restoring from it in an
emergency.
--
bd
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Aug 7 04:57:07 2004