NetBackup deduplication disk pool/disk volume intermittently goes to a DOWN state. Backups/duplications can fail with status 213 no storage units is available and 2074.

Problem

NetBackup deduplication disk pool/disk volume intermittently goes to a DOWN state. Backups/duplications can fail with status 213 no storage units is available and 2074.

Error Message

Status Code: 213
Status Code: 2074

Cause

The NetBackup Disk Polling Service (DPS), which is responsible for telling NetBackup whether a disk pool / disk volume is up, polls stats from the MSDP / PDDO storage server via bpstsinfo.  However, by default DPS has a 1 minute timeout
limit, so if it does not get a reply back within a minute, DPS automatically treats it as an error on the disk pool / disk volumes as down.

Depletion of system resources can cause a delay in the DPS reply.

Solution

The formal resolution for this issue (Etrack 2601935) is included in the following version:

  • NetBackup 52x0 Appliances 2.0.2

NetBackup Appliances 2.0.2 is now available - download and README information can be found in the Related Article linked below.

Workaround:
Increase the polling timeout.

On Windows media server:

Create these three files and put inside them the value 1800 or the max of 3600.

Be certain that there are no extensions on the files. For example, no .txt extension. 

 
The 3600 value is the only thing inside each file: 

<install path>\netbackup\db\config\DPS_PROXYDEFAULTSENDTMO 
<install path>\netbackup\db\config\DPS_PROXYDEFAULTRECVTMO 


Restart nbrmms (NetBackup Remote Manager and Monitor Service) on the media server, or just stop and restart all services: 
<install path>\netbackup\bin\bpdown -f -v 
<install path>\netbackup\bin\bpup -f -v 

On UNIX or Linux: 

# echo "3600" > /usr/openv/netbackup/db/config/DPS_PROXYDEFAULTSENDTMO 
# echo "3600" > /usr/openv/netbackup/db/config/DPS_PROXYDEFAULTRECVTMO


Restart nbrmms (NetBackup Remote Manager and Monitor Service) on the media server: 
# pkill nbrmms 
# /usr/openv/netbackup/bin/nbrmms 


Or stop and restart all services on the MSDP media server: 
# /usr/openv/netbackup/bin/goodies/netbackup stop 
# /usr/openv/netbackup/bin/goodies/netbackup start 

If this issue reoccurs, uncomment/configure the CR_STATS_TIMER line in pd.conf on the affected media server:
#CR_STATS_TIMER = 300

WARNING: if the issue persists after one daily or nightly backup schedule window after employing the above configuration changes, please remove the touchfiles and troubleshoot the issue further via logs (nbrmms, dps, spoold, spad) to determine root cause.
 

Applies To

NetBackup 5220 appliances through version 2.0.1 using a deduplication disk pool writing to a Media Server Deduplication storage server or PureDisk storage server.

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)