cancel
Showing results for 
Search instead for 
Did you mean: 

Storage unit offline ,causing some jobs failed(213)

Vivi
Level 3
Certified

Hi,everyone!

Netbackup 7.1, Windows2008R2 Master/Media, Deduplication,AIR

Some backup sub-job failed with code 213,and the followed sub-job may backup successful.

The failed job details

==================================

2012/6/17 5:01:38 - Info nbjm(pid=8764) starting backup job (jobid=13679) for client czerp02.trinasolar.com, policy ERP_CZERP02_HCMPRD_ORA, schedule Default-Application-Backup 
2012/6/17 5:01:38 - Info nbjm(pid=8764) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=13679, request id:{1FC3734F-E846-4492-BF8C-E517F8B812DD}) 
2012/6/17 5:01:38 - requesting resource su01
2012/6/17 5:01:38 - requesting resource tsczbak02.trinasolar.com.NBU_CLIENT.MAXJOBS.czerp02.trinasolar.com
2012/6/17 5:01:38 - requesting resource tsczbak02.trinasolar.com.NBU_POLICY.MAXJOBS.ERP_CZERP02_HCMPRD_ORA
2012/6/17 5:01:38 - awaiting resource su01 Reason: Maximum I/O stream count has been reached for disk volume, Media Server: tsczbak03.trinasolar.com,
  Robot Number: NONE, Robot Type: NONE, Media ID: N/A, Drive Name: N/A,
  Volume Pool: NetBackup, Storage Unit: su01, Drive Scan Host: N/A
 
2012/6/17 5:03:38 - Info nbjm(pid=8764) Waiting in NetBackup scheduler work queue on server tsczbak02.trinasolar.com   
2012/6/17 5:03:51 - Error nbjm(pid=8764) NBU status: 213, EMM status: Storage units are not available  
no storage units available for use(213)

===================================

When the backup failed,There's some duplication job failed with code 2074

The failed duplication job details

===================================

2012/6/17 0:02:21 - requesting resource LCM_su01
2012/6/17 0:02:21 - granted resource LCM_su01
2012/6/17 0:02:21 - started process RUNCMD (6448)
2012/6/17 0:02:21 - requesting resource @aaaab
2012/6/17 0:02:21 - reserving resource @aaaab
2012/6/17 0:02:22 - awaiting resource @aaaab Reason: Maximum I/O stream count has been reached for disk volume, Media Server: N/A,
  Robot Number: NONE, Robot Type: NONE, Media ID: @aaaab, Drive Name: N/A,
  Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A
 
2012/6/17 0:04:51 - Error nbjm(pid=8764) NBU status: 2074, EMM status: Disk volume is down   
2012/6/17 0:04:51 - Error nbjm(pid=8764) NBU status: 2074, EMM status: Disk volume is down   
2012/6/17 0:04:52 - Error (pid=6448) RequestResources failed: 2074         
Disk volume is down(2074)

 

1 ACCEPTED SOLUTION

Accepted Solutions

Vivi
Level 3
Certified

Hi,all!

Sorry to delay several weeks,with Symantec support's help,My issue have solved.

On media server,

Create install_path\netbackup\db\config\DPS_PROXYNOEXPIRE

Create install_path\netbackup\db\config\DPS_PROXYDEFAULTSENDTMO and put inside the value 1800

Create install_path\netbackup\db\config\DPS_PROXYDEFAULTRECVTMO and put inside the value 1800

restart Netbackup service.

Then,all jobs are running normally.

View solution in original post

4 REPLIES 4

Marianne
Level 6
Partner    VIP    Accredited Certified
What other jobs are active when you see this? What Is maximum concurrent jobs set to in the STU? Hopefully you are running some 7.1 patch level and not just straight 7.1? Lots of MSDP fixes in recent patches. 7.1.0.4 patch is the newest for 7.1.

Nicolai
Moderator
Moderator
Partner    VIP   

Make sure you don't have Mcafee antivirus scanning the files in the DSU file path (or other antivirus products). The event log should indicate a lot of scanning timeout on files in the dsu path.

http://www.mass.dk/netbackup/quick-hints/89-netbackup-status-code-2074-a-mcafee.html

Vivi
Level 3
Certified

Hi,all!

Sorry to delay several weeks,with Symantec support's help,My issue have solved.

On media server,

Create install_path\netbackup\db\config\DPS_PROXYNOEXPIRE

Create install_path\netbackup\db\config\DPS_PROXYDEFAULTSENDTMO and put inside the value 1800

Create install_path\netbackup\db\config\DPS_PROXYDEFAULTRECVTMO and put inside the value 1800

restart Netbackup service.

Then,all jobs are running normally.

CRZ
Level 6
Employee Accredited Certified

Looks like these TechNote could have helped:

Status 213: PureDisk Volume is repeatedly being marked down and up automatically.
 http://symantec.com/docs/TECH156490

Windows MSDP Disk pool is down, backups and duplications failing with status 213, no storage units available for use
 http://symantec.com/docs/TECH159232

...and here's a UNIX version:

UNIX or Linux MSDP Disk pool is down, backups and duplications failing with status 213, no storage units available for use
 http://symantec.com/docs/TECH159707

(I have to admit I had never heard of these touch files before)