Enterprise Manager DBaaS

Enterprise Manager DBaaS:
Database, Schema, or
Terabytes of Data in Minutes
Adeesh Fulay
Consulting Product Manager

Matthew McKerley
Vice President of Development

Nilanjay Bhattacharjee
Assistant Vice President IT, HDFCBANK LTD

Description
Session: CON9530

Title: Oracle Enterprise Manager DBaaS: Database, Schema, or
Terabytes of Data in Minutes

Description: Database as a service (DBaaS) is the latest trend in
providing automated database services to a wide set of end users. In this
session, you will learn about the latest features in DBaaS, including
schema-based consolidation, thin provisioning of data, and other exciting
features.


Safe Harbor

The following is intended to outline our general product direction. It is
intended for information purposes only, and may not be incorporated into
any contract. It is not a commitment to deliver any material, code, or
functionality, and should not be relied upon in making purchasing
decisions. The development, release, and timing of any features or
functionality described for Oracle‟s products remains at the sole
discretion of Oracle.


Table of Contents

 What is DBaaS?

 Key Challenges

 Oracle’s Cloud Solution

– Database and Schema Consolidation

– Rapid Template based Provisioning

– Data Cloning (Storage Copy on Write and RMAN Backups)

 Customer Story – HDFC Bank


Total Cloud Control

Complete Cloud Integrated Cloud Business-Driven Application
Lifecycle Management Stack Management Management

Self-Service IT | Simple and Automated | Business Driven


Customers Have a Choice of Clouds

Exclusive Shared by multiple organizations

Private Cloud Hybrid Cloud Public Cloud

• CapEx & OpEx • Cloudbursting – overdraft • OpEx
• Lower total costs for peak loads • Fast & inexpensive to start
• Control & visibility • Dev/Test & production • Outsourced services
• Multiple apps sharing • B2B integration • Multiple tenants sharing
resources resources


Private Cloud: PaaS vs IaaS
Increasing Enterprise value with Private PaaS

Private PaaS
• Enforces standardization and consolidation
• Provides Security and Compliance
• Maximizes component re-use
• Minimizes hand coding
• Maximizes flexibility and control


Three  The problem of many and varied
Key  Manual, time consuming provisioning
Challenges
 Data, lots of data!


Key Challenge 1: The
problem of many and varied

Solution: Standardization
and Consolidation


Need for Standardization and Consolidation
High Complex and ever growing
cost of database estate
operation
High cost of
deployment

Poor Service
Utilization
Delivery
H/W, CPU,
Storage
Workload
multiple skills,
lots of disparate Poor service, “a mixture of versions, operating systems,
systems, long lead
poor automation hardware; rapidly falling
times
into legacy”


Consolidation at PaaS and IaaS Layers
Consolidate onto standard, shared
and elastically scalable PaaS App App App

• Standardized PaaS for all applications
reduces heterogeneity, cost and complexity
PaaS • Accelerated new application development
App App App
• Cost savings from less hardware, power and
data center space
vs.
App App App • Software stack heterogeneity, cost and
complexity persists
• No administration (O&M) cost savings
Consolidate onto shared IaaS • Cost savings from less hardware, power and
without standardization IaaS data center space


DBaaS Cloud Models
Infrastructure Cloud Database Cloud
Database Cloud
DW DB CRM ERP DW ERP CRM DW ERP CRM

DB

DB

DB

DB

DB

DB
OS OS OS

Hypervisor OS OS OS OS

Shared Server Shared Cluster Shared Database
Shared pool of hypervisors Shared pool of servers Shared database instances

Increasing Consolidation


Considerations for Choosing the Right Model

 Brownfield or Greenfield?
 Commodity Servers Vs Engineered Systems?
 Applications to be deployed, and their database footprint?
 Expected SLAs from business users?
 Isolation or Security requirements?
 Ease of management? Available skill set?
 Is self service needed? If yes, who is the user, and what do they expect from
this service?
Most Customers Settle On a Combination these Models


Comparison of DBaaS Cloud Models

Consolidation
Low High Highest
Density

Easy to Involved (based on
Maintenance Very complex (VM Sprawl) Easy
required resource isolation)

