Re: Backups versus snapshots
- From: Paresh Yadav <yparesh@xxxxxxxxx>
- To: kmoore@xxxxxxxxxxxx
- Date: Thu, 18 Sep 2014 22:48:00 -0400
Speaking about retention > 30 days. Has anyone actually has done
*successful* recall of a backup more than 3 years old and if the backup
was found, recovery was succesful i.e. backup media/pieces were good? If
yes how much time it took from ordering the recall to recovering the
database?
This is a theoretical question but I am very curious to find out what
happens to all the tapes that are few years old (physical condition of the
tape media, ability to locate them etc.).
Thanks
Paresh
416-688-1003
On Thu, Sep 18, 2014 at 7:01 PM, Keith Moore <kmoore@xxxxxxxxxxxx> wrote:
> That’s an interesting question that I’ve asked as well. They have two
> business units. One keeps backups for 30 days and then they are completely
> gone. The other business unit keeps them for 10 days and then they are
> gone. We’ve been asked to restore a copy of a database over 30 days old and
> had to tell them it couldn’t be done. They now want to reduce the retention
> to 3 days using archive logs which to me seems rather extreme.
>
> I’ve asked before about keeping monthly and yearly copies, etc but never
> received any response as to why the policy is what it is.
>
> Keith
>
> On Sep 18, 2014, at 2:22 PM, Martin Bach <development@xxxxxxxxxxxxxxxxx>
> wrote:
>
> > Just out of interest,
> >
> > What happens in that case if you have to restore the database system to
> what it was last month to check if there was a data entry error? That kind
> of scenario, in addition to longer term archival (think regulators) are my
> concerns when thinking about snapshot only based approaches. Snapshots
> before software releases, end of year processing etc sound nice to me
> though.
> >
> > Martin
> >
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
Other related posts:
