Learn more about migrating to Amazon RDS with Database Migration Service.

1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
March 16, 2017
Database Migration and Replication with AWS
AWS Database Migration Service

2. Agenda
• How does the cloud help?
• How do I get there?
• When should I use it?
• How does it work?
• Show me!
• What have others done?
• Resources and details

3. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Cloud benefits

4. • Multi-engine support: Aurora, MySQL, MariaDB,
PostgreSQL, Oracle, SQL Server
• Automated provisioning, patching, scaling,
backup/restore, failover
• High availability with RDS Multi-AZ
– 99.95% SLA for Multi-AZ deployments
Amazon RDS

5. • Lower TCO because we manage the muck
• Get more leverage from your teams
• Focus on the things that differentiate you
• Built-in high availability and cross region replication
across multiple data centers
• Available on all engines, including base/standard
editions, not just for enterprise editions
• Now even a small startup can leverage multiple data
centers to design highly available apps with over
99.95% availability.
The Cloud makes things cheaper, easier, better

6. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
The journey

7. How can I get to the cloud?
How will my on-premises data migrate to the cloud?
How can I make it transparent to my users?
Afterwards, how will on-premises and cloud data interact?
How can I integrate my data assets within AWS?
Can I get help moving off of commercial databases?

8. Migration used to be cost + complexity + time
Commercial data migration and replication software
Complex to set up and manage
Application downtime
Database-engine-specific application code

9. What are DMS and SCT?
AWS Database Migration Service (DMS) easily and securely
migrates and/or replicate your databases and data warehouses
to AWS
AWS Schema Conversion Tool (SCT) converts your commercial
database and data warehouse schemas to open-source engines or
AWS-native services, such as Amazon Aurora and Redshift
We have migrated over 20,000 unique databases. And counting…

10. Migration options
If you’re not switching engines and can take downtime:
- SQL Server: bak file import
- MySQL: read replicas
- Oracle SQL Developer, Data Pump, Export/Import
- PostgreSQL: pg_dump
- SAP ASE: bcp

11. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
When should I use it?

12. When to use DMS and SCT?
Modernize Migrate Replicate
Modernize your database tier –
• Commercial to open-source
• Commercial to Amazon Aurora
Modernize your Data Warehouse –
• Commercial to Redshift
• Migrate business-critical
applications
• Migrate from Classic to VPC
• Migrate data warehouse to
Redshift
• Upgrade to a minor version
• Consolidate shards into Aurora
• Create cross-regions Read Replicas
• Run your analytics in the cloud
• Keep your dev/test and production
environment sync

13. When to use DMS and SCT? Modernize
Modernize your Database Tier
• Commercial to open-source
• Commercial to Amazon Aurora
Modernize your Warehouse
• Commercial to Redshift
Amazon
Aurora
Amazon
Redshift

14. New SCT Data Extractors
Extract Data from your data warehouse* and migrate to Amazon Redshift
• Extracts through local migration agents
• Data is optimized for Redshift and Saved
in local files
• Files are loaded to an Amazon S3 bucket
(through network or Amazon Snowball)
and then to Amazon Redshift
Amazon
Redshift
AWS SCT S3 Bucket
* 1st release supports Oracle v11 and up and Teradata v14 and up

15. Why use DMS and SCT?
Secure
Cost Effective
Remove Barriers
to Entry
Allow DB
Freedom
Keep a Leg in
the Cloud
Easy to Use, but
Sophisticated…
Near-Zero
Downtime

16. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
How does it work?

17. Database migration process

18. SCT guidance

19. SCT helps with converting tables, views, and code
Sequences
User-defined types
Synonyms
Packages
Stored procedures
Functions
Triggers
Schemas
Tables
Indexes
Views
Sort and distribution keys

20. Customer
premises
Application users
AWS
Internet
VPN
Start a replication instance
Connect to source and target
databases
Select tables, schemas, or
databases
 Let AWS DMS create tables,
load data, and keep them in
sync
 Switch applications over to
the target at your convenience
Keep your apps running during the migration
AWS
DMS

21. Load is table by table
Replication instance
Source Target

22. Change data capture (CDC) and apply
Replication instanceSource Target
Update
t1 t2
t1
t2
Transactions Change
apply
after bulk
load

23. Source
Target
What else can I do?
Source
Source
Replication instance

24. What else can I do? Target
Source Target
Target
Replication instance

25. Source
Take it all—or not
Target
Replication instance

26. Homogenous or heterogeneous
SQL Server MySQL
Oracle Oracle
Oracle Aurora

27. Warehouses as well
Amazon Redshift
Schema Conversion Tool
S3 Bucket

28. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Demo

29. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
What have others done?

30. Our customers…

31. Heterogeneous Migration
Oracle private DC to RDS PostgreSQL migration
Used the AWS Schema Conversion Tool to
convert their database schema
Used on-going replication (CDC) to keep
databases in sync until they reached the cutover
window
Benefits:
• Improved reliability of the cloud environment
• Savings on Oracle licensing costs
• SCT Assessment Report let them understand
the scope of the migration

32. Scale Up Migration
RDS MySQL to Amazon Aurora Migration
Used DMS with on-going replication (CDC) to
migrate the data
Benefits:
• Aurora handles their larger data storage
requirements. Per regulations they are storing
120 TB of data for 2 years
• Reduced cost and improved performance when
compared to large MySQL instances

33. Homogeneous Migration
RDS MySQL on EC Classic to VPC
Database ran an end-user application so could
not take downtime
70 RDS instances have been migrated
Benefits:
• Leveraging CDC, they could decrease
outage per database to less than 5 mins
• 70 RDS instances have been seamlessly
migrated

34. Split Migration
35 million members on it’s site
Many interdependent applications built over the
last 15 years with unique High IOPS
requirements
Migration from legacy cloud service to AWS
Combination of migration to MySQL on EC2 and
Amazon Aurora
Benefits:
• DMS reduced the time required to migrate our
databases by 40 percent
• Realized 55 percent cost savings by moving
some db’s to Amazon Aurora

35. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
The fine print

36. Other database migration use cases
Migration of business-critical applications
Migration from Classic to VPC
Cheap Read Replicas for Oracle
Read Replicas for other engines
Cross-region Read Replicas for Oracle and SQL Server
Analytics in the cloud
Dev/test and production environment sync
Ongoing replication for BI
Minor version upgrade

37. Sources for AWS Database Migration Service
Customers use the following databases as a source for data migration using AWS DMS:
On-premises and Amazon EC2 instance databases:
• Oracle Database 10g–12c
• Microsoft SQL Server 2005–2014
• MySQL 5.5–5.7
• MariaDB (MySQL-compatible data source)
• PostgreSQL 9.4–9.5
• SAP ASE 15.7+
RDS instance databases:
• Oracle Database 11g–12c
• Microsoft SQL Server 2008R2–2014. CDC operations are not supported yet.
• MySQL versions 5.5–5.7
• MariaDB (MySQL-compatible data source)
• PostgreSQL 9.4–9.5. CDC operations are not supported yet.
• Amazon Aurora (MySQL-compatible data source)

38. Targets for AWS Database Migration Service
Customers can use the following databases as a target for data replication using
AWS DMS:
On-premises and EC2 instance databases:
• Oracle Database 10g–12c
• Microsoft SQL Server 2005–2014
• MySQL 5.5–5.7
• MariaDB (MySQL-compatible data source)
• PostgreSQL 9.3–9.5
• SAP ASE 15.7+
RDS instance databases:
• Oracle Database 11g–12c
• Microsoft SQL Server 2008 R2 - 2014
• MySQL 5.5–5.7
• MariaDB (MySQL-compatible data source)
• PostgreSQL 9.3–9.5
• Amazon Aurora (MySQL-compatible data source)
Amazon Redshift

39. AWS Database Migration service pricing
T2 for developing and periodic data migration tasks
C4 for large databases and minimizing time
T2 pricing starts at $0.018 per hour for T2.micro
C4 pricing starts at $0.154 per hour for C4.large
50 GB GP2 storage included with T2 instances
100 GB GP2 storage included with C4 instances
Data transfer inbound and within AZ is free
Data transfer across AZs starts at $0.01 per GB

40. Resources available to customers—DMS
Getting Started Guide: Review technical
documentation.
Features and benefits: Highlights DMS
features.
Pricing: Prices for replication instances,
storage, and data transfer.
Support: Post your questions to our
Support forum.
Java SDK: Java-based API for creating
and managing data migration tasks.
AWS Command Line Interface: Start
and stop replication tasks with simple
commands.

41. Resources available to customers—
AWS Schema Conversion Tool
User Guide: Review technical docs at
aws.amazon.com/documentation/SchemaConversionTool/
or choose the Download button.
Download area: Get installation files for the
Schema Conversion Tool.
Support forums: Ask questions and review
how-to guides.
https://forums.aws.amazon.com/forum.jspa?forumID=208.

42. AWS database migration partners

43. Thank you!
aws.amazon.com/dms
Learn more..