snapmirror design

NetApp Confidential - Limited Use

Database Refresh

By Phillip Bruce

© 2008 NetApp. All rights reserved. 2NetApp Confidential - Limited Use

Current BI Architect for Database refreshes

Archive Log

1Standby

1210g

9 10 118

765432

VolClone

Development

NEOEDWDMS

1Standby

9 10 118

765432

Vol Clone

QA / Staging

NEOEDWDMS

Archive Log

1210g

Production

RMANTo build DG

RMANTo build DG

1

2

3

2

1

3


DB Refresh Pain Points

Storage Allocated for Dev / STG /QA are not big enough to accommodate 8 set of production database.

To Accommodate 8 set of prod environment we have to follow RMAN backup and restore which is taking more then 10 days to refresh, Impacting SLA. (Using DataGaurd technology to keep database in sync)

Have to do refresh standby database after every month-end or quarter-end (due to no logging), many groups have to involved to get this done and taking everyone time.

RMAN backup impacts production database performance.

Existing Solution is not scalable. It is impacting development, QA and UAT cycle.


How NetApp SnapShot Works


Example of NetApp Snapshot Technology in Action

The live file system writes the blocks A, B, C, and D todisk and locates them with pointers.

The following figures assume that the file system is writing a filethat consists of the blocks A, B, C, and D.


A Snapshot is taken – no data is read, written, or copied todisk, the Snapshot simply points to the current locations.


The live file system modifies block C, and writes C’ todisk – there is no change to block C. The live file systempoints to C’ instead of C. The Snapshot still points toblock C, which is unchanged.


As more changes are made to the file system, it is clearthat the Snapshots are still able to recreate the file as itwas at the time they were taken.


FlexVol Cone


FlexVol Clone

DB

VOL

LUNFS

DB

VOL

LUNFS

DB

VOL

LUNFS

Vol Clone

Snap-S1

Snap-S2

Assigned to Project-1

Assigned to Project-2

As Database Changes

As Database Changes

Virtual Volumes (Do not consume any space)


BI Database Refresh Architect

sacprodflr05 sacprodflr 06 sacprodflr 11 sacprodflr 12

PEDW

PFINDM

PSLSDM

PCSDM

PCUSTIN

PRPNET8

Pcentric

Backup Filers

SnapMirror PEDW

PFINDM

PSLSDM

PCSDM

PCUSTIN

PRPNET8

Pcentric

svldevflr 09 svldevflr 10 svldevflr 11 svldevflr 12

PEDW

PFINDM

PSLSDM

PCSDM

PCUSTIN

PRPNET8

PcentricSnapMirror

PEDW

PFINDM

PSLSDM

PCSDM

PCUSTIN

PRPNET8

Pcentric

PEDW

PFINDM

PSLSDM

PCSDM

PCUSTIN

PRPNET8

Pcentric

Clone Clone

Production

Backup Filers

Dev / STG /QA


Solution

Using FlexVol Clone we can create many private copy of database using single physical copy of database.

We do not have to manage / refresh standby databases after each quarter-end or month-end.

Dev /QA /UAT databases are not impacted by no logging operation on primary database (POROD).

It consumes much lesser storage. NetApp on NetApp. No additional investment is required.


Limitations

Cloned Database instance should not changed data more then 20-30% of total size.

We have to keep refreshing databases frequenctly (minimum once in a quarter).

snapmirror design

Documents