Re: exp and archive available.... recover table

Alexander Skwar wrote:

> Preston <dontwantany_at_nowhere.invalid> wrote:
>
> > A few bits of advice, if I may. Firstly, ditch Google Groups & use a
> > usenet client & account instead (I recommend XanaNews &
> > http://news.individual.net).
>
> LOL :) Congrats to you as well - you managed to fetch the "only" post
> I sent over GG :)

Typical! I didn't look at the headers of any others.

> I now "played" a bit and am (again G) not so convinced that RMAN would
> be my best solution. What advantage does RMAN offer over backing up
> the "hot" database .dbf files in combination with the archived redo
> log files? I'm only interested in doing backup to disk. At least for
> now.

To do a hot backup, you need to put the tablespace in backup mode. While it's in backup mode, any activity will result in the writing of the complete changed blocks, plus the changes themselves, to redo. This doesn't happen with RMAN, so there's less overhead. It doesn't sound like that would be much of a concern for you though, given that the database isn't normally being used when you do the backups.

> What I'm now considering to do is, that I'd copy all the .dbf files
> and also the redo log files. When I have the archived redo log files
> available, I am able to do a media recovery, aren't I? And I (might)
> need to do a media recovery, when I try to startup the database and
> give it .dbf files, which are "hot". Or am I overlooking something
> again?
>
> I guess the advantage in RMAN would be, that I could do everything
> (restore & recover) from one interface. And, if configured properly, I
> also could control backup to/restore from tape.

To be honest I can't really see any reason for you /not/ to use RMAN, in conjunction with weekly cold backups. It's the 'correct' way to do it, & the best way if you do the vault backup first & use PIT when required.

-- 
Preston.