On Jan 15, 2009, at 11:09, David Mills wrote:
> I'm currently administering a repository which is used for document
> synchronisation and transfer between 2 sites.
>
> Over the years, the size of this repository has grown to represent
> over 12Gb. Most of which consists of redundant change sets (deleted
> files mostly).
>
> I would like to improve this situation by flattening the repository
> so that only 3-6 months of changes are kept.
>
> My plan was to use the following command to do this:
>
> svnadmin dump enki_old/ -r {`date --date="6 months ago" +%Y-%m-%
> d`}:HEAD | svnadmin load enki
>
> The problem is that using this command I invalidate every checkout
> of the repository (I get invalid revision errors). Re-checking out
> will be onerous for me as the checkouts are around 4Gb in size, and
> a lot of our users are non-technical.
>
> Is there any way for me to do this operation in a way that my users
> can just update their checkouts to be in sync with the new repository?
No, there isn't. As you've noticed, any such surgery on the
repository makes the repository a fundamentally different one,
hopefully with a totally new unique id (use "svnadmin load --ignore-
uuid" to ensure this), and new checkouts will be required.
I recommend you keep the repository as it is, with all its history,
and add server disks if necessary to keep up with the repository's
growth.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1029780
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-27 22:49:27 CET