Back Up the Data Aggregator

To avoid losing your settings and custom certifications due to an unexpected failure, back up the data aggregator. Back up the data aggregator and the data repository during specific events, such as before an upgrade.
capm360
To avoid losing your settings and custom certifications due to an unexpected failure, back up the data aggregator. Back up the data aggregator and data repository during specific events, such as before an upgrade.
Stop the data repository, the data collector, or the data aggregator services when you back up the data aggregator. Backups are stored in the location that you specify, which can be on the data aggregator system or on a different backup host system.
Prerequisite:
You have root or sudo privileges.
Follow these steps:
  1. From a command prompt, create a backup directory in a secure location on the same or different backup host system by issuing the following command:
    mkdir
    DA_Backup
    • DA_Backup
      Specifies the directory path and name of the backup directory.
  2. Create subdirectories within DA_Backup using all the following commands:
    mkdir
    DA_Backup
    /deploy_backup
    mkdir DA_Backup/cert_backup
    mkdir
    DA_Backup
    /MIBDepot_backup
    mkdir
    DA_Backup
    /CustomDeviceType_backup
    mkdir
    DA_Backup
    /etc
    mkdir
    DA_Backup
    /data
  3. Run the following commands to back up the files on the data aggregator:
    • This command backs up the deploy directory:
      cp -r
      DA_install_directory
      /apache-karaf-
      version
      /deploy/*
      DA_Backup
      /deploy_backup
      • DA_install_directory
        Specifies the data aggregator install directory.
        Default:
        /opt/IMDataAggregator
    • This command backs up your certifications:
      Do not back up the
      local-jms-broker.xml
      file and the README files from that directory.
      cp -r
      DA_install_directory
      /data/certifications
      DA_Backup/cert_backup
      In a fault-tolerant environment, a shared directory (example:
      /DASharedRepo
      ) is defined to help limit data loss. Therefore, in a fault-tolerant environment, the files would be located in the following directory:
      cp -r DASharedRepo
      /certifications
      DA_Backup/
      cert_backup
      For more information, see Fault Tolerance.
    • This command backs up all the custom MIBs in the MIBDepot directory:
      cp -r
      DA_install_directory
      /apache-karaf-
      version
      /MIBDepot/
      DA_Backup
      /MIBDepot_backup
      If there are no customizations, this directory might be empty.
    • This command backs up all the custom device subtype xml files:
      cp
      DA_install_directory
      /data/custom/devicetypes/DeviceTypes.xml
      DA_Backup
      /CustomDeviceType_backup/
      In a fault-tolerant environment, the files would be located in the following directory:
      DASharedRepo
      /custom/devicetypes/DeviceTypes.xml
    • This command backs up the etc directory files:
      cp -r
      DA_install_directory
      /apache-karaf-
      version
      /etc
      DA_Backup
      /
    • This command backs up the data/log directory:
      cp -r
      DA_install_directory
      /apache-karaf-
      version
      /data/log
      DA_Backup
      /data/
    By default, a
    caVerticaUtility.sh
    script is located in the
    /opt/CA/IMDataRepository*/
    directory. This script is a support tool available for exporting the iRep data from an existing system and importing it into a different schema. You can then query the iRep data to determine how the original system was configured.