Hi everyone,
Why can't you do the "svnadmin dump -r 1:5000 repos" to back up the
old revisions, then an "svnadmin dump -r 5001:HEAD" and restore this, to
have a new repository without the old revisions? All your revision
numbers have changed for the new version, but that's the only drawback
(unless I'm missing something here).
Lee
> Wadsworth, Eric (Contractor) wrote:
>
>> We've been using subversion for about a year, and our repository is
>> getting
>> bulky. We are looking for a way to amputate the really old stuff, so our
>> backups are smaller and more managable. We very rarely need revisions
>> more
>> than 6 months old. We'd keep an archive of the complete repository, of
>> course, just in case.
>
>
> Suppose up to r5000 is considered 'old' and can be 'frozen' - by which
> I mean, we will back it up once, secure those backups, and not back it
> up ever again. Note the tradeoff is that you will not be backing up
> any changes to log messages or other revprops in the old range - that
> shouldn't be a problem, if you've set the threshold sufficiently far
> in the past, but to be sure, you may want to edit the
> pre-revprop-change hook to disallow revprop changes on 'frozen'
> revisions.
>
> We do a 'freezing' backup: "svnadmin dump -r 1:5000 repos".
>
> Now, your routine backup becomes "svnadmin dump --incremental -r
> 5001:HEAD repos".
> Note that you *will* *need* the r1-r5000 dump too should you ever need
> to restore this backup.
>
>
--
+=========================================================
+ Lee Merrill lee@bustech.com 919-866-2008
+=========================================================
Unless otherwise stated, any views presented in this email are solely those of the author and do not necessarily represent those of the company.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 8 14:56:02 2004