Netbackup Status 800 Robotic Library is not Defined in EMM

Question

Hello, i had a other thread about another issue for some time ago but we solved that issue
	
	However this popped up now instead been trying to fix it during the summer vacations but i think i need some help.
	
	I Get Status code 191 also but i assume this is because of the Status 800:
	
	8/3/2015 8:10:20 AM - begin Duplicate
	8/3/2015 8:10:21 AM - requesting resource bup01-TL4000
	8/3/2015 8:10:21 AM - Error nbjm(pid=3140) NBU status: 800, EMM status: The robotic library is not defined in EMM
	8/3/2015 8:10:21 AM - Error nbjm(pid=3140) NBU status: 800, EMM status: The robotic library is not defined in EMM
	8/3/2015 8:10:28 AM - end Duplicate; elapsed time: 00:00:08
	resource request failed(800)
	
	I have been reading up on the issue and it seems its a pathing issue somewhere? but im not sure where to look,

&nbsp;

First one all. One Media server, One robot but two tapes. Windows 2003 R2 ( We are trying to convince the finance department to upgrade ) Netbackup 7.5
	
	Stuff i have tried:
	Shutdown the server, remove all tapes from the drives and reboot the robot / server, and repeated that step while inserting the tapes.
	Did an robot inventory so all tapes are up to date.
	
	I Found thishttps://support.symantec.com/en_US/article.TECH56270.html however im unsure where to type this command or know what information to look into, basically i feel stuck and im very very new with Netbackup in general in the NBUI where i can see the error code i can also check the built in Troubleshooter where i get
	
	Locate the EMM reason string, correct the problem, and rerun the job.
	Some generic EMM reason strings (such as Disk volume is down) may require generating some reports to determine the cause of the failure. Generate the report by using either bperror or various log entry reports, such as Reports &gt; Disk Reports &gt; Disk Logs in the NetBackup Administration Console.
	
	And it sounds simple enough but as i stated i have no clue what to look for here aswell.
	
	Im only at this office 3 times a week but i will try to answer / Troubleshoot as much as possible, Thanks for the help

riaanbadenhorst · Accepted Answer

Hi,

&nbsp;

Your problem is that you're using a DSSU (Disk staging storage unit) and its referring to a storage unit that is not configured anymore. If you check the storage unit called DISK_STAGING's properties you'll find that in the schedule section its referring to igsest1bup01-TL4000 but we don't see that robot (TLD0) configured in the output of tpconfig -l.

&nbsp;

It was probabably removed/replaced and you now have TLD1 with storage unit igsest1bup01-hcart3-robot-tld-1. You can use the new storage unit in the disk staging schedule.

&nbsp;

Alternatively it could be the same type of issue but in an SLP. If the scenario above doesn't apply you can post

&nbsp;

nbstl -L

riaanbadenhorst · Answer

PLease tell us more about the duplication job. Is it part of an SLP? Or is it a manual duplication.

&nbsp;

Please post

master server name

media server name

bppllist "policy name" -L

nbstl "slp name' -L

and the bptm log for the time frmae 8/3/2015 8:10:21 AM as an attachment to the post

marianne · Answer

In addition to info requested by Riaan, tell us more about bup01-TL4000 config. 
Is bup01 master/media server or separate media server?

Show us output of : 
bpstulist -U
tpconfig -l

Does the robot number in STU  config and device config match.

My guess is that you have reconfigured the devices that may have added the robot number as 1 but STU config is still pointing to robot 0. 
Output of above commands will confirm.

niklasv · Answer

For some reason i changed the name to just bup01-TL4000 when i posted but the fullname is abit different,i was&nbsp;just slightly paranoid i gues&nbsp;so the proper full name is igsest1bup01-TL4000
	Sorry for the massive wall of text that will appear now:
	
	Master server: igsest1bup01.dom.oad.lcl

Lets see, i will start with the commands:

C:\Program Files\VERITAS&gt;bppllist FPS05_HDD -l
	CLASS FPS05_HDD *NULL* 0 750000 0 *NULL*
	NAMES
	INFO 13 0 0 4 *NULL* 0 0 2147483647 0 0 0 2 0 0 0 1 0 0 1354874613 0BE35DE6279C4
	FED9C351E58FA4CF5BE 1 0 0 0 0 0 0 0 2 0 0 0 0 0 0 3 0 7 0 0 0
	KEY *NULL*
	BCMD *NULL*
	RCMD *NULL*
	RES DISK_STAGING *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
	POOL Windows_Clienter NetBackup NetBackup NetBackup NetBackup NetBackup NetBacku
	p NetBackup NetBackup NetBackup
	FOE 0 0 0 0 0 0 0 0 0 0
	SHAREGROUP *ANY*
	DATACLASSIFICATION *NULL*
	CLIENT igsest1fps05.iuser.iroot.adidom.com PC WindowsNET 0 0 0 0 *NULL*
	INCLUDE D:\
	SCHED Full 0 2 432000 4 0 0 0 *NULL* 0 0 2 0 0 0 -1 0 0
	SCHEDWIN 0 25200 0 0 0 0 0 0 0 0 79800 6600 0 21600
	SCHEDRES DISK_STAGING OFFSITE_DISK_STAGING *NULL* *NULL* *NULL* *NULL* *NULL* *N
	ULL* *NULL* *NULL*
	SCHEDPOOL NetBackup NetBackup *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *
	NULL*
	SCHEDRL 4 3 1 1 1 1 1 1 1 1
	SCHEDFOE 0 0 0 0 0 0 0 0 0 0
	SCHEDSG *ANY* *ANY* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
	SCHED Incremental 4 5 86400 3 0 0 0 *NULL* 0 0 0 0 0 0 -1 0 0
	SCHEDWIN 0 0 0 0 7200 22200 7200 22200 7200 22200 7200 22200 0 0
	SCHEDRES *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
	SCHEDPOOL *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*
	SCHEDRL 3 0 0 0 0 0 0 0 0 0
	SCHEDFOE 0 0 0 0 0 0 0 0 0 0
	SCHEDSG *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL* *NULL*

