NBU status: 830, EMM status: No drives are available

[halogen]

Hello community,

We are having an issue with doing restores at the moment, an example log can be shown below.

11/25/2014 15:17:20 - begin Restore
11/25/2014 15:17:21 - number of images required: 1
11/25/2014 15:17:22 - media needed: MF071A
11/25/2014 15:17:22 - media needed: MF036A
11/25/2014 15:17:26 - restoring from image gandalf-backup_1194765667
11/25/2014 15:17:26 - Info bpbrm (pid=7049) backup is the host to restore to
11/25/2014 15:17:27 - Info bpbrm (pid=7049) telling media manager to start restore on client
11/25/2014 15:17:27 - Info bpbrm (pid=7049) spawning a brm child process
11/25/2014 15:17:27 - Info bpbrm (pid=7049) child pid: 7057
11/25/2014 15:17:27 - connecting
11/25/2014 15:17:27 - Info bpbrm (pid=7057) start tar on client
11/25/2014 15:17:27 - Info tar (pid=7063) Restore started.
11/25/2014 15:17:27 - connected; connect time: 0:00:00
11/25/2014 15:17:27 - requesting resource MF071A
11/25/2014 15:17:27 - Error nbjm (pid=4965) NBU status: 830, EMM status: No drives are available
11/25/2014 15:17:27 - Error nbjm (pid=4965) NBU status: 830, EMM status: No drives are available
11/25/2014 15:17:28 - Error bptm (pid=7052) NBJM returned an extended error status: No drives are available (2001)
11/25/2014 15:17:33 - Info bpbrm (pid=7049) got ERROR 252 from media manager
11/25/2014 15:17:33 - Info bpbrm (pid=7049) terminating bpbrm child 7057 jobid=387452
11/25/2014 15:17:33 - restored from image gandalf-backup_1194765667; restore time: 0:00:07
11/25/2014 15:17:33 - Warning bprd (pid=7030) Restore must be resumed prior to first image expiration on INFINITY      
11/25/2014 15:17:33 - end Restore; elapsed time 0:00:13
Failed to get status code information (2826)

Aditional info:

Issue started after we relocated server room, everything was unplugged/powered down then setup the same.

Media ID: MF071A, Barcode: MF071A, Density: hcart, Access Mode: Read,

/usr/openv/volmgr/bin/tpconfig -d
Id  DriveName           Type   Residence
      Drive Path                                                       Status
****************************************************************************
0   TD01                 hcart  TLD(0)  DRIVE=1
      /dev/nst0                                                        UP
1   TD02                 hcart  TLD(0)  DRIVE=2
      /dev/nst1                                                        UP

Currently defined robotics are:
  TLD(0)     robotic path = /dev/sg2

EMM Server = backup

NetBackup is running on a linux server and I'm running the Admin console from my Windows 7 Pro PC.

And if it makes any difference, it throws up the errors before tapes are even inserted into the drives, and again once inserted and imported.

Any help would be much appreciated.

Thanks!

[revarooo]

You say you reset the robot, but what about the drives? Have you power cycled them?

[Marianne]

Log folders do not exist by default. 
They must be created under /usr/openv/netbackup/logs.
bprd needs a restart for log to take effect. 

sazz has a good point.
Are backups working?

[Nicolai]

Is the backup you are trying to restore old ?

Created:                        11/05/2007 13:31
Time Assigned:                  11/09/2007 16:40
First Mount:                    11/09/2007 16:41
Last Mount:                     05/09/2008 11:58
Volume Expiration:              -
Data Expiration:                INFINITY
Last Written:                   11/12/2007 06:36
Last Read:                      05/09/2008 11:58

Is the drive type you are using now the same as in 2007 ?. Both LTO1, 2, 3 ,4 ,5 & 6 can be configured in Netbackup as HCART, but it does not mean they are mount compatible.

[Marianne · Accepted solution]

I have just noticed the following (not the cause of this issue):

CLIENT_NAME = bilbo
CLIENT_NAME = gandalf-backup
CLIENT_NAME = larry
CLIENT_NAME = morris
CLIENT_NAME = haldir

The ONLY CLIENT_NAME in bp.conf on a master must be itself.
Please delete ALL of the above entries and just add one CLIENT_NAME entry:
CLIENT_NAME = backup

