Private Database Cloud Database Consolidation …dbaexpert.com/PrivateDatabaseCloud.pdf · Private...

1 1 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

Private Database Cloud Database Consolidation Planning and Best Practices Nitin Vengurlekar Viscosity – CTO/Cloud Evangelist Charles Kim Viscosity – President/Oracle Architect


•  Oracle Product Strategy and Private Cloud Evangelist

•  17 Years with Oracle, 10 years Oracle RAC development

•  Over 24 years of Oracle Expertise, RAC, Data Guard, ASM, RMAN

•  Private Database Cloud Evangelist and author of the Cloud Best Practices, Isolation and Security Management in Private Database Cloud

•  Author of Oracle Press ASM Cookbook and Oracle Data Guard Handbook

Ni#n Vengurlekar


Charles Kim


Program Agenda •  What is Private Database Cloud

•  Why Database Cloud Consolidation

•  Private Database Cloud deployment models

•  Database Cloud Consolidation Planning and Considerations

•  Engineered Solutions and the Private Database Cloud


NIST Definition of Cloud Computing

Cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. This cloud model promotes availability and is composed of:

Source: NIST Definition of Cloud Computing v15

3 Service Models •  SaaS •  PaaS •  IaaS

4 Deployment Models •  Public Cloud •  Private Cloud •  Community Cloud •  Hybrid Cloud

5 Essential Characteristics •  On-demand self-service •  Resource pooling •  Rapid elasticity •  Measured service •  Broad network access


Customers Have a Choice of Clouds •  Own & Operate, Use Managed Services, Subscribe

Managed Build Subscribe

Customer owns. Service provider manages.

Either may host.

Customer owns, hosts and manages.

Customer subscribes. Service provider hosts

and manages.

Managed Cloud Services Private Cloud Public Cloud


Database Cloud Business Drivers

Reduce IT Costs

Reduce Complex

ity

Increase Quality

of Service

Increase Agility

Lower: •  CapEx

•  Servers •  Storage

• OpEx •  Maintenance •  Management

Reduce: •  Configurations •  Services

Standardize: •  OS •  DB Versions

Enhance: •  IT service time •  Availability •  Security

Enable: •  Online changes •  Rapid response •  Faster Time to market


Application

Platform

Customizations

Application

Customizations Customizations

Con

sum

er

Con

sum

er

Ser

vice

P

rovi

der

Ser

vice

Pro

vide

r

Customers Have a Choice of Clouds •  IaaS, PaaS or SaaS

IaaS Cloud

SaaS Cloud PaaS Cloud

IT Professional Developer Business End User

Different Users


Private Database Cloud Architectures Common building blocks are shared server and storage pools

Platform

ERP DW CRM

DB

Platform

DB

DB

Database Cloud

Database Consolidation Share server pool

Real Application Clusters

Platform

ERP DW CRM

Platform

DB

Database Cloud

Schema Consolidation

Share database instances Real Application Clusters

Infrastructure Cloud

Server Consolidation Deploy in dedicated VMs Server virtualization

Hypervisor

CRM DW ERP

OS

DB

OS

DB

OS

DB

Hypervisor


Infrastructure Cloud Server - Provision a Database in a VM

© 2011 Oracle Corporation

Hypervisor

CRM DW ERP

OS

DB

OS

DB

OS

DB

•  Reasons for adoption •  Simple to implement •  Excellent isolation •  Mixed workloads •  As-is consolidation •  Legacy support

•  Customer concerns •  Lower consolidation density •  Lower ROI •  Performance (latency) •  Managing sprawl


Database Cloud Database Consolidation – Provision Database


OS

ERP DW CRM

DB

OS

DB

DB

•  Reasons for adoption •  Consolidation density •  Good ROI •  Performance •  Supports any app

•  Customer concerns •  Requires OS standardization •  Database only


Private Database Cloud Database – Provision Schema


OS

ERP DW CRM

