Now that you have completed BallotOnline’s Cloud Deployment Programmatic Approach, you have a better understanding of the available programmatic cloud deployment approaches and options, and how these approaches differ from traditional IT deployment approaches. You are now prepared to perform activities to migrate workloads to the cloud infrastructure.
Your supervisor, Sophia, the vice president of Information Technology (IT), has tasked you with the migration of workloads to the cloud infrastructure and has selected the migration of a database that is part of a critical aspect of BallotOnline’s operation. You are also asked to migrate the corporate intranet to the public cloud. You will now evaluate and compare different data migration approaches and select the best approach for BallotOnline, along with your rationale for selecting the specific approach and tool set.
As always, your selection of the appropriate approach and tool set must incorporate industry best practices and standards and meet the relevant business and technical needs of the organization.
There are seven steps in this project.
Also, there are 3 discussions (Discussion: Data Migration Approaches + Discussion: Evaluation of AWS Database Migration Service + Discussion: Database Migration Options to AWS) these discussions need to be answer in a separate document.
Step 1: Research Industry Standard Data Migration Approaches
Professionals in the Field
“Data migration is the process of making an exact copy of an organization’s current data from one device to another device—preferably without disrupting or disabling active applications—and then redirecting all input/output (I/O) activity to the new device.”
—Best Practices for Data Migration, IBM
Part of BallotOnline’s cloud strategy includes keeping up with the latest developments in the industry and applying current best practices. So, before getting started with the migration, take some time to research best practices and industry standard data migration approaches.
Discussion: Data Migration Approaches.
Now that you have completed BallotOnline’s Cloud Deployment Programmatic Approach, you will discuss the data migration approaches. You should cover the following areas:
- Why migrate your data?
- What levels of attention should each workload get?
- What migration design would you prefer?
- What are the migration execution strategies?
- How would you transition postmigration?
Step 2: Review and Compare Data Migration Tool Sets
Now that you have reviewed and discussed best practices and industry standard data migration approaches, review a few of the leading migration tools.
There are two basic approaches to data migration: “lift and shift” and “create new.”
Tool Set Used
Lift and Shift
Also known as rehosting, lift and shift involves replicating current applications in the cloud without redesign, enabling users to migrate their existing servers along with the data.
AWS Server Migration Service
This method involves creating new servers in the cloud as needed, and only replicating the data to the cloud.
AWS Database Migration Services
Review the two toolsets: AWS Server Migration Service and AWS Database Migration Services, and compare them in the Cloud Data Migration Tool Sets Comparison Template.
Before completing the whole project Submit the Cloud Data Migration Tool Set Comparison Template completed with your findings.
Step 3: Explore and Evaluate AWS Database Migration Service
Sophia favors the “create new” approach, since this aligns to industry best practices. Not surprisingly, she wants to use as many AWS-owned services as possible because AWS is the cloud vendor of choice for BallotOnline thus far in the organization’s move to the cloud.
Before evaluating databases for migration, make sure you understand the tool set of choice for BallotOnline’s cloud data migration, AWS Database Migration Service, so you can use it effectively and educate other team members if needed.
To make sure you understand the tool set and how it is used, answer the Discussion: Evaluation of AWS Database Migration Service. Then proceed to the next step, in which you will consider options within AWS for the migration.
Now that you have discussed the data migration approaches, you will discuss and evaluate AWS Database Migration Service (DMS). You should cover the following areas:
How is AWS DMS different from other database migration tool sets?
How are AWS Database Migration Service (DMS) and AWS Schema Conversion Tool (SCT) related?
What sources and targets does AWS Database Migration Service support?
What are the security features supported by AWS DMS?
Step 4: Review Options for Database Migration to AWS
Sophia has asked you to migrate two of BallotOnline’s on-premise database environments to the cloud: the human resources database. There are different options for different source database types. Human resources uses a MySQL database instance.
Review the following three options for database migration to AWS:
- Migrating from an RDS MySQL database instance to AWS
- Migrating from a MySQL database external to Amazon RDS to AWS
- Migrating from a database that is not MySQL-compatible to AWS
Answer the Discussion: Database Migration Options to AWS, and then proceed to the next step, in which you will move data from human resources.
Now that you have discussed the AWS Database Migration Service, you will discuss the migration options available via AWS Database Migration Service (DMS). You should cover the following areas:
What sources does AWS DMS support?
What targets does AWS DMS support?
How does AWS DMS support encrypted data?
How does AWS DMS support on-premise to AWS data migration?
How does AWS DMS support AWS RDS to other AWS database services?
Step 5: Migrate Data from a MySQL Database to AWS
Now that you have finished researching approaches, tool sets, and options, you can start the migration process. In this step, you will migrate BallotOnline’s human resources data from the external MySQL database to an Amazon Aurora MySQL database.
Check Your Knowledge
You may want to review the following Qwiklabs activities on how to migrate data from a MySQL database to AWS:
- Introduction to Amazon Relational Database Service (RDS) (Linux) (1 credit)
- Using Amazon RDS for Applications (10 credits)
Follow the detailed migration instructions in the MySQL Database Migration Guide.
The basic steps are:
- Step 1: Deploy a Replication Instance
- Step 2: Deploy Source and Destination Endpoints
- Step 3: Create Migration Task
- Step 4: Complete Database Migration
Make sure you take screenshots for each task since the screenshots will be used in your final Cloud Migration Technical Report.
Once you’ve migrated the database to Amazon Aurora MySQL and saved screenshots, move to the next step, in which you will migrate the payroll database.
Step 6: Perform Private Hyper-V Cloud Migration to AWS
In the previous step, you migrated BallotOnline’s HR resources MySQL database to Amazon Aurora MySQL. Now, you will complete the migration of BallotOnline’s other servers to the AWS public cloud. This operation includes moving BallotOnline’s Hyper-V server, which hosts its intranet, FTP server, and Network Time Protocol (NTP) server.
Note that a server running Microsoft Hyper-V is considered a private cloud. Other software for private cloud includes vSphere, OpenStack, and Xen. You may want to go back to Cloud Deployment Models to review the differences between public, private, and hybrid cloud.
Follow the Private Cloud Migration Lab Guide for detailed instructions on how to perform the private cloud migration to AWS using Server Migration Service (SMS).
The basic steps are:
- Create a role for the migration and name it SMS. This role will be used in the next step.
- Create and complete the replication job in Server Migration Service. This step will create an AMI (Amazon Machine Image) off the migrated server.
- Deploy an EC2 instance using the AMI from Step 3 above to verify the migration.
Take screenshots for each step since they will be used in your final Cloud Migration Technical Report.
Don’t forget to clean up the AWS resources to avoid any charges.
Step 7: Write the Final Cloud Deployment Programmatic Approach Document
Now that you have migrated both databases, your Cloud Migration Technical Report will consolidate the work that you have completed in the steps along with some additional elements (scope, executive summary, etc.).
This report will provide BallotOnline with a comprehensive cloud migration approach and tool sets that align with BallotOnline’s technical and business requirements. The final document should be between eight and 10 pages. Sophia will present your work for approval at the executive meeting.