Jack Repenning wrote:
>>>-----Original Message-----
>>>From: Ritesh Nadhani [mailto:riteshp@webyog.com]
>>>...
>>>Reading the docs the various methods to backup a repository are:
>>>
>>>1.) svnadmin dump --incremental
>>>2.) Do a complete backup of the folder? (it is supposed to be
>>>unsafe as somebody might be checking at that time)
>>>3.) use hot-backup.py.
>
>
>
> #2 is unsafe if there's any slightest chance that anyone is accessing the
> repo, even merely for read purposes, during the process. It is not just
> checkins that concern you, here: any access at all can cause problems! You
> are utterly on your own to guarantee this does not happen. There are, of
> course, realistic situations where you have this confidence, and it may be
> that you're fine with #2. Just remember: this is your backup you're talking
> about! When you need to restore it, you're going to be desperate, and
> rushed, and you won't have any options left if, just this one time, someone
> happened to sneak in a little "svn ls" just as you were doing the backup.
Unsafe in what way? Can it corrupt the repository, or only the backup?
At the moment, we use #2 every night between 01:00 and 03:00 or so, and
since there's only two developers here, it seemed reasonable to assume
no-one accesses it at that time. However, a recent all night coding
session had me questioning that assumption.
If I just tell the backup software (Veritas Backup Exec 9.0) to copy the
files in the order used in hot-backup.py, is that guaranteed to be safe,
or does hot-backup.py do more?
Regards,
Roel Harbers
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 12 13:47:23 2005