Veritas-bu

Re: [Veritas-bu] Vault, waiting for resource

2010-10-14 12:37:49
Subject: Re: [Veritas-bu] Vault, waiting for resource
From: <Rusty.Major AT sungard DOT com>
To: Nic Solomons <Nic.Solomons AT attenda DOT net>
Date: Thu, 14 Oct 2010 11:35:36 -0500

Ahh yes, good one Nic, I had forgot about that. Here is a blog entry with more details:

http://netbackup.wordpress.com/2009/03/22/media-in-use-when-it-really-isnt/

Rusty Major, MCSE, BCFP, VCS ▪ Sr. Storage Engineer ▪ SunGard Availability Services ▪ 757 N. Eldridge Suite 200, Houston TX 77079 ▪ 281-584-4693
Keeping People and Information Connected® ▪ http://availability.sungard.com/
P Think before you print
CONFIDENTIALITY:  This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited.  If you received this e-mail in error, please notify the sender and delete this e-mail from your system.


Nic Solomons <Nic.Solomons AT attenda DOT net>
Sent by: <veritas-bu-bounces AT mailman.eng.auburn DOT edu>

10/14/2010 06:02 AM

To
"veritas-bu AT mailman.eng.auburn DOT edu" <veritas-bu AT mailman.eng.auburn DOT edu>
cc
Subject
Re: [Veritas-bu] Vault, waiting for resource





I don't use Vault, so this may not be relevant... BUT

With jobs that are hanging pending a specific resource request (that doesn't show up in resource querying lists), I use nbrbutil to break the MDS allocation.

nbrbutil -dump for a list of outstanding resource broker requests (in progress & pending), and then nbrbutil -releaseMDS <MDS ID> to clear out the one thats causing the log-jam.

Cheers,
Nic

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Nate Sanders
Sent: 13 October 2010 16:55
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Vault, waiting for resource

It appears the child duplicate job restarted. So I think I am good. Any
one have any input on what to do to avoid these day long freezes that
occur when a Tape because stuck waiting for resource?

On 10/13/2010 10:28 AM, Nate Sanders wrote:
>  Oct 12, 2010 5:38:58 PM - awaiting resource 400152. Waiting for resources.
>
> My Vault Duplicate child job has now had this same error with a
> different Media ID two weeks in a row. Last week this was not noticed
> until after Vault Eject failed . This week I was watching it and just
> saw this come up this morning. I checked available_media and the media
> ID is listed in use with other data. So how do I get the vault to let go
> of this tape and continue on? I can't afford to restart the whole job.
> Can I kill the child duplicate job and for the parent to continue?
>

--
Nate Sanders            Digital Motorworks
System Administrator      (512) 692 - 1038




This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


The information contained in this e-mail and its attachments is confidential.
It is intended only for the named address(es) and may not be disclosed to anyone else without Attenda's consent.


_______________________________________________
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>