Please ensure that all of these log folders exist on the master (which is also the media server here):
bprd bptm and bpbrm.
Copy log files in above folders to .txt files (e.g. bprd.txt) and upload as File attachments.

[halogen]

Hi Marianne

Thanks for the points, this actually resolved our issue

We removed CLIENT_NAME and only had gandalf-backup (OUR SOURCE for the backup), and CLIENT_NAME = backup

It seems it might have been us trying to use CLIENT_NAME = haldir.mf.com.au for the RESTORE location, which the system seems to know nothing about at the moment (DNS issues where it cannot resolve that link, but it points back to itself as 'backup')

Once we chose the correct restore location of 'backup' as the client_name, it succesfully picked up both tapes and restored the files

See succesful log

Thank you!

12/02/2014 15:27:08 - begin Restore
12/02/2014 15:27:08 - number of images required: 1
12/02/2014 15:27:08 - media needed: MF071A
12/02/2014 15:27:08 - media needed: MF036A
12/02/2014 15:27:12 - restoring from image gandalf-backup_1194765667
12/02/2014 15:27:13 - Info bpbrm (pid=28273) backup is the host to restore to
12/02/2014 15:27:13 - Info bpbrm (pid=28273) telling media manager to start restore on client
12/02/2014 15:27:13 - Info bpbrm (pid=28273) spawning a brm child process
12/02/2014 15:27:13 - Info bpbrm (pid=28273) child pid: 28287
12/02/2014 15:27:13 - connecting
12/02/2014 15:27:13 - Info bpbrm (pid=28287) start tar on client
12/02/2014 15:27:13 - Info tar (pid=28298) Restore started.
12/02/2014 15:27:13 - connected; connect time: 0:00:00
12/02/2014 15:27:14 - Info bptm (pid=28282) Waiting for mount of media id MF071A (copy 2) on server backup.
12/02/2014 15:27:14 - started process bptm (pid=28282)
12/02/2014 15:27:14 - mounting MF071A
12/02/2014 15:27:14 - Info bptm (pid=28282) INF - Waiting for mount of media id MF071A on server backup for reading.
12/02/2014 15:27:13 - requesting resource MF071A
12/02/2014 15:27:14 - granted resource  MF071A
12/02/2014 15:27:14 - granted resource  TD02
12/02/2014 15:27:45 - mounted MF071A; mount time: 0:00:31
12/02/2014 15:27:45 - Info bptm (pid=28282) MF071A
12/02/2014 15:27:46 - Info bptm (pid=28282) INF - Waiting for positioning of media id MF071A on server backup for reading.
12/02/2014 15:27:46 - positioning MF071A to file 41
12/02/2014 15:29:52 - positioned MF071A; position time: 0:02:06
12/02/2014 15:29:52 - begin reading
12/02/2014 15:30:35 - Info bptm (pid=28282) Waiting for mount of media id MF036A (copy 2) on server backup.
12/02/2014 15:30:35 - started process bptm (pid=28282)
12/02/2014 15:30:35 - mounting MF036A
12/02/2014 15:30:35 - Info bptm (pid=28282) INF - Waiting for mount of media id MF036A on server backup for reading.
12/02/2014 15:30:35 - current media MF071A complete, requesting next media TD02:MF036A
12/02/2014 15:30:35 - granted resource  MF036A
12/02/2014 15:30:35 - granted resource  TD01
12/02/2014 15:31:08 - mounted MF036A; mount time: 0:00:33
12/02/2014 15:31:08 - Info bptm (pid=28282) MF036A
12/02/2014 15:31:08 - Info bptm (pid=28282) INF - Waiting for positioning of media id MF036A on server backup for reading.
12/02/2014 15:31:08 - positioning MF036A to file 1
12/02/2014 15:31:08 - positioned MF036A; position time: 0:00:00
12/02/2014 15:32:19 - Info tar (pid=28298) done. status: 0
12/02/2014 15:32:19 - Info tar (pid=28298) done. status: 0 - the requested operation was successfully completed
12/02/2014 15:32:19 - end reading; read time: 0:02:27
12/02/2014 15:32:20 - Info bpbrm (pid=28273) media manager for backup id gandalf-backup_1194765667 exited with status 0: the requested operation was successfully completed
12/02/2014 15:32:20 - restored from image gandalf-backup_1194765667; restore time: 0:05:08
12/02/2014 15:32:20 - end Restore; elapsed time 0:05:12
the requested operation was successfully completed  (o)