One-stop Solution for Mass Migration with Disaster Recovery Methodology with Demo

Consulting | Cloud | Digital | Managed Services
AWS Workshop Series
Level 300: One-stop Solution for Mass Migration with
Disaster Recovery Methodology with Demo
Tony Lam
Solution Architect Manager, ICG
28th July 2017

Agenda
9:00am-9:30am Registration
9:30am-10:10am Introduction to Best Practice to Design & Accelerate Mass Migration to AWS
10:10am-10:40am
Using the Database Migration Service (DMS) for Database Consolidation, Data
Distribution and Replication (Include Live Demo)
10:40am-10:50am Break
10:50am-12:20pm Migrate and DR to AWS at Enterprise Scale (Include Live Demo)
12:20pm-12:30pm Q&A

Introduction to Best Practice to Design &
Accelerate Mass Migration to AWS

Who we are?
AWS Next-Generation MSP
The Leading AWS partner in Hong Kong, Macau and
China to achieve AWS MSP 3.1 status
Worldwide Top 50 AWS MSP
Selected by Top IT 3rd Party ChannelE2E
AWS China Region
Consulting Partner
AWS Advanced
Consulting Partner
Audited AWS
Managed Services
Partners
Marketing
& Commerce
Competency
AWS Marketplace
Consulting Partner
AWS
Channel Reseller
AWS Authorized
Government Reseller

4 KEY RESEARCH FINDINGS of
Cloud Mass Migration
 COMPANIES THAT MIGRATE TO CLOUD
FASTER ARE MORE SUCCESSFUL
 RAPID ADOPTION LEADS TO EARLIER PAYOFF
 LEADERSHIP EXPECTS FASTER PATH,
PRESSURE ON DIRECTOR-LEVEL EMPLOYEES
TO IMPLEMENT
 COST-SAVINGS BECOMES LESS IMPORTANT
AS PICK UP PACE
83%
76%
AGILITY
SCALABILITY
TO SUPPORT
GROWTH
TOP REASONS
TO MIGRATE:
Source: Accelerating the cloud migration dividend - IDG Research

Cloud Mass Migration = Move to new home
Home Cloud
1) Find new home a) Select cloud provider
2) Inspect the security of new home b) Inspect the security of cloud and get
approval of your security team
3) Negotiate legal contracts to purchase
new home
c) Get procurement to negotiate the legal
contracts to your cloud
4) Design layout of new home d) Determine what cloud service and 3rd
party add-ons you need
5) Hire contractor to make new home
ready
e) Hire SI to create a minimum viable
cloud environment

Cloud Mass Migration = Move to new home
Home Cloud
6) Assess and discover everything you
owned
f) Application assessment
7) Pack what you want to keep g) Revise the application deployment
script for cloud
8) Hire movers and moving boxes to new
home
h) Hire SI with migration tools
9) Move in, unpack and tidy up your new
home
i) Deploy application to cloud and refactor
application of performance
10) Learn to navigate your new home j) Train team to use cloud environment

ICG
Successful
Enterprise
Cloud Adoption
Journeys
9
G O L D S P O N S O R

ICGis AWS Next Generation MSP
Your Trustworthy Partner on Enterprise Cloud Adoption Journey
G O L D S P O N S O R

Consulting | Cloud | Digital | Managed Services© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
21 July 2017
Enterprise Cloud Migration
Overview

Data Center
Consolidation
Digital
Transformation
Cost
Reduction
Acquisitions
or Divestitures
Real-estate
decisions
Colocation
or outsourcing
contract changes
Large scale compute
intensive workloads
Agility/Dev
Productivity
Why enterprises are migrating to the cloud

Migration Challenges
1. Maturity
2. Security
3. Ineffective Asset Management
4. Mergers and Acquisitions
5. Operational readiness
6. Application Complexity
7. Lack of Reusable Resources
8. Manual and Time Consume
9. Lack of Expertise
10. Legacy Applications

Value
Time
Foundation
Migration
Optimization
Project
 Early Discovery
 Proof of Concept
 TCO/ROIAnalysis
 Security & Risk Preparation
 Foundational Architecture
 Test and Development
 Production Application Migration
 Operational Integration
 Billing Optimization
 Mass Migration Portfolio
 DataCenter(s) Shutdown
 Horizontal Solutions (VDI, Back-up/Archive)
 Advanced Operational Patterns (CI/CD)
 Fully automated solution stack with
tools and service catalogs
Cloud Adoption is a Journey

Decision Gate Decision Gate
Migration Journey
ASSESS PREPARE EXECUTE

Planning is everything!

Use Cloud Adoption Framework (CAF)
to perform a maturity assessment
Use the results to identify gaps in
organizational maturity for the cloud
adoption
Ensure your cloud strategy closely
aligns to your business goals to drive
business outcomes and value.
Assess Your Current Maturity and Strategy