OS

DB

•  Reasons for adoption •  Most efficient •  Extremely fast provisioning •  Best ROI •  Performance •  Efficient memory use

•  Customer concerns •  App qualification required •  Requires OS and DB standardization •  Isolation


Private Database Cloud Deployment

•  Most efficient •  Highest consolidation density. Capability to consolidate large number of

applications. •  Efficient use of memory. Single large SGA opposed to several disparate SGAs •  Minimizes items to manage. Less OS, databases, and configurations to manage •  Reduces overall operational costs and overhead

•  Extremely fast provisioning •  Provisioning is simply a schema and tablespace creation

•  Performance •  Native performance

Schema Consolidation - Provision a Schema

OS

ERP DW CRM

OS

DB


Private Database Cloud Deployment •  Requires OS and DB standardization

•  Application certification required

•  Isolation Management

Schema Consolidation Considerations



Schema

Database

Servers Consolidation

Storage

ROI


Database Cloud


Private Database Cloud Greatest consolidation, maximum ROI


A View of the Private Database Cloud Cloud, An Aggregation of Cloud Pools

Dev/test Cloud Pool


Cloud Pool Schema Consolidation

11gR1 Cloud Pool Database Consolidation

Cloud Pool Infrastructure Cloud

11gR2 Cloud Pool Exadata - Database Consolidation

Cloud Pool Schema Consolidation


Cloud Architectural Assessment Pick the architecture that best suits your needs

Business Value Infrastructure Consolidation

Database Consolidation

Schema Consolidation

Implementation Easy Easy Difficult*

Application Suitability Some All Some

Isolation Highest High Limited Availability High Highest Highest Scalability Limited Excellent Excellent

Consolidation Density Low High Highest

ROI Low High Highest


* = Need to ensure application schemas can co-exist


Recommended Cloud Architectures Each architecture has unique capabilities that warrant its use for

specific workloads: Workload Type Optimal Cloud Architecture

Mission or Business Critical Deployment Database (Dedicated Pool)

Packaged Applications Infrastructure,Database or Schema

Data Warehouse Applications Database or Schema Standardized environment Database or Schema Internal Applications Database or Schema

Rapid provisioning (i.e. Test and Dev) Database or Infrastructure

Mixed workload consolidation Infrastructure As-Is consolidation Infrastructure


PRIVATE DATABASE CLOUD PLANNING


Planning

Rationalize/Consolidate

Discovery

Architecture Selection

Exception Handling

Application Migration

Selling the Plan

•  Before designing and implementing a Cloud, it is critical to carefully plan for the deployment.

•  Many of the Cloud benefits are delivered from rationalizing the existing environment and standardizing the deployment model.

•  A thorough and complete planning phase will ensure that a customer’s Cloud environment is optimal and provides the most benefit.

Cloud Planning Process


Rationalize Infrastructure •  IT rationalization determines the best use of IT services to reduce

non-productive redundancy in enterprise IT solutions

•  By standardizing on a set of building blocks, IT departments can easily deploy pre-defined configurations and scale-out using modular components.

•  Standardization results in a more homogeneous environment that is easier to manage, lower cost, less complex, and more agile.


Rationalize Infrastructure

•  Can the customer reduce the number of OS and DB versions? –  Standardizing OS & DB versions will result in improved ROI –  Customers should look for opportunities to do this

•  Can the customer standardize its hardware infrastructure? –  Reduce server and storage configurations –  Consider pre-integrated hardware platforms (Exadata)

•  Can the customer standardize its workloads to run against a single database?


Rationalize Infrastructure How will the customer rationalize the Cloud infrastructure?

•  Can the customer reduce the number of OS and DB versions? –  Standardizing OS & DB versions will result in improved ROI –  Customers should look for opportunities to do this

•  Can the customer standardize its hardware infrastructure? –  Reduce server and storage configurations –  Consider pre-integrated hardware platforms (Exadata)

