Forum Discussion

Pritesh_Pisal's avatar
Pritesh_Pisal
Level 5
11 years ago

Status 2074 - Disk Volume Down

**** Moved to new discussion from https://www-secure.symantec.com/connect/forums/nbu-status-2074-emm-status-disk-volume-down ****   I am facing the exactly the same issuewith EMC DD. I have follo...
Backup and Recovery
NetBackup
  • Mark_Solutions's avatar
    Mark_Solutions
    11 years ago

    I think the parameter referenced by Yogesh will be the DPS_PROXYDEFAULTRECVTMO file

    If it doesnt exist create it (on all Master and Media Servers) and add a value of 800 to it.

    However, if you are sure that @aaaai does not exist this may not help.

    To double check run nbdevquery -listdv -stype PureDisk to see what ID all of your pools actually have

    If @aaaai is definately not one of your pools then you can try running the following to see if that resolves your issue:

    nbstlutil remove_exp -force

    It is still persists then usually it is caused by you deleteing a disk pool and creating another one without re-starting NetBackup services on the Master between those operations (though it doesn't actually say anywhere that you need to!!)

    If that is the case the entry is stuck in EMM and you need to raise a case with support who will write you a little sql script to remove it from EMM - there is no other way i know of to get rid of these issues.

    This is all assuming that you are running NBU 7.5 - if you are running 7.1 you can just run:

    nbstlutil remove_all -mediaid @aaaah –force

    Hope this helps

    #EDIT# ONLY DO THIS IF YOU ARE SURE THE POOL NO LONGER EXISTS - IF IT DOES IT WILL REMOVE EVERYTHING FROM YOUR LIVE DISK POOL !!!!

Mark_Solutions's avatar
Mark_Solutions
Level 6
11 years ago

I think the parameter referenced by Yogesh will be the DPS_PROXYDEFAULTRECVTMO file

If it doesnt exist create it (on all Master and Media Servers) and add a value of 800 to it.

However, if you are sure that @aaaai does not exist this may not help.

To double check run nbdevquery -listdv -stype PureDisk to see what ID all of your pools actually have

If @aaaai is definately not one of your pools then you can try running the following to see if that resolves your issue:

nbstlutil remove_exp -force

It is still persists then usually it is caused by you deleteing a disk pool and creating another one without re-starting NetBackup services on the Master between those operations (though it doesn't actually say anywhere that you need to!!)

If that is the case the entry is stuck in EMM and you need to raise a case with support who will write you a little sql script to remove it from EMM - there is no other way i know of to get rid of these issues.

This is all assuming that you are running NBU 7.5 - if you are running 7.1 you can just run:

nbstlutil remove_all -mediaid @aaaah –force

Hope this helps

#EDIT# ONLY DO THIS IF YOU ARE SURE THE POOL NO LONGER EXISTS - IF IT DOES IT WILL REMOVE EVERYTHING FROM YOUR LIVE DISK POOL !!!!