Re: Hot Backups...am I off base??

Having been a SysAdmim I can see your co-workers point. If you were operating in an environment where disk resources are scarce then I would have to agree with them. In the case you described, the hot backup files are a subset of the full system backup and so are redundant.

If you have enough disk, then I would keep the hot backup available on disk (the best case on a different controller and media from current database files). I do not like having to wait for tape if I need to perform a restore. If you really have a lot of excess disk, I would schedule exports for all application schemas as well (different controller and media as well). Also handy to have in case tragedy strikes.

SC

> I am writing Korn shell scripts to create nightly hot backups on UNIX
> (SUN Solaris.)
>
> Another "DBA" (ex-System Admin I might add) recommends 1. making a hot
> backup of the database, 2. make a system backup, 3. then DELETE the
> hot backup we just created relying only on the system backup with a
> verify option. He say this is good for housekeeping on the system.
>
> I highly opposed this scenario. There is plenty of space available on
> the system for the backup files so that is not an issue. I'd rather
> have both.. the system backup and the hot backup on disk drives.
>
> Am I off my rocker not to rely solely on the system backup?
>
> Would any of you use this strategy in production???
>
> Thanks in advance!
> Val
> Valerie H. Webber
> Management Systems Designers, Inc
> Valerie.H.Webber_at_m1.irs.gov
Received on Fri Aug 04 2000 - 16:11:37 CDT