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

Cloudera Manager 4 and CDH 4 have reached End of Maintenance (EOM) on August 9, 2015. Cloudera will not support or provide patches for any of the Cloudera Manager 4 or CDH 4 releases after that date.

Importing Cloudera Manager Settings

Backing up your Current Deployment

To back up your current deployment, please see the section on backing up your database in Database Considerations for Cloudera Manager Upgrades . The import feature should not be relied on for backup and recovery at this time.

Building a Cloudera Manager Deployment

You can use the Cloudera Manager API to programmatically build a Cloudera Manager Deployment — a definition of all the entities in your Cloudera Manager-managed deployment — clusters, service, roles, hosts, users and so on. See the Cloudera Manager API documentation on how to manage deployments using the /cm/deployment resource.

Uploading a Cloudera Manager 4.0 Configuration Script

  Note: As of Cloudera Manager 4.1, the import of configuration settings through the Cloudera Manager Admin Console UI has been deprecated. If you have exported a configuration using the Export tab in an older version of Cloudera Manager, you can still import it following the instructions below. However, going forward, importing a deployment should be done using the Cloudera Manager API. See the documentation for /cm/deployment for details.
  Important: You must import the configuration settings on a clean cluster that does not have existing hosts or services.
  Important: When you first installed the Cloudera Manager Server, you set up a database to store the Cloudera Manager service configuration information (see Installing and Configuring Databases). That database also stores the Cloudera Manager license information. If the original database is lost (for example, the database was deleted and you recreated a new one), you must first upload your license on the Administration > License page and restart the Cloudera Manager Server before importing the configuration settings. If you don't upload your license first to store the license information in the new database, the import will fail.

To import the configuration script into Cloudera Manager:

  1. On every Cloudera Manager Agent host, run this command to stop the Cloudera Manager Agent:
    $ sudo service cloudera-scm-agent stop
  2. Delete all services on the Services tab by choosing Delete from the Actions menu next to each service instance.
  3. Delete all hosts on the Hosts tab by clicking the check box at the top of list of hosts, and then click Delete.
  4. Copy the configuration script file that you downloaded during export to the host with the new Cloudera Manager server.
  5. Pull down the Administration tab and select Import.
  6. Click Browse, navigate to the file location, and click Open.
  7. Click Import.
  8. On every Cloudera Manager Agent host, run this command to start the Cloudera Manager Agent:
    $ sudo service cloudera-scm-agent start
This page last updated September 8, 2015