To ensure data security you must log to a volume other than where the database resides. You can specify the volume as an
SDISK (a serial disk, acts like a very fast tape drive) or specify it as a normal private volume and let MPE handle file sizes, etc.
(recommended). The only reason I mention SDISK  is I don't know if your application software will allow normal logging. A 2Gb
disk which will cost $250 used should suffice.

Paul Courry


On Fri, 1 Oct 1999 14:24:17 -0400, Rob Havens wrote:

>Classic HP: logged to 7970E  (don't laugh)
>
>New HP: would like to log to disk but don't want it in the public disk
>domain because don't have raid or mirroring and if lose public spindle
>then what's the purpose? (You lose the log file; unless I misunderstand
>logging to disk).
>
>Can you log to a private volume?  Thus if the log disk fails, you do a
>fulldump and replace your logging disk drive.  If system drive(s) fails,
>restore and recover.  Not very likely that both system drive and private
>drive both fail at same time.
>
>Once again, TIA
>