Skip to main content

Create a deployment plan for Amazon EC2 using the migration advisor

Contributors netapp-mwallis netapp-rlithman
PDFs

Log in to the NetApp workload factory to access the VMware migration advisor. You'll follow the steps in the wizard to create a deployment plan or migration plan that is customized for your needs.

Note that you must have a user name and password to access workload factory. If you don't have access, create an account now. See the instructions here.

Create a deployment plan based on an on-premises vSphere environment

You can migrate your current virtual machine configurations in on-premises vSphere environments to virtual machines in Amazon EC2 and use customized Amazon FSx for NetApp ONTAP file systems as external datastores.

Requirements

  • You must have created the inventory file from your existing systems by using the migration advisor VM collector (.zip file) or by using RVTools (.xlsx file).

  • You must have access to the inventory file from the system on which you are logging in to workload factory.

Steps

  1. Log in to workload factory using one of the console experiences.

  2. From the VMware workloads tile, select Access and plan and then select Migration to AWS native compute. The VMware migration advisor splash screen is displayed.

    Review the information to learn about the benefits of the migration advisor.

  3. When ready, select Let's start.

  4. Select Create a new deployment plan.

  5. Select the type of inventory file you'll be using to populate workload factory with your current VM configuration and select Next.

    • Select Use the migration advisor VMware data collector to use the file that you created using the VMware data collector.

    • Select Use RVTools to use the .xlsx file that you created using RVTools.

    The "Prepare for AWS Cloud onboarding" page is displayed.

  6. In the Upload VM configuration section, select the upload button and select the inventory file that you want to use.

    • Select the .zip file when using the Migration advisor VM collector.

    • Select the .xlsx file when using RVTools.

    The VMs summary section is populated from the inventory file to reflect the number of VMs and the total storage capacity.

  7. In the VM inventory considerations section, select the options to filter the list of VMs that you want to migrate.

    1. Consider VMs: Indicate which VMs will be extracted from the inventory file based on their operating power state. You can bring in all VMs, or only those that are on, off, or suspended.

    2. VM Storage to consider: Select whether the datastores created for each onboarded VM are sized based on their currently utilized size (recommended) or their provisioned size.

      The external datastores will be implemented using Amazon FSx for NetApp ONTAP file system volumes.

  8. In the Cloud deployment configuration section, enter details about the required Amazon EC2 configuration.

    1. Region: Select the region where Amazon FSx for NetApp ONTAP file systems will be deployed.

      For optimal performance and cost efficiency, this is typically the same region as where your existing Amazon EC2 SDDC is deployed.

    2. VM estimated performance requirements: This option is available only when using RVTools. The Migration advisor VM collector captures this information from your environment. Provide the following per virtual machine average performance parameters that you want to be applied to your new VMs that will be deployed:

      • Average IOPS per VM: Enter the number of IOPS required for your file systems. If you are unsure, you can use the default of 3 IOPS per GiB of SSD storage for Amazon FSx for ONTAP file systems. For example, if you deploy 2,000 GiB of capacity, this will be translated to 6,000 IOPS. We recommend that you begin with a smaller IOPS setting. You can increase your provisioned SSD IOPS after the file system is created as workloads are migrated or deployed.

      • Average I/O block size: The size of each block containing read or write operations. The default size is 4 KB. A larger block size might be better for large sequential read and write workloads. A smaller block size might offer better performance for workloads that perform small random writes to sparse files or to large files.

      • Average write ratio: The percentage of operations that are write operations for your workloads. The default ratio is 30% writes and 70% reads.

  9. In the Target capacity and protection considerations section, select from a few storage options.

    1. Average data reduction ratio: Choose from among the three common data reduction ratios. Select "1:1 - No reduction", "1:1.25 - 20% reduction", or "1:1.5 - 33% reduction".

      Select Help me decide if you're unsure which ratio to choose. The Data reduction ratio assistant dialog appears. Select any statements that apply to your VM inventory and storage estate. The assistant will recommend an appropriate data reduction rate. Select Apply to use the recommended ratio.

    2. Headroom percentage: Enter the percentage of capacity growth that is added to the capacity for your FSx for ONTAP file systems.

      Note that if you select an amount less than 20% you won't be able to create volume snapshots for protection and long-term backups.

    3. VM snapshot protection: Enable this option to protect the VMs with snapshots.

  10. Select Next.

  11. On the Review EC2 volume assignment page, review the VM information, volume classification rules, volume assignments, and list of volumes that will be migrated as part of deployment.

  12. Select Next.

  13. On the Review instance storage assignment page, review the EC2 instances and the volumes assigned to different FSx for ONTAP clusters.

  14. On the Review your migration plan page, review the estimated monthly cost for all the VMs that you plan to migrate.

    The top of the page estimates the monthly savings for FSx for ONTAP file systems and EBS volumes. You can expand each section to view details for the suggested filesystem configuration, estimated savings breakdown, assumptions, and technical disclaimers.

  15. When you are satisfied with the migration plan, you have a few options:

  • Select Download plan > Instance storage deployment to download the external datastore deployment plan in a .csv format so you can use it to create your new cloud-based intelligent data infrastructure.

  • Select Download plan > Plan report to download the deployment plan in a .pdf format so you can distribute the plan for review.

  • Select Export plan to save the migration plan as a template in a .json format. You can import the plan at a later time to use as a template when deploying systems with similar requirements.

Create a deployment plan based on an existing plan

If you are planning a new deployment that is similar to an existing deployment plan that you've used in the past, you can import that plan, make changes, and then save it as a new deployment plan.

Requirements

You must have access to the .json file for the existing deployment plan from the system on which you are logging in to workload factory.

Steps

  1. Log in to workload factory using one of the console experiences.

  2. From the VMware workloads tile, select Access and plan and then select Migration to AWS native compute.

  3. Select Import an existing deployment plan.

  4. Select the upload button and select the existing .json plan file that you want to import in the migration advisor.

  5. Select Next.

    The Review plan page is displayed.

  6. You can select Previous to access previous pages and modify the settings for the plan as described in the previous section.

  7. After you have customized the plan to your requirements, you can save the plan or download the plan report as a PDF file.