Hi
It seems that Symantec considers 134 as a 'feature' rather than a problem.
Here's an 'In-depth Troubleshooting Guide for Exit Status Code 134', which is
merely an explanation, rather than a fix.
http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise_Server/277622.pdf
We also see that a tape drive is not assigned to a media server for the
duration of a job. If a tape is filled up and dismounted in order to mount
another tape, another media server that has queued jobs will 'grab' the drive
as soon as the 'SCSI_RELEASE' is registered. Media server 1 will keep on trying
to use the same drive and keep on requeue'ing the job with status 134...
We have a large customer that is now moving away from SSO and going back to
dedicated drives because of this irritation.
Regards
Marianne
-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu]On Behalf Of Paul
Keating
Sent: 06 September 2006 08:30 PM
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] Q about status 134
So I've been testing in my lab to determine what happens when several
storage units "over subscribe" the available number of drives.
So basically, 3 drives, 2 STUS, each STU configured to use "max 2
drives".
So the STUs are oversubscribed by "1".
It seems jobs won't "queue", but re-try, over and over and over, every
approx 15 seconds, each time throwing a status 134, then "requeuing" for
a couple seconds, then retrying.
Is it possible to get the re-trying job to just "queue" properly and
wait untill there is a drive available?
The behavious right now, seems kind of dirty.
Is this what happens when you have drives shared with SSO?
Ie. Jobs assigned to a given media server behave like this from the time
the window opens, untill a drive is available for that media server?
Paul
DISCLAIMER:
This message may contain information which is confidential, private or
privileged in nature. If you are not the intended recipient, you may not
peruse, use, disseminate, distribute or copy this message or file which is
attached to this message. If you have received this message in error, please
notify the sender immediately by e-mail, facsimile or telephone and thereafter
return and/or destroy the original message.
Any views of this communication are those of the sender except where the sender
specifically states them to be those of Faritec (Holdings) Limited (Faritec)
and/or any of its subsidiaries including (but not limited to) Faritec
Enterprise Solutions (Proprietary) Limited, Faritec Strategic IT Services
(Proprietary) Limited, Faritec Contracting (Proprietary) Limited, Ebis and/or
any of its subsidiaries.
Please note that the recipient must scan this e-mail and any attached files for
viruses and the like. While we do everything possible to protect information
from viruses, Faritec accepts no liability of whatever nature for any loss,
liability, damage or expense resulting directly or indirectly from the access
and/or downloading of any files which are attached to this e-mail message.
|
