Re: Real life implementation of 7 year data retention requirement

From: Kevin Jernigan <kevin.jernigan_at_oracle.com>
Date: Thu, 13 Feb 2014 13:33:17 -0800
Message-ID: <52FD3A1D.10504_at_oracle.com>

As the PM for Flashback Data Archive (FDA), I strongly agree with your suggestion to use FDA to keep track of all changes to data over time ;-) This will give you easy Flashback Query access to view your data AS OF any point in time back to "the beginning of time" (i.e. whenever you enabled FDA on the underlying tables).

Now you might be saying "Wait a minute, that's a lot of disk space / expense / etc!" And you might be right - but you can use compression, partitioning, and even HCC on Oracle Storage to keep the older FDA-managed history data online in cheaper / denser storage, while transparently keeping the more recent (usually hotter) data on Tier 1 storage etc etc. And, the question is always "What's the value to the business of having online access to the historical data using Flashback Query?" versus the slower more complex approach of restoring the right backup, rolling forward to the right point in time, etc etc...

-KJ

-- 
Kevin Jernigan
Senior Director Product Management
Advanced Compression, Hybrid Columnar
Compression (HCC), Database File System
(DBFS), SecureFiles, Database Smart Flash
Cache, Total Recall, Database Resource
Manager (DBRM), Direct NFS Client (dNFS),
Continuous Query Notification (CQN),
Index Organized Tables (IOT), Information
Lifecycle Management (ILM)
+1-650-607-0392 (o)
+1-415-710-8828 (m)

On 2/13/14, 12:50 PM, Freek D'Hooge wrote:


> But not a history of how a record changed through time.

>

> I think the reasoning behind the restore to any point between now and 

> 7 years back is the need to be able to show what a record looked like  

> x time back.

> If so, maybe flashback data archive and / or auditing could be used to 

> fulfil such a requirement?

>

> regards,

>

> -- 

> Freek D'Hooge

> Exitas NV

> Senior Oracle DBA

> email: freek.dhooge_at_exitas.be <mailto:freek.dhooge_at_exitas.be>

> tel +32(03) 443 12 38

> http://www.exitas.be <http://www.exitas.be/>

>

> On do, 2014-02-13 at 21:36 +0100, Frits Hoogland wrote:

>> Just as a bold statement, and something to think about: isn't your 

>> most recent backup a complete backup of all the history contained in 

>> your database?

>>

>> Frits Hoogland 

>>

>>

>

>>

>> http://fritshoogland.wordpress.com 

>> frits.hoogland_at_gmail.com <mailto:frits.hoogland_at_gmail.com> 

>> Phone: +31 20 8946342 

>>

>>

>> (Sent from my iPhone, typo's are expected) 

>>

>>

>>

>> Op 13 feb. 2014 om 21:13 heeft Paresh Yadav <yparesh_at_gmail.com 

>> <mailto:yparesh_at_gmail.com>> het volgende geschreven:

>>

>>

>>> Thank you David, Rich, Frits, and Johnson for your useful replies. 

>>>

>>>

>>> The point about compatibility and cost is very important. Isn't it 

>>> necessary by law with so many businesses to retain 7 years of data? 

>>> What do people do in this case? In many places that I know of 

>>> (including fortune 100 organizations) there is a 7 year retention 

>>> policy for backup in place but as I had mentioned God only knows 

>>> what actually happens to those tapes. At times I have asked to test 

>>> a restore from backup taken long time a go but no one wants to open 

>>> that can of worms. 

>>>

>>> Thanks

>>> Paresh 

>>> 416-688-1003 

>>>

>>>

>>>

>>>

>>> On Thu, Feb 13, 2014 at 1:44 PM, Johnson, William L (TEIS) 

>>> <WLJohnson_at_te.com <mailto:WLJohnson_at_te.com>> wrote:

>>>

>>>     I may be kicked off this list for making this comment...but I

>>>     would look into a simple Hadoop cluster to store the data...I am

>>>     not sure if your data is written once and done - or if you

>>>     update it frequently, but there is a lot to be said for the

>>>     cost/TB and the ability to store data long term in a Hadoop cluster.

>>>     Bill 

>>>

>>>

>>>     -----Original Message-----

>>>     From: oracle-l-bounce_at_freelists.org

>>>     <mailto:oracle-l-bounce_at_freelists.org>

>>>     [mailto:oracle-l-bounce_at_freelists.org

>>>     <mailto:oracle-l-bounce_at_freelists.org>] On Behalf Of Rich Jesse

>>>     Sent: Thursday, February 13, 2014 12:36 PM

>>>     To: oracle-l_at_freelists.org <mailto:oracle-l_at_freelists.org>

>>>     Subject: Re: Real life implementation of 7 year data retention

>>>     requirement

>>>

>>>     Paresh writes:

>>>

>>>     > period (say 6 or 7 years from "now") (e.g. challenges in

>>>     locating the

>>>     > tapes (physical or virtual), rman catalog not having record of

>>>     backup

>>>     > pieces for the time period etc.). Does magnetic tape remain

>>>     good for 7

>>>     > years in a climate controlled environment or you do copy them

>>>     after 3

>>>     > years or so to a new tape? If yes, is this automated as manual

>>>     process

>>>     > will be too much cumbersome and prone to errors.

>>>

>>>     And don't forget about compatibility.  For example, an LTO-3

>>>     tape written 7 years ago won't be able to be read on an LTO-6

>>>     drive -- a very plausible timeline example.

>>>

>>>     Rich

>>>

>>>     --

>>>     http://www.freelists.org/webpage/oracle-l

>>>

>>>

>>>

>>>     --

>>>     http://www.freelists.org/webpage/oracle-l

>>>

>>>

>>>

>>>



--
http://www.freelists.org/webpage/oracle-l

Received on Thu Feb 13 2014 - 22:33:17 CET