ec2009

Are these 4 ACS drives the only devices on the media server?

How many Storage Units configured for this media server?

We see the following error in /var/adm/messages:

Dec  3 11:52:16 asprd434 tldd[9163]: [ID 886097 daemon.error] daemon terminating because no devices are configured, tldcd has not been started

This indicates that there should be a direct-attached TLD robot with drive(s) on this media server.

What does 'bpstulist -label asprd434-ebr_lto -U' show?

bpstulist -label asprd434-ebr_lto -U

Label:                asprd434-ebr_lto
Storage Unit Type:    Media Manager
Host Connection:      asprd434-ebr.aldc.att.com
Number of Drives:     2
On Demand Only:       no
Max MPX/drive:        4
Density:              hcart - 1/2 Inch Cartridge
Robot Type/Number:    ACS / 0
Max Fragment Size:    2048 MB

Is master/EMM server aware of the UP state of the drives?

What does the following command on Master show?

vmoprcmd -h asprd434-ebr.aldc.att.com -d ds

Please also post 'MDS allocations' section of 'nbrbutil -dump'. 

vmoprcmd -h asprd434-ebr.aldc.att.com -d ds

                                  DRIVE STATUS

Drv Type   Control  User      Label  RecMID  ExtMID  Ready   Wr.Enbl.  ReqId
  0 hcart3   ACS                -                     No       -         0
  1 hcart3   ACS                -                     No       -         0
  2 hcart  DOWN-ACS             -                     No       -         0
  3 hcart    ACS                -                     No       -         0

when i try to reset and up the drive..

 vmoprcmd -reset 2
Unknown drive name
 vmoprcmd -up 2
Invalid Drive Number
 

Are you issuing -reset and -up from master on from media server?

If master, remember to add -h <hostname>.

You need to check messages file to see what is wrong with drive(s). 
Find DOWN in messages file, then look at the lines above that to see what caused this.

This could be part of the problem:

 timed out after waiting 901 seconds for ready, drive (0,8,1,8)

Some issue between OS and device?

Try to troubleshoot outside of NBU - mount tape in drive using ACSLS.

Check status from OS:

mt -f /dev/rmt/## status

thanks for reminding..i gave cmd from media server and it worked and drive also came up..

Problem which i think is in the tape mounting...

2/05/2012 18:45:56 - requesting resource asprd434-ebr_lto
12/05/2012 18:45:56 - requesting resource asprd212.aldc.att.com.NBU_CLIENT.MAXJOBS.asprd434-ebr.aldc.att.com
12/05/2012 18:45:56 - requesting resource asprd212.aldc.att.com.NBU_POLICY.MAXJOBS.asprd434
12/05/2012 18:46:04 - granted resource  asprd212.aldc.att.com.NBU_CLIENT.MAXJOBS.asprd434-ebr.aldc.att.com
12/05/2012 18:46:04 - granted resource  asprd212.aldc.att.com.NBU_POLICY.MAXJOBS.asprd434
12/05/2012 18:46:04 - granted resource  GX0467
12/05/2012 18:46:04 - granted resource  A00_LI001_LS8_D08_L3
12/05/2012 18:46:04 - granted resource  asprd434-ebr_lto
12/05/2012 18:46:05 - started process bpbrm (pid=19317)
12/05/2012 18:46:06 - connecting
12/05/2012 18:46:06 - connected; connect time: 0:00:00
12/05/2012 18:47:07 - mounting GX0467

generally it fails after this.

Try to troubleshoot outside of NBU - mount tape in drive using ACSLS--for this we did try to mount and unmount tape..and it worked fine.

Did you confirm that OS is seeing tape mount with 'mt -f /dev/rmt/xx status'?

Shekaib,

did you ever have the succuess full backup with this Drives?

Did you set the access control in the ACLSLS servers?

do you have 4 Drives connected in OS level?

 mt -f /dev/rmt/0cbn status
/dev/rmt/0cbn: write protected or reserved.