Migrate Dynatrace managed clusters & Activegates to cloud

[Gabor]

Currently we manage an environment where we have all dynatrace managed cluster nodes and activegates on physical machines running linux, monitoring both on premise environments and aws eks cloud.

We are planning to migrate our on premise Dynatrace managed clusters and activegates to a private AWS EKS cloud while still staying with Dynatrace managed.

As an end result we will have dynatrace managed cluster nodes running on AWS EKS alongside with activegates running on AWS EKS, monitoring both on premise hosts and  the aws eks environment. 

Is there anyone who has experienced such migration, is there any documentation provided covering the parts that can be problematic?

Thanks for your help,

[Islam_Zedan · Accepted solution]

Hello @Gabor 

I'd recommend to migrate using backup & restore method. To configure automatic backup for a Dynatrace Managed cluster

1. In the Dynatrace menu, go to Settings > Backup.

2. Enable cluster backup and choose the scope:

   • User sessions may contain sensitive information.
     Exclude user sessions from the backup to remain compliant with GDPR.

   • Exclude timeseries metric data from the backup if your historical data isn't relevant and you only want to retain configuration data.

   • Include backup of Log Monitoring events.

3. (Optional) Select data center. This step is required only if you have multiple data center deployment (Premium High Availability deployment). For more information on Premium High Availability deployments, see High availability for multi-data centers and Disaster recovery from backup

4. Provide a full path to the mounted network file storage where backup archives are stored.

5. Configure start time.

For cluster restore, please follow the below document and put into consideration 

• To restore a cluster on the same host as the source cluster, make sure to uninstall it first.
• Machines have a similar hardware and disk layout as the original cluster and sufficient capacity to handle the load after the restore.
• Make sure the existing cluster is stopped to prevent two clusters with the same ID connecting to Dynatrace Mission Control. See Start/stop/restart a cluster.
• Make sure that system users created for Dynatrace Managed have the same UID:GID identifiers on all nodes.
• On each target node, mount the backup storage to, for example, /mnt/backup. This path is referred to as <path-to-backup> in the steps below.
• Ensure the installer has read permissions to the NFS. For example: sudo adduser dynatrace && sudo chown -R dynatrace:dynatrace <path-to-backup>
• Create your cluster inventory. You'll need this information during the restore.
  • IDs of nodes in the cluster. The backup of each node is stored in a dedicated directory whose name is based on the node identifier, in the format node_<node_id> (for example, node_1, node_5, etc).
  • IPv4 addresses of the new machines.
  • The IP address of the target machine for each node.
  • The node ID of the node that will become the seed node in the cluster.

https://www.dynatrace.com/support/help/shortlink/managed-cluster-restore#restore-from-backup

For further details, please check the main document for cluster backup and restore.

https://www.dynatrace.com/support/help/shortlink/managed-cluster-restore

Thanks,

Islam

[Gabor]

Thank you Islam for your help!