A day in the travels (and Sametime catch up from May)
Tags :Sametime
I started the threads
and posting back in
May to a nice set of comments
wanting to know the outcome and what the final solution was. Well
I shall unveil it to you this fine day in August.
The customer stuck with the F5 solution. Testing went well over the
past few moths and the actual server hardware arrived and got loaded with
the operating system of Windows 2000. The current plan is creating
an exact duplicate of the single, existing Sametime server and moving that
into the cluster architecture. Which in turn, mirrors the test cluster
we built in all the configurations. Let me bring one point to the
front that you should know and is verified in technotes. Make sure
you have a loopback
record in stconfig.nsf and
the world may be at peace. Not really, but with some proper planning,
good budget, etc etc.
Ok, that is a bit strong as there is a myriad of patches and the recent
FP1 to be applied to 6.5.1 of Sametime to start. Interestingly enough,
moving the database across that had transaction logging enabled threw a
bit of a wrench in the works for a few minutes. Some compact -t to
remove that flag assisted. We ended up with a corrupt NAB on one
server for some unknown reason, but replacing that made the universe at
harmony once again.
So how are we moving from the single server to the load balancer and having
two new servers as a Community Cluster? Sounds like you will have
to wait until after the sauteed mushrooms, pesto basil pasta and tiramisu
at my current location.
blog comments powered by Disqus
On Monday, August 22nd, 2005 by Chris Miller