Need to have a good insight of your
current IT portfolio and application
workloads and on how things are
done today.
Ensures you have a directional cost
validation based on high-level
understanding of business value
across the application portfolio
Building a Business Case

Portfolio Discovery

Disconnected
and Incomplete Data
Asset
Inventories
CMDB
Tribal
Knowledge
SLA/OLA
App
Configuration
Data
Performance
Information
Architecture
Outcomes
Cost Model
Migration Patterns
Gathering Data and Organizing
“Discovery & Planning”
Application
Discovery Service
Applications
Infrastructure
Performance
Resource Model
Migration Plan
Business Value
Portfolio Discovery and Planning

Application Portfolio Assessment
DetailedAssessment
High Level
Portfolio
Assessment
Not Cloud
Now
Detailed Cloud
Assessment and 6R
treatment
Strategic Decisions
(Based on business
priorities and roadmap)
Initial Assessment
Migration
Project
Cloud Now

Portfolio
Assessment
Not Cloud
Now
Application
Inventory
Business
Priorities
Inflight
Migrations • Cloud
Compatibility
• Licensing Model
• Compliance
• Dependencies
 Hardware appliance
 Non-x86 workload
 Licensing Restrictions
 On Premise dependency
 Already virtualized x86
 Well-defined boundaries
 Cloud licensing model
 Known dependencies
 Horizontally scalable
 Leverages services
 “12 factor” applications
 Vendor cloud image
 Microservices
architecture
 “API- first” design
 Built in fault Tolerance
 Bundled metrics
Eligible
Friendly
Cloud
Native
Initial Assessment

Executing Application Migrations

Plan
Activate
• Prioritized backlog
• Application groups
• Migration strategy
• Success criteria
• Ops Integration -
Foundations and
Landing zone (target
zone setup)
• Setup Factory (Tools,
Teams, Process)
• Pilot migration
Execute
Optimize
• Application optimization
• Process optimization
• Operational optimization
• Cost optimization
Discover
Design
Build
Integrate
Validate
Cutover
Prioritized
Backlog
(PLAN)
AWS Migration Framework

Discover
Design
Build
Integrate
Validate
Cutover
Execute
Agile Application Migration Factory
 Application optimization
 Process optimization
 Operational optimization
 Cost optimization
Optimize
Prioritized
Backlog (PLAN)

Migration Best Practices

#1 AWS MigrationTools
AWS Database
Migration Service
Migrate between
on-premises and
cloud databases
AWS
Marketplace
3500+ products
over 35
categories
help you with
migrations and
a cloud
operating model
VM Import /
Export
Deploy
workloads
across your
infrastructure
AWS Server
Migration Service
Streamlines
migration of
existing
virtualized
applications
Simple large-
scale data
transfer
Exabyte-scale
data transfer
service used
to move
extremely
large amounts
AWS Snowball AWS
AWS Snowball Edge Snowmobile

Hardware – Server, Rack
Chassis PDUs, ToR
Switches (+Maintenance)
Software - OS,
Virtualization Licenses
(+Maintenance)
Hardware – Storage Disks,
SAN/FC Switches Storage Admin costs
Network Hardware – LAN
Switches, Load Balancer
Bandwidth costs
Network Admin costs
Server Admin / Virtualization Admin4
Facilities Cost
Space Power Cooling
Facilities Cost
Space Power Cooling
Facilities Cost
Space Power Cooling
Server Costs
Storage Costs
Network Costs
IT Labor Costs
1
2
3
#2: Analyze the Total Cost of Ownership

#3: Pick your Low Hanging Fruits
 Standalone applications are easy to move
 New Applications have more documentation and organizational
knowledge
 Loosely coupled (SOA based integrations) applications are good
candidates
Watch out for…
 16/32 bit, non-x86 systems, multicast clustered systems, engineered
systems and applications

#4: Get your hands dirty
Your initial migrations will…
 Answers tons of questions and build support within organization
 Provides vital learning’s & act as valuable point of reference
(validation) of what is possible
 Identifies gaps and touchpoints
 Provides correct estimation of the migration and operational costs
“There is no compression algorithm for experience”

#5: Accelerate your migrations
 Iterate using sprints to realize value
 Invest in people and skills development to accelerate learning
 Retire old applications where possible
 Celebrate your success

Cloud Migration Strategies -
6R Treatment

Migration Strategies

Comparing Cloud Migration Strategies
Time Cost
Business
Value
Retain N/A
Retire N/A
Re-host
Re-platform
Re-purchase
Refactor
Low
High
MigrationComplexity

Assessment-based approach
• Financial assessment
• Security assessment
• Compliance and regulatory
assessment
• Business assessment
• Technical assessment
• Contractual assessment

Mapping drivers to migration strategy
BusinessAgility/Value
Migration EffortLow High
High
Retain (Revisit)
Retire
Rearchitect (Replace)
Refactor
Replatform
Rehost

