Occupancy data missing from some NW-servers

Hi Teemu,

Though the problem could be in multiple areas such as reporter process, listener process or collector process we would start with the collector process is debug low to see what errors of data collection may be in the log. Put the collector in debug low mode (File-->System settings --->select the particular collector and set the debug mode to 'Debug Low'). Restarting the collectro should make all assignations run. After 15 minutes or so you can check the collector log to see what errors there may be. If that does not assist then best ot open a support case so the problem can be examined in more detail.

Thanks

Dan

Hi Teemu,

No this wouldn't cause occupancy data to not appear. Now that you have gathered some logs it may be best to open an SR so that a member of the support team can investigate them for you.

Kind Regards

David

David Russell

EMC Technical Support

Finally had time to pursuit this issue forward. I did as admin quide tolds, put one NW-server's collector-process to "Debug low" settings and recycled log-file and procesess. Result: After 2 minutes I had three 128MB log files generated (max. size per log-file). So there is quite big task to go through those. Any suggestions that I should be after, little bit easier to find if you know what to look for.

.teemu

Hi Teemu,

It can be difficult to troubleshoot the client occupancy request in a Debug low log as the request can run for a long time and generate lots of log data. Before looking into these logs can you run the following 2 reports against one of the servers not returning client occupancy data:

DPA Request History - On the menu under DPA, History, Request History

Collector Errors - On the menu under DPA, Errors, Collector Errors

For the first report (Request History) can you check to the NetWorker Client Occupancy requests to see if they have been running and finishing correctly? Could you then also check the Collector Errors report for any errors relating to the Client Occupancy requests?

Thanks

David

David Russell

EMC Technical Support

Hi,

Did try both of those reports agains working NW and non-working NW. Same result, no data is logged related to Occupancy-data at either cases. So this way it seems to be impossible to tacle this issue or gain anything relevant info. Only fail that occured was on that non-working NW:

Storage node and master server clocks not synchronized - backup job data for client nnn may be incorrect

I have asked our NW-admins to correct that issue but could it be reason for this?

.teemu