•  Can the customer standardize its workloads to run against a single database?


Customer Case Study Example of services for large commercial bank

Service Levels Silver OLTP Gold OLTP Pla2num OLTP Pla2num OLAP Pla2num OLTP+OLAP

High Availability VM High Availability Dual Node Cluster 2N+1 Clustering 2N+1 Clustering 2N+1 Clustering Support Hours Office Hours Only Extended Office Hours 24 x 7 24 x 7 24 x 7

Disaster Recovery Point Objec2ve Zero Data Loss Zero Data Loss Zero Data Loss Zero Data Loss Zero Data Loss

Disaster Recovery Time Objec2ve 2 Business Days < 4 Hours < 4 Hours < 4 Hours < 4 Hours

Performance Not Defined Defined Minimum Dedicated Benchmark

Environment Dedicated Benchmark

Environment Dedicated Benchmark

Environment

Point-‐in-‐Time Recovery

1 Weekly + Daily Incremental Backup

1 Weekly + Daily incremental + REDO Logs Historical Data Management Historical Data Management Historical Data Management

Typical Applica2ons Departmental ApplicaQons Line of Business ApplicaQons Enterprise TransacQon

Processing ApplicaQons Enterprise Datawarehouse Near-‐Real Time AnalyQcs

Database Cloud (ODA)

Infrastructure Cloud (OVM)

Database Cloud

(on Exadata)


Private Database Cloud Deployment • Tenant Isolation

•  Resource •  Operational •  Security •  Fault

•  Bottom line : Contain “Noisy” neighbor

DB Cloud changes how you think about deployment


Private Database Cloud Deployment DB Cloud changes how you think about deployment •  Resource Management

–  Enable Instance Caging with default resource plan

– Enable Resource Profile limits

– Enable Oracle QoS Management • Trades-off resources just-in-time to maintain SLAs • Ensure business critical applications get serviced and meet response

time SLAs – Quarantine application by shutting down service or move workload


Database Consolidation •  Instance Caging: Partitioning Approach

Provides maximum isolation

•  For performance-critical databases

•  If one database instance is idle, its CPU allocation is unused

•  Set CPU_COUNT minimally to 2 0

4

8

12

16

20

24

28

32

Instance A: 4 CPUs

Instance B: 4 CPUs

Instance C: 4 CPUs

Instance D: 4 CPUs

OS 16

16 CPUs

DB

D

DB

C

DB

B

DB

A


Database Consolidation •  Instance Caging: Over-Provisioning Approach

•  Best used for non-critical databases that are typically well-behaved

•  Best approach if the goal is fully utilized CPUs

•  CPU contention typically not enough contention to destabilize OS or DB instances

•  If assumptions listed are met. •  If the load is significant and of

longer duration, system stability can get impacted.

0

4

8

12

16

20

24

28

32

Instance A: 4 CPUs

Instance B: 4 CPUs

Instance C: 6 CPUs

Instance D: 8 CPUs

OS 16

22 CPUs

DB

A D

BB

D

BC

D

BD


Private Database Cloud Deployment •  Patch and Upgrade

– Define a Patching and planned outage strategy –  Leverage Rolling Upgrades

• Minimize downtime using out of place patching • Leverage 11.2 Standby Apply First feature

– Emergency patch scenarios for specific application • Clone new ORACLE_HOME • Unplug/plug schema using TTS into new database but same diskgroup • Patch the new database and new ORACLE_HOME



Private Database Cloud Deployment • Recovery strategies

– How you backup affects your recoverability – Recovery Granularity Objective (RGO) becomes very important – Recover the application using least impacting method

• Flashback technologies (Flashback transaction, table, query) • TTS/PIT recovery or Datapump restore • Flashback DB



Private Database Cloud Deployment •  Security Management

–  Only Cloud DBA should have SYSDBA, SYSOPER and SYSASM privileges

