Re: Hot backup

In article <4ec8pj$5g3_at_news.nyc.pipeline.com> Sameer Utrankar <utrankar_at_nyc.pipeline.com> writes:
>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 ?
>

I would think you would use hot backups for situations where transaction downtime is an issue. If you have enough time for everything to be down while everything is backed up, you might as well use cold backups. They should go faster because you don't have to worry about so many details. More archive space is required during hot backups.

If you have a situation where you need to keep read access during low usage times, but also need to backup, you still would want to do one at a time, so that in the case of a recovery you wouldn't have to recover everything - just the necessary tablespace(s). Hot backups have to be made consistent in a recovery situation - this can lead to mistakes. You also don't want to make your entire database subject to an error in one tablespace.

See the Concepts Manual - again. :)

jg

-- 
Joel Garry               joelga_at_rossinc.com               Compuserve 70661,1534
These are my opinions, not necessarily those of Ross Systems, Inc.   <> <>
%DCL-W-SOFTONEDGEDONTPUSH, Software On Edge - Don't Push.            \ V /
panic: ifree: freeing free inodes...                                   O