On Thu, Feb 12, 2009 at 6:19 PM, Hyrum K. Wright <
> On Feb 12, 2009, at 1:29 PM, Hari Kodungallur wrote:
>> On Thu, Feb 12, 2009 at 8:37 AM, Justin Case <
>> send_lotsa_spam_here_at_yahoo.com> wrote:
>> --- On Wed, 2/11/09, Hari Kodungallur wrote:
>> > > Or can I load a hot copy instead of a dump for
>> > > restoring a repository?
>> > > Probably not, but I'm really unsure what that hot
>> > > copy can be useful for.
>> > I am not sure if there is a way to estimate the size of the
>> > dump. However, you can use the hot copy as a repository. The hot copy is
>> > identical to your repository (no need to "load").
>> My plan is to upgrade the repository from 1.4 to 1.5 so I kind of need
>> that load :)
>> No, you can not use the hotcopy for an upgrade. Hotcopy is, well a hot
>> copy. It is a method to back up your repository without bringing down the
>> server (i.e, with no downtime). It creates an exact copy of the repository
>> that you can use to backup.
>> The hotcopy, as mentioned, is an exact copy. So one thing you could try is
>> to test an upgrade on the hotcopy using 'svnadmin upgrade' and see if it
>> works for you (it should). If that works, then you don't need any dump /
> Actually, in place of hotcopy, why don't you try svnsync? You can load the
> new repository while the old one is still online, minimizing the amount of
> time cutting over to the new repository.
Basically OP wants to upgrade from 1.4 to 1.5 and wants to know how large
the dump file size is going to be. From the question it seems like he also
had a hot copy. I guess my answer was for him to try the 'svnadmin upgrade'
on the hot copy and if it works, just do the same on the actual repository,
instead of doing the dump.
He could do the 'svnadmin upgrade' on the svnsync-ed copy as well.. I have
no issues with it ;-)
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-13 03:58:59 CET