Hello everyone, I have 4 scalabilities that are collecting information, however, within the DSM \ ServerDB \ SECTOR \ COLLECT \ 00000001 directory it accumulates 50,000 files.I also noticed that the engine is processing very slow, someone has already gone through something similar?
It means either your collect engine is not running or the collect job fails, check your domain manager to find the collect job for that specific SS then see what it is dong.
Principal Engineering Services Architect
Mobile: +1 703 655 7161 | Richard.Lechner@ca.com
These are inventory files sent by the agents, to the scalability server. Is the same happening for all SS, or only one of them?
These files get collected by an Engine on the DM. You mention you have (4) SS, so you should have (5) Collect Tasks running on the DM. One for the DM's own built-in scalability server, and four more for each remote scalability server.
So what are the status of these collect tasks on the engine?
Are all (5) collect tasks linked to an engine?
What are the status and last run dates?
In the activity window of the engine, you should see files getting processed.
Hello Brian, I have 4 scalings and one engine for each. It's happening in 3 out of 4 scalabs. On the screen of the engine I see the files being processed, but it is processing only 1 files every 15 seconds, approximately.
kb000046211: Scaling Client Automation: How to improve Collect Task and Replication Task Performance by Limiting the amount of Hardware and Software scans sent by Agents.https://comm.support.ca.com/kb/scaling-client-automation-itcm-how-to-improve-collect-task-and-replication-task-performance-by-limiting-the-amount-of-hardware-and-software-scans-sent-by-agents/kb000046211
Follow these two recommendations from the linked document:
- Recommendation: Reduce the frequency of hardware inventory scans
- Recommendation: Advanced engine settings
Hello Brian, thanks for the tip.I performed the tunning of the environment as the document indicates, however, it remains extremely slow.I opened a ticket in support to help with the problem.
There could be MANY reasons for the engines not keeping pace with the collections, from architectural problems to database issues, network issues and many others. Please open a support case so some investigation can be performed.
Steve McCormick, ITIL
Principal Services Consultant
Hello Stephen, I already opened a ticket on the media. Thank you.