Objective: To backup the configuration for cloudera manager. If we lose config manager 1, we won't be able to rebuild if we don't have the configuration. The process for generation of un-redacted file will require a restart and need prior notification for end-users. Once we have the un-redacted config file, it needs to be stored securely with appropriate access control in place.

Cloudera manager host: az-mdc-cm-1 (10.25.13.4)

Minimum Required Role: Cluster Administrator (also provided by Full Administrator) This feature is not available when using Cloudera Manager to manage Data Hub clusters.

By default, Cloudera Manager redacts sensitive information from the exported configuration JSON file. If you need the ability to restore the Cloudera Manager configuration, you must do one of the following:
Disable redaction. The JSON file will contain all the configurations, including sensitive information and can be used to restore the Cloudera Manager configuration.
Replace the redacted information. The JSON will contain the word "REDACTED" where sensitive information was redacted. Replace these values with the correct values before restoring the Cloudera Manager configuration.
In this ticket we will perform the task of exporting the Cloudera Manager Configuration as follows:
 To export the configuration without redaction, disable redaction by setting a JVM parameter:
Log in the Cloudera Manager server host using ssh from mdclone jump host (10.25.13.18).
Need to edit the /etc/default/cloudera-scm-server file by adding the following property (separate each property with a space) to the line that begins with export CMF_JAVA_OPTS.
Create copy over cloudera-scm configuration:
  cp /etc/default/cloudera-scm-server /etc/default/cloudera-scm-server.restore
Update JVM options in /etc/default/cloudera-scm-server file:
export CMF_JAVA_OPTS="-Xmx2G -Dcom.cloudera.api.redaction=false"
Restart Cloudera Manager:
sudo service cloudera-scm-server restart
Export the Cloudera Manager configuration:
Log in to a host that has network access to the Cloudera Manager server host using ssh from mdclone jump host (10.25.13.18).
Run the following commands:
read -sp "admin password? " pass
 curl -u admin:$pass "http://localhost:7180/api/v48/cm/deployment" > /root/backups/cm-deployment.json
Reset cloudera-scm configuration:
Log in the Cloudera Manager server host using ssh from mdclone jump host (10.25.13.18).
Create copy over cloudera-scm configuration:
  cp /etc/default/cloudera-scm-server.restore /etc/default/cloudera-scm-server
Restart Cloudera Manager:
sudo service cloudera-scm-server restart