Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Copying configuration between two instances of DPOD is sometimes required if you wan to sync useful for moving configuration between environments, synchronizing a DR Instance, or reinstall DPOD on a different hardwarewhen reinstalling DPOD.
The following method will allow allows users to export the configuration from one instance of DPOD and import it to another.
The configuration is divided into these categories and users can choose which categories to export:

NameCategory

Configuration

UI Location

Reports

Reports queries and metadata. Not including executions and outcomesresults.

UI Web Console → Reports / Alerts → Reports

Alerts and Health Metrics.

Alerts and Health Metrics. Not including executions and outcomesresults.

UI Web Console → Reports / Alerts → Alerts

LDAP

LDAP connections dataconnection properties.
UI Web Console and Admin console login settings.
System parameters with LDAP category.

UI Web Console → Manage → Customize → System Parameters (LDAP Category)

System Parameters.

All System parameters.

UI Web Console → Manage → Customize → System Parameters

System Parameters Category

All System parameters related to a category provided by the user.

UI Web Console → Manage → Customize → System Parameters (Category columnprovided category)

Users and Roles

UserLocal users, Roles roles and Custom Roles custom roles managed by DPOD.

UI Web Console → Manage → Security

Maintenance Plans.

Metadata and plans of Backup, Synchronization. Firmware Upgrade and Appliance Migrations maintenance task.UI backup, synchronization, firmware upgrade and appliance migrations maintenance tasks.

Web Console → Manage → Maintenance

Devices

Monitored Devices, Monitored Devices Groups

Web Console → Manage → Topology

Custom Dashboards

Custom dashboards from both API-C and Gateways product views

Web Console → Dashboards → Custom

or

Web Console → Manage → Customize → Dashboards Editor

Prerequisites

  1. Two active DPOD instances with the same version , deployment profile (e.g.: minimal, low, high(one for export and one for import).

  2. Access to the server CLI with root user privileges.

  3. FTP / SSH access to allow fetching the export tar from the origin DPOD server.

  4. FTP / SSH access to allow uploading the export tar to the target DPOD server.

Configuration Export

To export the configuration

...

, run the export command on the origin DPOD server CLI

...

.

...

Copy the export tar file and the md5 file created by the command to the target server.

...

See the following examples:

  • Export all the configuration (recommended):

    Code Block
    /app/scripts/app_configuration_export.sh -t <path to export tar file>
  • Export selected categories (one or more can be

...

  • exported):

    Code Block
    /app/scripts/app_configuration_export.sh -t <path to export tar file> --devices --reports
  • Export a specific system parameters category:

    Code Block
    /app/scripts/app_configuration_export.sh -t <path to export tar file> --system-parameters-category 'Email SMTP'
  • Show help and list of

...

  • available options and categories:

    Code Block
    /app/scripts/app_configuration_export.sh -h

Configuration Import

To import the configuration:

  1. Import Copy the export tar file and the md5 file created by the command on the origin server to the target server.

  2. Run the import command on the target DPOD server CLI:

    Code Block
    /app/scripts/app_configuration_import.sh -f <path to export tar file> -m <path to export tar md5 file>

...