-
Title
Dsamain.exe process is taking close to 80-100% CPU resources. -
Description
On the server where ADAM is installed, the Dsamain.exe process is running at a very high CPU rate. Quest Migration Manager (QMM) console is very slow to respond, and it takes a long time to bring up the GUI interface. What can be done to improve it? -
Cause
Please refer to the resolution section for more details.
-
Resolution
Dsamain.exe is the Microsoft ADAM process. DSA (Directory Synchronization Agent) is querying the ADAM project database, checking for configuration changes on a frequent basis, even if no jobs are running. The load is increased if migration sessions or synchronization jobs are performed. In the environments where multiple DSA agents are pointing to the same ADAM server the load on the server can become very high and Dsamain.exe process will come close to 100 % of CPU time.
Here are some workarounds that can be considered:
1. Consider the distributed model of the project setup covered in QMM for AD User Guide. In this scenario multiple ADAM servers are setup as replication partners and DSAs point to different ADAM servers.
2. Plan for just a few DSA agents to be installed.
3. If there is an idle DSA agent stop Configurator service in the Services applet on this DSA server. Don't forget to turn it back on when agent will be used for other jobs.
NOTE:
In order to determine what ADAM server DSA points to open this registry key on the DSA server:
HKEY_LOCAL_MACHINE\SOFTWARE\Aelita\Migration Manager\CurrentVersion\Agents\<DSAHOSTNAME>\DATABASE
Key "server" contains ADAM server name.