Troubleshooting DpmBackup and DPM Writer
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. |
|
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:
|
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. |
|
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. |
|
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. |
|
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. |
|
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. |
|
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. |
|
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. |
|
Error 4210: DpmBackup encountered an internal error. Please try the backup operation again. |
This error can have numerous causes. |
|
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. |
|
Error 4213: The backup operation failed. DpmBackup was unable to start the DPM Writer service. |
This error can occur when:
|
|
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:
|
|