Retain
• Unsupported OS and applications
• Legacy applications that do not have
a business justification for migrating
to the cloud
Operating System Files
Disk Volumes
Disk Drives
Memory
NIC
Physical Machine/Virtual Machine Image
App Binary User Data
Retain Retire Rehost Replatform Refactor
Rearchitect
(Replace)

Retain (Revisit)
• Example: HR platform
• Why:
• Recent infrastructure investment
• Older technology with few cloud examples
• Proprietary third party software, no obvious support
• Limited depth of expertise in-house
• Limited lifespan
• Cost and risk of moving >> leaving in place
• Limited value in moving
• Outcome: left in place for 2+ years until retired

Retire
• Duplicate resources due to M&A
• Resources part of an existing
decommissioning program scope
• Clustered hosts for DR purposes
• Alternative HA hosts
Disk Volumes
Disk Drives
Memory
NIC
Rearchitect
(Replace)

Retire
• Example : Legacy Product (AS400)
• Why:
• EOL technology
• No clear migration path (cloud or other)
• No clear refactoring path
• No clear replatform option
• No funding source or clear ROI horizon
• Overlap with other enterprise options
• Outcome: Almost all legacy technologies retired. Some
product lines retired.

Rehost
Disk Volumes
Disk Drives
Memory
NIC
Amazon EC2
New Disk Volumes
Rehost
• Servers running packaged
software
• Applications without an
active roadmap
• Ad hoc, dev, and test
environments
Rearchitect
(Replace)

Replatform
Disk Volumes
Disk Drives
Memory
NIC
EC2
New Disk Volumes
Fresh New OS
App Binary User DataReplatform
• Changing the OS or
DB engine
• Upgrading to the
latest release of an
application
• Upgrading the OS
from Windows 2003
to Windows
2008/2012
• Upgrading from
Oracle 8 to Oracle 11
Rearchitect
(Replace)

Rehost <-> Replatform
• Example : Marketing website infrastructure
• Why:
• Technologies very well supported by AWS
• Strong in-house team
• Low risk migration path
• Lots of independent pieces, easily testable.
• Cost and risk of moving < leaving in place.
• Outcome: migration + upgrades under 3 months

LISTED GAMING & ENTERTAINMENT GROUP
- Secured Web Application Solution
68%
Cost
Savings/Year
80%
Efficiency
Gained
Challenges
• System migration
• Spiky traffic and enhance security

Refactor
Disk Volumes
Disk Drives
Memory
NIC
EC2
New Disk Volumes
New Operating System
App Binary User DataRefactor
© 2016, Amazon Web Services, Inc. or its Affiliates. All rights
• Changing middleware
• Recoding application
components
• Changing application
code to utilize cloud
native feature for
performance, scaling,
agility
Rearchitect
(Replace)

Scholastic: Refactor (+ Replatform)
• Example: Business Intelligence Solution plus DevOps Pipleline
• Why:
• Good match for AWS
• Obvious and self-contained pain points
• Strong development team
• New solution available (Cloud Services)
• Outcome: launched May, 10x performance benefits,
5–10x reliability/recovery improvement

CROSS-INDUSTRY Enterprise
– Multi-cloud Solution on AWS
55%
Cost
Savings/Year
90%
Efficiency
Gained
Challenges
• System migration in Multiple sites
• DevOps on App development and delivery

Rearchitect (Replace)
App Binary
Operating SystemFiles
Disk Volumes
Disk Drives
Memory
NIC
User Data User DataRearchitect
SaaS on
Hosted Solution
• Changing from RISC to
x86
• Changing
application
components
• Rebuilding application
•architecture
• Replacing the application
with a SaaS offering or
COTS product
• Purchasing a cloud-
•compatible license
Rearchitect
(Replace)

Rearchitect
• Exampe: Mobile Application & Digital Platform
• Why:
• Desire for investment
• Strong future product growth
• Strong development team
• Good architectural and service fit
• Outcome: Strong Cost and Performance improvements

REGIONAL MEDIA & TV BROADCAST
– Video Live Streaming Solution FOR HUGE TRAFFIC
58%
Cost
Savings/Year
80%
Efficiency
Gained
Challenges
• Handle large data streaming
• Require on-demand service

Consulting | Cloud | Digital | Managed Services© 2017, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
Migrating your Databases to AWS:
Deep Dive on Amazon RDS andAWS
Database Migration Service

Relational Databases
Managed Service
Simple and fast to scale
Fast, predictable performance
Low cost, pay for what you useAmazon
RDS
Amazon
Aurora

Key Features
Provision a database in 6 minutes
Provision a MAZ database with a few mouse clicks
Scale a database up/down with 60-90 seconds downtime
Apply patches with 60-90 seconds downtime
Add read replicas with a few mouse clicks
Protect your backups and logs with 11 9’s of durability
Recover to any point in time from nightly backups + logs
Detailed metrics, down to 1 second intervals
Secure your data with single click encryption at rest
Start/Stop your dev/test databases for up to 7 days
Amazon
RDS

