New Control-M server Install

rajesekhar · Post by **rajesekhar** » 17 Oct 2008 1:56

We have a Control-M server(installed on BOX1) in production. Now, we want to install new Control-M server on BOX2.
BOX1 to be changed to DEV server.
BOX2 to be made the PROD server.

I have the following questions:

1)What all needed to install Control-M server on BOX2 in clustered mode?
2)How do we migrate all the jobs from BOX1 to BOX2?
3)Ho do we run jobs simultaneously on both the servers?
4)Do we need to have two separate databases for those two Control-M servers?
5)How does the "failover" works?

Thanks in advance,
Raj

xbassx · Post by **xbassx** » 17 Oct 2008 9:47

We have a Control-M server(installed on BOX1) in production. Now, we want to install new Control-M server on BOX2.
BOX1 to be changed to DEV server.
BOX2 to be made the PROD server.

I have the following questions:

1)What all needed to install Control-M server on BOX2 in clustered mode?
2)How do we migrate all the jobs from BOX1 to BOX2?
3)Ho do we run jobs simultaneously on both the servers?
4)Do we need to have two separate databases for those two Control-M servers?
5)How does the "failover" works?

To install it in a clustered environment you should consult the Cluster installation guide on the BMC website.

To move jobs from dev to prod you can simply pull up all your jobs in Desktop and do a mass update for the CONTROL-M name. So if dev CONTROL-M is called ctm-dev and prod is ctm-prod then you will mass update from ctm-dev to ctm-prod and then write it to the EM Database and Upload.
(Note: You will need to make sure that you have your Prod CONTROL-M already defined in either the Admin Facility or CCM depending on your version.)

If you want to keep the jobs in dev and simply create a new copy of these jobs in prod then Load jobs in Desktop and save it as a draft. Open the Draft and then do a mass update for CONTROL-M Name.
(Note: You will need to make sure that you have your Prod CONTROL-M already defined in either the Admin Facility or CCM depending on your version.) You may also need to updae the Agent nodes where these jobs run. This can also be done via mass update.

If you are maintaining a dev CONTROL-M and a Prod CONTROL-M then each will have its own database. The schemas can reside on the same DB Server again this depends on how your environment is setup.

rajesekhar · Post by **rajesekhar** » 20 Oct 2008 4:05

Thanks for the reply.

Can we install the new Control-M server with the same database server as the old one(which is already installed)?

Does the two Control-M servers(PROD and DEV) have two separate databases?

How can we differentiate them in Control-M EM? Is the Control-M EM database different from the database on which Control-M server is installed? or both are the same?

And one more question, can we move the Control-M database from one database server to another database?

We are using SQL server for the database.

Thanks,
Raj

xbassx · Post by **xbassx** » 20 Oct 2008 4:48

Can we install the new Control-M server with the same database server as the old one(which is already installed)?
Yes

Does the two Control-M servers(PROD and DEV) have two separate databases?

Yes, each CONTROL-M has its own database. So if you have prod and dev each will have its own schema. They can both reside on the same database Server

How can we differentiate them in Control-M EM? Is the Control-M EM database different from the database on which Control-M server is installed? or both are the same?

EM database is separate from the CONTROL-M database. In EM using CCM or Admin Facililty you will define a gateway to each CONTROL-M and once the gateway is connected you can monitor multiple CONTROL-Ms from EM.

And one more question, can we move the Control-M database from one database server to another database?

We are using SQL server for the database.

Yes you can...are you creating a new CONTROL-M environment and want to move everything over to the new environment? If so then after you have installed a new environment then you you can use the backup and recovery utilities provided within CONTROL-M to export and import the data. The backup utilities are ctm_backup_bcp and Restore is ctm_restore_bcp. Check out the CONTROL-M/Server admin guide for further information on usage of the utilities.

rajesekhar · Post by **rajesekhar** » 21 Oct 2008 7:18

wow, your info was very helpful. Thank you very much.

For the timebeing, we need to move the existing Control-M database from one database server to another database server.

What all are we supposed to do that offcourse without disturbing the present production environment.