Veritas-bu

[Veritas-bu] 196 error codes

2002-10-08 14:52:03
Subject: [Veritas-bu] 196 error codes
From: scott.kendall AT abbott DOT com (scott.kendall AT abbott DOT com)
Date: Tue, 8 Oct 2002 13:52:03 -0500
usually...

However, you have to keep multiplexing in mind.  If two jobs are queued and an
mpx stream becomes available on an active drive and one of the queued jobs
could join in to fill the available mpx stream (same retention, etc.) it will
do so regardless of priority on the other queued job.

example:  You have enough jobs launch at 8pm to keep all your drives busy
throughout the night.  These jobs all have the same retention and are all
capable of mpx'ing.  At 9pm several jobs get queued that have the highest
priority of any jobs in your environment.  These high priority jobs won't run
until a drive becomes available... and when that happens they will get
priority.  But these lower priority queued jobs will keep going active one at
a time as the mpx jobs finish on the drives and these take their places.  You
could potentially do this through the night until your high priority jobs fail
with 196, while several of the lower priority jobs finish without problems.


- Scott



                                                                                
                                                   
                    "Bob Grabbe"                                                
                                                   
                    <GRABBEB AT dominos DOT com>                To:     
<browndav AT bronsonhg DOT org>, <veritas-bu AT mailman.eng.auburn DOT edu>     
                    Sent by:                             cc:                    
                                                   
                    veritas-bu-admin AT mailman DOT eng.        Subject:     
Re: [Veritas-bu] 196 error codes                             
                    auburn.edu                                                  
                                                   
                                                                                
                                                   
                                                                                
                                                   
                    10/08/2002 09:56 AM                                         
                                                   
                                                                                
                                                   
                                                                                
                                                   




Check the priority of the jobs that fail against the ones that run in
place of them also. If two jobs are queued, and the one that is last in
the queue has a higher priority, it will start frst.

Robert Grabbe
Dominos Pizza LLC
734-930-3703
grabbeb AT dominos DOT com

>>> "David Brown" <browndav AT bronsonhg DOT org> 10/8/02 10:27:03 AM >>>
For some reason, I have been suddenly bombarded with failures resulting
in the error code 196, client backup was not attempted because backup
window closed.  I'm trying to track down what is causing this, as the
clients that this is happening to have been scheduled to run before any
other clients or policies kick in.

I understand that this error can be generated if a backup needs a drive
and none are available during it's window, but I don't see how this
could happen if the backup has already started with media in the drive.
Is there some time limit somewhere that I might need to change to allow
for longer run times?

Any and all help is appreciated, thanks!
Dave

David Brown
McKesson Information Solutions
Bronson Methodist Hospital
browndav AT bronsonhg DOT org
(269) 341-7054 : office
(269) 217-0743 : cell
(269) 212-0273 : pager

Confidentiality Notice: This e-mail message, including any attachments,
is
for the sole use of the intended recipient(s) and may contain
confidential
and privileged information.  Any unauthorized review, use, disclosure
or
distribution is prohibited.  If you are not the intended recipient,
please
contact the sender by reply e-mail and destroy all copies of the
original
message.


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu





<Prev in Thread] Current Thread [Next in Thread>