Follow the instructions in this section to start the primary companion as a service monitored by the high availability system.
Before monitoring begins on the primary companion, make
sure that there is no need to shut down the primary server for maintenance
or any other purpose. Once monitoring begins, the primary companion
must be moved to suspended mode to bring it down. If you are unsure,
start the primary server using the startserver script
in $SYBASE/$SYBASE_ASE/install,
finish configuring the companion, then restart the server using
the steps described here.
To start the primary companion as a resource monitoring for fail over:
Restart the TruCluster resource by executing this command as “root” at the command line:
caa_start server_name
This automatically executes the <server_name>.scr monitor script, which brings up the primary companion and monitors if it has stopped responding.
Repeat this process on the secondary node to start the secondary companion.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
