Migrating Oracle to AWS

 Migrating Oracle to AWS 

Very good article and Presentation BY Daniel

■ Gather stats

■ Migrate data to RDS

■ Monitoring

Presentation - Migrating Oracle to AWS

AMAZON WEB SERVICES EC2

Amazon Elastic Compute Cloud (Amazon EC2)

Amazon Elastic Compute Cloud (Amazon EC2)

 provides secure, resizable compute capacity in the cloud as Amazon EC2 instances. 

Imagine you are responsible for the architecture of your company's resources and need to support new websites. With traditional on-premises resources, you have to do the following:

• Spend money upfront to purchase hardware.
• Wait for the servers to be delivered to you.
• Install the servers in your physical data center.
• Make all the necessary configurations.

By comparison, with an Amazon EC2 instance you can use a virtual server to run applications in the AWS Cloud.

• You can provision and launch an Amazon EC2 instance within minutes.
• You can stop using it when you have finished running a workload.
• You pay only for the compute time you use when an instance is running, not when it is stopped or terminated.
• You can save costs by paying only for server capacity that you need or want.

Types Of EC2 Instances and Their Uses Cases

1. General Purpose Instances: 

Balance of Compute, Memory and Networking Resources

 and can be used for a variety of workloads.

Series: A (Arm Ecosystem), M & T

USES:
* A- Webserver, Containerized Micro Services, Caching Fleets
* M- Gaming Server
* T- Website and Webapp, Code Repo

2. Compute Optimize Instance: 

Ideal for compute bound application (Banking applications) that benefit from high performance processors. (Processing Thousands of requests at a particular point of time)

Series: C (C4, C5)

USES:
* C4- Batch Processing, Video Editing
* C5- High Performance Web Servers, Gaming

3. Memory Optimized Instance:

* High performance relational and NoSQL databases.
* Well suited for Memory Intensive Enterprise Application and SAP HANA (High performance Analytic Appliance)

Series: R, X & Z

USES:

* R- Financial Services, Hadoop
* X and Z- Electronic Design Automation

4. Storage Optimized Instances:

Designed for workloads that require high, sequential read and write access to very large datasets on local storage.

Series: I, D & H

USES:
* I- Data Warehousing Application, OLTP
* D- Massive Parallel Processing Data Warehouse
* H- Data-intensive workloads such as MapReduce and distributed file systems

5. Accelerated Computing Instance: 

Uses hardware accelerators and co-processors to perform same functions such as floating-point number calculation, graphic processing or data pattern matching more efficiently than it is possible in software running on CPUs.

Series: P, G & F (FPGA)

USES:
* P- Machine Learning, Seismic analysis
* G- Video Creation Services, 3D Visualization
* F- Genomics Research, Financial Analytics

6. High Memory Instance:

Purpose built to run large - in - memory databases including production developments of SAP HANA in the cloud.

Series: U

USES:
* U- Reducing the management overhead associated with complex networking and ensuring predictable performance.

 

Amazon RDS Reserved Instances

Amazon RDS Reserved Instances give you the option to reserve a DB instance for a one or three year term and in turn receive a significant discount compared to the On-Demand Instance pricing for the DB instance.
You can choose between three payment options when you purchase a Reserved Instance. With the All Upfront option, you pay for the entire Reserved Instance with one upfront payment. This option provides you with the largest discount compared to On-Demand Instance pricing. With the Partial Upfront option, you make a low upfront payment and are then charged a discounted hourly rate for the instance for the duration of the Reserved Instance term. The No Upfront option does not require any upfront payment and provides a discounted hourly rate for the duration of the term.
All Reserved Instance types are available for Aurora, MySQL, MariaDB, PostgreSQL, Oracle and SQL Server database engines.

Features

