Re: Real life implementation of 7 year data retention requirement

From: Frits Hoogland <>
Date: Thu, 13 Feb 2014 21:36:30 +0100
Message-ID: <8636852334475744382_at_unknownmsgid>

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
Phone: +31 20 8946342

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

Op 13 feb. 2014 om 21:13 heeft Paresh Yadav <> 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.


On Thu, Feb 13, 2014 at 1:44 PM, Johnson, William L (TEIS) <
> 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: []
> On Behalf Of Rich Jesse
> Sent: Thursday, February 13, 2014 12:36 PM
> To:
> 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
> --
> --


  • application/pkcs7-signature attachment: smime.p7s
Received on Thu Feb 13 2014 - 21:36:30 CET

Original text of this message