hi,guys:

   maybe it is mounting tape . but cannt it  find a request tape , perhaps  you  need to manual

assistance.  do you check the status of device monitor  .

best regards

Well you could check the below and let us know if it helps

1.Are you using only one storage unit or do you have more than one.

Reason: If you have more than one check if there is already a job running for the client that you are trying to test. may be the option to run simultaneous jobs for the client is not permitted.

2. As mentioned above check the status of the drive and see if it is in AVR mode for which manual intervention might be required

3. Check and see if ltid daemon is running

4. In your policy attributes check if you have specified to use specific storage or Any available

5. When you say nothing is showing in the detail page of the job do you mean it is completly blank

6. Check the storage unit properties and see if you have allocated "X" number of drive for backup? i.e Maximum Cuncurrent write drives is not "0". Make sure you never put a figure more than the total number of drives available coz it will lead to even more problem.

7. If you are using disk storage check if the maximum concurrent job is not equal to "0"

Etrack Incident = ET960587
Associated Primary Etrack = ET860114
Titan cases: 240-288-856

Description:
Jobs were remaining queued even though there were drives available in
the master server.

The above taken from 5.1 MP7 release notes.

I would recommend you are at 5.1 MP7 on both master and media.

This does not however say it is a fix other than its been documented.

Find and download NetBackup Enterprise Server 5.1 Maintenance Pack 7 (MP7) from this complete listing of 5.1 MP7 patches.
http://seer.entsupport.symantec.com/docs/303010.htm

Both master and mdia server 5.1 MP7. still same problem

bash-2.03$ /nas/usr/sbc/sudo/bin/sudo /usr/openv/volmgr/bin/vmoprcmd

                                PENDING REQUESTS

                                     <NONE>

                                  DRIVE STATUS

Drv Type   Control  User      Label  RecMID  ExtMID  Ready   Wr.Enbl.  ReqId
  0 hcart    ACS                -                     No       -        -
  1 hcart    ACS                -                     No       -        -
  2 hcart    ACS                -                     No       -        -
  3 hcart    ACS                -                     No       -        -
  4 hcart    ACS                -                     No       -        -
  5 hcart    ACS                -                     No       -        -
  6 hcart    ACS    root       Yes   KZ1566  KZ1566   Yes     Yes        0
  7 hcart    ACS    root       Yes   KZ3951  KZ3951   Yes     Yes        4
  8 hcart3   TLD                -                     No       -        -
  9 hcart3   TLD                -                     No       -        -
 10 hcart3   TLD                -                     No       -        -
 11 hcart3   TLD                -                     No       -        -
 12 hcart3   TLD                -                     No       -        -
 13 hcart3   TLD                -                     No       -        -

                             ADDITIONAL DRIVE STATUS

Drv DriveName            Shared    Assigned        Comment
  0 D-0-0-10-5            Yes      -
  1 D-0-0-10-8            Yes      -
  2 D-0-0-10-2            No       -
  3 D-0-2-10-6            Yes      -
  4 D-0-0-10-4            No       -
  5 D-0-0-10-3            Yes      -
  6 D-0-2-9-6             Yes       -
  7 D-0-1-10-6            Yes      -
  8 ks320_2_28            No       -
  9 ks320_2_26            No       -
 10 ks320_2_27            No       -
 11 ks320_2_29            No       -
 12 ks320_2_30            No       -
 13 ks320_2_32            No       -
 

Hi Friends

backup queued from 5 hours.after that backup fail with error  "the required storage unit is unavailable(219)". Please help.

Please let me know how you have configured the drives. Did you use the GUI or tpconfig ?

May be you can try to reconfigure your tape unit once more and check if the error repeats.

Please have a look at this technote.

http://seer.entsupport.symantec.com/docs/274544.htm

it normay happed
just check it is this policy have diffrent  retantion level

some time it's happen i have faced same problem

& that was the solution i get..

Thanks..