Migrating On-Premises NFS Using AWS DataSync and Amazon File Gateway
SPL-247 - Version 1.0.4
© 2021 Amazon Web Services, Inc. and its affiliates. All rights reserved. This work may not be reproduced or redistributed, in whole or in part, without prior written permission from Amazon Web Services, Inc. Commercial copying, lending, or selling is prohibited. All trademarks are the property of their owners.
Corrections, feedback, or other questions? Contact us at AWS Training and Certification.
AnyCompany relies heavily on the use of Network File System (NFS) file shares to conduct their day-to-day business. The CIO has expressed concerns that the data on the on-premises NFS file server is not adequately backed up or protected from a disaster at their primary data center. The budget is tight. She would rather spend money to improve the business over expensive backup or replication solutions, which will also require many staff hours to deploy and maintain. She approaches you, as the Systems Engineer, to come up with a solution that meets the following criteria:
- Ensures that the data on the on-premises NFS file shares is protected against a disaster in the company data center
- Is cost-saving
- Easy to deploy and maintain
- Can quickly migrate their existing data
- Can replicate future data off-site with minimal interaction from support teams
After extensive research, you have decided to do a proof of concept (POC) using AWS DataSync and AWS Storage Gateway file gateway.
AWS DataSync satisfies many of the requirements:
- Copies the existing data from the on-premises NFS file server to Amazon Simple Storage Service (Amazon S3) for secure, redundant storage
- Can transfer data at up to 10 MBps to migrate the data quickly
- Is priced per-gigabyte of data moved, making it cost effective and predictable
- Can be deployed in minutes
However, DataSync tasks are run manually, not automatically. Though it is an ideal solution for transferring large amounts of data, AWS Storage Gateway file gateway provides the ongoing data transfer to and from Amazon S3. It is essentially acting as a file system mount on an S3 bucket. The file gateway NFS file share will replace the existing on-premises NFS file server, allowing for that server to be retired. Doing this will free up local resources and reduce maintenance time.
Refer to the Additional resources section at the end of the lab for more information about requirements, pricing, and FAQs for AWS DataSync, Amazon S3, and AWS Storage Gateway file gateway.
The lab begins with two Linux instances in separate subnets: one instance acting as the on-premises client host and one instance acting as the on-premises Linux NFS file server.
You then deploy a DataSync agent instance into the same subnet as the on-premises NFS file server. Configure it to copy sample data to an S3 bucket.
Lastly, you do the following:
- Deploy a file gateway appliance into the same subnet as the on-premises NFS file server
- Create an NFS file share on it
- Reconfigure the Linux client to connect to the new share
By the end of this lab, you will be able to:
- Deploy and activate an AWS DataSync agent as an EC2 instance.
- Create a DataSync task to copy data from a Linux-based NFS server to an Amazon S3 bucket.
- Deploy and activate an AWS Storage Gateway file gateway appliance as an Amazon Elastic Compute Cloud (Amazon EC2) instance.
- Create an NFS file share on a file gateway.
- Configure a Linux host to connect to an NFS share on a file gateway.
Technical knowledge prerequisites
To successfully complete this lab, you should be familiar with basic navigation of the AWS Management Console and be comfortable editing Linux configuration files.
- At the top of your screen, launch your lab by choosing
This starts the process of provisioning your lab resources. An estimated amount of time to provision your lab resources is displayed. You must wait for your resources to be provisioned before continuing.
If you are prompted for a token, use the one distributed to you (or credits you have purchased).
- Open your lab by choosing
This automatically logs you in to the AWS Management Console.
Do not change the Region unless instructed.
Common Login Errors
Error: Federated login credentials
If you see this message:
- Close the browser tab to return to your initial lab window
- Wait a few seconds
- Choose again
You should now be able to access the AWS Management Console.
Error: You must first log out
If you see the message, You must first log out before logging into a different AWS account:
- Choose click here
- Close your browser tab to return to your initial lab window
- Choose again
Inscrivez-vous sur Qwiklabs pour consulter le reste de cet atelier, et bien plus encore.
- Obtenez un accès temporaire à Console Amazon Web Services.
- Plus de 200 ateliers, du niveau débutant jusqu'au niveau expert.
- Fractionné pour vous permettre d'apprendre à votre rythme.