Philip Martin wrote:
<snip>
> The fact that our current backup script has a problem indicates that
> it's possible to get the backup procedure wrong. I like the idea of
> having a standard, robust, reliable method of making a hot backup.
> The question is whether it is better to script it, or to make it a
> standard command. Scripting has the advantage that it can more easily
> be customised, but that also allows it to be broken.
>
> On the whole I am in favour of an 'svnadmin copy' command.
>
Just to clarify. The command I am working on will make a hot copy of a
repository. To do backups a user could wrap copy command in a script.
For example, to retain the latest 64 copies, like hot-backup.py does.
This way user does not need to know how to make a hot copy, but it
leaves user free to script the backup any way they want. Well at least
as long as they can make a copy first. :)
Sincerely,
Vladimir Berezniker
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 28 02:31:01 2003