One of the most important things during the start of a cloud migration project is to know your capacity needs of your existing environment. The reason for this fact is that you have a near to unlimited flexibility of sizing your environment perfect for your demands. By side of provisioning your perfect dimensioned system in the cloud, you implicitly save pure money by spending any costs for unneeded capacity. During the presentation, I would like to show the needed metrics and the method to create a proper report for your needed capacity.

1. BASEL BERN BRUGG DÜSSELDORF FRANKFURT A.M. FREIBURG I.BR. GENF
HAMBURG KOPENHAGEN LAUSANNE MÜNCHEN STUTTGART WIEN ZÜRICH
Migrating to the Oracle Cloud: Capacity
Management
Martin Berger
Senior Consultant
martinberger_ch
www. martinberger.com
KESTENHOLZ

2. Agenda
1. Steps
2. Learn
3. Evaluate
4. Move and Run
5. Gather
6. Compare and Scale
7. Conclusion
Migrating to Cloud: Capacity Management

3. About me
Migrating to Cloud: Capacity Management
Martin Berger – 4703 Kestenholz / Jurasüdfuss / Switzerland / non-EU
Senior Consultant – @Trivadis AG Bern
2 Junior DBAs, Firefighter / Firefighter Trainer
Trainer for Trivadis Architecture and Cloud Trainings
martinberger_ch
www. martinberger.com

4. COPENHAGEN
MUNICH
LAUSANNE
BERN
ZURICH
BRUGG
GENEVA
HAMBURG
DÜSSELDORF
FRANKFURT
STUTTGART
FREIBURG
BASEL
VIENNA
With over 600 specialists and IT experts in your region.
14 Trivadis branches and more than
600 employees
200 Service Level Agreements
Over 4,000 training participants
Research and development budget:
CHF 5.0 million
Financially self-supporting and
sustainably profitable
Experience from more than 1,900
projects per year at over 800
customers
Migrating to Cloud: Capacity Management

5. Steps
Migrating to Cloud: Capacity Management

6. Steps
Migrating to Cloud: Capacity Management
1. Learn your system know
2. Evaluate a cloud service
3. Move your data to the cloud and run your workload
4. Gather cloud stats
5. Compare and Scale
6. Conclusions

7. Learn
Migrating to Cloud: Capacity Management

8. Important metrics for capacity management
Migrating to Cloud: Capacity Management
There are three metrics which are the most important regarding measuring the
needs of your database environment
CPU
– Average / Maximum values
Memory
IO
– IOPS / Throughput values

9. Oracle Database Metrics
Migrating to Cloud: Capacity Management
Categorization of wait situations in the Oracle Database
Ability the track down the workload profile
– CPU bounded
– IO bounded
Data is centrally stored in “Automatic Workload Repository” or Statspack schema

10. Migrating to Cloud: Capacity Management
TVD-CapManTM
Repository based collection of workload metrics
– Server metrics (CPU, RAM, ...)
– Database metrics (AWR, Statspack, ....)
Ability to centrally analyze and compare workload profiles
Gathering the data using SSH connection (no agents needed)

11. Migrating to Cloud: Capacity Management
TVD-CapManTM – Big Picture

12. Migrating to Cloud: Capacity Management
TVD-CapManTM – CPU consumption

13. Migrating to Cloud: Capacity Management
TVD-CapManTM – Memory consumption

14. Migrating to Cloud: Capacity Management
TVD-CapManTM – IOPS

15. Enterprise Manager Database Performance
Migrating to Cloud: Capacity Management

16. Dell Foglight
Migrating to Cloud: Capacity Management

17. Evaluate
Migrating to Cloud: Capacity Management

18. Oracle Compute Block Storage
Oracle Storage
Cloud
Oracle VM – Oracle Linux
Oracle REST
Data Services
RDBMS
Cloud Tooling
(EM Express,...)
Compute
Metrics
Database
Metrics
EM
Compute Infrastructure
/u03 /u02 /u01
Archives
My Services
Store
cloud.oracle.com
JaaS Compute Service
DBaaS
On premises
Local DB
Dev Tools
Source: oracle.com
Migrating to Cloud: Capacity Management
ODCS Managed - Architecture

19. Shapes – General Purpose
1 OCPU = Intel(R) Xeon(R) CPU
Shape Cores Threads Memory(GB) Local disk
OC3 1 2 7.5 60 GB
OC4 2 4 15 60 GB
OC5 4 8 30 60 GB
OC6 8 16 60 60 GB
OC7 16 32 120 60 GB
Migrating to Cloud: Capacity Management

20. Non-Metered vs. Metered Services
Migrating to Cloud: Capacity Management
Non-Metered Service
■ Monthly subscription
■ Used OCPUs is the cost KPI
■ Caution with breathing environments
 Good for permanent solutions
Metered Service
■ Usage based subscription
■ Billed in hourly chunks
■ Need to build up a uptime utilization
 Perfect for short-time needs
 Looking for break even point

