Migrate Data from Classic On-Premises to Virtual Appliance

AppDynamics provides a migration tool that enables safe and reliable data migration from Classic On-Premises (source) to Virtual Appliance (destination). Migration to the Virtual Appliance delivers Kubernetes-based deployment automation, containerized scalability, and expanded functional capabilities. This migration process covers the transfer of key data stores, including MySQL, Elasticsearch, and Filestore snapshots. Data from critical components such as the Controller, End User Monitoring (EUM), Events Service, and Synthetic Monitoring is migrated from the Classic On-Premises deployment to the Virtual Appliance. The migration uses a Network File System (NFS) server as an intermediary to facilitate the secure and efficient transfer of these datasets.

The tool operates based on configuration parameters defined in the config.yaml file, which is essential for establishing secure and efficient communication between the source and destination environments. See Migration Tool Overview.

Migration Tool Overview

When you start the migration tool, the migration process begins with taking a full backup from the Classic On-Premises source and restoring it on the Virtual Appliance destination by using a shared NFS server. After it completes the initial backup and restore, a marker file gets created by the tool. If new data is detected, the tool continues running multiple cycles to migrate incremental changes until the data flow stabilizes and becomes consistent.

Verify the migration status in the {HOME}/migration-tool/SERVICE-MIGRATION-STATUS.txt file. Once the migration status reaches saturation, initiate the cutover by redirecting agent traffic from the Classic On-Premises to the Virtual Appliance. After cutover, the migration is finalized, and you can start monitoring your applications using the Virtual Appliance with the migrated data.

Overview of Migration Steps