This is the documentation for Cloudera Manager 5.1.x. Documentation for other versions is available at Cloudera Documentation.

Moving the Cloudera Manager Server to a New Host

You can move the Cloudera Manager Server if the database information is still available for either of the following reasons:
  • The database server is still available.
  • A current back up of the Cloudera Manager database is available.
To move Cloudera Manager Server:
  1. Record the old host's name hostname and IP address. It is not absolutely necessary to have the old Cloudera Manager server hostname and IP address, but it simplifies the process. You could use a new hostname and IP address, but this would require updating the configuration of every Agent to use this new information. Because it is easier to use the old server hostname and address in most cases, using a new hostname and IP address is not described.
  2. Identify a new host on which to install Cloudera Manager. Assign the failed Cloudera Manager Server's hostname and IP address to the new host.
      Note: If the Agents were configured with the server's hostname, you do not need to assign the old host's IP address to the new host. Simply assigning the hostname will suffice.
  3. Install Cloudera Manager on a new host, using the method described under Install the Cloudera Manager Server Packages. Do not install the other components, such as CDH and databases.
  4. If the database server is not available,
    1. Install the database packages on the host that will host the restored database. This could be the same host on which you have just installed Cloudera Manager or it could be a different host. The details of which package to install varies based on which database was initially installed on your system. If you used the embedded PostgreSQL database, install the PostgreSQL package as described in Embedded PostgreSQL Database. If you used an external MySQL, PostgreSQL, or Oracle database, reinstall that following the instructions in Cloudera Manager and Managed Service Databases.
    2. Restore the backed up databases to the new database installations.
  5. Update /etc/cloudera-scm-server/ with the necessary information so that the Cloudera Manager Server connects to the restored database. This information is typically the database name, database instance name, user name, and password.
  6. Start the Cloudera Manager Server.
At this point, Cloudera Manager should resume functioning as it did before the failure. Because you restored the database from the backup, the server should accept the running state of the Agents, meaning it will not terminate any running processes.

The process is similar with secure clusters, though files in /etc/cloudera-scm-server must be restored in addition to the database.

Page generated September 3, 2015.