Frequently Asked Questions › Preconditions and Environment to Run Arcserve UDP Data Store Capacity Planning Tool › Can We Set Normal Priority for Data Collection on the Client Node?

Can We Set Normal Priority for Data Collection on the Client Node?

To mitigate the CPU impact to other processes running on the client node when data collection is ongoing, the default value of NodeScanPriority of probe service process is set as low. The probe service process has lower priority to get CPU resource on the client node. As a result, the data collection might not impact other processes with high CPU utilization much on the client node. But data collection might need more time if the client node is with high CPU utilization.

You can modify NodeScanPriority in the Config.ini file to specify normal priority for data collection.

[Server]
NodeScanPriority=normal

The Config.ini file is on the server node. Once NodeScanPriority is modified on the server node, you need to restart Arcserve UDP Data Store Capacity Planning Tool to recognize the change. Then, the new value of NodeScanPriority is pushed to the client node to take effect when the client binaries are deployed to the client node.

• All client nodes that are newly added after you change the value of NodeScanPriority would run data collection with the new value of NodeScanPriority.
• All client nodes that were added before you change the value of NodeScanPriority would run data collection with the original value of NodeScanPriority. If you want to run data collection with new value of NodeScanPriority on these nodes, use one of the following options:
  • Delete the client node, and then add the client node again.

    The new value of NodeScanPriority is pushed to the client node when you add the node back and deploy client binaries to the node.

  • Select to remove the probe service from all source nodes when you exit/close Arcserve UDP Data Store Capacity PlanningTool.

    The new value of NodeScanPriority is pushed to all client nodes when Arcserve UDP Data Store Capacity PlanningTool is started next time and redeploys client binaries to all client nodes.