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: RMAN Backups/Recoveries

Re: RMAN Backups/Recoveries

From: Joel Garry <joel-garry_at_home.com>
Date: 17 Dec 2003 14:56:20 -0800
Message-ID: <91884734.0312171456.2f706521@posting.google.com>


"Ofer Razon" <orazon_at_012.net.il> wrote in message news:<brl15q$92s$1_at_news2.netvision.net.il>...
> Hi All.
>
> Using Oracle 8.1.7, I am considering the use of RMAN in order to run a
> continous recovered DB, so I`ll do a full recovery once and then, every X
> days I`ll run an incremental recovery for this DB.
> I know that the DB will never be "open". My actual plans are to use PIT
> disks features and open a copy of the database everytime I`ll need it,
> without ruining the recovery process.
>
> At first we considered using a Stand By DB, but then we`ve found that every
> time we`ll add/resize a datafile we`ll have to do it on the standby too, so
> we dropped this idea.

Why is that such a deal-killer? From your subsequent posts, sounds like this is really what you want to do. Sounds like you have hardware that can snap a mirror of the recovering db. You would want to do this while it is in between applying archived logs to the standby db. This is because there is a process called RFS that runs on the standby machine to apply the archived log sent from the primary machine. The primary machine waits for RFS to tell ARCH that it is done applying, before the primary can move on (even if the standby is an optional location). So several things can go wrong if you try to snapshot the recovering db while RFS is applying the log, including slowing down the primary, and splitting off a mirror with an unrecoverable redo log.

I wouldn't have believed it, but I've recently had the experience (on 8.1.7.2 hp-ux 11) that if the Standby platform dies while RFS is running, it can stop the primary from archiving. What is supposed to happen is there is a timeout based on TCP parameters, (which many places set too long, see metalink note 255959.1) but what I saw was that it didn't work at all. This locked up my production database, with no way to switch more than a few logfiles short of a resetlogs. O HA support is still trying to figure this one out for me.

>
> Will RMAN solve me this problem?
> Do you think that it is possible to run in a "continous recovery" as I
> described?
> BTW: I`m couting on the feature that every "incremental recovery" will
> update only the affected blocks in the DB and won`t create the full datafile
> from scratch.

RMAN can be used to create the standby, RMAN can be used to recover a backup. Standby is for continuous recovery.

RMAN can also be used to do the old style hot backup, perhaps in concert with your hardware snapshot ability you can use it to quickly clone (ie, silver third mirror, place all tablespaces in hot backup mode, break mirror, end backups)? How often do you add datafiles, anyways?

>
> Thanks,
> Ofer Razon.

jg

--
@home.com is bogus.
http://www.signonsandiego.com/news/uniontrib/wed/news/news_1n17spam.html
Received on Wed Dec 17 2003 - 16:56:20 CST

Original text of this message

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