Richard, Paul,

Thanks for the tips, I'll kep an eye on my tape drives, and on DB disk
activity !

Emil,

> For big storage pools that can take quite some time, and especially if
running at the same time as expiration or other DB heavy activity.

In my case, the storage pool size is approximatively 1,4 TB, would it
make sense for you, that this computational phase lasts 3 hours on a 6h0
system, having 2 cpu and 2 GB RAM ? I find it really looong !

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group     |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01       | 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



-----Original Message-----
From: Richard Sims [mailto:rbs AT BU DOT EDU] 
Sent: Tuesday, 01 April, 2003 14:03
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Copy job "freezed"


>Richard,
>
>That would make sense, if the job was "freezing" in the middle of the 
>copies, but apparently, it just waits a while before starting to write 
>the first bit of data to tape, and then goes fine till the end !

Then that speaks to a defective tape (or even drive) problem, as I
suggested.  That is, the drive is having trouble mounting the tape.
Observing the drive during one of these instances could be illuminating.

  Richard Sims, BU