Hi Marc Reynolds here. I have seen some issues lately where users of System Center Data Protection Manager (DPM) protected clients have experienced slow performance on their clients after installing the DPM client. There have been two scenarios reported:
1. When booting up a DPM protected client the system is unresponsive for several minutes.
2. Users experience slow performance on their client while DPM synchronization is occurring.
In the first scenario the DPM client has a scheduled task that runs at boot up. This can adversely impact the performance of the computer especially if there are multiple applications that start loading at the boot up time.
In the second scenario the DPM synchronization is monopolizing disk reads. Once the DPM synchronization completes performance then returns to normal.
Resolving slow start ups:
To avoid the DPM client backup from interfering with regular boot up, we need to delay the triggering of backup by few minutes. There should be a hotfix available for this in an upcoming QFE. Until then, the workaround is to create a new scheduled task for the ScheduledDPMClientBackup and include a delay start of 15 – 30 minutes.
1. Open Task Scheduler (or Scheduled Tasks on XP clients).
2. Navigate to the Task Scheduler Library.
3. Select “ScheduledDPMClientBackup” and note the settings on each tab as you will use these when you create a new task.
4. Click "Create Task" from the Actions pane.
5. Create a new scheduled task with properties the same properties as the default ScheduledDPMClientBackup.
6. On the "Triggers" tab of the new task click on the trigger to highlight it and then click "Edit".
7. Under "Advanced settings" check "Delay task up to" and select 30 minutes in the drop down box.
8. Delete the original scheduled task created during agent install & just keep the new scheduled task created for the same purpose.
Note Editing the old scheduled task to delay it by 15/30 minutes will not solve the problem.
Resolving slow performance during DPM synchronizations:
To improve performance on the client during DPM synchronization use the registry keyDWORD WaitInMSPerRequestForClientRead. This key is not created by default. You must create it at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\ClientProtection.
The default value for this DWORD is 50 (32H) and the supported range is 40 to 100. You can increase it to 75 to improve responsiveness. If you want to increase backup speed at the expense of responsiveness, reduce the value to 40.
Note Increasing the WaitInMSPerRequestForClientRead value will cause the DPM synchronization jobs to take longer.
Marc Reynolds | Senior Support Escalation Engineer
App-V Team blog: http://blogs.technet.com/appv/
AVIcode Team blog: http://blogs.technet.com/b/avicode
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
OOB Support Team blog: http://blogs.technet.com/oob/
Opalis Team blog: http://blogs.technet.com/opalis
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: http://blogs.technet.com/mdm/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/