Prerequisites

Component Description
Virtual Appliance
Deploy the Virtual Appliance 25.10.0 with necessary hardware requirements. You require the Virtual Appliance profile that can support the classic On-Premises load requirements. For guidance on choosing the right VA profile, see サイジング要件.
Note: The migration tool currently supports data transfer up to 12 TB from Classic On-Premises environments to Virtual Appliances deployed on AWS, KVM, Microsoft Azure, VMware vSphere and ESXi.
Ensure the following:

  • MySQL version is 8.0.x or higher.

  • The datastores and filestores in Virtual Appliance have sufficient space.

  • Grant super user privileges for the required user to install the NFS libraries.
Extra Large Sizing Profile For deployments that exceed the Large profile configuration defined, contact Splunk AppDynamics Professional Services for a thorough viability evaluation of your Controller.
Classic On-Premises Setup
Upgrade the following components:

Configure a load-balancer for the classic on-premises Controller, Events, and EUM server to receive agent traffic. This is an important configuration to initiate a cutover after you successfully migrate data to Virtual Appliance.

Verify that all Elasticsearch indices for the Events Service are in the green and open state. Run the following command within the classic on-premises Events Service environment:
CODE 
curl -vk http://localhost:9200/_cat/indices
NFS Server
CAUTION: Do not install the NFS Server on VA machine or any components running in classic on-premises environment.
  • Throughput in all the machines have 16,000 IOPS and 2,000 mbps.
    Note: If the machines throughput are low, the data migration from classic setup to Virtual Appliance will be slow. It might result in the data migration failures.
  • The NFS server must have a storage capacity of at least double the combined size of all initial datastores. For example, if
    • EUM MySQL = 100 GB

    • EUM Filestore = 100 GB

    • Events Elasticsearch = 200 GB

    • Controller MySQL = 500 GB

    • Synthetic Filestore = 100 GB

    The total size is 1000 GB. So, the NFS server storage capacity must be at least 2000 GB.

  • When migrating to a Virtual Appliance on VMware, the NFS server requires an SSD data disk.
Controller (MySQL) Select the appropriate hardware configuration based on the data volume for your migration from on-premises to the virtual appliance:
5 TB
Hardware Specification Max Metric Ingestion Per Minute
128 vCPU and 512 GiB RAM

(Example AWS VA Instance Type: m6a.32xlarge)

 2,500,000
12 TB
Hardware Specification Max Metric Ingestion Per Minute
128 vCPU and 1024 GiB RAM

(Example AWS VA Instance Type: r6a.32xlarge)

 2,500,000
Events Service (Elasticsearch) Select the appropriate hardware configuration based on the data volume for your migration from on-premises to the virtual appliance:
5 TB
Hardware Specification Max Metric Ingestion Per Minute
128 vCPU and 512 GiB RAM

(Example AWS VA Instance Type: m6a.32xlarge)

 2,500,000
12 TB
Hardware Specification Max Metric Ingestion Per Minute
128 vCPU and 1024 GiB RAM

(Example AWS VA Instance Type: r6a.32xlarge)

 2,500,000
EUM (Filestore) Select the appropriate hardware configuration based on the data volume for your migration from on-premises to the virtual appliance:
50 GB
Hardware Specification Max Metric Ingestion Per Minute
128 vCPU and 512 GiB RAM

(Example AWS VA Instance Type: m6a.32xlarge)

 2,500,000
200 GB
Hardware Specification Max Metric Ingestion Per Minute
128 vCPU and 1024 GiB RAM

(Example AWS VA Instance Type: r6a.32xlarge)

 2,500,000
Synthetic Server (Filestore) Select the appropriate hardware configuration based on the data volume for your migration from on-premises to the virtual appliance:
100 GB
Hardware Specification Max Metric Ingestion Per Minute
128 vCPU and 512 GiB RAM

(Example AWS VA Instance Type: m6a.32xlarge)

 2,500,000
300 GB
Hardware Specification Max Metric Ingestion Per Minute
128 vCPU and 1024 GiB RAM

(Example AWS VA Instance Type: r6a.32xlarge)

 2,500,000