Forum Discussion

LT2000's avatar
LT2000
Level 4
13 years ago

OpsCenter data collection not working

Hello,

One of our NB domains has been having issues with VBR. So we installed OpsCenter 7.1.0.3 to see if that would resolve the problem, and it did not.

Basically we have to disable/enable data collection to get up to date "Job" information. Some of the other data types (Device, Volume, Media Server) have relatively recent (ie., within the last 10 minutes) "Last Run Time" and "Last Successful Load". But the most important metric, the Job data type stops collecting after the initial enabling of data collection. The team responsible for this environment does have an open case with Symantec, but thus far they have not gotten anywhere. No exception messages appear in the status.

We are reporting on a NetBackup 6.5.6 environment running on a solaris master server.

I did increase a timeout parameter in the scl.conf file (set it to one hour), and although that did aleviate a timeout condition with the Subjobs collection, we are still having the problem with Jobs.

Thanks

3 Replies

  • Since you are collecting NBU 6.5.x data, I assume you have an Agent Installed...

    Tune the Agent Heap Size first... 

     

    Adjusting the default heap size for the OpsCenter Agent

     
    Next, verify how many jobs show in Activity Monitor? 
    How many days are reflected in Activity Monitor?
     
    In addtion, verify if there are any old nbproxy_nbsl*.ior  / nbproxy_nbsl*.ior.mgr files present on the system.
     
    Unix:           /usr/openv/var/
    Windows:    /installpath/netbackup/var/
     
    There should be some ior / ior.mgr files present, however, if you see these files with dates older then your last service cycle on your master, you will want to clean these files up.
     
    Please stop NetBackup on the Master, remove these files ( *.ior / *.ior.mgr) and restart NetBackup on the Master.
     
    Cycle Data Collection, and verify the Jobs Data Type Collection completes or fails.
     
    Let me know your results.
     
    --Tom
     
     
     
  • I did increase the heap size on the agent. however, I do not have the flexibility to restart the NB daemons on the master (nor do I have the access). However, one thing I forgot to mention is that the master is clustered...not sure if that makes a difference.

    I did check for those ior and ior.mgr files and there are some dating back to 2009...

    On the passive node:

    -rw-rw-rw-   1 root     other       1303 Jul 23  2009 nbproxy_nbsl-DeviceManagement-10.ior.mgr
    -rw-rw-rw-   1 root     other       1303 Jul 23  2009 nbproxy_nbsl-DeviceManagement-11.ior.mgr
    -rw-rw-rw-   1 root     other       1303 Jul 23  2009 nbproxy_nbsl-DeviceManagement-12.ior.mgr
    -rw-rw-rw-   1 root     other       1303 Jul 23  2009 nbproxy_nbsl-DeviceManagement-13.ior.mgr
    -rw-rw-rw-   1 root     other       1303 Jul 23  2009 nbproxy_nbsl-DeviceManagement-14.ior.mgr
    -rw-rw-rw-   1 root     other       1303 Jul 23  2009 nbproxy_nbsl-DeviceManagement-15.ior.mgr
    -rw-rw-rw-   1 root     other       1303 Jul 23  2009 nbproxy_nbsl-DeviceManagement-16.ior.mgr
    -rw-rw-rw-   1 root     other       1319 Jul 23  2009 nbproxy_nbsl-ServiceManagement-10.ior.mgr
    -rw-rw-rw-   1 root     other       1319 Jul 23  2009 nbproxy_nbsl-ServiceManagement-11.ior.mgr
    -rw-rw-rw-   1 root     other       1319 Jul 23  2009 nbproxy_nbsl-ServiceManagement-12.ior.mgr
    -rw-rw-rw-   1 root     other       1319 Jul 23  2009 nbproxy_nbsl-ServiceManagement-13.ior.mgr
    -rw-rw-rw-   1 root     other       1319 Jul 23  2009 nbproxy_nbsl-ServiceManagement-14.ior.mgr
    -rw-rw-rw-   1 root     other       1319 Jul 23  2009 nbproxy_nbsl-ServiceManagement-15.ior.mgr
    -rw-rw-rw-   1 root     other       1319 Jul 23  2009 nbproxy_nbsl-ServiceManagement-16.ior.mgr
    -rw-rw-rw-   1 root     other       1319 Jul 23  2009 nbproxy_nbsl-ServiceManagement-5.ior.mgr
    -rw-rw-rw-   1 root     other       1319 Jul 23  2009 nbproxy_nbsl-ServiceManagement-6.ior.mgr
    -rw-rw-rw-   1 root     other       1319 Jul 23  2009 nbproxy_nbsl-ServiceManagement-7.ior.mgr
    -rw-rw-rw-   1 root     other       1319 Jul 23  2009 nbproxy_nbsl-ServiceManagement-8.ior.mgr
     

    On the active:

    -rw-rw-rw-   1 root     root        1735 Jul 21  2009 nbproxy_nbsl-JobManagementEx-1.ior.mgr
    -rw-rw-rw-   1 root     root        1767 Jul 24  2009 nbproxy_nbsl-ServiceManagement-13.ior.mgr
    -rw-rw-rw-   1 root     root        1751 Aug  4  2009 nbproxy_nbsl-DeviceManagement-32.ior.mgr
    -rw-rw-rw-   1 root     root        1023 Sep  2  2009 nbproxy_nbsl-ManageMedia-44.ior.mgr
    -rw-rw-rw-   1 root     root        1023 Sep  3  2009 nbproxy_nbsl-ManageMedia-46.ior.mgr
    -rw-rw-rw-   1 root     root        1023 Sep  3  2009 nbproxy_nbsl-ManageMedia-48.ior.mgr
    -rw-rw-rw-   1 root     root        1023 Sep 18  2009 nbproxy_nbsl-ManageMedia-49.ior.mgr
    -rw-rw-rw-   1 root     root        1023 Sep 21  2009 nbproxy_nbsl-ManageMedia-51.ior.mgr
    -rw-rw-rw-   1 root     root        1023 Sep 21  2009 nbproxy_nbsl-ManageMedia-50.ior.mgr
    -rw-rw-rw-   1 root     root        1023 Sep 21  2009 nbproxy_nbsl-ManageMedia-52.ior.mgr

  • When you are able to perform the maintenance on the master, also request to cycle the OC-Agent Daemon for the new heap size adjustment.