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

Florian Weimer wrote:

>>Sure, do the backups nightly (or hourly), but dumping
>>the database for every rev (even with an incremental) is, to put it
>>delicately, quite insane. ;~)
>
>
> I disagree. Most databases offer this functionality. It's required for
> some forms of backup. Even Subversion supports it (but of course not
> with plain-text data).

It's called a transaction log and, yes, Berkeley (and Oracle ;~) supports it.
Disable the automatic log purges and use the hot backup script on a schedule.
With the Berkeley log files, it is possible to roll the repository to any given
point in time. I believe you can even configure Berkeley to store the log files
on a different partition.

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.

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