Forum Discussion

sagar666's avatar
sagar666
Level 5
10 years ago

Getting error code 2009

Hi,

All Backups are failing with error code 2009. earlier also same issue i follewed below it was working but this time its not working

http://www.symantec.com/business/support/index?page=content&id=TECH177880

Job Details:

03/02/2015 10:15:19 - Info nbjm (pid=2167) starting backup job (jobid=5127) for client inbmaster, policy ecad, schedule Differential-Inc
03/02/2015 10:15:19 - Info nbjm (pid=2167) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=5127, request id:{EDA3E186-C096-11E4-A9E8-B824872B9160})
03/02/2015 10:15:19 - requesting resource inbmaster-hcart-robot-tld-0
03/02/2015 10:15:19 - requesting resource inbmaster.asicdesigners.com.NBU_CLIENT.MAXJOBS.inbmaster
03/02/2015 10:15:19 - requesting resource inbmaster.asicdesigners.com.NBU_POLICY.MAXJOBS.ecad
03/02/2015 10:15:19 - Error nbjm (pid=2167) NBU status: 2009, EMM status: All compatible drive paths are down, but media is available
03/02/2015 10:27:35 - job 5127 was restarted as job 5128
All compatible drive paths are down but media is available  (2009)


Please help me and let me know any more details require

 

  •  All compatible drive paths are down.

    Check Device Monitor or 'vmoprcmd' command for drive status.

    Before you UP drives, you need to find out why they were DOWN'ed in the first place.
    Check /var/log/messages and bptm log on media server for clues.

    Add VERBOSE to /usr/openv/volmgr/vm.conf and restart ltid for increased device-level logging to /var/log/messages. 

    PS:

    Seems you need to make a decision on new hardware sooner rather than later, or get your hardware vendor to fix or replace faulty tape drives and/or library:

    New Hardware for Backup 

    NBU is reporting the errors - nothing we can do from NBU side to fix hardware issues.

  •  All compatible drive paths are down.

    Check Device Monitor or 'vmoprcmd' command for drive status.

    Before you UP drives, you need to find out why they were DOWN'ed in the first place.
    Check /var/log/messages and bptm log on media server for clues.

    Add VERBOSE to /usr/openv/volmgr/vm.conf and restart ltid for increased device-level logging to /var/log/messages. 

    PS:

    Seems you need to make a decision on new hardware sooner rather than later, or get your hardware vendor to fix or replace faulty tape drives and/or library:

    New Hardware for Backup 

    NBU is reporting the errors - nothing we can do from NBU side to fix hardware issues.