Backups fail with status code 2505 or 252

[TimWillingham]

This started happening this past weekend.  I made the changes in this technote (http://www.symantec.com/business/support/index?page=content&id=TECH203066), but got the errors again last night afterwards.

05/19/2014 12:49:34 - Info nbjm (pid=24705) starting backup job (jobid=1371237) for client flciffs04, policy ar_cif_win_nt, schedule cal-w
05/19/2014 12:49:34 - Info nbjm (pid=24705) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1371237, request id:{F075453A-DF7D-11E3-9A14-3B3B5248F30F})
05/19/2014 12:49:34 - requesting resource flciftb02
05/19/2014 12:49:34 - requesting resource alxaptb07xs.NBU_CLIENT.MAXJOBS.flciffs04
05/19/2014 12:49:34 - requesting resource alxaptb07xs.NBU_POLICY.MAXJOBS.ar_cif_win_nt
05/19/2014 12:49:34 - awaiting resource flciftb02. Maximum job count has been reached for the storage unit.
05/19/2014 14:01:25 - awaiting resource flciftb02. No drives are available.
05/19/2014 14:02:24 - awaiting resource flciftb02. Maximum job count has been reached for the storage unit.
05/19/2014 17:53:50 - awaiting resource flciftb02. No drives are available.
05/19/2014 17:54:49 - awaiting resource flciftb02. Maximum job count has been reached for the storage unit.
05/19/2014 22:53:10 - granted resource  alxaptb07xs.NBU_CLIENT.MAXJOBS.flciffs04
05/19/2014 22:53:10 - granted resource  alxaptb07xs.NBU_POLICY.MAXJOBS.ar_cif_win_nt
05/19/2014 22:53:10 - granted resource  F00176
05/19/2014 22:53:10 - granted resource  CIF_Drive02
05/19/2014 22:53:10 - granted resource  flciftb02
Failed to get status code information (2505)
 

[Marianne]

What type of backup is this? Started by NBU scheduler?

It could be caused by the fact that there is a shortage of  physical resources (tape, not logical resources in the form of shared memory)  for more than 10 hours.

I find it strange that the backup goes Active and is not queued due to shortage of tape drives.

[TimWillingham]

Did some EMM tuning with support and then I discovered /usr/openv was full due to log files.  I have cleaned that up and made EMM DB changes , so we should be good to go!

[Marianne]

Does that mean that EMM was stopped/shutdown?

NBU will automatically shutdown EMM to prevent corruption.
Evidence can be seen in server.log.