Re: versioning unversioned metadata + anonsvn strategies....

Perry E. Metzger wrote:

> John Peacock <jpeacock@rowman.com> writes:
>
>>There is no reason (AFAICT) to duplicate the database's own mechanisms
>>for maintaining transaction history through so crude a method as
>>performing incremental dumps after every transaction.
>
>
> The subversion developers themselves run hot-backup.py in their commit
> script -- which makes a copy of the whole repository!

Which at was very important over the years (since various problems have caused
the database to go belly up). Early in the development, it made perfect sense;
at this point in the project, I think it is probably overkill. It also had the
useful behavior of purging un-used log files (which 4.2 has made unneeded).

If you are willing to maintain all of the infrastructure needed to have all of
those backups, and are sufficiently concerned about quick recovery at any time,
then it is a viable methodology. Most projects don't justify such level of
paranoia.

However, and this is precisely my larger point, hot-backup.py uses the
BerkeleyDB suggested procedure for performing database backups. It does not use
'svnadmin dump --incremental', which would be much harder to use for recovery
purposes.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org