Forum Discussion

Hamza_H's avatar
Hamza_H
Moderator
4 years ago

Ghost restore jobs on AM

Hello All,

One of our customers wants to know why there are some 'ghost' restore jobs on the activity monitor every Sunday night.

These jobs start at midnight (00:00) every Sunday and some errors are reported in Problem reports at the same time.

error messages :

Error 0 General Could not connect to for virtual browse operation, errno=0, bpcd_status=48

11 messages for 11 restore jobs.

The restore jobs don't show anything only requesting resources and status code is 0.

we looked up into bprd, nbpem, nbjm, bpdbm logs, and all what I can find is some information regarding the execution time and something like :

9/20/2020 00:00:57.898 [ExportRequest::getName] (00000000038B4E50) request has no name(ExportedResource.cpp:1965)

(000000000505BD40) NO matching exported resource for request of type=13, reqNum=0, consume=false(ExportedResourceMgr.cpp:626)

in bprd logs, I can see that there is an nbdeployutil started at the same time but I don't know from which server has initiated it.

We checked the task scheduler on master, opscenter we found nothing and on the opscenter, in reports, we didn't find any report that is executed at that time.

But I suspect this comes from the Opscenter, because of this technote

https://www.veritas.com/support/en_US/article.100028008.

On the scl.conf file, this line was already commented :

#nbu.scl.collector.enableBreakupJobDataCollection=false.

Any ideas please?

Thanks,

Master server: Windows Server 2016

NBU version: 8.2

Windows Server 2016
  • davidmoline's avatar
    davidmoline
    4 years ago

    Not sure I can fully answer your question, but I can give you some help. 

    1. The NetBackup master server will run an incremental nbdeployutil every Sunday night at midnight. This is new and used by Smart Meter to provide for continual reporting back to Veritas on license usage. The files are available for you to examine - on Windows they can be found under <INSTALL>\Veritas\NetBackup\var\global\incremental (log files and previous nbdeployutil reports).
    2. The OpsCenter item would need to be uncommented to make a difference. Although that tech note relates to NetBackup 7.5.0.3 so not sure if it is relvant still (no harm in trying though). 

    As for the ghost restore jobs - no idea, I've never seen that before. Can you share some more details on the jobs themselves (such as job details, assuming there are any)?

    Refer to his URL for details on how to control the nbdeployutil scheduling to see if this is causing the ghost jobs: https://www.veritas.com/content/support/en_US/doc/24437881-136359134-0/v137470892-136359134

     

     

  • Hamza_H's avatar
    Hamza_H
    4 years ago

    Hello davidmoline ,

    I just got an update regarding this case, by disabling nbedployutil (by setting the value FREQUENDY_BY_DAYS=0 in nbdeployutilconfig.txt) the client didn't get any error or restore jobs and he's happy with it.. 

    I don't know if disabling nbdeployutil is a good thing or not? could you please advise regarding this?

     

    Thank you;

  • davidmoline's avatar
    davidmoline
    Level 6
    4 years ago

    Not sure I can fully answer your question, but I can give you some help. 

    1. The NetBackup master server will run an incremental nbdeployutil every Sunday night at midnight. This is new and used by Smart Meter to provide for continual reporting back to Veritas on license usage. The files are available for you to examine - on Windows they can be found under <INSTALL>\Veritas\NetBackup\var\global\incremental (log files and previous nbdeployutil reports).
    2. The OpsCenter item would need to be uncommented to make a difference. Although that tech note relates to NetBackup 7.5.0.3 so not sure if it is relvant still (no harm in trying though). 

    As for the ghost restore jobs - no idea, I've never seen that before. Can you share some more details on the jobs themselves (such as job details, assuming there are any)?

    Refer to his URL for details on how to control the nbdeployutil scheduling to see if this is causing the ghost jobs: https://www.veritas.com/content/support/en_US/doc/24437881-136359134-0/v137470892-136359134

     

     

    • Hamza_H's avatar
      Hamza_H
      Moderator
      4 years ago

      Hello davidmoline,

      Thank you for your reply, I appreciate it.

      you actually kind of answered one of my main questions which is about nbdeployutil getting started every Sunday night at midnight so we might know what is causing those restore jobs

      regarding restore jobs in AM, as described in the technote, It has been found that data collection inside of OpsCenter can trigger these restore jobs, so this can happen.

      the restore jobs appear with only a resource request and resource granted message inside of the job's detailed status section.no other information:

      Sep 09, 2020 12:01:02 AM - requesting resource @aaaad
      Sep 09, 2020 12:01:03 AM - granted resource MediaID=@aaaad;DiskVolume=PureDiskVolume;DiskPool=DISKPOOL01;Path=PureDiskVolume;StorageServer=Mediaserver.com;MediaServer=Mediaserver.com
      the requested operation was successfully completed (0)

      Thanks again for your help.

      I have asked the client to send me the file nbdeployutilconfig.txt to take a look at it.

      • davidmoline's avatar
        davidmoline
        Level 6
        4 years ago

        Hi Hamza_H two things - first is that the nbdeployutilconfig.txt file only exists if you want to change something (i.e. it is not there by default - and then the default values are used as shown in the link I provided. Second is that you should have the customer try uncommenting that parameter from the old technote to see if it makes a difference.