Microsoft Office Tutorials and References
In Depth Information
DPM processes that impact DPM performance
Msdpm.exe : The DPM service is the core component of DPM. The DPM
service manages all core DPM operations, including replica creation,
synchronization, and recovery point creation. This service implements
and manages synchronization and shadow copy creation for protected file
servers.
DPMLA.exe : This is the DPM Library Agent Service .
DPMRA.exe : This is the DPM Replication Agent . It helps to back up and
recover file and application data to DPM.
Dpmac.exe : This is known as the DPM Agent Coordinator Service . This
manages the installations, uninstallations, and upgrades of DPM protection
agents on remote computers that you need to protect.
DPM processes that impact DPM performance
The Msdpm.exe , MsDpmProtectionAgent.exe , Microsoft$DPM$Acct.exe , and
mmc.exe processes take a toll on DPM performance. mmc.exe is a standard Windows
service. "MMC" stands for Microsoft Management Console application and is used
to display various management plug-ins. Not all but a good amount of Microsoft
server applications run in the MMC such as Exchange, ISA, IIS, System Center, and
the Microsoft Server Manager. The DPM Administrator Console runs in an MMC
as well. mmc.exe can cause high memory usage. The best way to ensure that this
process does not overload your memory is to close the DPM Administrator Console
when not using it.
MsDpmProtectionAgent.exe is the DPM Protection Agent service and affects both
CPU and memory usage when DPM jobs and consistency checks are run. There is
nothing you can do to get the usage down for this service. You just need to be aware
of this and try not to schedule any other resource intensive applications such as
antivirus scans at the same time as DPM jobs or consistency checks.
Mspdpm.exe is a service that runs synchronization and shadow copy creations
as stated previously. Like MsDpmProtectionAgent.exe , Mspdpm.exe also affects
CPU and memory usage when running synchronizations and shadow copies.
Like MsDpmProtectionAgent.exe there is nothing you can do to the Mspdpm.
exe service to reduce memory and CPU usage. Just make sure to keep the system
clear of resource intensive applications when the Mspdpm.exe is running jobs. If
you are running a local SQL instance for your DPM deployment you will notice a
Microsoft$DPM$Acct.exe process. The SQL Server and SQL Agent services use
a Microsoft$DPM$Acct account. This normally runs on a high level. This service
reserves part of your system's memory for cache. If the system memory goes low, the
Microsoft$DPM$Acct.exe process will let go of the memory cache it has reserved.
 
Search JabSto ::




Custom Search