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

How to Move Data Collector to a Different Host

Data Collector is a component of Data Aggregator. You can move Data Collector to a different host system without having to rediscover network devices and components or lose historical data. For example, if you are a tool administrator, your server administrator can instruct you to relocate Data Collector to another host. Data Collector is polling 500,000 devices and components so you do not want to lose data or perform rediscovery.

The Data Collector component can be moved even if you have device packs installed.

Note the following considerations:

• The amount of data loss is equal to the amount of time that has elapsed from the time the old Data Collector component is shut down to the time when the new Data Collector component has been deployed.
• If the old Data Collector component happens to start accidentally, this results in the double polling of SNMP data. You see a warning similar to the following in the Data Aggregator karaf log:

  WARN  | Session Task-810 | 2013-01-02 13:52:09,062 | DCHeartBeatLog | ore.collector.interfaces | 
        | HeartBeat message not received.  Expected: 93, Received: 255
  

  To fix this problem, stop or uninstall the old Data Collector component.

The following diagram shows how to move Data Collector to a different host:

To move Data Collector to another system, follow this process:

1. Determine the unique identifier for Data Collector.
2. Stop Data Collector.
3. (for CA Mediation Manager integration only) Migrate device packs.
4. Install Data Collector on a different host.