Run your Enterprise applications on Elastic Block Store (EBS). This session will discuss how you can leverage the block storage platform (EBS) as you move your Microsoft (SQL Server, Exchange, SharePoint) and Oracle (Databases, E-business Suite, Business Intelligence) workloads onto Amazon Web Services (AWS). The session will cover high availability, performance, and backup/restore best practices
2. Agenda
• AWS storage options and Amazon EBS
• Amazon EBS Provisioned IOPS
• Oracle and Microsoft stacks
–
–
–
–
Licensing
Sizing guidelines
Best practices
Demos
3. Storage Options on AWS
Instance storage
Use for:
• Temporary files
• Storage for
applications that
can withstand node
failures
Block storage
Use for:
• Access to raw
unformatted blocklevel storage
• Persistent Storage
Object storage
Use for:
• Pictures, videos,
highly durable
media storage
• Cold storage for
long-term archive
4. Amazon Elastic Block Store (EBS)
Elastic Block Storage: Persistent Storage for EC2
Feature
High-performance
file system
Flexible size
Performance
High-performance block storage
Secure
Available
Details
Mount Amazon EBS as drives and format
as required
Volumes from 1 GB to 1 TB in size
Up to 4000 IOPS per volume
Private to your instances
Replicated within an Availability Zone
device
Mount as drives to instances
Backups
Volumes can be snapshotted for point in
time restore
Persistent and independent of
instance lifecycle
Monitoring
Detailed metrics captured via Cloud
Watch
5. Two types of Amazon EBS Volumes
Standard volumes
• Moderate performance
• Boot volumes, light traffic
websites, file servers
Provisioned IOPS volumes
• Optimized for transactional
workloads
• Business applications,
relational and NoSQL
databases, etc.
6. Workloads on Amazon EBS
Relational
databases
NoSQL
databases
Data
repositories
Analytics
Oracle, SQL
Server
MongoDB,
CouchDB
DFS, Gluster,
Lustre
Fast sequential
I/O access
4 KB – 16 KB
random I/O
Random I/O, 10s
of thousands of
IOPS
Random or
sequential
access
Vertica, Hadoop
Totaljobs.co.uk
Parse
NASA JPL
Obama for
America
9. Block Size
Block sizes measures I/O in sizes of 16 KB
Throughput on a volume = IOPS * 16 KB
Number of volumes per instance depend on bandwidth to
Amazon EBS
10. Queue Depth
Drive enough I/O to get the IOPS that you provision
Very high IOPS may increase latency
Recommendation:
- Start of queue depth = 4
- Tune
11. Amazon EBS-Optimized Instances
- Use Amazon EBS-optimized
instances for performance
Instance
t1 micro
m1.small
m1.medium
m1.large
m1.xlarge
m3.xlarge
m3.2xlarge
c1.medium
c1.xlarge
cc2.8xlarge
m2.xlarge
m2.2xlarge
m2.4xlarge
cr1.8xlarge
hi1.4xlarge
cg1.4xlarge
vCPU
1
1
1
2
4
4
8
2
8
32
2
4
8
32
16
16
EBS
Optimized
No
No
No
Yes
Yes
Yes
Yes
No
Yes
NA
No
Yes
Yes
NA
NA
NA
Max
MB/s
32MB/s
64MB/s
64MB/s
64MB/s
128MB/s
64MB/s
128MB/s
32MB/s
128MB/s
800MB/s
64MB/s
64MB/s
128MB/s
800MB/s
800MB/s
800MB/s
Max
IOPS*
2000
4000
4000
4000
8000
4000
8000
2000
8000
50,000
4000
4000
8000
50,000
50,000
50,000
13. Snapshots
Duplicate volumes. Expand sizes of volumes. Move volumes.
Performance:
Write performance is affected while snapshot in progress
Schedule snapshots during off-hours
Snapshot often
15. Oracle on AWS
• AWS simplifies Oracle implementation
• Makes management easy
• Could reduce implementation cost and time by half
16. Some of the Oracle Products Our Customers Use on AWS
•
•
•
•
Oracle Database, GoldenGate, Data Guard
Oracle eBusiness Suite, PeopleSoft, Siebel, J D Edwards
Fusion Middleware, SOA suite, WebCenter, Weblogic
OBIEE, Hyperion, ATG Web Commerce
17. Oracle License Portability to AWS
• All Oracle licenses are fully portable to Amazon Web Services
•
Enterprise license agreement (ELA)
– Unlimited license agreement (ULA)
– Business process outsourcing (BPO)
–
•
Oracle Partner Network (OPN)
Processor and socket licensing:
– 0.25 core multiplier for standard licenses (sockets)
– 0.5 core multiplier for enterprise licenses (processor)
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31. Oracle Architecture Optimization
– Many ways to optimize web and middle tier
• Functional separation
• Vertical scaling
• Horizontal scaling and Auto Scaling
– Database performance is key to overall system performance
34. Oracle Database Performance Optimization
– Storage is key to database performance
– Good database performance needs consistent high IOPS
– It also requires low-latency, high-bandwidth connectivity to
storage subsystem
36. Oracle Database Performance Optimization
– PIOPS for every storage component of the database
– Storage separation helps to manage and scale
– Stripe together multiple PIOPS volumes for cumulative IOPS
and larger storage
– Use Oracle ASM for striping and storage management
– Amazon EBS-optimized instances
– Make good use of ephemeral disks
41. Oracle Database Backup and Archival
– Use Amazon S3 for all backups
– Snapshot non-data file volumes
– Use RMAN to backup the database to Amazon S3 using
Oracle Secure Backup Cloud Module (OSB)
– Archive data to Amazon Glacier for long term storage
44. Storage Performance Is Key in all Windows-Based
Enterprise Deployment Scenarios
SharePoint Enterprise Farm
Exchange Server
45. Planning and Sizing Your Storage Deployment
• Size as though you plan to deploy in a physical
datacenter
– E.g., use the Exchange Server Role Requirements Calculator
• Consider performance characteristics of a
shared computing, network, and storage
environment
• Provision IOPS based on the results of your
planning, and validate before production use
46. Deploy Storage Components Using the Tools You
Are Already Familiar With …
AWS Tools for Visual Studio
AWS Tools for Windows PowerShell
47. … from AWS CloudFormation or Windows
PowerShell CLI
AWS CloudFormation
Windows PowerShell CLI
PS C:> new-ec2volume –size 937
–AvailabilityZone us-west-2a –
StoredCredentials ulfpowershell
48. Configure Storage for Maximum Performance at
Instance Provisioning Time
DiskPart Utility
Windows PowerShell
49. Deployment Best Practices
• I/O contention removal
– Use ephemeral disks for page and temp files
• Striping for max IOPS
• SharePoint:
– RBS: Offload SQL content DB into Amazon S3 for lower TCO and
increased durability of the objects
• Exchange:
– Optimize DAG design for maximum throughput
– Monitor latency (I/O DB reads average latency, RPC latency to CAS
servers)
– Test and validate your storage design using Jetstress
50. Highly Available Windows Server and SQL Server
Solutions Running in the AWS Cloud
Demo
Windows Server Failover
Clustering (WSFC) cluster with
SQL AlwaysOn availability
groups
51. We are sincerely eager to hear
your feedback on this
presentation and on re:Invent.
Please fill out an evaluation form
when you have a chance.