• Reserved Instances provide three payment options: All Upfront, Partial Upfront, and No Upfront.
• Reserved Instances can save you up to 69% over On-Demand rates when used in steady state.
• Reserved Instances require no change to how you use Amazon RDS. When computing your bill, our system will automatically apply Reserved Instance rates first to minimize your costs. An instance hour will only be charged at the On-Demand rate when the total number of instances you run that hour exceeds the number of applicable Reserved Instances you own.
• Reserved Instances for the MySQL, MariaDB, PostgreSQL, and Amazon Aurora database engines as well as the “Bring your own license” (BYOL) edition of the Oracle database engine offer instance size flexibility.
• All Upfront and Partial Upfront Reserved Instances can be purchased for one or three year terms, while No Upfront Reserved Instances are only available for one year term.
• Reserved Instances are available in all the AWS regions.
• Reserved Instances are available for all supported DB Engines.
• Pricing for Reserved Instances is available on the Amazon RDS Pricing page.

When Should You Purchase Reserved Instances?

Reserved Instances are a great option for the steady state use case. Most production applications require database servers to be available 24×7. Reserved Instances could provide your business substantial savings if you currently use On-Demand DB instances for your production applications.  

Reserved Instances can also provide significant cost savings for mission critical applications that run on Multi-AZ database deployments for higher availability and data durability.

You can determine whether Reserved or On-Demand DB Instances best fit your needs by comparing On-Demand hourly rates and the effective hourly rate of Reserved Instances. In order to calculate an effective hourly rate, amortize the one-time fee over the term and add the hourly usage rate.

Reserved Instance Payment Options

• No Upfront RIs – No Upfront RIs offer a significant discount (typically about 30%) compared to On-Demand prices. You pay nothing upfront but commit to pay for the Reserved Instance over the course of the Reserved Instance term. This option is offered with a one year term.

• Partial Upfront RIs – Partial Upfront RIs offer a higher discount than No Upfront RIs (typically about 60% for a 3 year term). You pay for a portion of the Reserved Instance upfront, and then pay for the remainder over the course of the one or three year term. This option balances the RI payments between upfront and hourly.

• All Upfront RIs – All Upfront RIs offer the highest discount of all of the RI payment options (typically about 63% for a 3 year term). You pay for the entire Reserved Instance term (one or three years) with one upfront payment and get the best effective hourly price when compared to running the same DB instance on an On-Demand basis.

How Billing Works

During billing, running DB instance usage is first compared to your active Reserved Instances to minimize costs. Each hour, if the amount of running instances is less than or equal to the total Reserved Instances you have purchased, all running DB instances will be charged at the Reserved Instance rate. Any usage of running DB instances that exceeds the amount of applicable Reserved Instances you have purchased will be charged the On-Demand rate.

For example, if you own 3 Reserved Instances with the same database engine and instance type (or instance family, if size flexibility applies) in a given region, the billing system checks each hour to see how many total instances you have running that match those parameters. If it is 3 or less, you will be charged the Reserved Instance rate for each instance running that hour. If more than 3 are running, you will be charged the On-Demand rate for the additional instances.

If you purchase a Reserved Instance in a given region where you have a applicable running DB instance, the benefit will automatically be applied to that instance moving forward.

Reserved Instance Size Flexibility

Amazon RDS Reserved Instances provide size flexibility for the MySQL, MariaDB, PostgreSQL, and Amazon Aurora database engines as well as the “Bring your own license” (BYOL) edition of the Oracle database engine. With size flexibility, your RI’s discounted rate will automatically apply to usage of any size in the instance family (using the same database engine). Size flexibility does not apply to Microsoft SQL Server and the License Included (LI) edition of Oracle.

For example, let’s say you purchased a db.m4.2xlarge MySQL RI in US East (N. Virginia). The discounted rate of this RI can automatically apply to 2 db.m4.xlarge MySQL instances without you needing to do anything.

The RI discounted rate will also apply to usage to both Single-AZ and Multi-AZ configurations for the same database engine and instance family. For example, let’s say you purchased a db.r3.large PostgreSQL Single-AZ RI in EU (Frankfurt). The discounted rate of this RI can automatically apply to 50% of the usage of a db.r3.large PostgreSQL Multi-AZ instance in the same region.

How To Purchase Reserved Instances

Reserved Instances can be purchased using the AWS Management Console, AWS CLI or AWS API.

AWS Management Console

1. Log in to the AWS Management Console, select "RDS" under "Databases".
2. Ensure you have selected the Region in which you would like to make your Reserved Instance purchases.
3. Select “Reserved instances” in the navigation pane and click on the “Purchase Reserved DB Instance” button.
4. Select the database engine, DB instance class, offering type and the term length. You can also enter an optional ID for your purchase.
   
