depoyment

[Chris Muller]

Mmm, replaying commit-logs doesn't really assist the process of moving
it to a new server.

Moving to a new server can be done one of two ways; either by the
approach I mentioned in my earlier e-mail (shutting it down and
updating the Node manually) or by starting a warm-backup on the server
you want to become the new primary and then invoking a deliberate swap
of primary duty with the current primary.  This latter approach allows
Magma repositories to move between servers without stopping service
and is demonstrated by the test-suite, HA Test Case 4,
#verifyQuickSwapFunction.

HTH,
  Chris



On Sun, Aug 14, 2011 at 4:50 AM, Milan Mimica <milan.mimica at gmail.com> wrote:
> Chris Muller wrote:
>>
>> It's been a while since I've "moved" a repository from one host to
>> another.  IIRC, the Node must be updated manually in that case.
>>
>
> I think I'm just going to recreate the database. There's only a few test
> data in it.
> But sooner or later there is likely going to be some moving around. Can I
> rebuild the database from the commit logs maybe?
>
> --
> Milan Mimica
> http://sparklet.sf.net
>
>