| An active failover function is not rpesetn in V1.6 nor will it be in
V1.7. It's been spec'd for quite a while but there's a lot of work to
do and it will require a full functional release.
Now, you can setup a rudimentary form of failover. Assume that you have
two PCM engines with identical configuration databases. If you start
PCM on one of them it will assume control of the managed system
consoles. If you start PCM up on the other it will not be able to
assume control becuase the other PCM engine already has done so.
However, every 150 seconds the second PCM engine will attempt to
assume control. This attempt will fail as long as the first PCM engine
is still operational. If the first engine crashses or PCM is shutdown
the second engine will assume control the next time it attempts to do
so.
It isn't fancy but it works!
Regards,
dan
|
| I'll ask this question here, since it seems to be
somewhat related.
We have a customer who wants to develop and maintain
Console Manager from their headquarters location in the
US, but the actual use of Console Manager to manage systems
would be in Mexico.
Also, the US would be the operational backup for Mexico.
The questions is: how would they go about developing and
maintaining the Console Manager environment from headquarters
while "transferring" the result of that work (the database)
to the remote location in Mexico. Also, won't the network
appear "differently" depending on whether your looking at it
from the US or from Mexico. Is the database structured so this
kind of thing can be done easily?
Any suggestions as to an approach or customer examples would be
helpful.
Regards,
BC
|