If you are migrating the Server to a new host without upgrading to a new version, you only need to perform the applicable steps.
1. Install the new Server, Collectors, and Clients
Install the new AppMon Server, AppMon Collectors and Clients into a new directory, referred to as
<DT_HOME_NEW> in these instructions.
Important - Windows
At the end of the installation, you are prompted to start the Server, Collector, and Client. Do not start these components at this time.
Important - Unix
Do not unzip the
.jar installation files, but run
java -jar <FILENAME>.jar.
See Silent Installation for automation.
2. Deactivate and Upgrade License
3. Shut down the old version
Stop the old Client, Server, Frontend Server, Collector and Memory Analysis Server services.
Disable automatic startup of the old Server, Frontend Server, Collector and Memory Analysis Server:
- Windows: Click Control Panel > Administrative Tools > Services. In each service's properties, set the Startup type to Manual.
- Unix systems: Use
update-rc.dto disable all AppMon services.
4. Create backups
Using the configuration information collected during preparation:
- Back up your Performance Warehouse DB.
- Back up your Session Store.
- *On NIX, back up all AppMon scripts in
DT_HOME are backed up during the next step.
5. Services migration (Server, Collector and Memory Analysis Server)
Download and use the current Migration Tool on all Server and Collector machines as follows.
For migration without backup archives and further options see Migration tool details or run
java -jar dynatrace-migration.jar.
5.1. File collection
dynatrace-migration to create a migration archive. For example:
java -jar dynatrace-migration.jar -migration -sourceDTHome "<DT_HOME_OLD>" -targetArchiveDir "<ARCHIVE_DIR>"
<DT_HOME_OLD> is the old AppMon installation path. A
<MIGRATION_ARCHIVE> file named
<Server_name>_<creation_dateTime>.dtma is created in
Keep the resulting file as permanent backup.
5.2. File migration
On the target host, as Administrator or configured user, migrate the data to
<DT_HOME_NEW> using the following:
java -jar dynatrace-migration.jar -migration -sourceArchive "<ARCHIVE_DIR>/<MIGRATION_ARCHIVE>" -targetDTHome "<DT_HOME_NEW>"
Backups of files are changed in
<DT_HOME_NEW> and a migration log are created in a new directory in
5.3. Edit configuration files
dynatrace-migration lists files with configuration settings that may need to be migrated manually to the new release. Therefore, the applicable old files are copied with the suffix
.toBeMigrated. These files are found in
<DT_HOME_NEW>. Do not reuse the old files, because for AppMon 6.3 and later, changed boot bundles cause your Server to not start.
There are some files left, which have to be migrated manually: In `<DT_HOME_NEW>`: * `\dtanalysisserver.ini`: Edit and integrate custom settings from old `\dtanalysisserver.ini.toBeMigrated`. * `\dtcollector.ini`: Edit and integrate custom settings from old `\dtcollector.ini.toBeMigrated`. * `\dtfrontendserver.ini`: Edit and integrate custom settings from old `\dtfrontendserver.ini.toBeMigrated`. * `\dtserver.ini`: Edit and integrate custom settings from old `\dtserver.ini.toBeMigrated`. * `\server\selfmonitoring\dtselfmon.ini`: Edit and integrate custom settings from old `\server\selfmonitoring\dtselfmon.ini.toBeMigrated`. Do not re-use the old files. This may cause components to not start.
dtserver.ini: If you are upgrading and using continuous transaction storage (see Prepare to Upgrade), do not migrate
dtserver.ini: If it contains an entry regarding SQLSERVER, follow this KB article.
- Migrate all
5.4. Register and Auto-start additional collector instances
If you used Collector instances in the old installation:
- Windows: In the directory
<DT_HOME_NEW>, for each Collector instance, using the same
<CollectorInstanceName>as in the old version, execute:
dtcollector -service install -instance <CollectorInstanceName>
- *NIX: In
/etc/init.d, for each Collector instance, there is an old startup script named
<NN>is a number. For each such file:
- Take note of the values for the variables
- Replace it with the new version:
/etc/init.d/dynaTraceCollector<NN>and fill in the noted values for
- Take note of the values for the variables
6. Auto-start new services
update-rc.d, make sure that the new Server, Collectors, Memory Analysis Server, and Frontend Server are started automatically with
/etc/init.d shell scripts and that the permissions are correct.
7. Start the new Server components
If you configured a
DT_HOME environment variable, update it to
<DT_HOME_NEW>, and then start the AppMon Server and Frontend Server. When upgrading from 6.3 and earlier, for the first startup, leave a few minutes before starting the Analysis Server after the Frontend and Backender Server startup, to prevent JLT-194884 which could cause the loss of the PWH configuration.
8. Client migration
If users are allowed to reconfigure their client settings such as proxy, skip this step. Otherwise, compare old and new files and carry over your changes:
- After a first client start in each user home the old and new
- Defaults for new users on a machine:
9. Start the new Client
dtclient or use the Webstart Client at
Be sure to connect to the right AppMon Server (hostname) in the Settings > Dynatrace Server > Connectivity pane.
10. Activate licenses for the new Server
If you require a proxy server to access the Internet, manually configure the Client proxy settings to access the online licensing eServices site.
To import the Server and UEM licenses, click Settings > Dynatrace Server > License > Import and follow the instructions.
11. Select server sizing
After the license import, you are presented with different sizing options. Select the Sizing that you identified during the Preparations. It is important to perform this step before starting the new Collectors, to avoid Out-of-Memory problems.
12. Apply update to new AppMon
13. Connect the Performance Warehouse
In Settings > Dynatrace Server > Performance Warehouse, verify configuration for the old database, click Test and Connect.
An upgrade automatically occurs if needed after you connect to the Performance Warehouse. You must have appropriate permissions for the upgrade, since new columns and tables are introduced.
If migrations are pending, AppMon does not automatically connect to or upgrade the AppMon Performance Warehouse when starting or restarting the AppMon Server. Pending migrations occur when there is a major or minor version upgrade to the AppMon Server.
You must re-enter your DB-connection password after migrating to a newer AppMon release.
See Performance warehouse migration troubleshooting if you encounter an error.
14. Configure session storage
If you want to migrate your stored sessions, choose Settings > Dynatrace Server > Storage and verify that the directory points to your session storage data.
15. Start new Collectors
Start the new Collectors, then choose Settings > Dynatrace Server > Collectors and verify that all Collectors are connected to the Server. If you applied an update(to the new Server), you should immediately restart the Collectors from this dialog box for the update to be applied.
The AppMon Server and Collector now accept Agent connections.
Next: Upgrade Agents