Forum Discussion

Suporte_tpbr's avatar
11 years ago

Error code 2074 Netbackup 7.5

Hi folks,


I configured some server windows but showing error code 2074.
The issue occurred intermittence in sometimes.
Attached log bperror -disk in the master server.

Thanks for time

 

  • Try the following .. add a touch file to the Master and your media servers - this helps when a lot of backup traffic (very busy times) causes the status check not to get through and the disk gets marked down

    I have seen this help for Advanced (Enterprise) Disk and de-dupe:

     

    The touch file gets added as follows - no file extension and then open it up in notepad and put 800 inside it

    \program files\veritas\netbackup\db\config\DPS_PROXYDEFAULTRECVTMO

    See if that helps stop the disk going down occasionally

    #EDIT#

    Forgot to say you need a netbackup re-start (bpdown / bpup) to register this touch file

  • Status 2074 says that the disk volume is down.

    Please tell us more about this disk storage -

    What type of disk storage?
    On the master or a media server?
    How is disk connected to the server?

    What is the OS (and version) on master and media server?

    What is NBU 7.5 patch level?

  • Marianne,

    This issue didn't occur today, but on other days it occured with several bakcup jobs.

     

    I believe these are the information requested.

    My Storage it is Dell Equalogic PS6000.

    The OS to Master and Media it is Windows server 2008 R2 Standard.

    NBU used it is 7.5.0.6.

    Thank you in advance for your time and support.

  • So, What type of disk storage unit in NBU? Basic or Advanced?

    How is the disk connected to the server? NAS/DAS/SAN?

    Have you checked OS-level access to the storage at the time when status 2074 is seen?

  • Try the following .. add a touch file to the Master and your media servers - this helps when a lot of backup traffic (very busy times) causes the status check not to get through and the disk gets marked down

    I have seen this help for Advanced (Enterprise) Disk and de-dupe:

     

    The touch file gets added as follows - no file extension and then open it up in notepad and put 800 inside it

    \program files\veritas\netbackup\db\config\DPS_PROXYDEFAULTRECVTMO

    See if that helps stop the disk going down occasionally

    #EDIT#

    Forgot to say you need a netbackup re-start (bpdown / bpup) to register this touch file

  • Mark_Solutions,

    Thanks. I'll check .

     

    Marianne,

    Disk connect in SAN and type  MSDP

  • Have you checked OS-level access to the storage at the time when status 2074 is seen?

    errors usually occur in the period in which I cant monitor. 

    Try the following .. add a touch file to the Master and your media servers - this helps when a lot of backup traffic (very busy times) causes the status check not to get through and the disk gets marked down

    I have seen this help for Advanced (Enterprise) Disk and de-dupe:

     

    The touch file gets added as follows - no file extension and then open it up in notepad and put 800 inside it

    \program files\veritas\netbackup\db\config\DPS_PROXYDEFAULTRECVTMO

    See if that helps stop the disk going down occasionally

    #EDIT#

    Forgot to say you need a netbackup re-start (bpdown / bpup) to register this touch file

    I create the file, errors decreased but are still happening.

  • Apologies - only saw your last reply this morning.

    errors usually occur in the period in which I cant monitor. 

    I have often in my level 1 and 2 support days sat through the night at customers' site, staring at Activity Monitor while keeping an eye on system resources and other running processes.
    Quite often this the only way to find out what else is going on during peak backup hours.

    We see your backup destination is MSDP.

    What is the size of MSDP pool?
    How much memory in this server?
    Do you have a single master/media server?

    The MSDP guide says 1GB memory for each TB of dedupe storage.
    In real life we have seen that about 1.5GB/TB is best.
    On a master/media server, you need to add 4-8 GB RAM for master server processes.