Data control

17
Install Delphix Software on x86 VM x86 hardware Allocate Storage Any type Installs on any x86 hardware as a Vmware VM, and is shipped as OVA file Supports any major Oracle O/S such as Linux, AIX, HPUX, Solaris OpenSolaris Uses any storage

description

 

Transcript of Data control

Page 1: Data control

Install Delphix Software on x86 VM

x86 hardware

Allocate StorageAny type

Installs on any x86 hardware as a Vmware VM, and is shipped as OVA fileSupports any major Oracle O/S such as Linux, AIX, HPUX, Solaris, OpenSolarisUses any storage

Page 2: Data control

One time copy of source database

Database

Production

Instance

File system

RMAN APIs

After installation of Delphix, then the source database host is registered with Delphix.Delphix will auto discover any databases on the source host.A user then can pick a source database, and Delphix makes a one time only initial copy using RMAN APIs.

Page 3: Data control

Delphix Compress Data

Database

Production

Instance

File system

Data is compressed typically 1/3 size

Page 4: Data control

Incremental forever change collection

Database

Production

Instance

File system

Changes are collected automatically foreverData older than retention widow freed

Delphix will continue to pull in the changes, and only the changes incrementally and forever, holding on to 2 weeks of changes and purging changes older that 2 weeks. The 2 week window is called the timeflow. A virtual database can be provisioned from anywhere in the timeflow down to the transcation SCN. The two weeks is configurable and is often be extended longer.

Page 5: Data control

Typical Architecture : Before Virtualization

Database

File system

Production

Instance

Database

File system

Development

Instance

Database

File system

QA

Instance

Database

UAT

Instance

File system

3 or more copies of production, duplicating the majority of datablocks

Page 6: Data control

Architecture : after Virtualization

Development

Instance

Database

Production

Instance

File system

vDatabase

QA

Instance

UAT

Instance

vDatabase vDatabaseNFS

Source Database Clone Copies of Source Database

Fiber Channel

One compressed copy of production along with 2 weeks of changes stored on the virtualization appliance and all clone copies share the duplicate datablocks

Page 7: Data control

I/O Virtualization

3 physical clones 1 source 3 virtual clones of 1 source

Virtualization layer takes one source copy, compresses it, pulls in ongoing change to the source and orchestrates I/O access between clone database and storage

Space wastage and creation time delays

Page 8: Data control

Timeflow: Production change capture

Clones created in minutes

Developer VDB

QA VDB

Production

Development, QA

Can spin up a copy of production for use in development in minutes with almost no storage overhead. The development database along with all changes made to it can be forked off to be used by QA in minutes

Page 9: Data control

Devv2.6 v2.6v2.6

QA UAT

v2.6Production

v2.6 v2.6v2.6v2.7

v2.6 v2.6v2.6v2.8

Virtualization makes running parallel development tracks with different versions of database data and schema easy

v2.6v2.6 v2.6v2.6

v2.6v2.7 v2.6v2.7

v2.6v2.8 v2.6v2.8

Page 10: Data control

Dev

Prod

2.6

Dev copies production Database and starts modifying code and database schema and/or meta data and/or database contents

Production Time Flow

Development Virtual clone of Production

Page 11: Data control

Dev

QA

Prod

2.6

Dev finishes a sprint or point release and QA forks off a clone virtual database from Dev database

Production Time Flow

Page 12: Data control

Dev

QA

UAT

Prod

2.6

Dev might refresh from prod, re-implement changes, write more code and changes, then QA forks off a clone, and then UAT forks off a clone

Production Time Flow

Page 13: Data control

Dev

QA

UAT

Prod

Dev

QA

UAT

2.6

2.7All of this might be happening with a second parallel development release

Production Time Flow

Page 14: Data control

Dev

QA

UAT

Prod

Dev

QA

UAT

2.6

2.7

Dev

QA

UAT2.8

Or a third

and after one release finishes those changes have to be incorporated into the next release

Production Time Flow

Page 15: Data control

Dev

QA

UAT

Prod

Dev

QA

UAT

2.6

2.7

Dev

QA

UAT2.8

Data Control = Source Control for the Database

With Delphix, every step of the way can have a snapshot and be correlated to a point in the source control tree

Production Time Flow

Page 16: Data control

Dev

QA

UAT

Dev

QA

UAT

2.6

2.7

Dev

QA

UAT

2.8

Data Control = Source Control for the Database

Delphix Production Time Flow

Development, Test and QA can all share majority of storage across different development versions all easily managed with database snapshots

Clone database datafiles mounted via NFS, all storage on Delphix

Page 17: Data control

Dev

QA

UAT

Dev

QA

UAT

2.6

2.7

Dev

QA

UAT

2.8

Data Control = Source Control for the Database

Delphix

Source

Production Time Flow

Changes (via RMAN and TCP)

Development, Test and QA can all share majority of storage across different development versions all easily managed with database snapshots

Clone database datafiles mounted via NFS,All storage on Delphix