MySQL-compatible and PostgreSQL-compatible
relational database platform
Performance and availability of
commercial databases
Simplicity and cost-effectiveness of
open source databases
Delivered as a managed service
What is Amazon Aurora?

Feature Aurora MySQL MariaDB PostgreSQL Oracle SQL Server
VPC
High availability
Instance Scaling
Encryption
Read replicas Oracle
Golden
Gate / DMS
Cross region
replicas
DMS
Max Storage 64 TB 6 TB 6 TB 6 TB 6 TB 4 TB
Scale Storage Auto scaling
Provisioned
IOPS
NA 30,000 30,000 30,000 30,000 20,000
Largest Instance R3.8XL R3.8XL
M4.10XL
R3.8XL
M4.10XL
R3.8XL
M4.10XL
R3.8XL
M4.10XL
R3.8XL
M4.10XL
RDS Engine Capability Matrix

Customers Want to Migrate to AWS, but…
They can’t afford long periods of application downtime
Tools that enable minimal downtime are expensive
It seems too complex and expensive to migrate
They still need a copy of the data on-premise
They want to migrate to an open source database
Sending large volumes of data to AWS requires an
expensive international network link
They don’t have the skills inside their organization

Traditional Approach to Migrate to AWS
1. Create your AWS account
2. Setup your Virtual Private Cloud (VPC) inAWS
3. Connect to AWS with a VPN or Direct Connect
4. Shutdown and backup your database
5. Transmit the backup to S3
6. Configure an EC2 instance with the DB software
7. Restore the backup
8. Configure EC2 instances for the application
9. Switch the users to useAWS

Traditional Approach to Migrate to AWS
1. Create your AWS account
2. Setup your Virtual Private Cloud (VPC) inAWS
3. Connect to AWS with a VPN or Direct Connect
4. Shutdown and backup your database
5. Transmit the backup to S3
6. Configure an EC2 instance with the DB software
7. Restore the backup
8. Configure EC2 instances for the application
9. Switch the users to useAWS
Steps 4-9 could take a week or more!

Now There is a Better Way!

AWS Database Migration Service (AWS DMS)
DMS migrates databases to AWS easily and
securely with minimal downtime. It can migrate
your data to and from most widely used
commercial and open-source databases.
Amazon Aurora

New NoSQL support
Migrate to AWS
• Move from MongoDB to Amazon DynamoDB
• Move from MongoDB to relational db’s
Move between NoSQL and SQL
• Change technologies
Amazon Aurora
DynamoDB
DynamoDB
RDS

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
Database Migration
Service

Multi-AZ Option for High Availability
Customer
Premises
or AWS
AWS
Internet
VPN
AWS
Database Migration
Service
AWS
Database Migration
Service

Change Data Capture (CDC) and Apply
Replication instance
Source Target
update
t1 t2
t1
t2
Transactions Change
apply
after bulk
load

Load is Table by Table
Source Target

Replication
instance
Source Target
Multiple Targets
Target
Target

Replication
instance
Source Target
Multiple Sources
Source
Source

Customers Don’t Have to Take Everything
Source Target
instance

Homogenous or Heterogeneous
Replication
instance
SQLServer MySQL
Replication
instance
Oracle Oracle
Replication
instance
Oracle Aurora

Strengths and Focus
Areas
DMS can act as a replication/migration SwissArmy
knife, but is not a magic wand.
Use It
- Heterogeneous migrations
- Minimal downtime required
- No native solution
Caution
- Some tables with large LOBs
- Complex data types
- High load database
Don’t Use It
- Native no downtime solution exists
- Can take downtime + native
- > 5 TB + slow Internet****

AWS Schema Conversion Tool (AWS SCT)
SCT helps automate many database schema and
code conversion tasks when migrating between
database engines or data warehouse engines
Amazon Aurora

AWS Schema Conversion Tool
Supports Schema Copy and RDS Recommendations

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

SCT Helps with Converting Tables, Views & Code
Sequences
User-Defined Types
Synonyms
Packages
Stored Procedures
Functions
Triggers
Schemas
Tables
Indexes
Views
Sort and distribution keys

SCT can tell you how hard the migration will
be
1.Connect SCT to
Source and Target
databases.
2.RunAssessment
Report.
3.Read Executive
Summary.
4.Follow detailed
instructions.

Pricing and Terms and Conditions
$0
for software license
Allowed Use
 Use SCT to migrate database schemas to
Amazon RDS, Amazon Redshift, orAmazon
EC2-based databases
 To use SCT to migrate schemas toother
destinations, contact for special pricing
Pricing
 Free software license
 For active AWS customers with
accounts in good standing

Customer Successes

Case Study – Migration from
Microsoft SQL Server to
RDS PostgreSQL

