Re: Oracle Backup Strategy re: online redo log backup

From: Nate Jones <nathan.jones_at_bi-tech.com>
Date: 20 Mar 2002 13:31:18 -0800
Message-ID: <cde4fecc.0203201331.48b9d676_at_posting.google.com>


srivenu_at_hotmail.com (srivenu) wrote in message news:<1a68177.0203192128.3ace298c_at_posting.google.com>...
> You can backup all the datafile by putting all the tablespaces in
> backup mode at the same time(although this is not recommended as it
> generates more redo during that period).
> But your redo logs may not be usable if you back them up.
> All you need is the archive log files generated between the start and
> end of the backup.
> Your backup strategy can be like this
> 1)Find the current log info ARCHIVE LOG LIST
> 1)put all tablespaces in backup mode.
> 2)backup all the datafiles.
> 3)find the current log info ARCHIVE LOG LIST
> 4)Archive the current log
> ALTER SYSTEM ARCHIVE LOG CURRENT or
>
> ALTER SYSTEM SWITCH LOGFILE followed by
> ALTER SYSTEM ARCHIVE LOG ALL
> 5)backup the archive logs.
>
> In case of a restore.
> 1)restore the datafiles
> 2)recreate the controlfile using RESETLOGS clause
> 3)open the database using the RESETLOGS clause.

Thanks for the response. Just a little clarification...

The backup strategy you have listed is almost exactly what I do. However, when it comes time to restore, there will most definately be data in the CURRENT redo log. Is this CURRENT log going to be used in the restore? Or will it be overwritten? Howards doc makes it seem like that can be used during the restore....

Thanks,

Nate Received on Wed Mar 20 2002 - 22:31:18 CET

Original text of this message