On Jul 11, 2008, at 16:38, Gupta, Praful wrote:
> Thanks Ryan ... I had looked at svn sync a little while ago but
> couldnt go any further since it needs some sort of hooks on the old
> root as well as the new root, aint that the case? I dont wanna
> change or rather it would be a process to stop the current server
> to insert a hook script.
I haven't used svnsync myself. But you don't need to stop the old
server to add a hook script to it.
> Ryan Schmidt wrote:
>
>> On Jul 11, 2008, at 16:22, Gupta, Praful wrote:
>>
>>> Hello ... We are currently running a server on versio 1.2 and have
>>> purchased a new server to upgrade to 1.5. I wanted to get some
>>> suggestions on certain steps for this move:
>>>
>>> 1) I know the best way is to take a dump of the old root and load
>>> it onto the new server, is this still the best approach?
>>
>> Yes.
>>
>>> 2) Any variations of hotcopy cmd which would take a repository URL
>>> as a parameter rather than a path?
>>
>> No. Furthermore, a hotcopy is only useful if your new server has the
>> same processor architecture, same OS and same version of BerkeleyDB
>> as the old server. If any of these differ, dump and load.
>>
>>> 3) I also am looking for a suggestion on trying to keep the 2
>>> servers synced up until we decide to cut one off, any suggestions
>>> in this route will be help ful?
>>
>> svnsync. In fact you can use svnsync to handle your migration instead
>> of dump/load or hotcopy.
>>
>>> 4) Can I take a full dump of the old root and load it up to the new
>>> server and then run incremental updates like eveery night or
>>> something off a cron job?
>>
>> Yes. But use svnsync.
>>
>>
>> Note:
>>
>> svnsync and dump/load will not preserve repository hooks or config
>> files. Move these over manually.
>>
>> dump/load will not preserve locks. You can move the db/locks
>> directory over manually if you want to preserve locks (provided your
>> repository uses FSFS, not BDB).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-11 23:45:57 CEST