Which set of steps should the company take to complete the migration in the LEAST amount of time?
Use VM ImporvExport to create images of each VM. Use AWS Application Migration Service to manage and view the images. Copy the Windows file share data to an Amazon Elastic File System (Amazon EFS) file system. After migration, remap the file share to the EFS file system.
Deploy the AWS Application Discovery Service agentless appliance to VMware vCenter. Review the portfolio of discovered VMs in AWS Migration Hub.
Deploy the AWS Application Migration Service agentless appliance to VMware vCenter. Copy the Windows file share data to a new Amazon FSx for Windows File Server file system. After migration, remap the file share on each VM to the FSx for Windows File Server file system.C. Create and review a portfolio in AWS Migration Hub. Order an AWS Snowcone device. Deploy AWS Application Migration Service to VMware vCenter and export all the VMs to the Snowcone device. Copy all Windows file share data to the Snowcone device. Ship the Snowcone device to AWS. Use Application Migration Service to deploy all the migrated instances.
Deploy the AWS Application Discovery Service Agent and the AWS Application Migration Service Agent onto each VMware hypervisor directly. Review the portfolio in AWS Migration Hub. Copy each VM’s file share data to a new Amazon FSx for Windows File Server file system. After migration, remap the file share on each VM to the FSx for Windows File Server file system.
Explanations:
VM Import/Export is typically used for importing/exporting VMs, not for managing ongoing migrations. AWS Application Migration Service is more efficient for continuous migration and tracking of VM states. Amazon EFS is a suitable file share solution, but the process of copying the file data and remapping the file share would be slower due to large data size and potential manual intervention.
AWS Application Discovery Service is used to discover applications, but it does not handle the actual migration of VMware VMs. The service helps assess the infrastructure but doesn’t complete the migration itself. Therefore, it cannot fully satisfy the goal of completing the migration quickly.
Using AWS Application Migration Service (AMS) with agentless appliance for VMware vCenter, combined with Amazon FSx for Windows File Server, is the optimal solution for quick migration. AMS supports minimal downtime migration, and FSx provides an efficient, scalable solution for Windows-based file shares. This approach handles both the VMs and shared file migration effectively.
Deploying AWS Application Migration Service agent and AWS Application Discovery Service agent directly on VMware hypervisors is an unnecessary step that complicates the process. Additionally, copying each VM’s file share data to FSx individually may lead to manual inefficiencies, which would delay migration. The combined use of AMS and FSx in option C is more streamlined.
I chart that the answer is:
Deploy the AWS Application Migration Service agentless appliance to VMware vCenter. Copy the Windows file share data to a new Amazon FSx for Windows File Server file system. After migration, remap the file share on each VM to the FSx for Windows File Server file system.C. Create and review a portfolio in AWS Migration Hub. Order an AWS Snowcone device. Deploy AWS Application Migration Service to VMware vCenter and export all the VMs to the Snowcone device. Copy all Windows file share data to the Snowcone device. Ship the Snowcone device to AWS. Use Application Migration Service to deploy all the migrated instances.