Re: Solving Large Repositories...

- dump
- dump filter
- load

If you're concerned about space don't change the revision numbering or
any log messages and external documentation will refer to the wrong
revision.

Keep in mind that if your changes are typically evolutionary rather
than revolutionary then the repository will not grow as much in later
revisions as they have in the early revisions.

And consider that the capability of available infrastructure will
improve as well so unless the repository growth out-paces this you may
not need to eliminate history to manage repository size.

--
Talden
On 8/20/07, Adrian Marsh <Adrian.Marsh@ubiquisys.com> wrote:
> Hi All,
>
> When a repos becomes very large, are there any "maintenance" procedures
> to follow to archive away the "useless" data and reduce the size?
>
> Eg, I've a repos, now 12Gb in size, but its working copy is 300Mb, 1
> user, 50 revisions.
>
> Now in a few months/years time the original data of early revisions may
> be worthless (say from revision 10 and before).
> I'm guessing that I'd have to create a new respos, transfer 10+ into the
> new one, and then re-point all the clients to the new repos - but that
> sounds like a nightmare (clients being out of sync, having to re-check
> out the data again etc)..
>
> Surely theres an easier way?
>
> Adrian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org