Ambari DB should be backed up on a regular basis. This is the most important piece of information. It is also advisable to also back up /etc/ambari-server/conf/ambari-server.properties. If you have these two, you can restore Ambari Server back to a running condition on a different host. If the hostname of the Ambari Server changes, then you would have to update /etc/ambari-agent/conf/ambari-agent.ini to point to the new Ambari Server hostname and restart the agent.
Yusaku From: Clark Breyman <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Friday, June 26, 2015 5:10 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Ambari data corruption/recovery process I'm wondering if anyone can share pointers/procedures/best practices to handle the scenarios where: a) The sql database becomes corrupt. (Bugs, ...) b) The Ambari service host is lost (e.g. EC2 instance termination, physical hardware loss, ...)
