Re: backup best practices

The use of RMAN for your backups should obviate the need for cold backups, since RMAN ensures there's no block corruption and backs up data files in a recoverable state. Of course, unless you're using archive logging w/ your RMAN backup, you'll have to do a cold backup anyway.

Despite that, I like getting a cold backup once i've installed a database, just in case my rman procedures aren't quite right. But, once i've done disaster recovery testing no further cold backups are needed.

Should you bounce Oracle occasionally for no good reason? Probably not; bouncing oracle clears out buffer pools and memory, thus meaning all your queries will run more slowly until you re-populate your memory chain or keep pools.

my 2 cents,
todd

> Should off-line backups (RMAN or otherwise) be a part of a standard backup
> strategy? In the "old" days, cold backups were recommended for consistency -
> or at least that's how I understood it. Now, it seems that these are not
> deemed essential. What is the recommended best practice for off-line/on-line
> backups?
>
>
>
> Related to this: Should the DB be "bounced" occasionally? In my last
> oracle class, this was implied, although not stated. Any thoughts
>
>
>
> Thanks
> Susan White

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