Running Microsoft and Oracle Stacks on Elastic Block Store (STG303) | AWS re:Invent 2013

2,286 views
1,975 views

Published on

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

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,286
On SlideShare
0
From Embeds
0
Number of Embeds
40
Actions
Shares
0
Downloads
49
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Running Microsoft and Oracle Stacks on Elastic Block Store (STG303) | AWS re:Invent 2013

  1. 1. Running Microsoft and Oracle Stacks on Elastic Block Store [STG303] Jafar Shameem, Abdul Sathar Sait, Ulf Schoo (AWS) November 15, 2013 © 2013 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in part without the express consent of Amazon.com, Inc.
  2. 2. Agenda • AWS storage options and Amazon EBS • Amazon EBS Provisioned IOPS • Oracle and Microsoft stacks – – – – Licensing Sizing guidelines Best practices Demos
  3. 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. 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. 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. 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
  7. 7. Consistent Performance Within 10% of the IOPS performance 99.9% of the time over a given year
  8. 8. Consistent End-to-End Application Latency Before PIOPS: After PIOPS:
  9. 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. 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. 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
  12. 12. Avoid Throughput Saturation - Calculate maximum number of Amazon EBS volumes for the instance type
  13. 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
  14. 14. Oracle Stack on AWS Elastic Block Storage
  15. 15. Oracle on AWS • AWS simplifies Oracle implementation • Makes management easy • Could reduce implementation cost and time by half
  16. 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. 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. 18. 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
  19. 19. Enterprise Class Oracle Database Architecture
  20. 20. High-Performance Oracle Database Architecture
  21. 21. 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
  22. 22. PIOPS and EBS-Optimized Instances
  23. 23. 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
  24. 24. Instantiating Amazon EC2 instance for Oracle DB "Properties" : { ………… . "Volumes" : [ { "VolumeId" : { "Ref" : "RedoLogVolume" }, "Device" : "/dev/sde" }, { "VolumeId" : { "Ref" : "RedoLogVolumeMirror" }, "Device" : "/dev/sdf" }, { "VolumeId" : { "Ref" : "DataVolume01" }, "Device" : "/dev/sdi" }, { "VolumeId" : { "Ref" : "DataVolume02" }, "Device" : "/dev/sdj" }, { "VolumeId" : { "Ref" : "DataVolume03" }, "Device" : "/dev/sdk" }, { "VolumeId" : { "Ref" : "DataVolume04" }, "Device" : "/dev/sdl" }, { "VolumeId" : { "Ref" : "DataVolume05" }, "Device" : "/dev/sdm" }, ], "PrivateIpAddress" : "172.22.2.10", "SecurityGroupIds" : [{ "Ref" : "ORCLInstanceSecurityGroup" } ], "SubnetId" : { "Ref" : "PrimaryDBSubnet" },
  25. 25. Installing Grid Control # groupadd -g 1000 oinstall # groupadd -g 1031 dba # groupadd -g 1020 asmadmin # groupadd -g 1021 asmdba # groupadd -g 1022 asmoper # groupadd -g 1032 oper # useradd -u 1100 -g oinstall -G asmadmin,asmdba grid # useradd -u 1101 -g oinstall -G dba,oper,asmdba oracle #su grid
  26. 26. Installing Grid Control and Striping with ASM $ ./runInstaller -silent -ignoreSysPrereqs -ignorePrereq -responseFile /u01/SRC/grid/response/grid_install.rsp ORACLE_BASE="/u01/app/oracle" ORACLE_HOME="/u01/app/oracle/11.2.0/grid" oracle.install.option="HA_CONFIG" oracle.install.asm.OSDBA=asmdba oracle.install.asm.OSOPER=asmoper oracle.install.asm.OSASM=asmadmin INVENTORY_LOCATION="/u01/app/oraInventory" oracle.install.asm.diskGroup.name=DATA oracle.install.asm.diskGroup.redundancy=NORMAL oracle.install.asm.diskGroup.diskDiscoveryString="/u01/disks/data*" oracle.install.asm.diskGroup.disks ="/u01/disks/data1, /u01/disks/data2, /u01/disks/data3, /u01/disks/data4, /u01/disks/data5 " oracle.install.asm.SYSASMPassword=password oracle.install.asm.monitorPassword=password
  27. 27. Installing Database Using ASM striped disks dbca -silent -createDatabase -templateName General_Purpose.dbc -gdbName orcl -sid orcl SysPassword password -SystemPassword password -emConfiguration NONE -redoLogFileSize 100 -recoveryAreaDestination DATA -storageType ASM -asmSysPassword password -diskGroupName DATA -characterSet AL32UTF8 -nationalCharacterSet AL16UTF16 -totalMemory 800
  28. 28. 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
  29. 29. Windows Workloads on Amazon EBS Storage
  30. 30. Windows Workloads on AWS • Your solutions • At your scale • Powered by AWS
  31. 31. Storage Performance Is Key in all Windows-Based Enterprise Deployment Scenarios SharePoint Enterprise Farm Exchange Server
  32. 32. 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
  33. 33. Deploy Storage Components Using the Tools You Are Already Familiar With … AWS Tools for Visual Studio AWS Tools for Windows PowerShell
  34. 34. … from AWS CloudFormation or Windows PowerShell CLI AWS CloudFormation Windows PowerShell CLI PS C:> new-ec2volume –size 937 –AvailabilityZone us-west-2a – StoredCredentials ulfpowershell
  35. 35. Configure Storage for Maximum Performance at Instance Provisioning Time DiskPart Utility Windows PowerShell
  36. 36. 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
  37. 37. 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
  38. 38. 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.

×