You can test your MySQL resource hierarchy by initiating a manual switchover. This will simulate a failover of a resource instance from the primary server to the backup server.
Performing a Manual Switchover from the GUI
You can initiate a manual switchover from the LifeKeeper GUI by selecting Edit, Resource and In-Service from the drop‑down menu. For example, an In-Service request executed on a backup server causes the application hierarchy to be placed in service on the backup server and taken out of service on the primary server. At this point, the original backup server is now the primary server and original primary server has now become the backup server.
If you execute the Out-of-Service request, the application is taken out of service without bringing it in service on the other server.
LifeKeeper does not regulate or control internal operations such as rollbacks and backing up archives. Tape archiving and restoration are the responsibility of the application administrator.
When the primary server fails, the MySQL Recovery Kit software performs the following tasks:
- Mounts the file system(s) – shared or replicated – on the backup server
- Starts the daemon processes related to MySQL