5. Adjust the quantity of Reserved DB instances to purchase.
6. Click on “Continue”, verify the purchase information, and confirm.

Important Notes about Purchases

• Reserved Instance prices cover instance costs only. Storage and I/O are still billed separately.
• Region, DB Engine, DB Instance Class, Deployment Type and term length must be chosen at purchase, and cannot be changed later.
• You can purchase up to 40 Reserved Instances. If you need additional Reserved Instances, complete the form found here.
• Reserved Instances may not be transferred, sold, or cancelled and the one-time fee is non-refundable.

Best Practices for Running Oracle Database on AWS

 Best Practices for Running Oracle Database on AWS

Abstract

Amazon Web Services (AWS) offers you the ability to run your Oracle Database in a cloud environment. Running Oracle Database in the AWS Cloud is very similar to running Oracle Database in your data center. To a database administrator or developer, there are no differences between the two environments. However, there are a number of AWS platform considerations relating to security, storage, compute configurations, management, and monitoring that will help you get the best out of your Oracle Database implementation on AWS.

This whitepaper provides best practices for achieving optimal performance, availability, and reliability, and lowering the total cost of ownership (TCO) while running Oracle Database in the AWS Cloud. The target audience for this whitepaper includes database administrators, enterprise architects, systems administrators, and developers who would like to run their Oracle Database in the AWS Cloud.

Introduction

Amazon Web Services (AWS) provides a comprehensive set of services and tools for deploying Oracle Database on the reliable and secure AWS Cloud infrastructure. AWS offers its customers the following options for running Oracle Database on AWS:

1. Using Amazon Relational Database Service (Amazon RDS) for Oracle, which is a managed database service that helps simplify the provisioning and management of Oracle databases. RDS for Oracle makes it easy to set up, operate, and scale a relational database in the cloud by automating installation, disk provisioning and management, patching, minor version upgrades, failed instance replacement, as well as backup and recovery tasks. The push-button scaling feature of Amazon RDS allows you to easily scale the database instance up or down for better cost management and performance. RDS for Oracle offers both Oracle Database Enterprise Edition and Oracle Database Standard Edition. RDS for Oracle also comes with a License-Included service model, which allows you to pay per use by the hour.

2. Running a self-managed Oracle Database directly on Amazon Elastic Compute Cloud (Amazon EC2). This option gives you full control over the setup of the infrastructure and database environment. Running the database on Amazon EC2 is very similar to running the database on your own server. You have full control of the Oracle binaries database and have operating system-level access, so you can run monitoring and management agents and use your choice of tools for data replication, backup, and restoration. Furthermore, you have the ability to use every optional module available in Oracle Database. However, this option requires you to set up, configure, manage, and tune all the components, including Amazon EC2 instances, storage volumes, scalability, networking, and security based on AWS architecture best practices. In the fully-managed Amazon RDS (Amazon RDS) service, this is all taken care of for you.

3. FlashGrid Cluster virtual appliances enable running self-managed Oracle Real Application Cluster (RAC) and Oracle RAC extended clusters (across different AZs) on Amazon EC2. With FlashGrid Cluster you also have full control of the database and have operating system-level access.

4. Running a self-managed Oracle Database directly on VMware Cloud on AWS. VMware Cloud on AWS is an integrated cloud offering jointly developed by AWS and VMware. Like Amazon EC2, you have full control of the database and have operating system-level access. You can run advanced architectures like Oracle Real Application Cluster (RAC) and Oracle RAC extended clusters (across different AZs) in VMware Cloud on AWS.

Whether you choose to run a self-managed Oracle Database on Amazon EC2 or the fully-managed RDS for Oracle, following the best practices discussed in this whitepaper will help you get the most out of your Oracle Database implementation on AWS. AWS will discuss Oracle licensing options, considerations for choosing Amazon EC2 or Amazon RDS for your Oracle Database implementation, and how to optimize network configuration, instance type, and database storage in your implementation.

PDF 

Oracle-database-aws-best-practices.pdf