| Note |
|---|
The import script will override the target DPOD server configuration, run with caution. |
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:
Category | Configuration | UI Location |
|---|---|---|
Reports | Reports queries and metadata. Not including executions and |
results. |
Web Console → Reports / Alerts → Reports |
Alerts and Health Metrics |
Alerts and Health Metrics. Not including executions and |
results. |
Web Console → Reports / Alerts → Alerts | |
LDAP | LDAP |
connection properties. |
Web Console and Admin console login settings. |
Web Console → Manage → Customize → System Parameters (LDAP Category) |
System Parameters |
All System parameters. |
Web Console → Manage → Customize → System Parameters | |
System Parameters Category | All System parameters related to a category provided by the user. |
Web Console → Manage → Customize → System Parameters ( |
provided category) |
Users and Roles |
Local users, |
roles and |
custom roles managed by DPOD. |
Web Console → Manage → Security |
Maintenance Plans |
Metadata and plans of |
UI Console → Manage → Maintenance
Prerequisites
...
backup, synchronization and firmware upgrade 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 |
Cloud Agent | Cloud agent subscriptions. | Web Console → Manage → Topology |
Custom Logo | Custom logo configured by user. | Web Console → Manage → Customize → User Interface |
Prerequisites
Two DPOD instances with the same version , deployment profile (e.g.: minimal, low, high(one for export and one for import).
Access to the server CLI with
rootuser privileges.FTP / SSH access to allow fetching the export tar from the origin DPOD server.
FTP / SSH access to allow uploading the export tar to the target DPOD server.
Configuration Export
To export configuration
...
the configuration into a file, 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.
Export Examples
Export 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 --reportsExport 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 from a file:
Import Copy the export tar file, encryption key file and the md5 file created by the command on the origin server to the target server.
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> -k <path to export encryption key file>
Run the following command for help and list of available options:
| Code Block |
|---|
/app/scripts/app_configuration_exportimport.sh -h |