Bingo. Then you're data isn't dependent on any piece of technology being
available at that time.
Sent from my iPhone
On Apr 27, 2017, at 2:20 PM, Seth Miller <sethmiller.sm@xxxxxxxxx> wrote:
Depending on the RDBMS is very risky. Your quote says that the "data" must be
available. Flatten the data and export it into an open standard format. Then,
you don't have to worry about how to access the data, RDBMS support, etc.
On Thu, Apr 27, 2017 at 11:04 AM, Andrew Kerber <andrew.kerber@xxxxxxxxx>
Interesting you should ask that. The best method, as others noted, is
probably just to copy the whole running database to a VM and back up the VM.
Start the VM annually to make sure it will still run. I have a small
Oracle 7.3.4 database on Windows NT that I burned to DVD a few years ago, I
still start it up occasionally just for nostalgia.
On Thu, Apr 27, 2017 at 12:23 PM, Ruel, Chris <Chris.Ruel@xxxxxxx> wrote:
How about create VM with a copy of that database and an FRA with all 28
backups available? You can shut it down, export it, zip it up, whatever
you need to do.
Chris Ruel * Oracle Database Administrator * Lincoln Financial Group
cruel@xxxxxxx * Desk:317.759.2172 * Cell 317.523.8482
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 184.108.40.206. 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 220.127.116.11 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)
(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
Notice of Confidentiality: **This E-mail and any of its attachments may
Lincoln National Corporation proprietary information, which is privileged,
or subject to copyright belonging to the Lincoln National Corporation
companies. This E-mail is intended solely for the use of the individual or
which it is addressed. If you are not the intended recipient of this
E-mail, you are
hereby notified that any dissemination, distribution, copying, or action
relation to the contents of and attachments to this E-mail is strictly
and may be unlawful. If you have received this E-mail in error, please
sender immediately and permanently delete the original and any copy of this
and any printout. Thank You.**
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'