Yiannakis

One thought... you should send the meta data to a
disk only storage pool. These meta data objects are always
very small (less than 100K)... and to put them to a
tape is not good for performance. You do that by binding
the meta objects to a management class that points to
a disk only storage pool. That is done using the INCLUDE option.
For example (from the sample options files):

   INCLUDE "\...\meta\...\*"     SqlDbMetaMgmtClass

Where "SqlDbMetaMgmtClass" is the management class that
you set up with a disk only storage pool.
Take a look at the User's Guide for more details on
setting this up. It is in a section titled:
"Tivoli Storage Manager policy requirements and recommendations"

Thanks,

Del

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

> what I can see from the accounting log is that the backup has an
enormous
> amount of media wait. There are two records for that backup which I
> interprete as the two mount points. One mount point should be for the
tape
> that has the meta data and the other mount point for the data itself.
> Under normal conditions the first record has as many seconds as the
backup
> duration while the other record has 0 seconds.
> When I experience the delay the second record has as many seconds
accounted
> for as the first record.
>
> Of course what I don't understand is why on the same client on the same
day
> I get different responses for two databases.
>
> Any thoughts are welcome.