Using Dashboard › Troubleshooting Dashboard › Dashboard Troubleshooting › SRM data probe performance problem

SRM data probe performance problem

If the performance of your SRM probe is either taking an excessive amount of time or using an excessive amount of system resources, you can configure the number of simultaneous connections (parallel threads) to enhance this performance. To change the performance of the SRM data collection process you need to add a new registry key and then modify the value for these parallel threads to meet your specific needs.

To configure the SRM probe thread count setting in the Registry Editor

1. Open the Registry Editor.
2. Expand the tree in the browser of the Registry Editor by selecting the following:

   HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\CA ARCServe Backup\Base\Task\Common

3. Add a new key (if it does not already exist) and name it "SRMReportTime".
4. Add a new DWORD Value and name it "ThreadCount".
5. Double-click the Thread Count option to open the Edit DWORD Value dialog. You can now modify the DWORD setting.

   By default Arcserve Backup has this SRM data collection value set to 16 threads until you add this new key. The minimum allowable value is 1 (meaning a single thread will be used to collect the SRM data) and maximum allowable value is 32 threads. Any value entered greater than 32 will be ignored and revert to this maximum value of 32 parallel threads.

   • As you increase the number of parallel threads, it will reduce the overall SRM probe time; however, it will also increase the impact on your system resources.
   • As you decrease the number of parallel threads, it will reduce the impact on your backup server; however, it will also increase the overall SRM probe time.
6. When you finish configuring the Thread Count option for the SRM probe, close the Registry Editor and restart the Database engine service on the Arcserve Backup server.