Organizations have a choice when it comes to database platform. On the one hand, the dev platforms that cloud vendors provide are fast and loaded with tools, you don’t manage the infrastructure and only pay for what you use. On the other hand, deploying on premises can mean better control over performance, security, user experience and compliance. This session discusses making those choices – not for one app, but at enterprise scale. What should you consider? Which factors say “cloud”? Which factors say “on premises”? And can you get a consumption-based experience either way?

1. Finding your right mix
Using HPE Right Mix Advisor for EDB
Workloads

2. Core engine
Design the right mix for your enterprise
Auto-discovery
Discover
Plan
Assess
HPE Right Mix Advisor Process
Roadmap

3. Discover: Overview
Enabling an automated, complete picture to build the application portfolio
3
Automated-agentless
discovery, tools like iQCloud
Discover and map all services,
applications and infrastructure
across traditional datacenter,
hybrid and cloud – within days
Auto-grouping of applications
Extensible and scalable
Secure end-to-end encryption
Holistic view of all your
applications, their inter-service
communications and
dependencies
MDR stored data to drive future
analysis and further insights for
current and future migrations
Discover
Assess
Master Data Repository
(MDR)
CORE CUSTOMER DELIVERABLE

4. Discover: Detailed View
A foundation of high quality and up-to-date data
Application related data, including dependency
mapping, is used to make decisions on
where/what/how the application should be moved
Drill into a specific application to understand the
business service, technology components and
infrastructure dependencies
App
Collecting everything known about your application portfolio

5. Domains and topics categorize data
Weighted questionnaire to create
application profile
Patterns have logic used in
assessments
Assessments are iterative and
incremental enriching discovery data
to reflect your situation
Assessment: Overview
High level roadmap method for discovered applications
Assess
Discover
CORE CUSTOMER DELIVERABLE
High Level Roadmap
Migration
approach
Migration
targets
High Level Migration Roadmap
is informed by data collected
throughout the assessment phase
– Business service
– Application service
– Technology management
– Technology operations
– Security and compliance
– Etc.
MDR

6. Assess: Detailed View
Data enrichment provides “suitability scoring” for each application
Profiles
Applications are filtered through
domain specific profiles
Data enrichment
MDR is enriched with new data
throughout the engagement
Application suitability
Targets destinations and migration
approaches based on data
High Level Roadmap
80-100
60-80
<60
Readily
suitable
Mostly
suitable
Potentially
suitable
Unsuitable
Higher suitability
More complex/
difficult to migrate
Rehost
Re-platform
Refactor
Retain
Replace
Retire
Public Cloud
Private Cloud
Co-location
Data center
A data-driven, empirical, and repeatable process informing application migration planning
Migration
approach
Migration
targets
Iterative MDR

7. High Level Migration Roadmap
Profiles
(Domain specific
profiles)
Logical Groups
(Group of objects
such as servers,
workloads, etc)
Assessments
Data filtered against profiles
Performed on Logical Groups
Can combine in a wide
variety of ways
High Level
Roadmap
Data and
Profiles
Evaluation
groups
High Level Migration Roadmap
Method for all discovered applications
Quick and efficient
Analysis can be repeatedly run as your
environment or assumptions change
Core Customer Deliverable
How is it done?
High
Medium
Low
0%
100%
Suitability
Compliance
Feasibility

8. Plan
MDR High Level
Roadmap
CORE CUSTOMER DELIVERABLE
Wave 1 migration targets,
approaches, and first movers
Data is factored based on inherent complexity
Potential migration approach is aligned to
migration targets to determine Wave 1
candidates
First mover applications are
selected based on ease and
impact of actionable and
manageable application migration,
based on business rules
Discover
Assess
Plan: Overview
Determining Wave 1 candidates

