Just some hints. Consider putting builds at a different SVN repos than
the code and other data.
Consider putting builds that are unrelated (if you have that) at
different SVN repos than other builds.
JonB
On 29/04/2009, at 13.43, six24hourdays wrote:
> I have to migrate a repo that is 175GB. I have run a test with a 250MB
> repo and extrapolated the time for the production repo.
>
> Our build process commits all built binaries (which is why it is so
> large) and we are almost out of space (with no way to delete) which is
> why we have to move to a new server.
>
> Thanks,
> Dave
>
> On Apr 29, 6:09 am, Erik Huelsmann <ehu..._at_gmail.com> wrote:
>> On Tue, Apr 28, 2009 at 9:35 PM, six24hourdays
>> <six24hourd..._at_gmail.com> wrote:
>>> Hello,
>>
>>> do commits that occur while hotcopy is running (I expect mine to run
>>> 11-12 hours) get copied as well?
>>
>> Not all of it: the hotcopy will copy the state of the repository when
>> it was started as a standard guarantee, but changes after that might
>> not end up in the hot copy (most won't).
>>
>> Why do you expect your hotcopy to run 12 hours? Are you copying over
>> net connections? If so, wouldn't it be better to make a local copy
>> first and then transfer that snapshot over the (slower) network to
>> the
>> target disk/destination?
>>
>> Bye,
>>
>> Erik.
>>
>> ------------------------------------------------------http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessag
>> ...
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1978448
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1978500
Received on 2009-04-29 13:48:51 CEST