Delphix Patching Epiphany

The Patching Epiphany
The Case of the Limitless DBA
Kellyn Pot’Vin-Gorman | Technical Intelligence Manager

2© 2016 Delphix Corporation
Who am I?

Epiphany
e·piph·a·ny
əˈpifənē/
noun
a (1) : a usually sudden manifestation or perception of the essential nature
or meaning of something (2) : an intuitive grasp of reality through
something (as an event) usually simple and striking (3) : an illuminating
discovery, realization, or disclosure
b : a revealing scene or moment

I sat through his sessions.
I sat next to my husband the last couple years while he implemented
virtualization.
I virtualized environments with Oracle’s products in a number of
customer implementations as an expert in the area.
If I was this close to it and missed it, so possibly were others…
Kyle’s goal was this for years…

The goal here is to use one use case to help drive the epiphany of virtualization.
A Single Use Case

Why do we still patch and upgrade the old fashioned
way?
After three months at Delphix….
 Recognized the benefit of virtualization and addressing tedious tasks.
 How to describe a complex topic that simplifies?
 The message was challenging….
Maybe it was the sticky notes.

Patching and Upgrading….

Standard Database Environment
Finance
HR
CRM

Patching and Upgrading Databases
 Each patch, (PSU) would need to
be applied to a development
database, requiring outage to
development teams and then
tested before applying to test, QA
and then onto production.
 This has to be performed to
EACH environment, every
database, each quarter.
Finance
HR
CRM

• Downtime for valuable resources.
• DBAs working afterhours
• Each database must have it done and…
- The tedious task must be performed over and over
again.
- Little opportunity for advanced learning.
- Each database may experience different bugs.
Risks/Challenges Of This Approach

▶▶▶
Virtualize and Deployed▶ ▶ ▶
0.6 TB
Virtualization Eliminates 90%+ Common, Repeated Data
Storage Pool for Delphix
QA
DEV PATCH TEST
PRODUCTION
Database/App Tier
1
TB
1 TB
Read From Production
Spin a VIRTUAL database up a patch test, without having to remove a current development or test one.
TEST

The CLI, (Command Line Interface) is very robust for Delphix and Creating VDB is easy!
I’m a Command Line Person, Whatcha Got?
• The name of the VDB you want to create
• The group in which to create the VDB
• The Oracle database name
• The Oracle database unique name
• The Oracle database instance number
• The Oracle database instance name
• The source dSource or VDB from which you wish to provision
• The SCN or timestamp of the point you want to provision from, (commands
can be run to get the list of snapshots or timeflow ranges.)

https://docs.delphix.com/display/DOCS43/CLI+Cookbook%3A+Provisioning+a+VDB+from+a+TimeFlow+Bookmark
Choose Source Snapshot:
>snapshot list database=<dbname>
timeflow ”<dbname>" timeflowRanges;
commit;
Create A Virtual Database:
>database provision;
delphix database provision > defaults
delphix database provision defaults > set
container=<Vdbname>
delphix database provision defaults > commit;

What a CLI Scripted Refresh Looks Like
> database
> select <VDB name>
> refresh
> set timeflowPointParameters.type= (one of
TimeflowPointBookmark, TimeflowPointBookmarkTag,
TimeflowPointLocation, TimeflowPointSemantic,
TimeflowPointTimestamp as appropriate)
> set timeflowPointParameters.location= (the location,
timestamp, or bookmark you wish to refresh to)
> set timeflowPointParameters.timeflow= (the timeflow
associated with location)
> commit

• Monstrous deployments, (20+) benefit from a scripted, CLI option.
• Single or several VDB deployment.
• When investigating deep level issues, using the CLI can make details
easier to search through.
• When looking for “just the facts”, then a graphical UI is beneficial for
high level error messages.
• Self-service has great benefits and make it simple for those without
deep level skills to take advantage of virtualized environments for
development and testing.
When Do I USE the CLI or Graphical UI?

Cost Vs. Benefit…
• No Management Packs outside of database
feature licensing.
• Heterogeneous Opportunities

Spin up a new VDB
and apply patch
there- no need to
commandeer
existing!
Environment Virtualization, DB Style

No need to keep the
extra VDBs post
patch to prod.
After Testing, Apply to Production

The Compressed
Copies in the Delphix
Engine are Upgraded!

In minutes,
refresh and
complete!

• Not only did I save on 80% or more on storage usage overall.
• I didn’t have to take away a valuable resource’s database environment to test
the patch/upgrade.
• I didn’t have to apply the patch/upgrade to each environment, as they are
virtualized copies of the source.
• I save significant time that commonly has to be allocated to quarterly and
annual maintenance for patching and upgrading.
• I apply the patch twice- once to test, once to production. I only need to refresh
my environments after I’m done.
• This works for the database AND application tier.
Patching and Upgrading with Virtualization

The quickest way to complete a task is not having to do it.

@DBAKevlar
https://dbakevlar.com http://delphix.com
kellyn@delphix.com
https://linkedin.com/in/kellynpotvin
Connect With Me

Q&A
Thank you!
Want to try it out? Download the Delphix Express Version to your
laptop: https://www.delphix.com/products/free-trial-request

http://delphix.com
http://dbakevlar.com
https://www.delphix.com/products/free-trial-request
www.NEOOUG.org

Delphix Patching Epiphany

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (13)

Similaire à Delphix Patching Epiphany

Similaire à Delphix Patching Epiphany (20)

Plus de Kellyn Pot'Vin-Gorman

Plus de Kellyn Pot'Vin-Gorman (20)

Dernier

Dernier (20)

Delphix Patching Epiphany

Notes de l'éditeur