Troubleshooting DpmBackup and DPM Writer

  • Article

Published : September 27, 2005

When you encounter a problem with DpmBackup, wait 10 minutes and then run DpmBackup again, up to three times. If you are still unable to run DpmBackup successfully, see Table 6.9 for the steps you need to take to resolve the specific error condition you are experiencing.

DpmBackup can fail to complete successfully because of problems with communication, access, or space. Some of these problems are transient and will correct themselves.

Table 6.9   Resolving DpmBackup and DPM Writer Errors

Error message

Possible causes

To troubleshoot this error

Error 4200: DPM Writer could not be contacted. Make sure that Data Protection Manager is installed and that the DPM Writer service is running.

This error can occur if the DPM Writer is not registered with VSS and is not listed as an available writer in the system.

  1. Restart DPM Writer by using the Services snap-in.

  2. Restart Volume Shadow Copy by using the MMC Services snap-in.

  3. Run DpmBackup again.

  4. If the previous steps do not resolve the problem, examine the event log for DPM Writer errors.

Error 4201: The backup operation did not complete successfully. Some backup shadow copies could not be created. Please try the backup operation again.

This error can occur if the shadow copies fail to mount to the Shadow Copy folder or if the shadow copy is not created successfully.

This error message also displays when DpmBackup does not complete successfully and no other error message applies.

Delete any files in the Shadow Copy folder for the failing volumes, if files were created manually in that folder, and run DpmBackup again.

If DpmBackup still does not complete successfully, try the following steps:

  1. Restart DPM Writer by using the MMC Services snap-in.

  2. Restart the Volume Shadow Copy service by using the MMC Services snap-in.

  3. Run DpmBackup again.

  4. If the previous steps do not resolve the problem, examine the event log for DpmBackup errors.

Error 4202: The backup operation failed. One or more of the replica volumes does not have enough disk space for the backup shadow copy.

This error occurs when there is insufficient storage space on a replica volume in the storage pool.

  1. Determine which volume failed by reviewing the output of the DpmBackup command.

  2. Increase the disk space available to that volume.

  3. Run DpmBackup again.

Error 4204: The backup operation failed. DpmBackup could not delete the backup shadow copies that were previously created.

When you run DpmBackup, shadow copies that were created by DpmBackup in previous backup operations are deleted, and then new shadow copies are mounted to that path.

This error occurs if the previous shadow copies are not deleted successfully.

  1. Ensure that no user changes were made to the volume or disk configuration.

  2. Restart Volume Shadow Copy by using the MMC Services snap-in.

  3. Check the status of the disk or volume that you are backing up.

  4. Run DpmBackup again.

Error 4205: DpmBackup was unable to back up the DPM or DPM Report databases.

DPM uses SQL Distributed Management Objects (SQL-DMO) to back up the DPM and Report databases. This error occurs because of a problem with SQL-DMO Backup.

  1. Check the application event log for SQL Server messages.

  2. Verify the presence and functionality of the databases on the SQL Server server by using the SQL Enterprise Manager MMC snap-in.

  3. Ensure that permissions were not changed on the database and on the database backups folder.

  4. If the previous steps do not resolve the problem, restart the SQL Server services.

Error 4206: DPM Writer could not connect to the specified database. Make sure that the SQL Server services are running with appropriate privileges.

This error occurs when VSS and the DPM Writer are unable to connect through the Microsoft SQL Server Desktop Engine (MSDE) Writer to the DPM and Report databases.

If you encounter this DPM Writer error when running an application other than DpmBackup, use the documentation for that application as your source for troubleshooting assistance.

  1. Verify the presence and functionality of the databases on the SQL Server server by using the SQL Server Enterprise Manager MMC snap-in.

  2. Restart the SQL Server services.

Error 4207: DPM Writer could not query the specified database. Make sure that the SQL Server services are running with appropriate privileges.

This error occurs because of a SQL Server exception.

  1. Check the application event log for SQL Server messages.

  2. Verify the presence and functionality of the databases on the SQL Server server by using the SQL Server Enterprise Manager MMC snap-in.

  3. Restart the SQL Server services.

Error 4208: DPM Writer could not access the registry. Make sure that Data Protection Manager is installed correctly.

This error occurs when DPM registry keys have been changed incorrectly or are corrupt.

  • If you are aware of changes to the registry, revert the changes to the previous state.

  • You can attempt to resolve this problem by uninstalling DPM, using the retain data option, and then reinstalling the same version of DPM to the same location.

  • If you do not know of any changes to the registry, or you are unable to restore the registry, contact Microsoft Help and Support (https://go.microsoft.com/fwlink/?linkid=45276).

Error 4209: DPM Writer encountered an internal error. Please restart the DPM Writer service, and then try the backup operation again.

This error can have numerous causes.

  • Restart DPM Writer by using the MMC Services snap-in, and then run DpmBackup again.

  • Restart the DPM server and then run DpmBackup again.

  • Check the application and system event logs for information on the error.

  • Contact Microsoft Help and Support (https://go.microsoft.com/fwlink/?linkid=45276).

Error 4210: DpmBackup encountered an internal error. Please try the backup operation again.

This error can have numerous causes.

  • Restart DPM Writer by using the MMC Services snap-in, and then run DpmBackup again.

  • Restart the DPM server and then run DpmBackup again.

  • Check application and system event logs for information on the error.

  • Contact Microsoft Help and Support (https://go.microsoft.com/fwlink/?linkid=45276).

Error 4211: You do not have sufficient privileges to perform this operation.

This error occurs when you run DpmBackup by using an account that does not have the user right to back up files and directories.

  1. Verify that the account you are using to run DpmBackup is a member of the Backup Operators or Administrators groups.

  2. In the Local Security Policy snap-in, verify that the Backup Operators and Administrators groups are granted the right to back up files and directories. This user right is located in Security Settings\Local Policies\User Rights Assignment.

  3. Restart DPM Writer by using the MMC Services snap-in.

  4. Restart the Volume Shadow Copy service by using the MMC Services snap-in.

  5. Run DpmBackup again.

  6. If the previous steps do not resolve the problem, restart the DPM server and then run DpmBackup again.

  7. Also, ensure that security permissions in the Program Files\Microsoft Data Protection Manager\ directory structure have not been changed.

Error 4213: The backup operation failed. DpmBackup was unable to start the DPM Writer service.

This error can occur when:

  • The account under which the DPM Writer runs is changed or the incorrect account is specified. DPM Writer uses the Microsoft$DpmWriter$ account.

  • The password for the account under which the DPM Writer runs is changed or the incorrect password is specified.

  • Service Control Manager (SCM) cannot start DPM Writer because permissions have been changed or removed.

  • DPM Writer service has been deleted.

  1. Check application and system event logs for reasons why the service failed to start.

  2. Start DPM Writer by using the MMC Services snap-in.

Error 4214: DpmBackup was unable to stop the DPM Writer service. Please stop the service manually by using the MMC Services snap-in.

This error can occur when:

  • DPM Writer service is busy with a backup operation.

  • DpmBackup permissions have been changed so that it no longer has permission to stop the service.

  1. Check application and system event logs for reasons why the service failed to stop.

  2. Stop DPM Writer by using the MMC Services snap-in.