Veritas-bu

Re: [Veritas-bu] Not all drives appear to be used

2009-03-27 08:01:49
Subject: Re: [Veritas-bu] Not all drives appear to be used
From: "WEAVER, Simon \(external\)" <simon.weaver AT astrium.eads DOT net>
To: <VERITAS-BU AT mailman.eng.auburn DOT edu>
Date: Fri, 27 Mar 2009 11:58:33 -0000
Just one question on this....

Doesnt "nbrbutil" release the locks when the Server is rebooted?

Simon

-----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
mcw012765
Sent: Friday, March 27, 2009 10:52 AM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Not all drives appear to be used


I tried all of the suggestions and still had the problem.  I contacted
Symantec and we got it fixed.  Here is a summary:

ISSUE REPORTED: Not all 10 drives are in use at any given time backups
will use only 8 drives randomly. But it will always be any 2 drives out
of the 10 that won't be used.

INITIAL INVESTIGATION: 
-Max jobs per client is set to 99 under Host Properties >> Master Server
>> Global Attributes -Max concurrent drives is set to 10 under Storage
Units >> Problem Storage Unit.

TROUBLESHOOTING:
-Ran robtest (s d) to check if the two drives already had a tape stuck
in them. No.
-Guessing that it is an nbrb allocation issue.
-We ran <Install Drive>:\Veritas\netbackup\bin\admincmd\nbrbutil -dump
to check the point in time MDS Allocations within EMM.
-Saw two orphaned allocations without any attributes matching current
allocations.

MdsAllocation allocationKey=7191130 jobType=16 mediaKey=4002098
mediaId=002033 driveKey=0 driveName= drivePath= stuName=
masterServerName=mfbback01 mediaServerName=mfbback01 ndmpTapeServerName=
diskVolumeKey=0 mountKey=0 linkKey=0 fatPipeKey=0 scsiResType=0
serverStateFlags=0

MdsAllocation allocationKey=7191132 jobType=16 mediaKey=4000992
mediaId=002016 driveKey=0 driveName= drivePath= stuName=
masterServerName=mfbback01 mediaServerName=mfbback01 ndmpTapeServerName=
diskVolumeKey=0 mountKey=0 linkKey=0 fatPipeKey=0 scsiResType=0
serverStateFlags=0

-Looks like nbrb is holding up further resource allocation due to these
orphaned alloc holds.

-Released the holds by running nbrbutil -releasemds <allocation key as
underline above> -Verified last written date on one of the media by
running nbemmcmd -listmedia -mediaid 002033. It was dating back to 30th
January 2009.
-This is roughly the time frame when the issue started.
-After releasing the holds we are now able to fire up jobs on them
drives.


Thanks to everyone for your suggestions.  I think I am seeing
improvement from setting the max jobs higher.

+----------------------------------------------------------------------
|This was sent by mweathe AT fbinsmi DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------


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

This email (including any attachments) may contain confidential
and/or privileged information or information otherwise protected
from disclosure. If you are not the intended recipient, please
notify the sender immediately, do not copy this message or any
attachments and do not use it for any purpose or disclose its
content to any person, but delete this message and any attachments
from your system. Astrium disclaims any and all liability if this
email transmission was virus corrupted, altered or falsified.
-o-
Astrium Limited, Registered in England and Wales No. 2449259
Registered Office:
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu