On Fri, 06 Aug 2004 12:42:41 -0700, Kenneth Porter
<shiva@sewingwitch.com> wrote:
> --On Friday, August 06, 2004 5:36 PM +0200 Jacob Atzen <jacob@aub.dk> wrote:
>
> > Why would 'svnadmin hotcopy' be less safe than 'svnadmin dump'?
>
> I guess my concern is more with verifying backups, and the fact that DB4
> writes to files being "read". I was trying to verify a new release of dump
> (the disk backup system) and the DB4 files were the only things that didn't
> verify. So I had to run 'svnadmin dump' against the two DB's (tape and
> disk) and compare that. The experience has just made me a little uneasy
> about the ability to verify the integrity of the DB files. It's not
> anything concrete.
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)
--
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 01:06:07 2004