Drive Issue

[H_Sharma]

Hi Experts,

I have oracle SL 150 Drive in our setup and it has 8 drives. I had checked the drive status in Library Console it shows all drives have tapes.

If i check from Netbackup it shows the attached information. We have 17 jobs in queue and 18 are active.

1:- I dont understand how to check whether my 8 drives are writing to media or not.

2:-How could I set all drives should be busy and no one should be free while jobs are running.

Device Robot Drive       Robot                    Drive     Device         Second
Type     Num Index  Type DrNum Status  Comment    Name      Path           Device Path
robot      0    -    TLD    -       -  -          -     
  drive    -    0 hcart3    1      UP  -          Drive000  /dev/rmt/0cbn
  drive    -    1 hcart3    2      UP  -          Drive002  /dev/rmt/2cbn
  drive    -    2 hcart3    3      UP  -          Drive001  /dev/rmt/1cbn
  drive    -    3 hcart3    4      UP  -          Drive003  /dev/rmt/3cbn
  drive    -    4 hcart3    5      UP  -          Drive004  /dev/rmt/4cbn
  drive    -    5 hcart3    6      UP  -          Drive007  /dev/rmt/6cbn
  drive    -    6 hcart3    7      UP  -          Drive005  /dev/rmt/5cbn
  drive    -    7 hcart3    8      UP  -          Drive006  /dev/rmt/7cbn

Pls help.

[H_Sharma]

I have also a question why is it showing only 4 drives with media id and rest 4 are free. While many jobs are in queue?

[Marianne]

Firstly - check Job Details of queued jobs - you will see the reason for jobs being queued.
Please copy all text and show it here.

Device Monitor shows 5 drives active.

If the library console shows tapes in all drives, there is a problem. Three of the drives have tapes that NBU does not know about. You will have to manually eject those drives and return tapes to slots.

Also check NBU resource allocations for possible 'orphaned' allocations.

Run 'nbrbutil -dump' from cmd.
Post the bottom section that shows MDS allocations.

[H_Sharma]

Hi Marianne,

1 Job..... That is queued.

7/30/2014 1:32:33 PM - Info nbjm(pid=7792) starting backup job (jobid=54757) for client tn, policy esp, schedule cumulative_incremental  
7/30/2014 1:32:33 PM - Info nbjm(pid=7792) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=54757, request id:{0EDD9697-1678-46A4-B05B-BB5892B2AA62})  
7/30/2014 1:32:33 PM - requesting resource Any
7/30/2014 1:32:33 PM - requesting resource TN.NBU_CLIENT.MAXJOBS.tn
7/30/2014 1:32:33 PM - requesting resource TN.NBU_POLICY.MAXJOBS.esp
7/30/2014 1:32:33 PM - awaiting resource Any - No drives are available

2 Job.7/30/2014 1:27:02 PM - Info nbjm(pid=7792) starting backup job (jobid=54752) for client rmgdb01p-bkp, policy RMAN_Roaming_Sol, schedule Roaming_RMAN_FULL  
7/30/2014 1:27:02 PM - Info nbjm(pid=7792) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=54752, request id:{6D868C29-ECD0-4963-A38D-830C64127E52})  
7/30/2014 1:27:02 PM - requesting resource TN-hcart3-robot-tld-0
7/30/2014 1:27:02 PM - requesting resource TN.NBU_CLIENT.MAXJOBS.rmgdb01p-bkp
7/30/2014 1:27:02 PM - awaiting resource TN-hcart3-robot-tld-0 - No drives are available
7/30/2014 1:28:00 PM - awaiting resource TN-hcart3-robot-tld-0 Reason: Robotic library is down on server, Media Server: TN, 
     Robot Number: 0, Robot Type: TLD, Media ID: N/A, Drive Name: N/A, 
     Volume Pool: RMAN_Pool, Storage Unit: TN-hcart3-robot-tld-0, Drive Scan Host: N/A
    
7/30/2014 1:28:28 PM - awaiting resource TN-hcart3-robot-tld-0 - No drives are available
7/30/2014 1:29:02 PM - Info nbjm(pid=7792) Waiting in NetBackup scheduler work queue on server tnm   
7/30/2014 1:29:10 PM - awaiting resource TN-hcart3-robot-tld-0 Reason: Robotic library is down on server, Media Server: TN
     Robot Number: 0, Robot Type: TLD, Media ID: N/A, Drive Name: N/A, 
     Volume Pool: RMAN_Pool, Storage Unit: TN-hcart3-robot-tld-0, Drive Scan Host: N/A
    

[RiaanBadenhorst]

7/30/2014 1:29:10 PM - awaiting resource TN-hcart3-robot-tld-0 Reason: Robotic library is down on server, Media Server: TN

Recycle the service on this media server.

[INT_RND · Accepted solution]

A note about the device monitor:

1. The drive information is not live. It has a refresh period and the information displayed is whatever was sent from the library during the last query.

2. There are many tape states. Here is an example of tape activity:

Tape move, tape load, rewind, seek, read header, seek, read header, seek, write data, rewind, eject, tape move

The library console will have more up-to-date information about drive activity but it is also not real-time. Each console will have a different level of verbosity. The only way to really know what a drive is doing is to go watch it and listen to it. This is a limitation of the library firmware. YMMV