What I have ended up doing is just keeping the copy on a database,
upgrading and patching as needed. Expensive, yes. Data always available, yes.
What you have to lose if you lose the case should dictate how you keep the
CPB Database Group Manager
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Scott Canaan
Sent: Thursday, April 27, 2017 1:16 PM
Subject: Database Retention Question
We are trying to find a workable solution to a rather large problem. One
system has an Oracle database in Red Hat 6 and Oracle 220.127.116.11. Last August,
there was a legal request to freeze 28 different backups of this database.
That was done by the systems team, via CommVault (using RMAN). By asking more
questions, it has come to light that any and / or all of those backups need to
be quickly accessible as Oracle databases until Aug. 31, 2023. When I
mentioned to our legal department that there's no way that I can guarantee that
whatever version of Oracle we'll be using in 5, 6, 7 years will be able to even
open the database files, the response was "you have to guarantee that the data
is available if required in a lawsuit. No excuses are accepted by the courts.".
We've toyed with a couple of possible options. One is to keep a Red Hat 6 /
Oracle 18.104.22.168 environment running until Sept. 1, 2023, which the SAs hate
(not to mention the Security Office). Another is to restore from backup and
upgrade along with other database upgrades and take a new frozen backup, which
we aren't keen on doing 28 times.
Does anyone have any other ideas on how to save these backups and guarantee
that they are usable through Aug. 31, 2023? I'd appreciate any thoughts.
Scott Canaan '88 (srcdco@xxxxxxx<mailto:srcdco@xxxxxxx>)
(585) 475-7886 - work (585) 339-8659 - cell
"Life is like a sewer, what you get out of it depends on what you put into it."
- Tom Lehrer