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

Halogen, stop all jobs from running then type:

nbrbutil -resetAll

Note that this command will kill any jobs currently running.

This will clear out ALL allocations as the drives may be reserved.

If that fails to work, reset the drives by power cycling them (physically pull the power out of them).

Please verify MF071A is really a HCART media type by running:

nbemmcmd  -listmedia -mediaid MF071A

Look for the "Media Type". The error usally show when there is no compatible densities configured. E.g media type is HCART1 but drives are configured as HCART2

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

After relocation have you setup the device configuration again? What exact steps you took?

Restart the NBU services once if you have just unplugged and plugged everything.

provide the output of nbemmcmd -listhosts -verbose

If you simply relocated and nothing changed then nothing should need reconfiguring, so sounds like youve misconfigged it (physically) and/or then tried to fix it (possibly unneccesarily) with some netbackup reconfiguration,  so I would check and double check the connections, check the hcart logic vs drive logic as Nicolai alluded to. Moving it from A to B and reassembling as was cannot make Netbackup behave differently.

Maybe theres something else been added to the mix?

Jim

Cannot be too much of an emergency... No response in many hours....

Hi all,

Thanks for your response, I'm going to try the suggestions and get back to you all.

We are over in Aus so I was just leaving the office when I posted this.

Thanks

Halogen

Hi mate

Thanks for your response

We stopped all active jobs in the queue and the status was all "Done"

We then ran nbrbutil -resetAll and assume it succesfully completed (there was no output in the temrinal, just returned to the same path when the command was ran).

Once we then attempted another restore, the following log output:

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

Hiya mate,

We've reset the robot, NBU server many times, each time everything connects up fine.

Here is the output of the nbemmcmd -listhosts -verbose command

[root@backup admincmd]# /usr/openv/netbackup/bin/admincmd/nbemmcmd -listhosts -verbose
NBEMMCMD, Version:7.1.0.4
The following hosts were found:
backup
        MachineName = "backup"
        FQName = "backup.mf.com.au"
        MachineDescription = ""
        MachineNbuType = server (6)
backup
        ClusterName = ""
        MachineName = "backup"
        FQName = "backup.mf.com.au"
        GlobalDriveSeed = "VEND:#.:PROD:#.:IDX"
        LocalDriveSeed = ""
        MachineDescription = ""
        MachineFlags = 0x64
        MachineNbuType = master (3)
        MachineState = active for tape and disk jobs (14)
        NetBackupVersion = 7.1.0.4 (710400)
        OperatingSystem = linux (16)
        ScanAbility = 5
groucho
        MachineName = "groucho"
        FQName = "groucho.mf.com.au"
        MachineDescription = ""
        MachineNbuType = virtual_machine (10)
chico
        MachineName = "chico"
        FQName = "chico.mf.com.au"
        MachineDescription = ""
        MachineNbuType = virtual_machine (10)
harpo
        MachineName = "harpo"
        FQName = "harpo.mf.com.au"
        MachineDescription = ""
        MachineNbuType = virtual_machine (10)
samwise.mf.com.au
        MachineName = "samwise.mf.com.au"
        FQName = "samwise.mf.com.au"
        MachineDescription = ""
        MachineNbuType = virtual_machine (10)
Command completed successfully.
[root@backup admincmd]#

Nicolai asked you to check media output with:

nbemmcmd  -listmedia -mediaid MF071A 
(listmedia,  not listhosts....)

This will tell us 2 things:
1. The density of the media
2. The media server that wrote the backup

You then need to check drive availability on this media server with 'tpconfig -l' and 'vmoprcmd -d' 
and ensure that there are 'UP' drives matching the media density.

Hi mate,

We actually have replied, but the forum has published our posts in a moderation queue so they are waiting to be posted. If this is something you can action that would be very helpful.