Moving the Cloudera Manager Server to a New Host

You can move the Cloudera Manager Server if either the Cloudera Manager database server or a current backup of the Cloudera Manager database is available.

  1. Identify a new host on which to install Cloudera Manager.
  2. Install Cloudera Manager on a new host, using the method described in the topic Install the Cloudera Manager Server Packages.
  3. Copy the entire contents of the /var/lib/cloudera-scm-server/ directory on the old host to that same path on the new host. Ensure you preserve permissions and all file contents.
  4. Copy the entire contents of the local parcel directory on the old host to that same path on the new host. Ensure you preserve permissions and all file contents. (The default location is /opt/cloudera/parcel-repo but this can be configured with the Local Parcel Repository Path configuration property, under Administration > Settings.)
  5. 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. If you used the embedded PostgreSQL database, install the PostgreSQL package as described in the topic Managing the Embedded PostgreSQL Database. If you used an external MySQL, PostgreSQL, or Oracle database, reinstall the database following the instructions in Step 4: Install and Configure Databases.
    2. Restore the backed up databases to the new database installation.
  6. Update /etc/cloudera-scm-server/ with the database name, database instance name, username, and password.
  7. Do the following on all cluster hosts:
    1. In /etc/cloudera-scm-agent/config.ini, update the server_host property to the new hostname.
    2. If you are replacing the Cloudera Manager database with a new database, and you are not using a backup of the original Cloudera Manager database, delete the /var/lib/cloudera-scm-agent/cm_guid file.
    3. Restart the agent using the following command:
      sudo service cloudera-scm-agent restart
  8. Stop the Cloudera Manager server on the source host by running the following command:
    service cloudera-scm-server stop
  9. Copy any Custom Service Descriptor files for add-on services to the configured directory on the new Cloudera Manager host. The directory path is configured by going to Administration > Settings and editing the Local Descriptor Repository Path property. The default value is/opt/cloudera/csd. See Add-on Services.
  10. Start the Cloudera Manager Server on the new (destination) host. 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. See the Security documentation.