9. HPE Migration Services for Postgres EDB
– Duration depending on scope
– Conduct Workload Preparation, Migration, post
migration activities as per the assessment
recommendations and customers’ needs
– Test and verify the workload after the migration
– Emphasis on Business Continuity and Project
Governance during the migration
– Knowledge Transfer before operation handover
Outcome
– Complete Detailed Design Implementation
Planning documentation
9
One Program:
– Common Architecture
Standards
– Standard Migration
Strategy
– Common test Strategy
– Program wide plan
– Pre-agreed Budget
Speed
One Migration
Factory
a00068621enw For HPE and Channel Partner internal use only

10. HPE GreenLake Solutions
Each solution can be tailored according to…
10
SERVICES
Education
Services
Consumption
Services
Strategy
& Design
Installation
& Startup
Solution
Support
Monitoring
&
Operations
Servers, storage,
networking,
devices
Applications and
toolsets
SOFTWARE
SERVICES
HARDWARE
HPE
GREENLAKE
SERVICES
Education
Services
Consumption
Services
Strategy
& Design
Installation
& Startup Solution
Support
Monitoring
&
Operations
Servers, storage,
networking,
devices
Applications and
toolsets
SOFTWARE
SERVICES
HARDWARE
HPE
GREENLAKE
Scope…tailoring the solution components to
meet a customer’s specific requirements
SERVICES
Education
Services
Consumption
Services
Strategy
& Design
Installation
& Startup
Solution
Support
Monitoring &
Operations
Servers, storage,
networking,
devices
Applications and
toolsets
SOFTWARE
SERVICES
HARDWARE
HPE
GREENLAKE
SERVICES
Education
Services
Consumption
Services
Strategy
& Design
Installation
& Startup
Solution
Support
Monitoring &
Operations
Servers, storage,
networking,
devices
Applications and
toolsets
SOFTWARE
SERVICES
HARDWARE
HPE
GREEN
LAKE
Scale…appropriate sizing of the solution
HPE Internal Use Only

11. Oracle to EDB Engineered Solution
Oracle AWR Thresholds Large Medium Small

12. Greenlake Minimum Viable Solution
12
Elements
• 2 x DL380 G10, each with
• 2 x Intel 6126 12 core
• 16 x 32 G DIMMs (memory)
• 4 x 600G SAS drives
• 1 x 2 port 10GbE network card
• 2 x 16 Gb Dual port Fibre Channel HBA
• 1 x 3Par
• 240 x 1.2 TB SAS SFF drives (220 T Usable Raid 14+2)
• 16 x SFF enclosures
• 2 x 5950 ToR Switches
• 1 x 5900 iLO Switch
• Rapid Assessment & Data Platform Solution modeling
Ndb Total Number of Production Databases 8
` Nsvr Total Number of Servers [P or V] 2
Ainst Average Number of Oracle Instances 2
Napp Total Number of Custom Applications 16
%Mprod % of Production Servers 100
%Grepl % of Databases Data Guard replicated to Multiple Locations 1
%Clust % of RAC Instances 100
%Lrepl % of Databases replicated in Local Site 1
Asize Average Database Size [data, index, log] 500
Aobjs Average number of Database Objects 250
Aobjc Average number of Complex Database Objects [Procs and Packages] 200
Ausers Average number of Client Connections [ODBC, JDBC, OracleNet] 500
LOCs Average number of SQL statements in custom applications 100
%Esql SQL Transformational Complexity [0 - 100%] 50
Enter Values 4 Aver
25% growth yoy for 5 years
start end Y2 end Y3 end Y4 end Y5
Servers 2 4 5 7 9
DBs 8 12 16 24 28
Storage 220 344 430 538 673
Services
• Infrastructure & EDB
Design
• Target Infrastructure
Set-up
• EDB Install & Config
• Training & Support
Optional
• Migration Advisory
• POC

13. HPE GreenLake Database with EDB Postgres
Get better TCO with industry-leading open source database platform
13
Per Cores Used by Database
HPE GreenLake Database with EDB Postgres
Design
Implement
Operate
Optimized
HPE Servers
and Storage
EDB Postgres Software
Full-feature open source performance
HPE Expertise
Fast time-to-value: migrate, implement, train
HPE Reference architecture
Dev and production – ready
Operated for you
Free your teams for more valuable contribution

14. Thank You