Delphix implementation in Exadata environment

  • 0
  • 1
  • Question
  • Updated 4 years ago
  • Answered

I am trying to propose to my client regarding delphix implementation please let me know if my understanding is correct.

I have read many blogs and site and have come up with the below understanding of delphix

Problem definition

We have a production database on exadata m/c. For development and testing we are using 11g enteprise edition. When we ask for an environment it take a week or more to get the environment. Also we donot get the replica of production database. So when i came across delphix i though this needs to be proposed to the client to reduce the storage cost as well as getting time it takes to get the new environement. Also I have taken most of the text from various blogs,sites and white papers.

Below is what my understandig of delpix is

Possible Delphix Implementation for Client’x


The Delphix Engine on the delphix server links to source physical databases of the exadata server via standard APIs and asks the source databases to send copies of their entire file and log blocks to it. The Delphix Engine uses intelligent filtering and compression to reduce the copy of the source database down to as little as 25% of the original size. The copy of the source database is stored in the Delphix engine, along with the incremental updates. This copy is refered to as dSource in delphix terminology.

Using the dSource multiple VDB (Virtual database) can be provisioned from the delphix engine. Since the DB blocks are shared across the multiple VDB’s it does not incur any additional storage requirement.

So we can create multiple VDB for DEV,CIT,ST,SIT and UAT. This will reduce the storage and environment availability time drastically.

When a VDB is provisioned, the user selects a point along the timeflow of the parent database and a target environment in which to create the database instance. Delphix will:

·         Create a writeable copy of the physical storage in a time and space efficient manner

·         Export the physical storage to the target server over the appropriate protocol (e.g. NFS)

·         Configure a database instance in the target environment according to the settings provided by the administrator

·         Use the instance to take the database through recovery and replay (if necessary)

·         Take a consistent snapshot of the resulting storage

·         Make the database available to end users

Once provisioned, a VDB is an independent, read-write database, and changes made to the VDB by users or applications are written to new, compressed blocks in Delphix storage or to Target Server. VDBs can be provisioned from other VDBs, and the data within VDBs refreshed from its parent VDB or dSource.

Delphix Hardware Stack       


Delphix Server software installs on

·         standard x86 servers     

·         Supported databases: Oracle 9, 10g ,11g  , RAC,  Exadata, Standard, Enterprise on Linux, Solaris, HP-UX, and AIX.

·         Storage support: SAN or DAS storage

Photo of Jay Bane

Jay Bane

  • 122 Points 100 badge 2x thumb

Posted 4 years ago

  • 0
  • 1
Photo of Adam Bowen

Adam Bowen, Official Rep

  • 17,886 Points 10k badge 2x thumb
Official Response
Great synopsis and mostly spot-on. Clarification at the end, Delphix is a virtual machine, and runs on VMware vSphere, Amazon EC2, KVM, etc. More info on that can be found here:

If you want to reach out to, we can help you position with your client.