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

Disk Volume is down (2074)

Created: 16 Jul 2013 | 3 comments

Hi,

our daily backups two days ago went fine, but in the backups yesterday i had 10 jobs failing with error code 2074 disk volume is down.

This is what the detailed status is saying:

 

7/16/2013 11:00:00 PM - Info nbjm(pid=4848) starting backup job (jobid=89501) for client winmd002, policy W2K8_GEN_FS_WIN, schedule daily_cum  
7/16/2013 11:00:00 PM - Info nbjm(pid=4848) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=89501, request id:{0C656FBF-024C-4065-B8A4-F001092A2CF5})  
7/16/2013 11:00:00 PM - requesting resource Disk9TB
7/16/2013 11:00:00 PM - requesting resource winmd003.NBU_CLIENT.MAXJOBS.winmd002
7/16/2013 11:00:00 PM - requesting resource winmd003.NBU_POLICY.MAXJOBS.W2K8_GEN_FS_WIN
7/16/2013 11:00:01 PM - awaiting resource Disk9TB - Maximum job count has been reached for the storage unit
7/17/2013 1:03:25 AM - Error nbjm(pid=4848) NBU status: 2074, EMM status: Disk volume is down    
Disk volume is down(2074)

Same error for all 10 jobs...All other jobs on that Disk went fine.

Thanks,

Marcus

Operating Systems:

Comments 3 CommentsJump to latest comment

Jeremy32's picture

"Maximum job count has been reached for the storage unit"

 

Select Storage, Storage Units. Right click your storage unit that these are running to and select Change. Once in here increase "Maximum Concurrent Jobs"

Mark_Solutions's picture

A 2074 won't be caused by running out of streams so no real need to increase that, although it does seem to wait a long time before the failure so maybe you do need a bit more to help with the number of jobs

A few reasons for this, but as you say some jobs were OK and a few failed then as a first step i would do the following on the Master Server and each Media Server ad the following file:

Unix: /usr/openv/netbackup/db/config/DPS_PROXYDEFAULTRECVTMO

Windows : <installpath>\veritas\netbackup\db\config\DPS_PROXYDEFAULTRECVTMO

Open the file up and add a value of 800 into it.

Restart all NetBackup services to register this new file

See how it goes in the future

This is usually caused by a very busy system and this file just gives everything a bit more time to react instead of putting disks down all the time - works for Advanced Disk and De-Dupe disk pools

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

mkoeppl83's picture

Hello Mark,

 

i have added this and will get back if i see the first results.

 

Thanks,

Marcus