On Tue, 14 Jul 1998, Mathias Feiler wrote:
> On Fri, 10 Jul 1998, Nathan Rawling wrote:
>
> >
> ---- snip ----
> > In my experience, the best way is this:
> >
> > 1) Bring up new servers
> > 2) Add new servers to clients' CellServDB
> > 3) Wait a few days (I have bad luck)
> > 4) Kill the old servers
> > 5) Update clients' CellServDB files
> >
> > This results in minimal cell outage. There is a small downtime
> ---- snap -----
>
> Are You sure you did not mixed up some things ?
> I think of this :
> 3 new and 3 old one !
> Then : 4) Kill the old servers
> Resutls in Syncside is gone.
> If the New one get the higer IP , no new syncside is choosable.
> Eventualy 5) Update clients' CellServDB files can take a while
> Earliest then a new syncside is choosable; this take other 90 Sec.
It is worth noting that "bringing up" and "killing" DB servers
neccessarily involves modifying the server-side CellServDB on all
DB servers. If you try to bring up a DB server on a machine that is
not in the server-side CellServDB, you get _very_ strange results.
So, when you bring up the new servers, you have 6 servers, and any of
them can be the sync site. You have to tell the clients about all six
servers, for a while, or clients that will want to make changes will lose.
In general, the update order should be such that the clients always know
about all current DB servers; it is OK for them also to know about
machines that are _not_ db servers; that will only hurt performance a
little.
-- Jeffrey T. Hutzelman (N3NHS) <[EMAIL PROTECTED]>
Systems Programmer
School of Computer Science - Research Computing Facility
Carnegie Mellon University - Pittsburgh, PA
