Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Backup & Restore

Re: Backup & Restore

From: Brian Peasland <dba_at_nospam.peasland.net>
Date: Thu, 20 Sep 2007 08:45:08 -0500
Message-ID: <46f26d66$0$4530$88260bb3@free.teranews.com>


Ravip via DBMonster.com wrote:
> Hi Brian,
>
> Thanks for comprehensive detail. Obviously I'm not in a position to lose data
> generated in last minute as well. Again as you said it depends on backup
> strategy.
>
> My clarification is once the incremental backup taken on yesterday night,
> should I need to retain the
> the backup of archive redolog backups taken prior to yesterday's backup.
> Because the db incremental backups are available from yesterday and previous
> days. As I mentioned earlier that the backup of DB and archive log files are
> executed separately.
>
> Thank You.

You will not need the archived redo logs from prior to the incremental backup. However, if the last incremental backup was unusable for some reason, you would need the archvied redo logs since the previous incremental backup. Just to be safe, I keep the archived redo logs since the previous incremental level 0. And I keep at least 3 level 0 backups on hand. So if I generate a level 0 once a week, I'll have 3 weeks worth of backups on hand. To make sure that I can use any of those backups, I keep the archived redo logs for the last 3 weeks.

Keeping more than one generation of your backups is an old practice. The most recent backup is generation 0. The backup before that is generation -1. You may have generation -2 and maybe generation -3, depending on your retention policy.

The reason to keep multiple generations is that backups are often stored on tape media and tape media can fail. If there is only one backup and that tape fails, the safety net is lost. But by having more than one generation, we ensure we can get access to at least some of the data.

The other reason to keep multiple generations around is that one may discover a problem (i.e. bad data) and that problem is in the backup. One may occasionally desire to restore before that data became a problem. This is hard to do with only one generation. Multiple generations do not guarantee success here either.

In your reply, you stated "Obviously I'm not in a position to lose data generated in last minute as well.". This makes me ask...are you doing some sort of log shipping? Are you ensuring that your logs switch and get archived at least once a minute? If not, then you may be at risk of losing more than one minute's worth of data. Have you looked at Data Guard in your data protection strategy?

HTH,
Brian

-- 
===================================================================

Brian Peasland
dba_at_nospam.peasland.net
http://www.peasland.net

Remove the "nospam." from the email address to email me.


"I can give it to you cheap, quick, and good.
Now pick two out of the three" - Unknown

-- 
Posted via a free Usenet account from http://www.teranews.com
Received on Thu Sep 20 2007 - 08:45:08 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US