On Premises Database
MSSQL Server 2008 R2 Enterprise Edition
Database Stats (April 2016):
• Number of Tables: 102
• Database Size: ~ 55GB
• Server Specs: 128GB RAM, Intel Xeon CPU
with 24 Cores
>2 millionApproximate Registered SSO Users
(June 2016)
~37
Integrated Applications
(June 2016)
Ideal State
Approx. 66% penetration of TV households
183 TV channels including 53 HD channels
• database in AWS caters for SSO’s migration to the cloud
• able to manage current on-premises databaseload
• able to scale with the application
• must be highly available
• maintain cost efficiency while performing all of the above
Uberfusion Case Study – Data Migration for SSO Media
Company Profile
ASEAN Media Company
4.7 million residential customers

State of On-premise MSSQL Sever Database
Limited Scalability
As the on-premise MSSQL
Server Database is a
physical machine, scaling
requires purchasing and
installing additional
hardware.
Higher Costs
Hardware upgrades are
costly with a high hardware
delivery turn-around time.
Additionally, MSSQL
Server Enterprise Edition
licenses are high in costs.
Shared Infrastructure
The on-premises database
infrastructure is shared
across multiple
applications. A problem
caused by another
application could
potentially affect SSO.
New Mandate for SSO
To migrate the on-premise SSO system into Amazon Web
Services (AWS) cloud to reduce cost and improve
scalability.
Urgency
To be ready to handle
high load during Euro
and Olympics 2016
Zero Data Loss
All user-related data needed to be
migrated with zero data loss up tothe
point of migration.
Zero
Data Loss
The Challenge
Transparent to Users
There should be no visible impact to
SSO users. Encrypted data such as
passwords needed to be migrated
seamlessly.
Transparent
Short Migration Window
Data migration had to be completed
within a 90 minutewindow.
Time
Legacy Data
There is a lot of legacy data in the on-
premises database which is not clean.
Dummy data and special characters
exist where they shouldnot.
Legacy
Leverage Managed Services
To leverage Amazon’s relational
database service (RDS), instead of
managing our own databaseservers.
Managed
Service
System Needed to Be Testable
System needed to be testable on
migration night by a small team of
testers while ensuring the general
public cannot change thedata.
Testing
Migration into the Cloud
No data loss and completed in a short time frame at
minimal costs
The decision was made to go with RDS PostgreSQL, as:
- MSSQL on RDS does not support Multi Availability Zone
in AWS Singapore and hence cannot be highly available
- No need to maintain a VPN tunnel back to premise
- Lower OPEX costs compared to running MSSQL on
RDS or managing our own DB servers
Problem Statement, Mandate and Challenge
~11.5x cheaper
Compared to RDS MSSQL Server Enterprise

Challenge: Short Migration Window & Legacy Data
• Data cleansing was performed
• Instance created with access to both source and target database for
ease of migration
• Export scripts automated for speed and accuracy
• Multiple scripts to cater for special characters in data
• Logs offloaded from database to ElasticSearch and Kibana
Challenge: Leverage Managed Service
• Amazon’s RDS service for PostgreSQL was used
• System code base was updated to integrate with the new
database
Challenge: Testing
• Services were disabled pre-DNS migration for the SSO System
• Whitelist for specific users were created for testing and
verification of data
Challenge: Transparent to Users
• PostgreSQL Membership library was modified to mimic
ASP.NET Membership in regards to password encryption
• Migration was tested beforehand to ensure users would
still be able to login with their existing passwords
Amazon Kinesis AmazonElasticsearch
Firehose Service
Uberfusion’s Delivery for Data Migration for SSO System
Challenge: Zero Data Loss
• All user-related data tables were identified
• System was put into read-only mode before starting migration
• Views were created in the schema of the new PostgreSQL database, and exported to flat
files
• Number of records were verified for pre- and post-migration
• Data was verified for accuracy from a sample of users post-migration
The Solution
Amazon RDS Postgre SQL instance
Postgre SQL instance
Total Migration
Time
<1hr
Data size reduced
to
~1.5GB
~1.8 millionSSO users migrated

Migration Steps
Disable
SSO
Service
to export
data to
flat files
according
to new
schema
Remove
headers
from
Run script exported
files
Import
processed
files into
Amazon
PostgreSQ
L RDS
Test and
verify data
integrity
Create views to
match new schema
Re-enable SSO Service

