Neil,

An Exchange backup consists of one large object
that contains the database files and the
associated logs.

A few things that would force it directly to tape are:

1.) If there is not enough storage space in the disk
    storagepool to contain the entire backup.

2.) If you have a MAXFILESIZE parameter on the
    STORAGEPOOL so that backup object that is
    larger than a certain size, will go directly
    to tape.

3.) A management class that sends the backups
    directly to a tape storagepool.

Many customers choose number 2 or 3 above
for large database backups (like Exchange or SQL)
so that their disk pool does not get overloaded
for a single database backup.

Look into the things above to see if they
might be causing this.

Thanks,

Del

----------------------------------------------------

Del Hoobler
IBM Corporation
hoobler AT us.ibm DOT com

- Never cut what can be untied.
- Commit yourself to constant improvement.
========================================================================

>         Thank you, Exchange appears to be backing up right now. Strange,
>  though, all my other backups go to the backuppool on my TSM server's
>  disk, and get flushed from there to tape. The Exchange backup is going
>  directly to tape (I can see the tape writing while the backup is going).
>  Is there a setting to make this backup go to the same route, or is the
>  backup direct to tape for some purpose I'm not aware of?