Moving Cloudera Manager to a different server

[#1]

We have three management nodes mn01, mn02 and mn03. Currently our install has the Cloudera Manager (CM) on mn01. Due to the fact that we have the primary and secondary namenode processes on mn01 and mn02, we want to migrate the CM to mn03. We are using mysql on mn01 as well. 

I have tried to do the following in a virtual lab: 

• Install CM Server on mn03
• Replicate database to mn03 or rsync all the db and configs.
• Edit /etc/Cloudera-scm-server/db.properties to match mn01 to mn03 (uses localhost)
• Startup CM on mn03
• Export the settings from mn01

# Export settings:

curl -u user:password "http://localhost:7180/api/v11/cm/deployment" >/tmp/cm-deployment.json

• Import to mn03

# Export settings:

curl --upload-file /tmp/cm-deployment.json -u user:password http://localhost:7180/api/v11/cm/deployment?deleteCurrentDeployment=true

The services don't start and when I try to view logs I get a lot of 502 "bad gateway" errors. 

Has anyone ever done this successfully? What would I be missing? We are concerned that if CM ever goes down, no matter which system it resides on, that it will be difficult to get it up and running again. 

[#2]

Hello, 

The process is actually documented here http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ag_restore_server.html

What database is Cloudera Manager server is connected to?

michalis

[#3]

it's mysql. Thanks for the link. I'll check that out now. 

[#4 · Accepted solution]

I was missing the change of ip in the agent configs. It's working now. Thanks again. 

[#5]

Great to hear.