Re: Hot backup

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 ?

Hi Sameer,

This will also work, but you must be aware of the following :

When a tablespace is in "begin backup mode" and there is still activity going on ( insert, update, delete ) lots more of redo information is generated. This is due to the fact that not only change vectors are written to the redologs, but the complete modified blocks. This will cause a certain overhead resulting in a possible performance degradation ( more redo generated, more redos to archive etc. )

The advantage of your option is that you have the possiblity to backup the database files in parallel, whereas in the other option you have to back them up sequentially.

This is a trade-off. Up to you to deceide.

Kind Regards,
Alain Received on Sun Jan 28 1996 - 00:00:00 CET