Re: Backups versus snapshots

From: Paresh Yadav <yparesh_at_gmail.com>
Date: Fri, 19 Sep 2014 00:15:27 -0400
Message-ID: <CAPXEL0JwAFjrhw2P-UGEN1DKBEYzJVseVp9Ym5PAwVz3DhEZSw_at_mail.gmail.com>

Thanks Matthew for sharing your valuable experience at Amazon.. As Hemant mentioned you must have preserved all associated tech (tape library to read the old tapes, machine and OS version that can run the old db software version, db software at version that can restore the backups etc.). And this needs to be done for all possible tech (hardware and software) and its version that gets used over a period of time. Amazon can afford the infrastructure and manpower required to maintain this but how does a SMB meet 7 year regulatory retention requirement?

What was typical time to recover a 1997 Oracle db backup (probably Oracle version 7.x) in 2010 after having to install Oracle 7.x software on a compatible OS and hardware? This will involve not only locating the backups but also the software install media and the hardware that can run the software.

Thanks
Paresh
416-688-1003

On Fri, Sep 19, 2014 at 12:04 AM, Iggy Fernandez <iggy_fernandez_at_hotmail.com
> wrote:

> snapshots or backups are just means to an end; that is, meeting the
> availability and regulatory requirements within the available budget. if,
> for example, you have regulatory requirements to store data for a certain
> number of years, then you could copy the contents of the snapshots to tape.
>
> re: if the database goes poof then the snapshot is gone as well
>
> if the database goes poof, then the snapshot remains
>
> iggy
>
> > To be clear, the snapshots are not physical copies of the database. They
> only track the differences between the database at the time of the snapshot
> and the current time. So if the database goes poof then the snapshot is
> gone as well.
>

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

Received on Fri Sep 19 2014 - 06:15:27 CEST