Migrate the Data Aggregator

To migrate the Data Aggregator, install the Data Aggregator on a new host with a new IP address and hostname and copy over your files. The following situations might require migration:
capm360
To migrate the Data Aggregator, install the Data Aggregator on a new host with a new IP address and hostname and copy over your files. The following situations might require migration:
  • You are moving to new hosts for a major OS upgrade (for example, RHEL 6.9 to RHEL 7.3).
  • The current database hardware no longer meets sizing requirements.
  • You are moving from virtual machines to physical hardware for the database.
You must upgrade the existing system to the product version you are migrating to before migrating.
Install the Data Aggregator on the New Host
Prepare the host and install the Data Aggregator on the new host. During installation, use the details for the Data Repository for the new Data Aggregator host.
You can find the Data Repository details on the current Data Aggregator host in the following location:
  • DA_Install_Directory
    /apache-karaf-<
    version>
    /etc/dbconnection.cfg
If the Data Repository was migrated, follow the Data Aggregator installation instructions in the console, and answer NO when prompted to drop the schema and the installation continues. If you answer YES, you lose your migrated data.
Migrate the Data Aggregator to the New Host
Create a backup and copy it over to the new host.
To avoid corrupting the Vertica database, ensure the old Data Aggregator host is not pointing to the new Data Repository host.
Follow these steps:
  1. Back up the Data Aggregator. For more information, see Back Up Data Aggregator.
  2. Package the files:
    tar czf DA.tgz
    backup_dir
  3. Copy the backup directory from the old Data Aggregator host to the new Data Aggregator host.
    scp -r
    backup_dir
    /DA.tgz
    DA_use
    [email protected]
    backuphost
    :/tmp
    • DA_user
      User who owns the DA process (root or sudo user)
      If /tmp is not a preferred location, specify another directory location.
  4. Restore the Data Aggregator. For more information, see Restore Data Aggregator.
  5. Do one of the following steps:
    • Stop the Data Aggregator service:
      service dadaemon stop
      For RHEL 7.x or OL,
      service
      invokes
      systemctl
      . You can use
      systemctl
      instead.
    • (Fault tolerant environment) If the local Data Aggregator is running, run one the following commands to shut it down and prevent it from restarting until maintenance is complete:
      • RHEL 6.x:
        service dadaemon maintenance
      • RHEL 7.x, SLES, or OL:
        DA_Install_Directory/scripts/dadaemon maintenance
  6. Do one of the following steps:
    • Start the Data Aggregator service:
      service dadaemon start
    • (Fault tolerant environment) Run one the following commands to enable the fault tolerant Data Aggregator so that it can start when necessary:
      • RHEL 6.x:
        service dadaemon activate
      • RHEL 7.x, SLES, or OL:
        DA_Install_Directory
        /scripts/dadaemon activate
Update the Data Repository Configuration
On the Data Aggregator host, ensure the
dbconnection.cfg
file points to the correct Data Repository hosts.
Follow these steps:
  1. Open the
    DA_installation_directory
    /apache-karaf-<
    version
    >/etc/dbconnection.cfg
    file on the Data Aggregator host.
  2. Modify the following line in the
    dbconnection.cfg
    file. Modify the line to reference the hostname or IP address of each Data Repository host:
    dbHostNames=
    dbNode1Hostname
    ,
    dbNode2Hostname
    ,
    dbNode3Hostname
  3. Save the
    dbconnection.cfg
    file.
  4. Do one of the following steps:
    • Restart the Data Aggregator service:
      service dadaemon start
    • (Fault tolerant environment) Run one the following commands to enable the fault tolerant Data Aggregator so that it can start when necessary:
      • RHEL 6.x:
        service dadaemon activate
      • RHEL 7.x, SLES, or OL:
        DA_Install_Directory
        /scripts/dadaemon activate
Update Data Collector Configurations
Update the Data Collectors to point to the new Data Aggregator host. On each Data Collector host, edit the Data Aggregator host information in following files:
If you are upgrading or migrating the Data Collectors, do this procedure after the upgrade or migration.
  • /opt/IMDataCollector/apache-karaf-<
    version
    >/etc/com.ca.im.dm.core.collector.cfg
  • /opt/IMDataCollector/broker/apache-activemq-<
    version
    >/conf/activemq.xml
Run the following commands to restart the Data Collector Karaf and Data Collector ActiveMQ services:
service activemq stop
service activemq start
service dcmd stop
service dcmd start
Update the Data Aggregator Data Source in
CA Performance Center
Update the Data Aggregator Data Source in
CA Performance Center
to point to the new Data Aggregator host. For more information, see Configure a Data Source.
Follow these steps:
  1. Go to
    Administration
    , and click
    Data Sources
    .
  2. Click
    Edit
    and specify the IP address or hostname of the new Data Aggregator host.
  3. Configure the Data Aggregator settings:
    If SSL is configured, specify HTTPS for the communication protocol.
    • Synchronize component items that are not currently present on the monitored device
      When the Data Aggregator finds a device component that is no longer present in the environment, that status of the component is set to
      Not Present
      .  By default, the Data Aggregator does not synchronize these items because data can no longer be collected for the item. Historical data that has not reached the data retention limit is still available for these items.
      If the properties of an active component match the identifying properties of the not present component, the components are indistinguishable.  Data from the old component might contribute to group based dashboards instead of data from the active component. Enable this feature only under the following circumstances:
      • You want to report on historical data for items that are no longer present in the environment.
      • You can ensure that the not present item does not conflict with an actively monitored item.
      • You can identify the not present items so that you can exclude the items from groups.
    • Discover devices from other data sources
      This option specifies whether synchronization includes devices that are reported by other data sources. Automatic synchronization includes only devices that are discovered after you select this option. To discover previously discovered devices, perform a full synchronization of the Data Aggregator.
      CA Performance Management
      creates a discovery profile that includes the IP addresses of the devices. This discovery profile attempts discovery once per day.
  4. Click
    Save
    .
    If the Data Aggregator data source is enabled, data appears in
    CA Performance Center
    after the next synchronization.