Challenge: DB Migration from MSSQL to
Postgres
• Data exported into flat files with same
schema as new Postgres DB
libraries
same encryption
modified to
in
• Membership
replicate
PostgreSQL
> 500,000sessions in June 2016)
> 4x
TPS improvement
for login
Challenge: Scaling and Simplified Provisioning
• Separate applications on Amazon EC2
• Individual scaling groups according to load
Challenge: End-to-End Monitoring
• Silicone and service metrics monitored with Amazon
Cloudwatch
• Runscope used for API uptime and response time
monitoring
• Extensive logs input into Amazon Elastisearch via
Amazon Firehose, visualised via Kibana
Page load
times
50%
Challenge: Maintaining Connectivity
• Citrix Cloudbridge is leveraged to ensure
connectivity between AWS Cloud and on-
premise DC
Amazon EC2Auto Scaling CloudFormation
Amazon Kinesis
FirehoseAmazon CloudWatch
AmazonElasticsearch
Amazon S3 Service
Uberfusion’s Delivery for SSO Migration to AWS
Challenge: Improve System Performance
• Use of Redis cache instead of DB for sessions and time-based tickets
• Frequently accessed data is cached to reduce repeated DB reads
• Compression and Browser Caching enabled on Amazon CloudFront,
improving page load times by 50%
• TPS improved to 179 TPS for login on 4 auto-scaled servers vs 40 TPS
during on-premise
AmazonSES AmazonSQSAmazonCloudFront Amazon ElastiCache AmazonS3
Fast Provisioning of Infrastructure
• Scales independently and onlypay
for what you use.
• <1 day to duplicate environmentsvs
>5 days for on-premise.
The Benefits
Improved Development Efficiency
By leveraging AWS PaaS components,
man-days can be focused on other
parts of the system.
Improved Availability and System
Performance
• 50% improvement in page load
times.
Increased Visibility Allows for
Proactive Teams
• Detected McAfee FIM tool causing
CPU spikes.
• Detected iOS production application
hitting SSO Staging.
Sustain High Loads
• Anticipating Euro 2016 and
Olympics 2016load.
• 179 TPS in AWS vs 40 TPS on-
premise.
The Solution and Benefits

Understanding Database
Migration Projects

It’s Not Just the Database!
Application code
Scripts and integration points
Backup and recovery
General management procedures
• Monitoring
• Notifications
• Auditing
• Tuning and Diagnostics
People!

Database migration – multi phase process
Phase Description Automation Effort (%)
1 Assessment SCT 2
2 Database Schema Conversion SCT/DMS 14
3 Application Conversion/Remediation SCT 25
4 Scripts Conversion SCT 7
5 Integration with 3rd partyapplications 3
6 Data Migration DMS 4
7 Functional testing of the entire system 29
8 Performance tuning SCT 2
9 Integration and deployment 7
10 Training and knowledge 2
11 Documentation and version control 2
12 Post production support 3

Database Migration Process

Migrate and DR to AWS at Enterprise
Scale

AWS Cloud Adoption Framework (CAF)

The AWS Cloud Migration Process
•Portfolio discovery
•Goals and Drivers
•Prioritized backlog
•Foundations (target
zone setup)
•Setup Factory (Tools,
Teams, Process)
•Application optimization
•Process optimization
•Operational optimization
•Cost optimization
Discover Analyze Plan
Design Migrate Integrate
Validate Operate
Migration
Factory
Initiate
Optimize
Prioritized
Backlog (PLAN)
App 1
…
App n

Large migration planning
and execution considerations

 Data center lease ending
 Major capital depreciated
 Strategic decision to go all in AWS
Drivers

Business needs are a major factor in defining migration timelines:
 Short (< 3 months)
 Mid range (3 – 12 months)
 Longer term (1 – 3 years)
Timelines

 Migrate dev first, then production
 Live migrate production, then backfill dev
Workload migration approaches

 Hundreds to thousands of servers
 Aggressive migration timeline
 Large number of participants
 Combination of the above
What is a large migration?

Application migration challenges
 Lack of accurate discovery tools and processes
 Lack of application contexts / information
 Inaccurate on premise costs
 Lack of detail and scope with respect to operating
model, governance, risk, compliance, security,
software licensing, etc.
 Increased cost
 Longer time to value
 Inaction
Challenges

Additional large migration challenges
 Efficient coordination and communications across a large team made up of
business, application, development, operations, and partner participants
 Discovering, transforming, and deploying complex sets of workload
components
 Demand for automated management of AWS infrastructure and applications
 Insufficient WAN bandwidth to support ongoing operations + parallel server
and data migrations

Small to medium migration
Area Characteristic
Program & project management Can get by with PMs managing activities with Microsoft Project & spreadsheets
Can successfully leverage email and status calls to collect verbal updates, and report
on status
Infrastructure provisioning &
workload migration
Can get by with manual AWS infrastructure provisioning and workload migration
Team size Small to medium IT team, possibly some business stakeholders
Team skills Combination of IT & business staff that manage and execute the migration; may use
contractors/partners to assist
Level of project scope & visibility Smaller IT project or major business initiative in a smaller company

Large migration
Area Characteristic
Program & project management Requires automated workflow and tracking for technical and program-level visibility
Infrastructure provisioning &
workload migration
Requires automation of AWS infrastructure provisioning and workload migration
Team size 10s to 100s of staff performing coordinated/sequenced activities
Team skills Combination of IT & Business staff that have the context, and AWS and/or Partner
staff that have the specific SME skills to drive down risk & optimize every aspect of
the migration
Level of project scope & visibility Typically Tier 1 Business initiatives tied to strategic business goals/outcomes

