(biz305) case study: migrating oracle e-business suite to aws | aws re:invent 2014

Post on 02-Jul-2015

733 Views

Category:

Technology

1 Downloads

Preview:

Click to see full reader

DESCRIPTION

With the maturity and breadth of cloud solutions, more enterprises are moving mission-critical workloads to the cloud. American Commercial Lines (ACL) recently migrated their Oracle ERP to AWS. ERP solutions such as Oracle E-Business Suite require specific knowledge in mapping AWS infrastructure to the specific configurations and needs of running these workloads. In this session, Apps Associates and ACL walk through the considerations for running Oracle E-Business Suite on AWS, including deployment architectures, concurrent processing, load balanced forms and web services, varying database transactional workloads, and performance requirements, as well as security and monitoring aspects. ACL shares their experiences and business drivers in making this transition to AWS.

TRANSCRIPT

American Commercial Lines

3

Prior to AWS migration

Prior to AWS migration

Drivers for considering AWS

Internet

Enterprise storage requirements

• Requires consistent performance, each application has unique requirements

• Addressed by storage layers like SSD, SAN, NAS etc..Performance

• Addressed by using RAID, Disk Backups, Tape BackupsDurability and availability

• Requires high CAPEXCost

• Often addressed by over provisioningElasticity and scalability

• Requires consistent performance; each application has unique requirements

• Addressed by storage layers like SSD, SAN, NAS, etc..

• Addressed by using RAID, disk backups, tape backups

• Requires high CAPEX

• Often addressed by over-provisioning

Enterprise storage on AWS

• Requires consistent performance, each application has unique requirements

• Addressed by storage layers like SSD, SAN, NAS etc..Performance

• Addressed by using RAID, Disk Backups, Tape BackupsDurability and availability

• Requires high CAPEXCost

• Often addressed by over provisioningElasticity and scalability

• Provisioned IOPS, SSD, Amazon Elastic Block Store (Amazon EBS) Optimized Instances

• Built in replication across AZ; snapshots can be replicated across regions

• Pay for what you use, buy vs. build

• Use as little or as much as you want or need

Storage option General Database Applications Speed Durability

Instance store Swap Temporary files Reports cache,

web server

cache

Very low

latency

Very low; volatile

EBS—PIOPS Data files, redo

logs

Low latency Moderate; needs to be

backed up regularly

EBS Boot

volume

Binaries,

archive logs

Binaries Moderate

latency

Moderate; needs to be

backed up regularly

Amazon S3 Backups Backups Backups Longer latency Very high durability

Amazon Glacier

Long-term

backups

Long-term

backups

Long-term

backups

Restore times

of 3–5 hours

Very high durability

SGA

Buffer Cache

100% cache hit ratio is ideal

for OLTP workloads

Cache miss Cache Hit

Select Update Select Update

Disk I/O Time

CPU Time

2. User volume is increasing...

1. Data size is increasing...

SGA

1. Huge amounts of data

2. Not possible to cache

all data

3. Many I/O operations

Buffer cache

Source: Oracle Corporation

Impact of I/O on CPU response times

0.00

2.00

4.00

6.00

8.00

10.00

12.00

14.00

16.00

0

100

200

300

400

500

600

700

800

100 200 300 400 500 600 700 800

Re

sp

on

se

Tim

e(N

orm

al-

10

0T

hre

ad

=>

1.0

0)

TP

S(N

orm

al-

10

0T

hre

ad

=>

10

0)

Thread

TPS RES

I/O bottleneck

Low throughput and slow response

Low CPU usage

Source: Oracle Corporation

Storage type Comments

Binaries EBS volume Standard volume;

EBS snapshots enabled

Data files PIOPS—EBS

volumes

Striped across multiple volumes using ASM or any

other technology

PIOPS of 1000 or above

Redo log files PIOPS—EBS

volumes

Use separate EBS volumes for each group

Preferable to use ASM disk groups

Archive log

files

EBS volumes Standard volumes for normal database workloads

PIOPS for highly transactional environments

Backup files EBS volumes /

Amazon S3

Standard EBS volumes for local backups

Use OSB / other technology to push to Amazon S3

Amazon S3 Bucket

Amazon Glacier

Life

Cycle

Policies

+DEV_DATA

4 EBS

Volumes

500 PIOPS

DEV TEST

Striping

+PROD_DATA

4 EBS

Volumes

4000 PIOPS

+PROD_FRA

4 EBS

Volumes

1000 PIOPS

PROD

StripingStriping

ASM instance with 16,000+ IOPS

+PROD_DATA

4 EBS

Volumes

4000 PIOPS

+PROD_FRA

4 EBS

Volumes

1000 PIOPS

PROD

Striping

RMAN Local Backup /backupfs EBS Snapshot

OSB Cloud Module

Using RMAN

Amazon

S3 Bucket

Striping

Security

It’s a shared responsibility

You

and/or your

service

provider

IaaS

provider

(AWS)

Access Control Encryption Networking Other

Identity and Access

Management (IAM)

Multi-factor

Authentication

(MFA)

Security Groups and

Network ACL

Dedicated instances

Amazon S3 Server-

Side Encryption

(SSE)

Amazon RDS

Oracle Transparent

Data Encryption

(TDE)

AWS CloudHSM

Client-Side SDK

data encryption

AWS Virtual Private

Cloud (VPC)

SSL Certificate

Management

AWS Direct Connect

VPN

Service Health

Dashboard

Trusted Advisor

Security Bulletins

Signed API Access

Amazon S3 Access

Logs

AWS Marketplace

Security Products

Best Practices

GovCloud

Security Attestations, Reports and Certifications

© Copyright 2014. Apps Associates LLC. 30

Proposed AWS Infrastructure

US East

AZ-1 Public Subnet

Private Subnet

Internet

VPN Tunnel

Production Test/Dev

NMS NAT

ACL corporate WAN

US West

Public Subnet

VPC Private Subnet

Internet

SnapshotReplication Backup Snapshots

App AppApp App

CRP

Backup Snapshots

American Commercial Lines

31

Post-AWS observations

Future plans relative to AWS

Please give us your feedback on this session.

Complete session evaluations and earn re:Invent swag.

http://bit.ly/awsevals

top related