| Note |
|---|
The import script will override the target DPOD server configuration, run with caution. |
Overview
...
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 → 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 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 |
Prerequisites
Two active DPOD instances with the same version (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.
...
To export the configuration into a file, run the export command on the origin DPOD server CLI.
...
To import the configuration from a file:
Copy the export tar 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>
...