Low (Server and Storage High (Servers, storage, and Highest (Servers, Storage,
ROI Only) OS) OS, and DB)

Isolation Excellent Good Least

Implementation Difficult (standardize on DB
Easy Easy
& Onboarding and OS version)

Application Some (excessive in many Home grown; requires app
All
Suitability cases) validation


Examples of DBaaS Cloud Model Usage


Junior DBA Application DBA Application Developer
Build test environment to Provision database for a Provision one or more
verify a database patch complex packaged schemas for a
application e.g. eBiz homegrown custom
Application Developer application
Provision application Application Tester
middleware and Clone a production Sales Engineer
database on the same database for Provision schema with
VM performance testing data for a training app


Key Challenge 2: Manual and
admin based provisioning

Solution: Rapid provisioning
of Standardized Templates


Need for Rapid Template based Provisioning
Database-as-a-Service
Traditional App Deployment Deployment
(Admin driven) Specify and procure (End-user driven)
hardware DEPLOYMENT
PORTAL

Configure hardware Request database
deployment

Deploy hardware
Database
Adjust capacity as
OS and Storage demand changes Databases
Server Hardware Deploy operating system
and configure storage
Retire database
when not needed
Deploy database
User unaware of
underlying infra
Self-Service Provisioning


EM 12c: Most Comprehensive DBaaS Solution
 Self service paradigm for database deployment and
management
– Pre-packaged, pre-configured database configurations
– One-click provisioning and deployment of databases
– On-demand scalability of underlying platform
 Support for all three DBaaS deployment models
 Metering and chargeback/showback for IT
accountability
 Data cloning using Storage copy on write and RMAN
Backups
 Intelligent Auto-placement, Quota Management, Role
based access, and so on ..

Schema as a Service

• Ultimate consolidation of databases (shared
database deployment model)
• Each application user gets one or more database
schema(s)
• Service level guarantee through Database
Resource Manager
• Security isolation through Data Vault
• Integrated with Database 12c Pluggable Databases
• Multiple pluggable databases within a single container
database


Schema as a Service User: Portal
• Out-of-box console ; no additional
set up required
– Supports custom background
• Rich service catalog:
- Database instances
- Schemas
• Database portal functions
– List all databases and
schemas
– List requests, quota usage,
and notifications
– Resource Monitoring
– Backup/restore
• RESTful Web Service based APIs
and CLIs


Schema as a Service User: Features
 A „Schema‟ request provides
– 1 Database (Application) Service
– N schemas/users
– 1 master account that has grants over other schemas
– 1 tablespace

 Request for a „Schema‟ instance
– Choose service templates with/without seed data
– Rename and set passwords for schemas
– Upload custom SQL scripts for execution
– Pick duration

 Home page for management of provisioned instances


DBaaS Setup: Schema as a Service
Roles and Responsibilities

Cloud Administrator Self Service Administrator
Provision Servers, Storage,
Provision Databases
and Network

Manage Cloud Resources Setup Zones and Pools

Configure EM and Software
Create Profiles
Library

Setup Roles and Users Publish Service Templates to
Service Catalog

Manage Security and Policies
Set Quota, and Metering &
Chargeback


DBaaS Cloud Resource Model
4N RAC DB
PaaS Zone 11.2.0.3
Collection of various pools – MW & DB
Based on geography, cost center, … RAC
11.2.0.2

RAC SI
Database Pool 11.2.0.2 10.2.0.5
Defines a homogeneous collection of Databases SI
10.2.0.5
or Oracle Homes SI
10.2.0.5
Mandatory criteria
- platform, db version, availability (SI/RAC)
Optional criteria
- SLAs, security, product lifecycle, …
N = Node
Databases and Oracle Homes – Single instance SI = Single Instance
and clustered RAC = Real Application Clusters


Setup Service Catalog
Capture -> Publish to Catalog

Capture Database Provisioning Profiles Publish Service Template to Service Catalog
• Capture schema and data from existing • Schemas with or without data and objects
databases • Assign roles and privileges for master account
• Uses datapump for export/import • Register pre and post creation SQL
• Tablespace encryption for secure environments


