Which data migration strategy should the company use?
Use the file gateway option in AWS Storage Gateway to replace the existing Windows file server, and point the existing file share to the new file gateway.
Use AWS DataSync to schedule a daily task to replicate data between the on-premises Windows file server and Amazon FSx.
Use AWS Data Pipeline to schedule a daily task to replicate data between the on-premises Windows file server and Amazon Elastic File System (Amazon EFS).
Use AWS DataSync to schedule a daily task to replicate data between the on-premises Windows file server and Amazon Elastic File System (Amazon EFS).
Explanations:
AWS Storage Gateway is suitable for hybrid setups but does not directly replicate data to AWS file systems like Amazon FSx or Amazon EFS. This option would replace the file server rather than simply replicating data.
AWS DataSync is designed to transfer data between on-premises storage and AWS. Using it with Amazon FSx provides a managed file system compatible with Windows-based workloads, making it the best fit for this scenario.
AWS Data Pipeline is not optimized for file server replication tasks. It is primarily used for orchestrating data workflows, not efficient data transfer between file systems.
Although AWS DataSync can transfer data to Amazon EFS, EFS is primarily designed for Linux workloads. Since the workload is Windows-based, Amazon FSx is a more appropriate target.
I surmise that the answer is:
Use AWS DataSync to schedule a daily task to replicate data between the on-premises Windows file server and Amazon FSx.
I gauge that the answer is:
Use AWS DataSync to schedule a daily task to replicate data between the on-premises Windows file server and Amazon FSx.