Migrating server instances to separate installations

Overview

If you use AppMon Server instances that you created using the dtserver -instance command, you likely have two or more servers configured. The following steps let you to separate them into two separate installations, or distinct installation folders.

You should not perform an upgrade and separate the instances in a single step. First, split the instances into two distinct installations, for example inst1 and inst2. Once you have split the installation instances, then upgrade each one separately. The following shows the workflow.

undefined
undefined

Windows requires a separate OS installation for each of the server installations, matching its sizing requirements. This can imply new hardware, virtual machines or Windows licenses. The .msi installer prohibits multiple installations on the same OS.

With separate server, differentiate between the following:

  • The default server instance with most configuration files in <DT_HOME>/server/conf.
  • The (zero to many) server instances with the most configuration files in <DT_HOME>/server/instances/<INST_NAME>/conf.

Perform the following before making any changes:

  1. Download the latest Migration Tool.
  2. Stop all components in all instances running from <DT_HOME>.
  3. Back up all system before starting, especially the existing full installation directory using the following command:
    java -jar dynatrace-migration.jar -migration -sourceDTHome "<DT_HOME>" -targetArchiveDir "<ARCHIVE_DIR>"

Separation

Migrate the default server instance using the additional parameter -migrateInstances default when migrating from the migration archive to <DT_HOME_NEW> which is the target migration directory. See the AppMon 2017 May Upgrade and Migration Guide for more information.

For the remaining server instances, where <DT_HOME_OLD> is the original AppMon installation directory, for each AppMon Server instance, where <INST_NAME> denotes the instance name, perform:

  1. Install a new AppMon Server using the installer on the target host.
  2. Migrate all files, including files such as .ini files and agent resources shared between the default server instance and the server instance by executing the following command.
    java -jar dynatrace-migration.jar -migration -sourceDTHome "<DT_HOME_OLD>" -targetDTHome "<DT_HOME_NEW>" where <DT_HOME_NEW> is the selected installation folder, for example /opt/dynatrace-7.0-instance1.
  3. Execute the following command to migrate the server instance files to the default server instance.
    java -jar dynatrace-migration.jar -migration -sourceDTHome <DT_HOME_OLD>" -targetDTHome "<DT_HOME_NEW>" -migrateInstances serverinstances -makeServerInstanceDefault "<INST_NAME>".
  4. Delete the <DT_HOME_NEW>/server/instances folder for cleanup and configuration verification.

Port offsets for the previous instance server remain in place.

Manual steps

  1. All system profiles of the default instance and the migrated instance are migrated. From <DT_HOME_NEW>/server/conf/profiles, remove all *.profile files that are only in <DT_HOME>/server/conf/profiles and not also in <DT_HOME>/server/instances/<INST_NAME>/conf/profiles.
  2. Dashboard files have server instance references included. Either open each dashboard in the AppMon Client and set correct data source, or replace the server instance name in XML files before starting the server.
  3. For Linux only, update all init.d files. To do this, remove the variable values for <DT_INSTANCE> and <DT_FE_INSTANCE>. Keep the -portoffset parameter in the <DT_OPTARGS> and <DT_FE_OPTARGS> for new services (DTANG Adapter).

Apply general rules for multiple installations on the same system, for instance:

  • different startup and shutdown scripts referencing the correct installation (init.d)
  • separate TCP / UDP ports

Continue with the Upgrade and Migration Guide after the file migration for each instance.