Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrade.
Please accept our apologies in advance for any inconvenience this might cause.

Error 830 "All compatible drive paths are down, but media is available" but in the console everything is green

Created: 09 Sep 2013 • Updated: 10 Sep 2013 | 9 comments
This issue has been solved. See solution.

Hello,

Last weekend, the backups failed with the status 830 and the error, All compatible drive paths are down, but media is available

While, in the NBU console, everything was green

Here is a log of the job:

08/09/2013 00:20:00 - requesting resource srvseaco-nbu-1-hcart-robot-tld-0
08/09/2013 00:20:00 - requesting resource srvseaco-nbu-1.NBU_CLIENT.MAXJOBS.srvseaco-ctx1.seaco.intranet
08/09/2013 00:20:00 - requesting resource srvseaco-nbu-1.NBU_POLICY.MAXJOBS.CTX1
08/09/2013 00:20:00 - Error nbjm(pid=588) NBU status: 830, EMM status: All compatible drive paths are down, but media is available
drive(s) unavailable or down(830)

How can i diagnose this issue please? and is there anything to do to prevent this from happening again?

Regards!

Operating Systems:

Comments 9 CommentsJump to latest comment

Marianne's picture

I have learned to trust cmd more than I trust the GUI.

Please provide output of the following commands on the master server:

<install-path>\veritas\volmgr\bin\vmoprcmd

<install-path>\veritas\netbackup\bin\admincmd\nbrbutil -dump

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

Marianne's picture

Everything seems fine at the moment. 
Are your backups working now?

Check output of these 2 commands next time the error is seen.

Also enable logging on this server for further troubleshooting:

Add VERBOSE entry to <install-path>\veritas\volmgr\vm.conf followed by restart of NBU Device Management service.
Create bptm log folder under <install-path>\veritas\netbackup\logs

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

revaroo's picture

As Mariane mentioned, are backups now ok? Is this a 1 time occurrence or has it happened on many occasions? Perhaps look in your system logs to see if anything was reported about the drive paths at the time?

Lotfi BOUCHERIT's picture

The backups are running normally now, and it is the first time

And the only thing reported in the system event log that time, was the file attached to this message

Code830.jpg
revaroo's picture

Lotfi,

 

Seems like it was a "blip" - I would ignore it unless it happens again.

SOLUTION
Marianne's picture

Please enable logging as per my post above. This way you will be able to find the reason for errors and/or DOWN'ed drives next time it happens.

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

ibrahimbaba's picture

i also have the same issue but it is consistent and as such almost none of my jobs can complete successfully 

 
                           HOST STATUS
Host Name                                  Version   Host Status
=========================================  =======   ===========
td002                                      700000    ACTIVE
 
                                PENDING REQUESTS
 
 
                                    <NONE>
 
                                  DRIVE STATUS
 
Drive Name               Label   Ready  RecMID  ExtMID  Wr.Enbl.  Type
    Host                       DrivePath                            Status
=============================================================================
HP.ULTRIUM4-SCSI.000     No      No                     No        hcart
    td002                      {2,0,2,0}                            TLD
    td002                      {1,0,2,0}                            RESTART
 
C:\Program Files\Veritas\NetBackup\bin\admincmd>nbrbutil.exe -dump
 
Allocation Requests
(AllocationRequestSeq )
 
 
Allocations
(AllocationSeq )
 
MDS allocations in EMM: