On Tuesday, Apr 1, 2003, at 16:47 Australia/Sydney, PAC Brion Arnaud wrote:
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 ! Thanks anyway ;-)
Sounds like database operations to me - building the list of aggregates and sorting for minimal tape mounts... can be a reasonably intensive operation. Check the activity on your DB volumes during the "freeze".
-----Original Message----- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Monday, 31 March, 2003 18:46 To: [EMAIL PROTECTED] Subject: Re: Copy job "freezed"
Could anybody explain me why I consistently see "backup stg" jobs "freezing" ? What happens is that the job begins, but thereafter hangs for a while, doing nothing at all, and suddenly starts copying data on tape. ...
A common cause is tape defects or un-cleaned drives which make for time-consuming retries in reading the input tape or writing the output tape.
Richard Sims, BU
-- Paul Ripke Unix/OpenVMS/TSM/DBA 101 reasons why you can't find your Sysadmin: 68: It's 9AM. He/She is not working that late. -- Koos van den Hout