Setup Service Catalog contd.
Workload Sizing and Placement

Resource Management

Intelligent Capacity Service Level
Placement Planning Guarantees

Placement Algorithm Workload Sizes • Resource Manager for
• Simple: By number of • Based on projected CPU allocation
services usage of CPU, Memory, • Fixed Datafile Size for
• Advanced: Based on and Storage storage allocation
projected workload • Define Small/ Medium/
characteristics Large workloads
• Attach to Service
Templates


Chargeback Reporting

Chargeback Administrator Self-Service Portal User Line of Business User
• Rollup based on LDAP • Charge Trend reports • Integrate with BI Publisher
hierarchy broken down by resource • Generate Reports in
• Summary and Trending • Selectable detail levels variety of formats
reports for Usage and
• Charge Plan • Excel, Word, HTML,
Charge
configuration PowerPoint, PDF
• Drilldowns
• Email or FTP reports


Chargeback Database Metrics
Database Instance Shared Database (Service)

Edition
Memory Usage
Option
Option
Edition
Configuration Storage Usage
Release
Release
RAC Node Count
Version
RAC Node Count

CPU Time
CPU Time Per Service
CPU Utilization (%)
CPU Utilization Per Service
CPU Utilization (SPECInt)
DB Time Per Service
Network IO
Usage Disk Read (Physical) Operations Per Service
Disk Read (Physical) Operations
Disk Write (Physical) Operations Per Service
Disk Write (Physical) Operations
SQL Executes Per Service
SQL Executes
User Transactions Per Service
28
User Transactions
Copyright © 2012, Oracle and/or its affiliates. All rights reserved.
Insert Information Protection Policy Classification from Slide 16

Key Challenge 3: Data, lots of
data!

Solution: Data Cloning using
Storage copy-on-write
technology and RMAN
backups


Data Cloning Overview

 Functional Testing of Applications
– Most functional tests require minimal data changes
– Testers frequently need to rollback data

 Most storage based solutions lack lifecycle management capabilities
– DBA Friendly. Clone „Databases‟ instead of „Storage Volumes‟
– Monitoring and configuration management of the cloned database
– Upstream Test Master creation workflows (integrated with Masking, Subsetting, etc)
– Monitor, implement quota and chargeback based on QoS


Data Cloning Options
Technology Comparison

Copy on Write RMAN Backup

• Oracle Database based
technology; Storage neutral
• Storage based technology
• Restore time proportional to
• Saves space and time
backup size
• Ideal for "use and throw“ i.e.
• Leverages existing
short lived databases
technology and infrastructure
• Storage Admin involved Data Cloning
• Completely managed by
DBAs

Database Instant Cloning Using Copy on Write
Production Test Master
Database Database
Masking &
Sub setting
NAME SSN SALARY
NAME SSN SALARY
AGUILAR 203-33-3234 40,000
MILLER 112-23-4567 40,000
BENSON 323-22-2943 60,000
SMITH 111-22-3333 60,000
010110011
101001010
000111010
Functional Copies – User
can create multiple
• Initial Support for Sun ZFS Storage and NetApp copies for functional
Storage testing without
consuming space
• More than just storage volume cloning
• Users can create snapshots and „timetravel‟ to an
earlier snapshot


DBaaS Setup: Database Instant Cloning

Enable Databases for cloning
and Network


Configure EM and Software Create Profiles using Storage
Library Snapshots

Service Catalog

Chargeback


Database Cloning Using RMAN Backups
1

RMAN Duplicate
1. Backup-Based Duplication
Connect With a Target Connection
Target Connect
Auxillary 2. Backup-Based Duplication
Without a Target Connection
3 3. Backup-Based Duplication
2
Without a Target Connection
Connect or a Recovery Catalog
Catalog
Connection


DBaaS Setup: RMAN Backups

Stage RMAN Backup Archives
and Network


Configure EM and Software Create Profiles using RMAN
Library Backups

Service Catalog

Chargeback


HDFC BANK DBaaS Journey into Oracle
Database Cloud with EM12c

Nilanjay Bhattacharjee
Assistant Vice President IT
Lead Database COE