Application Migration & Disposition
Options
Application
Interviews
App.
Automated
Discovery
App.
Migration
Options
App.
Analysis
Application Discovery
Migration & Disposition Options
Retain
Retire
Rehost
Repurchase
Replatform
Refactor
This is the “do nothing” option. Legacy costs remain
and obsolescence costs typically increase over time
Decommission and archive data as necessary
“Lift and Shift” or “Forklifting.” Automated and
scripted migrations are highly effective
Either a replacement through procurement, or/and
upgrade
Opportunities to address significant infrastructure
upgrades can be realized which positively affects
compliance, regulatory and obsolescence drivers
Re-architecting and recoding require investment
in new capabilities. Potentially significant
business disruption
DescriptionComplexity
Low
Low
Med
Med
High
High

Application Owner Meeting
Connectivity Requirements
Data Migration Requirements
Identify Application Artifacts
Document Success Criteria
Identify Testing Process
Resolve Dependency ConflictsApplication Dependencies
Review Existing Blueprints
Verify VPC Connectivity
Complete Artifact Checklist
Firewall RequestsFirewall Port Determination
Intra-port Requirements
Week 1 Week 2
Initial Architecture Design
Application Installation
VPC Port
Exception
Allocate Credentials
Verify Subnet
Connectivity
Deploy AMI’s
App Owner ReviewApp Architecture Review
VPC Architecture Design
Identify Enhancement Opportunities
Test Connectivity
Migrate Data
End to End Testing
Owner Sign-off
Update Final Design Document
Baseline Performance
Map out application migration activities
Discover Design Build
Key

Develop an Agile Phased Migration Plan
Phase 1
AWSGOVDEV1
AWSGovDev2
AWSIntranet1
AWSInventory1
AWSKEYSTONE2
AWSrectrac1
AWSWEB10
Phase 2
AWSEMS3
AWSFireDEV2
AWSFirehouse2
AWSOneRoof2
AWSPAGEGATE2
Phase 3
AWSAWATCH1
AWSFBO1
AWSSQL12
AWSSQLDW1
AWSSQLFBO1
AWSTicketMGR3
AWSTicketMGR4
AWSTKTMGRWEB1
Phase 4
AWS3MSelfCHK1
AWSAPPSQL1
AWSAPPSQLDEV1
AWSILS3
AWSPAC3
AWSPRIVATESP1
AWSSPPRODAPP1
AWSSPPRODAPP2
Phase 4 – Cont.
AWSSPPRODAPP3
AWSSPPRODSQL1
AWSSPPRODSQL2
AWSSPPRODWFE1
AWSSPPRODWFE2
AWSSQLDEV2
AWSTime3
AWSTimeDEV3
Each Phase – Multi Week Sprint + 2-Days for Lessons Learned

Workload Migration Playbook phases
Varies by customer but typically ~9 phases and ~40 high-level activities

Application Migration Level of Effort
2 – 4 hours 4 – 6 hours 6 – 8 hours 10 – 14 hours 20 – 24 hours
VM Conversion
Host Cloning
VM Conversion
Host Cloning
Host Cloning Live Migration
App
Containeriza
tion
Live Migration
App
Containeriza
tion
Live Migration
Migration
Method

Application (Infrastructure) Migration
Options

Application (Infrastructure) Migration
Use Cases

CloudEndure Network Diagram

CloudEndure Platform Support
CloudEndure allows replication of any machine, whether bare-metal, virtualized or
cloud-based.
Supported operating systems:
• Ubuntu v10.04 or higher, 32/64 bit
• Redhat Enterprise Linux v6 or higher, 32/64 bit
• CentOS v6 or higher, 32/64 bit
• SUSE Linux v11 or higher
• Oracle Linux v6 or higher
• Amazon Linux 2013.03 or higher, 32/64 bit
• Microsoft Windows Server 2003, 2003 R2, 2008, 2008 R2, 2012, 2012 R2, 32/64 bit

How CloudEndure Live Migration
Works ?
CloudEndure Live Migration works in 5 steps.
Installation
Selection
Continuous Replication
Testing
Cutover

1. Installation
Install the
CloudEndure Agent
on all of the machines
(physical, virtual or
cloud-based) that you
want to migrate.

2. Selection
Choose your target
location, what kind of
server you
want to create, and
what kind of network
you want to use.

3. Continuous Replication
Continue to work as
usual and let the
block-level,
continuous replication
take place in the
background. Neither
your servers nor your
business are affected.

4. Testing
When the replication is
complete, click “Test” to
spin up a copy of your
machines in the target
location and check that
everything has migrated
correctly. There is no
system disruption or
performance impact
during tests.

5. Cutover
When ready,
schedule a short
cutover window and
click “Cutover” to
finalize the migration
and redirect users to
the target location.

