Thanks guys. Some good responses there and yes i can now see why its a 
good idea and extremely useful for people who don't have down time.

My systems are not large enough for me to hit that problem thankfully 
and so it hasn't been a requirement of mine as yet.

I think what i am best doing is enabling hot backups but to run during 
the day when i can assume most of the jobs have finished. If a job is 
still running the information for that will be backed up on the next 
catalogue hot backup, which while will leave me exposed should 
everything hit the fan before this second hot backup has ran, will still 
leave me with the majority of good images.

Cheers

Dave Markham wrote:
> guys i'm newish to version 6 and one of the big things is it's ability 
> to run hot catalogue backups.
>
> Im on solaris with various media servers yada yada
>
> I'm just confused as to why running a hot catalogue backup, potentially 
> when other backups are running, is a good thing?
>
> I have the catalogues cold backed up when scheduled backups have 
> finished. This runs automatically.
> I also do a second catalogue backup to disk (invoked from a script 
> calling bpbackupdb -dpath) which waits until any job has finished before 
> running.
>
> I just assume this is the best way as you get an up to date latest 
> catalogue backup after the nights backups have finished.
>
> Can someone enlighten me or point me to a white paper as to why the hot 
> method is better?
>
> I'm sure it is i just can't get it into my small head why at the mo :)
>
> Cheers
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
>   

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu