Re: Hot backup

I just recovered a database that was saved while 'HOT'. I do not think that having the database in backup mode causes significant increase in recovery time. I believe activity on the database during the backup will have a bigger impact. Rember that to backup HOT, you must be running in archivelog mode. You will need to roll the archive logs forward. You will need all the archive logs from the time the hot backup was taken to the time you want to recover the database up to. The more logs, the more time to recover.

Hope this helps,
David

lsnyder_at_mail.dex.com (Lowell R. Snyder Jr.) wrote:

>In article <4ec8pj$5g3_at_news.nyc.pipeline.com>,
> Sameer Utrankar <utrankar_at_nyc.pipeline.com> wrote:
>>Usual examples of Hot backup scripts are :
>>
>>Alter tablespace1 begin backup
>>backup tablespace1
>>alter tablespace1 end backup
>>
>>alter tablespace2 begin backup
>>..
>>and so on ?
>>
>>It is a lot easier to setup and manage a script which does begin backup
>>on all tablespaces, backups all and then does end backup on all of them.
>>What is the problem in doing so ? Any downside ?
>>
 

>My understanding is that if you crash the system during this type of backup,
>then recovery will take longer (since there are more datafiles that will need
>recovery).
 

>-------------------------------------------------------------------
>Lowell R. Snyder, Jr. Lord Einar Sclater of Orkney
>Network Manager Kingdom of Caid
>Data Exchange Corp. Society for Creative Anachronism
>lowells_at_dex.com einar_at_dex.com
Received on Tue Feb 06 1996 - 00:00:00 CET