Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

219 error

Created: 16 Sep 2013 • Updated: 25 Oct 2013 | 14 comments
This issue has been solved. See solution.

NBU 7.5

WINDOWS OS 2008

Hi ALL,

Backup jobs are failing with error 219(no storage unit available).

We have set any available in the policy storage and st unit has 3 media manager  st units with on demand unckecked.

Please let me what else to check.

Operating Systems:

Comments 14 CommentsJump to latest comment

RamNagalla's picture

Please post us the failed job  detail status...

and also try using the one of the STU for backup and see the results

Marianne's picture

There are lots of TNs about status 219 that is specific to NBU version and MSDP and/or third-party dedupe devices.

Important that you share all relevant info - exact NBU version and patch level (hopefully not unpatched 7.5), media server OS and patch level, type of STU and software versions in the case of OST appliances, as well as all info in Details tab of failed job.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

nike_new's picture

16.09.2013 16:38:04 - Info nbjm(pid=7072) starting backup job (jobid=86415) for client VIPOPB39DNS0W.mgmt.local, policy VIPOP_WIN2k8_1, schedule Full_Saturday_Sunday 
16.09.2013 16:38:04 - Info nbjm(pid=7072) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=86415, request id:{7479191C-614A-48A1-9BCA-5EBCDFCE915A}) 
16.09.2013 16:38:04 - requesting resource SYSMP06BKS0L-robot-NEW
16.09.2013 16:38:04 - requesting resource sysmp03bks0w.mgmt.local.NBU_CLIENT.MAXJOBS.VIPOPB39DNS0W.mgmt.local
16.09.2013 16:38:04 - requesting resource sysmp03bks0w.mgmt.local.NBU_POLICY.MAXJOBS.VIPOP_WIN2k8_1
16.09.2013 16:38:05 - Error nbjm(pid=7072) NBU status: 219, EMM status: Storage unit is not defined in EMM
the required storage unit is unavailable(219)
16.09.2013 16:41:27 - job 86415 was restarted as job 86417

nike_new's picture

D:\Veritas\NetBackup\bin>bpstulist -label SYSMP06BKS0L-robot-NEW
no entity was found - Storage unit is not defined in EMM(2002002)

D:\Veritas\NetBackup\bin>bpstulist -U|find "NEW"
Label:                sysmp01bks0w-robot-NEW
Label:                sysmp03bks0w-robot-NEW

why that st unit was taken by the job ,if it is not there?

Marianne's picture

So, you can see - you have defined a Storage Unit in policy VIPOP_WIN2k8_1 that no longer exists.
Maybe the STU existed at some point which allowed you to select it in the policy. 
When you delete an STU, you need to update each policy where it is selected.

Open the policy and select a valid STU.
 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
nike_new's picture

in policy i have selected any available.

now what to do so that these unknown storage unit does not comes up again?

Marianne's picture

Check schedules as well for this STU.

Fact is - this STU existed at some point in time which allowed NBU to choose it.

Always a good idea to select a specific STU or STU group or else SLP in backup policies.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

nike_new's picture

Fact is - this STU existed at some point in time which allowed NBU to choose it.

now my query is what i can do so that NBU does not choose any such st unit which existed at some point but not now.

I mean any command which I can run to remove all previous existed st unit ?

Marianne's picture

Collect output of all policies in a text file:

bppllist -allpolicies -U >/tmp/policies.txt

Search the text file for the deleted STU name and make a note of policy names.

Manually update policies.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

nike_new's picture

i have selected any availabe in the policy. .Then why it is choosing already deleted st unit?

is my EMM updated?

Marianne's picture

Probably because the backup started shortly after you deleted the STU and the STU still existed in memory.

In future, do NOT select Any Available in policies and run these commands after you have made configuration changes (such as deleting STU and/or changed policies)::

bprdreq -rereadconfig

nbpemreq -updatepolicies 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

nike_new's picture

this commands will update EMM?

Marianne's picture

These commands will update the 'in memory' config.

EMM is already updated.

Policies is not part of EMM database - see 'Parts of NetBackup Catalog' in NBU Admin Guide I.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

nike_new's picture

thanks marianne.

one last question.If i delete a st unit,i have not run any command,then how EMM IS UPDATED?