About HDFC Bank
• Incorporated in August 1994
• India‟s second largest Private Bank with a nationwide network of
– Branches: 2,564
– ATMs: 10,000 (In 1,416 Indian towns and cities) & 20 million customers
– Debit Cards: 14.9 Million
– Credit Cards: 5.8 Million
• Industry: Retail & Corporate Banking
• Employees: 56,000
• Revenue: USD 5 Billion


Business Drivers
• Retail Assets Segment [Lending Business]
• 50% of HDFC Bank‟s Top Line
• Always under pressure to launch “New Schemes” to compete and
stay ahead in this segment
• IT must respond to this Business need because each new Scheme
means – changes to application and testing against Production data
[UAT database]
• Agility in launching new business initiatives

Life Before Database Cloud
• Average 3.5 days to provision UAT Database for Loan Management
Application
• Silo‟ed environment with Average 30% utilization
• Compliance requirement consume UAT testing resources.
• DBA activities mean $$ paid to SI for provisioning databases manually
• Overhead in managing configuration drift between production and test
environments.
• Rollout impact/delay on new business initiatives

Database Consolidation – Application Classification
• Classify application based on system availability requirement/criticality

System classification Application Classification

Tier 1 Top 15 in terms of systemic risk Customer facing mission critical systems

Tier 2 Top end & middle tier High visibility & enterprise wide usage

Tier 3 Bottom end of middle tier Smaller user base but critical business function
Surround Systems - Satellite system build around core
Tier 4 Low tier system

Database Consolidation Planning
• Identify candidate application for Cloud
• Further Group them based on availability requirement and sub
classification based on OS/DB

Cloud Zone Zone based on criticality Sub category based on version
Highly critical 11g zone
Exadata Zone
UAT system 11g zone (For pilot)
10 g zone
Highly Critical
AIX zone 11g zone
UAT system 11g zone (For pilot)
11g zone
Windows Medium critical
10g zone

Database Cloud Solution Architecture

Cloud Administration Setup
• Zones
 Exadata Zone
 AIX zone
• Role for each application on Exadata and AIX zone
• Quota is set based on existing infra available
 7 Databases on LOS Application
 5 Databases on LMS Application
 5 Databases on Web collection Application
• Universal charge plan
• Service Templates
 Exadata -Three templates with data
 Exadata -Three templates with only structure
 AIX template for Small, Medium, Large database only structure

Provision Databases using RMAN Backups
• Beta Customer for RMAN restoration integration feature with DBaaS
• Level 0 RMAN Backups of Production Databases from
Standby[Bunker Copies]
• Service Templates created for each of Level 0 Backups
• Process to Provision Databases through RMAN is same as Empty
Databases

Life after Database Cloud Go-live – Time to Provision
Sno List of activity during New DB infra requirement

If Database infra not available time taken

Post DBaaS implentation using EM 12c
1 IT team fill tech questionnaire and submit for discussion 0.5 0.5 0

If Database infra available time taken
2 Discussion and TCO in 3 days from discussion 3 0 0
3 Floating of funding proposal based on TCO 10 0 0
4 Approved funding raising PO for infra procurement 3 0 0
5 Delivery of server and infra structure 28 0 0
6 Asset code allocation and movement to DC 3 0 0
7 OS and other infra configuration 3 0 0
8 Identify server (compute+ memory ) 0 0.5 0
9 Storage allocation and publishing for new DB instance 3 0 0
10 Database installation and database creation 1 1 0
11 Database restoration 1 1 3
12 OEM or monitoring configuration 0.5 0.5 0
Total time taken in days /hour Day 56 Day 3.5 Hour 3

Summary
 DBaaS supports three different DBaaS models
– Database in a dedicated VM
– Databases in a shared cluster or installation, and
– Schemas in a shared database
 Special focus on data cloning
– Storage copy-on-write technology, and
– RMAN backups
 Out of box portal to deliver all types of services


DBaaS is the Sweet Spot for Enterprise Clouds
Benefits All Stakeholders


Graphic Section Divider


Enterprise Manager DBaaS

More Related Content

What's hot

Similar to Enterprise Manager DBaaS

Recently uploaded

Enterprise Manager DBaaS

Editor's Notes