–  Tenant DBAs should only have schema level access –  Use database roles and privileges to further limit data access –  Secure each application/schema with an Oracle Database Vault Realm –  Deploy Multi-factor rules to enforce who, where, when, and how data is

accessed –  Enable encryption on the tablespace



POLL: • How many customers have implemented Self-Service

Provisioning? –  If so, what tools or products are they using

• How are customers implementing IT Provisioning? –  What is the workflow process

• What is the turnaround time for typically database deployments?

Provisioning How will tenants request Cloud Services?


Planning

• What type of database provisioning – Self Service

• Requires a robust Self Service Catalog • Need UI for provisioning • Provisioning Workflow

–  IT Based • Very Manual • Need a method for queuing and reconcillation

Database Cloud Considerations


Metering and Chargeback Customer Consideration and Questions

POLL •  How many customers have or will implement chargeback

–  What chargeback tools are used, are they home grown or off-the-shelf?

–  How are customers measuring resource consumption?


Planning

•  Chargeback –  Provides cost relief –  Chargeback is a good mechanism to prevent database sprawl –  Many customers have chosen not to implement any chargeback

•  Show-back –  Don’t actually do chargeback, but do “show-back “ –  Makes tenants and consumers cost conscious and consumption aware –  Provides accounting of usage patterns –  Can easily switch to chargeback model if needed.

Metering-Chargeback Considerations


Metering and Chargeback What are your Chargeback models?

•  Typical Fixed Costs •  Tenancy (i.e. Monthly charge, configuration) •  Resource allocations (storage, CPU) •  Deployment options - Data Guard, GoldenGate, etc. •  Service levels

–  Charge for addiQonal service level support or higher availability

•  Typical Variable Costs •  Resource utilization

–  CPU Used - peak, average, time of day (common) –  Network, IOPS (rarer), Storage


Metering and Chargeback Do you charge for operational changes? •  Service charge for operational changes

– Prevents excessive changes in the environment – Define quantity and type of pre-paid operational requests.

• What is considered an additional request (i.e. first 3 change requests could be built-in to the deployment)?

– Additional changes in a calendar year are subject to cost/change •  Init.ora change • Create test/dev environment • Additional physical backup • Additional Patching


DB Cloud Planning Application Migration Readiness •  Applications may be in various states of technical readiness for a cloud

environment, based on application characteristics and requirements –  Name-space conflicts (relevant for schema consolidation) –  Character set requirements (relevant for schema consolidation) –  I/O rate requirements

•  Applications may have business constraints on their ability to be migrated to the cloud

–  Service level agreements –  Security –  Compliant restrictions – PCI-DSS, HIPPA, etc. datasets cannot be co-

mingled


DB Cloud Planning Application Migration Readiness •  Special requirements for a given application may make it difficult to migrate

•  Decide whether the cloud will be used for new deployments only, or existing deployments as well

•  Determine when applications will be migrated –  During an existing maintenance window? –  As part of a stand alone event for the application to be migrated?

•  Plan a migration process that will cause minimal disruption •  Choose applications that will provide the biggest benefit •  Choose “low hanging fruit” first; Go for quick wins •  Ensure that early migrations are successful!


Application Selection Customer Example

Con

stra

int t

o M

igra

te

Technical readiness for the Platform

No constraints

Many constraints

Not Ready Very Ready

... 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

19 20 21 22 23 24 25

....

....

....

....

..

....

....

...

...

..

...

...

...

... ... ... ... .

...)

..

...

...

... ...

26 27 28 29 30 31 32

...

...

...

....

... ...

...

33 34 35 36

....

...

....

... 37 ....

1

2 3

5

6

7

8 9

10 11

12

13

14

15 16

17

18

19 20

21

22

23

24 25

26

27

28

29 30 31

32 33

34

35

36

37

4 Workload Legend

Immediate Platform candidates

Longer term Platform prospects

Unlikely to be migrated