21. Metered Services – Break even point
Migrating to Cloud: Capacity Management
0
500
1,000
1,500
2,000
2,500
3,000
3,500
4,000
24 120 240 360 480 600 720
PriceperOCPU
Operating hours per month
DBaaS (1OCPU, Enterprise Edition)
Metered NON-Metered
Key points
■ Break even point at
595 hours (~24,8 days)
■ 22 working days * 8 h =
176 hours
■ Uptime should be utilized

22. Scale up/down
Options:
– Change Compute Shape
– Create new storage volume
– Extend Data Storage Volume
– Extend Backup Storage Volume
Restart of all regarding is needed !
Migrating to Cloud: Capacity Management

23. Monitoring - Oracle DBaaS Monitor (1)
Analysis, start, stop, clone, plug-in, unplug
Session monitoring, troubleshooting
Login with dbaas_monitor / *SYS password*
Migrating to Cloud: Capacity Management

24. Monitoring - Oracle DBaaS Monitor (2)
Migrating to Cloud: Capacity Management

25. Oracle Bare Metal Service
Migrating to Cloud: Capacity Management
HighHigh
Performance
Compute
Performance
Storage

26. Move and Run
Migrating to Cloud: Capacity Management

27. Transfer your Data into the Oracle Cloud
Migrating to Cloud: Capacity Management
There are several ways to move the data
SQL*Loader
Oracle Data Pump
Transportable Tablespaces
Pluggable Databases (PDBs)
Oracle Public Cloud Data Transfer Services (ZFS Appliance)

28. Run your Workload
Migrating to Cloud: Capacity Management
Oracle Real Application Testing with Database Replay or SQL Performance Analyzer
(The High Performance Shape contains the license for RAT)
Own scripts

29. Gather
Migrating to Cloud: Capacity Management

30. Gather Cloud System Statistics
Migrating to Cloud: Capacity Management
Get AWR reports / Statspack
Integrate the Cloud Instance in your local Enterprise Manager 12/13c
Integrate the Cloud Instance in TVD-Capman
Monitor network latency

31. Compare and Scale
Migrating to Cloud: Capacity Management

32. Compare the Gathered Data
Migrating to Cloud: Capacity Management
But do not only compare data
Let application users work with it to get a feeling

33. Scale your Cloud Instance
Migrating to Cloud: Capacity Management
And what ist if the performance of the cloud instance is not what you need?
1. Scale and Test again
2. Scale and Test again
3. Scale and Test again

34. Conclusion
Migrating to Cloud: Capacity Management

35. “Lift and Shift” – Projects
Migrating to Cloud: Capacity Management
Moving some or all of your database environments to the cloud
Adopting the existing environments
Workflow:
1. Measure the needs of your on-premises environments
2. Adopt this needs to the given environments in the cloud
3. Choose the shape which fits your needs its best
4. Migration of the environments
5. Constantly monitor of resize potentials

36. Measure the needs of your on-premises environments
Migrating to Cloud: Capacity Management
Setting up a workload gathering tool e.g. TVD-CapManTM
Generation of utilization reports from the chosen environments
– Average values for trend analysis
– Maximum values for analyzing high load phases
Summarize the needs for your environments
– CPU
– Memory
– IO

37. Adopt this needs to the given environments in the cloud
Migrating to Cloud: Capacity Management
Measured CPU utilization hardly is depends on the CPU model
– Processor Frequency
– Cache
Comparison of the CPU model is needed
– Customized CPU compute capability (TVD CPU Benchmark)
– Standardized CPU Benchmark e.g. SPECint2006

38. Migration of the environments
Migrating to Cloud: Capacity Management
Performing the migration the environments
Planning of possible reorganizations or changes for performance purpose
– Data reorganization e.g. Data Pump
– Changing LOBs to secure file
– Reviewing your index and constraint structures

39. Constantly monitor of resize potentials
Migrating to Cloud: Capacity Management
Include also your cloud environments in the workload gathering tool
Periodically analyze your environments regarding optimization
Define thresholds for up or down scaling
Include predictions regarding growth trends

40. Finally
Migrating to Cloud: Capacity Management
Gathering the metrics of your environments is the key to success
Deeply analyze the performance capabilities of the cloud products
Constantly gather and maintain your performance data
There is a high potential for cost optimization when performing periodic capacity
management routines in cloud environments
 Capacity management is getting more and more important!

41. Additional information...
Oracle Cloud landing page
https://cloud.oracle.com
Oracle DBaaS price calculator
https://shop.oracle.com/cloudstore/?product=database
Oracle Bare Metal Cloud Services
https://cloud.oracle.com/en_US/bare-metal
Trivadis Cloud Offering
http://www.trivadis.com/en/disaster-recovery-high-availability
Migrating to Cloud: Capacity Management

42. Migrating to Cloud: Capacity Management

43. Any questions...?
Martin Berger
Senior Consultant
Migrating to Cloud: Capacity Management