Product Administration › How to Move Data Collector to a Different Host › Install Data Collector on a Different Host

Install Data Collector on a Different Host

After you stop Data Collector services on the old host, you install Data Collector on a new host. The Data Collector data from the old host is exported to the new host during this procedure.

Follow these steps:

1. (For integration with CA Mediation Manager only) Migrate your device packs. On the old Data Collector host, run the $CAMM_HOME/tools/migratePMtoCAMM script with the –t flag.

   This step assumes that you are running the script on a Data Collector server where a Local Controller is installed. You must also have the CA Mediation Manager Console running on another server.

   Note: Migrated device packs are copied to $CAMM_HOME/MigratedIMDevicepacks in the form of .zip files. For more information about migrating device packs, see the "How to Migrate Device Packs" scenario.

2. Log in to the new host system and open a command shell session.
3. Set an environment variable with the ID you copied previously by running this command:

   export DCM_ID=data collector id
   

4. Install Data Collector from the same session by running the install.bin binary.
5. Install the CA Mediation Manager LC on the same server.
6. If you have previously installed device packs for this Data Collector, perform these additional steps:
   1. Copy the zip files that you created previously with the migration script to local directories on this host.
   2. Use the CA Mediation Manager web Console to deploy these device packs and start them.

      Note: You do not need to redeploy the certification packs to the Data Aggregator host.

Note: After a few polling cycles, verify that data is being collected by the new Data Collector host.

As a best practice, uninstall the old Data Collector and delete any associated EMS profiles after verifying that data is being collected on the new host. This best practice is optional.