Follow the instructions in this section to start the primary companion as a service monitored by the high availability subsystem.
Before monitoring begins on the primary companion, make
sure that there is no need to shutdown 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 reboot the server using the
steps described here.
To start the primary companion as a resource monitoring for failover:
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 it during crash or hang situations.
Repeat this process on the secondary node to bring up the secondary companion.