OLTP OLQP DW /BI Hybrid


0 4 8

12 16 20 24 28 32

Instance A: 4 CPUs

Instance B: 4 CPUs

Instance C: 4 CPUs

Instance D: 4 CPUs

Best Practices Consolidate & Share as much as possible

•  Dedicate resources to pools •  Share as much as possible

within a pool –  Dedicate when necessary to

meet SLAs –  Some resources should not be

shared •  Partitioning vs. Over-

subscription models •  Focus on both physical and

logical resources

Physical resources Servers

CPU, Memory Storage

Capacity, IOPS Network

Logical resources OS images, Homes,

Instances, Schemas, Configurations

0 4 8

12 16 20 24 28 32

Instance A: 4 CPUs

Instance B: 4 CPUs

Instance C: 6 CPUs

Instance D: 8 CPUs

OS 16

16 CPUs

DB

A D

BB

DB

C D

BD


Best Practices Implement Dynamic DB Services

•  Dynamic Database Services enable Cloud functionality

–  Virtualize service location –  Availability –  Agility –  Resource management –  Performance

•  Required to get most value from deployment

Load Balancing Load Balance Advisory Connection Load Balancing Runtime Load Balancing

Agility SCAN

Availability Fast Application Notification Fast Connection Failover Transparent Application Failover

Performance Data affinity Temporal affinity


How are Customers Deploying Private Database Cloud

–  Some call it by a different name - OaaS, DBaaS, Private Oracle Cloud –  Most use modularized building blocks (standard server type, storage,

network) –  Typically use fixed number of Cloud Pool nodes with Data Guard for DR –  Schema Consolidation very common consolidation model for in-house

applications

•  Typically configurations •  Typically 20-30 consolidated schemas in Schema Consolidation Model and

10-20 databases in Database Consolidation Model • Use Database Vault and/or tablespace encryption (ASO) andDatabase

Resource Manager


ENGINEERED SOLUTIONS


Private Database Cloud

•  Build-your-own Database Cloud – Requires customers to purchase, validate and configure all

components – Must ensure all components are certified with each other – Requires installing and testing of configuration

•  Exadata is a pre-built environment for Database Clouds – Pre-tested, pre-configured, pre-installed – All components are ensured to work together – Reduces overall time-to-market

Build vs Buy


The Evolution of the DBA

