Video Screencast Help

Backups are running very slow for some client windows servers

Created: 30 Dec 2012 | 3 comments

We have issues with some windows client server:

Either backups are running too slow or fail with following errors:

 Error nbjm (pid=2505) NBU status: 2009, EMM status: All compatible drive paths are down, but media is available
All compatible drive paths are down but media is available  (2009)

Multiple backups are failing with EC : 84(media write error ).

Please assist, as even when we restart jobs, they  seem to run slow and hung up.


Samrat Chowdhury

Comments 3 CommentsJump to latest comment

mph999's picture

Running slow and status 84 could be two different problems.

They could be connected, can't tell yet.

FIrstly, what is the error seen in bptm when the drive has a problem (hopefully we see something in here). 

Also create these logs on the media server :

In volmgr/debug dir ... create these dirs.



In volmgr debug dir create these empty files (if windows media server make sire it does not add any suffix to the filename)



I would also add the word VERBOSE into vm.conf (in volmgr dir).

This should give info on the drive down issue.

For the slow running ....

Look in the job details in activity monitor for a job that ran slowly, but has completed.

x2 click the job and goto the details tab.

Somewhere in the text, there should be a line or lines that look like this :

Waited for Full/ Empty buffer xx times, delayed yy times  - please post these up.


Regards,  Martin
Setting Logs in NetBackup:
Marianne's picture

Slow backups and Device I/O problems are 2 separate issues that need separate troubleshooting.

Slow backups:
Slow disk on client, heavy fragmentation, inadequate resouces on client (low memory, slow processor, etc),  NIC, slow network, etc. etc...
Some TNs:

Device I/O errors (Status 84, drives down):
Problem between media server OS and devices. 
This can be anything from faulty tape drives, bad media, faulty cable between media server and device, faulty HBA, bad/old HBA drivers, bad/old tape drivers, etc.. etc...
Some TN's: 

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

Nicolai's picture

Slow backup could also be caused by tape drives in bad shape. Modern tape drives does read after write and any write errors are corrected on the fly. The cost is write speed - tape drive need to stop rewind and re-write the same data pattern. 

When you well us, you have down writes and status 84, it would say it's highly likely this is the cause. Start by using a cleaning tape (a brand new one). Then do know fast backup on each tape drive you have (you will need to up/down drives). Any tape drive that are way off baseline need to be replaced.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.