&nbsp;

C:\Program Files\VERITAS&gt;bpstulist -U

Label:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; igsest1bup01-TL4000
	Storage Unit Type:&nbsp;&nbsp;&nbsp; Media Manager
	Host Connection:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; igsest1bup01.dom.oad.lcl
	Number of Drives:&nbsp;&nbsp;&nbsp;&nbsp; 2
	On Demand Only:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	Max MPX/drive:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4
	Density:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hcart3 - 1/2 Inch Cartridge 3
	Robot Type/Number:&nbsp;&nbsp;&nbsp; TLD / 0
	Max Fragment Size:&nbsp;&nbsp;&nbsp; 1048576 MB

Label:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; igsest1bup01-hcart3-robot-tld-1
	Storage Unit Type:&nbsp;&nbsp;&nbsp; Media Manager
	Host Connection:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; igsest1bup01.dom.oad.lcl
	Number of Drives:&nbsp;&nbsp;&nbsp;&nbsp; 2
	On Demand Only:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	Max MPX/drive:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1
	Density:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hcart3 - 1/2 Inch Cartridge 3
	Robot Type/Number:&nbsp;&nbsp;&nbsp; TLD / 1
	Max Fragment Size:&nbsp;&nbsp;&nbsp; 1048576 MB

Label:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DISK_STAGING
	Storage Unit Type:&nbsp;&nbsp;&nbsp; Disk
	Storage Unit Subtype: Basic (1)
	Host Connection:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; igsest1bup01.dom.oad.lcl
	Concurrent Jobs:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4
	On Demand Only:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; yes
	Max MPX:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1
	Path:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "F:\STAGING"
	Max Fragment Size:&nbsp;&nbsp;&nbsp; 2000 MB
	Stage data:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; yes
	Block Sharing:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	High Water Mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 90
	Low Water Mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 60
	Ok On Root:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no

Label:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; OFFSITE_DISK_STAGING
	Storage Unit Type:&nbsp;&nbsp;&nbsp; Disk
	Storage Unit Subtype: Basic (1)
	Host Connection:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; igsest1bup01.dom.oad.lcl
	Concurrent Jobs:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4
	On Demand Only:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; yes
	Max MPX:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1
	Path:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "F:\OFFSITE"
	Max Fragment Size:&nbsp;&nbsp;&nbsp; 2000 MB
	Stage data:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; yes
	Block Sharing:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
	High Water Mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 90
	Low Water Mark:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 50
	Ok On Root:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no

&nbsp;

C:\Program Files\VERITAS&gt;tpconfig -l
	Device Robot Drive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Robot&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Drive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Device

Type&nbsp;&nbsp;&nbsp;&nbsp; Num Index&nbsp; Type DrNum Status&nbsp; Comment&nbsp;&nbsp;&nbsp; Name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Path

robot&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; TLD&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; {2,0,0,1}

&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 1 hcart3&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IBM.ULT3580-TD3.001&nbsp; {3,0,0,0}

&nbsp; drive&nbsp;&nbsp;&nbsp; -&nbsp;&nbsp;&nbsp; 2 hcart3&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; UP&nbsp; -&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IBM.ULT3580-TD3.002&nbsp; {2,0,0,0}

&nbsp;

Basically im really new with this so im abit unsure how i can verify the STU Config/Device Config match as marianne mentioned.Not to sure what&nbsp;nbstl "slp name' -L not sure what the SLP name is.
	
	The Media should be same as Master Server, atleast what i can find in our previous logs / Anyway i can confirm this?
	Quote:
	and the bptm log for the time frmae 8/3/2015 8:10:21 AM as an attachment to the post
	
	Do you mean when checking it from the Grafical UI or any type of command to see it?
	
	//Regards.

marianne · Answer

As per my previous post and pointed out by Riaan -

Your robot number in device config is 1.
	robot&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1 &nbsp;

The robot number in Storage Unit config is 0.:

Label:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; igsest1bup01-TL4000
	Robot Type/Number:&nbsp;&nbsp;&nbsp; TLD / 0
	&nbsp;

Either delete the STU and recreate it or else modify attributes to select robot 1.&nbsp;

niklasv · Answer

This sounds great, im back in the office at wednesday so i will have a chat with my boss and inform him that we need to do these changes and i will update whenever i can hopefully at wednesday!
	
	Thanks for the help and i will update whenever i can.

Forum Discussion

Netbackup Status 800 Robotic Library is not Defined in EMM

11 Replies

Related Content

Robotic library is down

Steps to configure robot on Flex appliance

Robot error

Robotic library problem

Robotic library

Recent Discussions

command: bperror

MS-SharePoint policy restore error (2804) .

How to restore a backup

How to configure RBAC

10 years old netbackup appliance database service down, ssl certification out date