This documentation is archived and is not being maintained.

Verifying Status of the DPM Service

Updated: April 21, 2010

Applies To: System Center Data Protection Manager 2010

The DPM service runs only when DPM jobs are being processed, and it stops automatically after a job is completed. If the instructions for troubleshooting an issue direct you to verify the status of the DPM service, follow these steps.

To verify status of the DPM service

  1. On the DPM server, in Administrative Tools, open Services.

  2. In Services, right-click the DPM service in the Details pane, and then click Properties.

  3. On the General tab, ensure that Startup type is set to Automatic.

  4. To start the service, on the General tab, click Start.

    If the DPM service starts successfully, the General tab displays the service status as Started. If the DPM service is running normally, scheduled protection jobs and other DPM jobs should start.

  5. If the DPM service does not start, use Windows Event Viewer to look for possible shutdowns of services on which DPM depends. The following services are of interest:

    • DPM File Agent

    • SQLAgent$MICROSOFT$DPM$ (SQL Agent)


    • Virtual Disk Service (VDS)

    • Volume Shadow Copy (VSS)

  6. If you see a service shutdown event for any of these services, start the service and ensure that the Startup type is set to Automatic.

  7. If you cannot resolve the problem by enabling any disabled services listed in step 5, try restarting the individual services:

    1. Shut down individual services in the following order: VDS, VSS, SQL Agent, SQL Server. The DPM service shuts down automatically.

    2. Start the VSS service.

    3. Start the DPM service. If the DPM service starts successfully, all dependent services—VDS, SQL Agent, and SQL Server—will also restart.

  8. If the DPM service still does not start, restart the Windows Server operating system.

    If restarting the server does not fix the problem, a database failure might be causing the DPM service to shut down. For information on troubleshooting database failures, see Troubleshooting Database Issues.

  9. If none of these solutions resolves the problem, contact Microsoft Product Support Services for help. For information, see Microsoft Help and Support (