Kind of DBA Timeline CLI DBA Early 90’s DBAs GUI DBA Late 90’s and Dot Com Google DBA Dot Com and 2000’s iDBA Dot Com, IOUG iDBA Master Curriculum RAC DBAs 2000+ a[er 9.2 (but major spike with 10.2) DMA 2010+ Database Machine Administrator vDBA / vRAC DBA 2010+ Evolving role of a DBA in the virtual world

Cloud DBA 2011+


•  All Engineered Systems are the same •  Delivered tested and ready-to-run •  Highly optimized •  No unique configuration issues

• Runs existing OLTP and DW applications – No special certification required

•  Features optimized for mixed workloads –  IORM, DBRM

Oracle Engineered SoluQons


Why Exadata

XTreme Performance Up to 1.5 Million IOPs Infiniband – 40gigE

Instance Caging

IORM DBRM

Flash Cache

Storage Index

EHCC

DBFS


Oracle Database Appliance (ODA) •  4 TB of Usable Space Triple Mirrored •  All of RAC Best Practices in a box •  4 SSD for Redo Logs and performance

•  Pre-configured - ready to use out of the box •  Provision in hours not weeks

•  Ideal for SMB

•  Leverage ZFS to increase storage requirements beyond 4TB

•  Leverage ZFS with HCC Support


Business Drivers •  Reduce number of databases

•  Reduce OpEx – Cost to managed services provider for tape backups –  Less number of personnel to manage the Exa Stack

•  Reduce CapEx – Reduce storage requirements with HCC


Private Cloud Database Consolidation • Oracle enables all levels of consolidation

–  Infrastructure, Database, Schema

•  The higher the consolidation density –  The greater the return on investment

• Oracle Exadata Database Machine –  Ideal Private Cloud consolidation platform –  Fastest time-to-market

• Customers already saving with consolidation



Backup Architecture D2D Forever Incrementals

Exadata 1/2 Rack Production

ZFSSA Production

Exadata 1/4 Rack Development

IB2 Leaf Switch-B

ZFSSA DR

Non-EXA Development

Non-EXA Production

Infiniband GigE

IB1 Leaf Switch-A

IB2 Leaf Switch-B IB1 Leaf Switch-A

Net0 for Mgt and Data


Tiered Storage Model – Customer Case Study •  Leverage high transactional data on

DATA disk group as Tier 1 storage

•  Move data that is older than 3 months from Tier 1 to Tier 2

•  Move data that is older than 3 years from Tier 2 to Tier 3

•  Free up 11+ TB of storage from RECO disk group

Tier1 DATA

Tier2 RECO

Tier3 ZFSSA


Information Life Cycle Management Save more space as you go to the ZFSSA

Tier1 DATA

Tier2 RECO

Tier3 ZFSSA

•  Leverage Warehouse Compression for Tier 1 storage

•  Leverage Partitioning strategy to move data from different tiers of storage

•  Leverage Deeper HCC (Archive High) as we move data from Tier 1 to Tier 2

•  Make Datafiles on Tier 2 storage to be READ-ONLY so that we can skip RMAN backups (backup once and forget about it)

•  After three years convert data to external tables or move the datafiles to the ZFS


Benefits of ZFS Appliance •  With Exadata, we can only perform backups over network •  Perform disk to disk backups over extremely low latency 40 GigE

Infiniband •  Leverage Oracle’s Direct NFS •  Provides deep de-duplication and Exadata Hybrid Columnar

Compression (EHCC) •  Provides cloning capabilities •  Perform backups and restores of 4+ TB Per hour


Summary - Roadmap to Database Cloud

Standardize on Oracle

Oracle DB on Exadata

Oracle DB Service Catalog

Oracle DB-as-a-Service

Heterogeneous DB Environments


Summary •  Private Database Clouds consolidate servers, storage, operating systems,

databases, and workloads –  Many customers are successfully deploying Private Database Clouds today –  They are benefiting from high quality of service, low cost, reduced complexity and

increased agility

•  Oracle EM 12c provides customers with end to end Cloud Management –  Self-service paradigm for database deployment and management –  On-demand scalability of underlying platform –  Metering and chargeback for IT accountability –  Extreme “agility” for developers, with “enterprise” control for IT


The Perfect Marriage: Oracle Exadata with Sun ZFS Storage Appliance Session ID: UGF4410 Sunday 30-SEP-2012 9:00AM Moscone West - 2018

Expert Panel: Exadata Data Protection Best

Practices Session ID: CON8435

10/1/12 (Monday) 12:15 PM Moscone South - 252


Questions ?


Content •  Oracle Cloud Site : •  http://www.oracle.com/technetwork/database/focus-areas/database-cloud/index.html

•  Private Database Cloud White Papers –  Database Consolidation onto Private Clouds –  Private Database Cloud on Oracle Database Appliance –  Best Practices for Database Consolidation in Private Clouds –  Best Practices for Database Consolidation on Exadata Database Machine –  Multiple Public Networks in Private Database Clouds Network –  Isolation in Private Database Clouds

•  DbaaS Cookbook http://www.oracle.com/technetwork/oem/cloud-mgmt/em12c-dbaas-cookbook-1432364.pdf

Private Database Cloud Database Consolidation …dbaexpert.com/PrivateDatabaseCloud.pdf · Private...

Documents

Transcript of Private Database Cloud Database Consolidation …dbaexpert.com/PrivateDatabaseCloud.pdf · Private...