Application Migration with AI Driven
DevOps

Static Monitoring Doesn’t Work Any Longer
And isn’t just about analyzing logs & exceptions
and finding bad code through CPU Sampling

•ShipDevelop
•Scale
•Deploy
•Run
Because Apps And Services Delivery Has
Transformed
•Compute

Which Is Why Monitoring Has To Be
Redefined!
Every user, every app, everywhere, AI-powered, full stack, automated

Learnings: Monitoring as Pipeline Feature
CI CD
Unit Perf
Cont. Perf
New Deploy
New Capability
Remove/Promote
Triage/Optimize
Update Tests
Innovate/Design
Faster Innovation with Quality Gates
Faster Acting on Feedback
+
–
Happy
Users

Transformation Led To Key Monitoring
Capabilities
 Full Stack with OneAgent
 100% End-to-End
 Log Analytics
 Part of DevOps Pipeline
 Artificial Intelligence
 VoiceOps, ChatOps, Automation APIs

Dynatrace Transformation by the Numbers
More Quality
More Agile 26
500
Releases / Year
Deployments / Day
93%
Production bugs found by Dev
More Stability
31000
Unit & Int Tests / hour
~120
Code commits / day
450
Global EC2 Instances
60h
UI Tests per Build
340
Stories per sprint
99.998%
Global Availability

•Supporting
Enterprise and
Cloud
Technologies
100% Capturing of
End User Experience
and Ability to Replay
•Artificial
Intelligence:
Predictive
Analysis &
Remediation
Actions
•Integrated into
DevOps Pipeline:
Enabling Shift Left &
Shift Right
4 Pillars Benefits

#1: Application, Cloud And Container Tech
Support

#2: 100% End User Experience and Behavior

#2: 100% End User “Replay”

#3: Integrated into DevOps Pipeline
CI CD
Dev Perf/test Ops

#4: Dynatrace Artificial Intelligence for the Cloud
Dynatrace
Artificial Intelligence

#4: Dynatrace AI: Alerting on Anomalies –
Not on the Noise in the Cloud

#4: Dynatrace AI: Impact and Root Cause Details

#4: Auto Healing – Auto Remediation




Advice for Cloud Transformation Projects
Automate Traditional Ops
towards NoOps
Monitoring is a Pipeline Capability
rather than after thought
Monitoring is Mandatory and
has to be fully automated
Artificial Intelligence to Reduce Noise with so many moving points

Understand YOUR Strategy and Market
Drivers
Industry drivers
Market drivers&
innovation
CloudAdoption
StrategyBusiness strategy
Key Activities:
• Develop your cloud strategy aligned to
business requirements.
• Engage your stakeholders from the start
and bring them on the journey with you.
• Communicate the value to the business.
• Define measurable goals and monitor.
Set the stage for the journey. Be bold, but be smart!

Understand Where YOUR Are Today
Baseline
Gap
Initiatives
• Assess and baseline current
cloud / IT capabilities with
respect to people, process
and technology
• Prioritize list of
activities/initiatives when
executed result in delivery
of the business strategy
• Define the key cloudadoption
capabilities required to
achieve business objectives
Key Activities:
• Assess current capabilities: application
portfolio, talent, operational readiness,
architecture
• Define gaps in current state capabilities to
deliver on cloud vision and strategy
• Run workshop(s) on gap analysis,
presenting and verifying results with
stakeholders
Determine what capabilities you require to achieve your cloud vision

Plan Cloud journey for YOU
Cloud Activities Matrix
Cloud Roadmap
Key Activities:
• Develop prioritized set of
recommendations and initiatives
• Develop cloud adoption roadmap with
function dependencies and timelines
• Develop communications plan and
schedule
• Organize resources, partners,etc.
• Track progress, measure andreport
success often.
Develop and prioritize key initiatives for your cloud adoption roadmap to guide your execution.

Execute, Deliver and Managed for YOU
Explore
Prepare
Migrate /
Develop
Optimize
Business
Value
Optimization
Automation
Cost
Reduction
Implement roadmap items. Start small and iterate based on lessons learned. Enjoy the journey and
reap the value!!!
Key Activities:
• Explore - why do it, what business value,
gap analysis
• Prepare - project plan for activity, training,
establish platform, establish operations,
establish security
• Migrate/Develop - Move an existing
application to the cloud or develop a new
cloud native application
• Optimize - measure and identify
opportunities to improve
• Managed- monitoring and governance
cloud resources
Managed

Thank you

One-stop Solution for Mass Migration with Disaster Recovery Methodology with Demo

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (20)

Similaire à One-stop Solution for Mass Migration with Disaster Recovery Methodology with Demo

Similaire à One-stop Solution for Mass Migration with Disaster Recovery Methodology with Demo (20)

Plus de Amazon Web Services

Plus de Amazon Web Services (20)

One-stop Solution for Mass Migration with Disaster Recovery Methodology with Demo