AN!Cluster Recovery
 |
Note: This tutorial is designed for users and customers who are running AN!Clusters, based on the 2-Node Red Hat KVM Cluster Tutorial tutorial. |
This tutorial is designed to provide very basic, to the point steps to guide you through recovery of an AN!Cluster after a fault. It is not designed as a primary education on this topic. For a proper understanding of the steps below, please take the time to study the main tutorial.
Node Was Rebooted Uncleanly Rebooted, VM(s) Offline
If a node was rebooted using the reboot command, then it is possible for the VMs to have crashed in such a manner to leave them in the failed state. Once a VM goes into a failed state, it will not recover without human intervention. This section checks for and recovers from this scenario.
{{note|1=This section assumes you have a dedicate "cluster monitor" machine. If you don't, then use a machine running linux with virt-manager installed.
Recovery Steps When Both Nodes Are Running
This recovery procedure assumes that the rebooted node was restored.
- Log into your cluster monitor machine (or a workstation with virt-manager) installed.
- Open up four terminals as described here.
- On the top two terminals, ssh into the first node in the cluster. On the top-right terminal, run clear; tail -f -n 0 /var/log/messages.
| Any questions, feedback, advice, complaints or meanderings are welcome. | |||
| Alteeve's Niche! | Enterprise Support: Alteeve Support |
Community Support | |
| © Alteeve's Niche! Inc. 1997-2024 | Anvil! "Intelligent Availability®" Platform | ||
| legal stuff: All info is provided "As-Is". Do not use anything here unless you are willing and able to take responsibility for your own actions. | |||