Support Center > Search Results > SecureKnowledge Details
How to backup and restore Log Exporter configuration on R80.X upgrades Technical Level
Solution

This article details the steps for backup and restore of Log Exporter configuration on R80.X upgrades, or as part of Jumbo Take upgrade in R80.10.

 Backup & restore the Log Exporter configuration:

By default, Log Exporter configuration is not transferred as part of the upgrade to R80.20.M1 and not fully updated during an upgrade to R80.20 or above.


Before the upgrade: Backup

  • On Single-Domain device:

    1. # cd $EXPORTERDIR

    2. # tar -cvzf targets.tar.gz targets

  • On Multi-Domain, follow these steps on each domain-server that has configured log_exporter:

      1. # mdsenv <CURRENT DOMAIN> (use mdsenv without parameters for mds level log exporter)

      2. # cd $EXPORTERDIR

      3. # tar -cvzf <CURRENT DOMAIN>_targets.tar.gz targets

    Note: Copy the compressed file/s to a temporary location that is available from the upgraded device

After the upgrade : restore

  • On Single-Domain device:

    1. # cp targets.tar.gz $EXPORTERDIR

    2. # cd $EXPORTERDIR

    3. # tar -xvzf targets.tar.gz targets

    4. # cp_log_export reconf

    5. # cp_log_export restart

  • On Multi-Domain, follow these steps on each domain-server that has configured log_exporter:

    1. # mdsenv <CURRENT DOMAIN> (use mdsenv without parameters for mds level log exporter)

    2. # mkdir -p $EXPORTERDIR

    3. # cp <CURRENT DOMAIN>_targets.tar.gz $EXPORTERDIR

    4. # cd $EXPORTERDIR

    5. # tar -xvzf <CURRENT DOMAIN>_targets.tar.gz targets

      After applying steps 1-5 to all domain servers, run:

    6. # cp_log_export reconf

    7. # cp_log_export restart

      In case the following error appears: "Error: No log_exporter has been found for name: [all] domain-server: [all]".

      use the following commands in steps 6-7:

         6.  #  cp_log_export reconf domain all mds

         7.  #  cp_log_export start domain all mds

Notes:

  • If you are using TLS encryption, the path to the certificates may change after the upgrade, and you will need to set it accordingly. You may use the cp_log_export set command in order to so.

  • If you are using a custom mapping file or custom format configuration (not one of the generic/leef/cef/syslog), the path to the file may have changed after the upgrade, and you may need to change it manually in the targetConfiguration.xml file. See sk122323.

Related solutions:

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment