On 10/12/06, Andy Malato <[EMAIL PROTECTED]> wrote:
We are interested in setting up an additional SunRay server to act as a
secondary server (failover) in case the primary server fails.
Usually groups are set up so that sessions get spread across the
servers in the group. If you want to place sessions on the
secondary only when the primary is unavailable then you can
mark the secondary "offline" ('utadm -f') so that it does not bid to
become the home for new sessions. This will not prevent people
from explicitly placing sessions on the secondary but it does
prevent them from landing there by default.
If you are running the servers in "configured" mode so that they
share configuration data through the Sun Ray Data Store, and
you expect that the primary might be unavailable for long periods
of time (more than just a reboot or a few hours of planned downtime
for maintenance) then you should familiarise yourself with the
procedure for promoting a Data Store secondary to a Data Store
primary. Only primaries can apply updates to the Data Store. And
you should familiarise yourself with the procedure for demoting a
primary to a secondary, because when the original primary comes
back you'll probably want it to act as a secondary so that you don't
discard Data Store changes that were made while it was down. In
any case, when the original primary comes back you'll need to
demote one of the servers. If you expect that this is going to be a
frequent occurence then you might grab a third more-stable
machine and dedicate it to acting as the Data Store primary. It
needn't offer Sun Ray sessions so it can be a very small machine.
OttoM.
__
ottomeister
Disclaimer: These are my opinions. I do not speak for my emplyer.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
