This page describes AppMon backup and disaster recovery. Backing up AppMon settings and data is simple compared to most enterprise software data backups.
AppMon Server and Collector settings and data backup
Ensure that all components in the directory to be backed up are shut down, including the Server, Frontend Server and Collector.
Use the dynatrace-migration tool to backup essential Server and Collector settings such as
.iniand configuration files, and data such as Collector caches, dashboards, and custom Sensor packs.
Create an archive using the first step in Services Migration as a guideline.
java -jar <path>/dynatrace-migration.jar -migration -sourceDTHome "<DT_HOME>" -targetArchiveDir "<archiveDir>"
A file named
<Server_name>_<creation_dateTime>.dtma (actually a
.zip file with all the backup items) is created in
Repeat this with
<Collector_home> for a distributed architecture.
If you need to restore a backup, use the second step in Services Migration as a guideline. Install the Server and / or Collector component and restore settings and data with the following command.
java -jar <path>/dynatrace-migration.jar -migration -sourceArchive "<archiveDir> /<archiveFile.dtma>" -targetDTHome "<DT_HOME>"
Optional session store and Performance Warehouse backup
Session Store file backup is normally not needed. The data is very dynamic, of limited historical value, and the files are potentially large.
The situation is similar for the Performance Warehouse database, though older data in the Performance Warehouse is aggregated for better insights in the developments over time, which may warrant backup.
An AppMon upgrade may be the situation with the best argument for a backup if you want to keep your data, or be able to roll back in case something goes wrong. Otherwise the Session Store starts from scratch and a new Performance Warehouse database must be created.