Maintaining a LifeKeeper Protected System
When performing shutdown and maintenance on a LifeKeeper-protected server, you must put that system’s resource hierarchies in service on the backup server before performing maintenance. This process stops all activity for shared disks on the system needing maintenance.
Perform these actions in the order specified, where Server A is the primary system in need of maintenance and Server B is the backup server:
- Bring hierarchies in service on Server B. On the backup, Server B, use the LifeKeeper GUI to bring in service any resource hierarchies that are currently in service on Server A. This will unmount any file systems currently mounted on Server A that reside on the shared disks under LifeKeeper protection. See Bringing a Resource In Service for instructions.
- Stop LifeKeeper on Server A. Use the command /etc/init.d/lifekeeper stop-nofailover (or, LKSTOP_MODE=stop-nofailover systemctl stop lifekeeper) to stop LifeKeeper. Your resources are now unprotected.
- Shut down Linux and power down Server A. Shut down the Linux operating system on Server A, then power off the server.
- Perform maintenance. Perform the necessary maintenance on Server A.
- Power on Server A and restart Linux. Power on Server A, then reboot the Linux operating system.
- Start LifeKeeper on Server A. Use the command /etc/init.d/lifekeeper start (or, systemctl start lifekeeper) to start LifeKeeper. Your resources are now protected.
- Bring hierarchies back in-service on Server A, if desired. On Server A, use the LifeKeeper GUI to bring in service all resource hierarchies that were switched over to Server B.
Thanks for your feedback.
Post your comment on this topic.