System Center Data Protection Manager 2012 R2

  1. DPM is unable to generate reports. This may be because of an invalid or inaccessible web.config file for the SQL Server Reporting ...
  2. DPM is unable to protect your mirrored SQL Server database(s) %Component; until you install protection agents on the following ...
  3. DPM needs to read tapes that contain the selected datasource to display the recoverable items. This operation can only be ...
  4. DPM needs to read tapes that contain the selected datasource to display the recoverable items. When tapes are offline you ...
  5. DPM network bandwidth usage throttling is not working because the Windows Quality of Service (QoS) Packet Scheduler is not ...
  6. DPM Online activation failed when trying to retrieve information from the Windows Management Instrumentation (WMI) service ...
  7. DPM protection agent on %AgentTargetServer; could not complete the operation due to insufficient resources on the computer. ...
  8. DPM protects SQL Server databases differently depending upon how they are configured. The configuration 2 databases below ...
  9. DPM reporting is not yet activated because the required security settings could not be applied to the DPMReport local account. ...
  10. DPM requires a unique and exclusive user account to communicate with the workgroup server. Goto the protected computer and ...
  11. DPM requires the Microsoft$DPM$ instance of SQL Server. None of the existing SQL Server installations have the name Microsoft$DPM$. ...
  12. DPM requires the Replica writer to be disabled for protecting Exchange 2007 with LCR. Please disable the replica writer by ...
  13. DPM Self Service Recovery feature uses port 6075. Please ensure the firewall rules are configured to accept incoming connections ...
  14. DPM Self Service Recovery Tool was unable to get a response from the DPM Server %ServerName;. This may be because the server ...
  15. DPM Setup could not create a required service. This computer may be protected by another computer running DPM. You cannot ...
  16. DPM setup could not schedule the launch of SQL System Configuration Checker post restart. Restart the machine and run the ...
  17. DPM Setup creates the following restricted local user accounts. Specify a strong password for the accounts. This password ...
  18. DPM Setup detected that the SQL Agent on node %PhysicalNode; runs under a different account name than other nodes in the ...
  19. DPM Setup detected that the SQL server provided to it is clustered. For clustered SQL server, the SQL Reporting server needs ...
  20. DPM Setup detected that the SQL server provided to it is not clustered. For non-clustered SQL server, the SQL Reporting server ...
  21. DPM Setup failed to get the fully qualified domain name for either the computer running DPM or the computer with the selected ...
  22. DPM Setup has detected an existing installation of DPM on this computer. The existing installation is a later version than ...
  23. DPM Setup has detected that the current installation of DPM uses an expired instance of the Evaluation Edition of SQL Server ...
  24. DPM Setup has detected that the current installation of DPM uses the Evaluation Edition of SQL Server 2000 Reporting Services. ...
  25. DPM Setup has detected that the currently installed Data Protection Manager is lower than the System Center 2012 SP1 Data ...
  26. DPM Setup has detected that the specified user does not belong to the Administrator group on the computer running the SQL ...
  27. DPM Setup has detected that the specified user does not belong to the sysadmin role on the specified SQL Server instance. ...
  28. DPM setup has detected that Windows PowerShell 2.0 CTP is installed on this server. Uninstall any pre-release versions of ...
  29. DPM Setup has detected that: 1)The specified user does not belong to the Administrator group on the computer running the ...
  30. DPM Setup has not configured Reporting Services to use Secure Sockets Layer. For more information on how to configure the ...
  31. DPM Setup is unable to detect if the SQL server specified is clustered. Check if the SQL server instance name provided in ...
  32. DPM skipped cloud backup for %DatasourceType; %DatasourceName; on %ServerName; because the latest disk backup is already ...
  33. DPM Synchronization completed. Your tape library status may have changed. Recommendation: Go to the Library tab in the Management ...
  34. DPM tried to do a SQL log backup, either as part of a backup job or a recovery to latest point in time job. The SQL log backup ...
  35. DPM was not able to apply the permissions existing at the time of creation of recovery point while recovering SharePoint ...
  36. DPM was unable to access the cluster resource group %VirtualName; for %DatasourceName; of protection group %ProtectedGroup; ...
  37. DPM was unable to access the cluster resource group %VirtualName; for %DatasourceName; of protection group %ProtectedGroup;. ...
  38. DPM was unable to compile a list of recoverable objects for %DatasourceType; %DatasourceName;. You will be unable to perform ...
  39. DPM was unable to configure Active Directory for end-user recovery because a recent change to Active Directory has not yet ...
  40. DPM was unable to configure and start the VmmHelperService on the DPM Server. Server name: %ServerName;. Exception Message: ...
  41. DPM was unable to detach the content database %ContentDatabase; from the recovery farm. Exception Message = %ExceptionMessage;. ...
  42. DPM was unable to determine the right node for backing up the Availability Group database and hence failed the backup. Database: ...
  43. DPM was unable to establish a connection with the Virtual Machine Manager (VMM) server. Server name: %ServerName;. Exception ...
  44. DPM was unable to export the item %SiteUrl; from the content database %ContentDatabase;. Exception Message = %ExceptionMessage;. ...
  45. DPM was unable to get the content sources of the SharePoint Service Provider (SSP) %DatasourceName; to a consistent state. ...
  46. DPM was unable to get the list of data sources on %PSServerName; that are protected by the primary DPM server %ServerName;. ...
  47. DPM was unable to protect the members in the resource group %ObjectName;. This resource group contains some resources that ...
  48. DPM was unable to recatalog the tape in %MediaLocationType; %MediaLocationInfo; in %LibraryType; %Library; because this tape ...
  49. DPM was unable to remove the protected computer %ServerName; from one of the following groups: 1. Distributed COM users 2. ...
  50. DPM was unable to remove the protected computer %ServerName;, which includes active or inactive protection on this DPM server. ...
  51. DPM was used to trigger the recovery for %DatasourceType; %DatasourceName; on %ServerName;. After this operation is complete, ...
  52. DPM will create an online recovery point using the latest DPM replica on disk. No new data will be transferred from the protected ...
  53. DPM will create an online recovery point using the latest DPM replica on disk. No new data will be transferred from the protected ...
  54. DPM will look for your recovery tapes only in the selected library. Ensure that you load the tapes required for recovery ...
  55. DPM will recatalog the selected imported tapes to extract information about the data that they contain. After the recatalog ...
  56. DPM will verify whether the selected items can be read from the tape that contain them. Readability of data in a tape is ...
  57. DPM writer was unable to snapshot the replica of %DatasourceName;, because the replica is not in a valid state (Validity: ...
  58. DPM writer was unable to snapshot the replica of %DatasourceName;. This may be due to: 1) No valid recovery points present ...
  59. DpmWriter service encountered an error during PrepareBackup as more than one component is selected for backup in the same ...
  60. Drive %DriveName; will be automatically cleaned by DPM. If you are seeing this error frequently, please service the drive. ...
  61. During recovery, backup data from the Microsoft Azure Backup Service needs to be temporarily downloaded to a local staging ...
  62. During recovery, backup data from the {0} needs to be temporarily downloaded to a local staging area before it is recovered ...
  63. Dynamic disks use a private region of the disk to maintain a Logical Disk Manager (LDM) database. The current occupancy of ...
  64. Dynamic disks use a private region of the disk to maintain a Logical Disk Manager (LDM) database. The LDM database is currently ...
  65. Dynamic disks use a private region of the disk to maintain a Logical Disk Manager (LDM) database. The LDM database will be ...
  66. Dynamic disks use a private region of the disk to maintain a Logical Disk Manager (LDM) database. This volume creation or ...
  67. Either %ServerName; needs reboot or if %ServerName; is part of a cluster then some/all nodes in the cluster need to be rebooted. ...
  68. Either because this replica was restored from a backup that was not created using the DpmBackup tool, or because the GUID ...
  69. Either run a synchronization, or wait for the next scheduled synchronization to occur. If the problem persists, check your ...
  70. Either stop protecting this data source from this DPM server or take over ownership of the data source for this DPM server. ...
  71. Either stop the DPM protection agent service on %ServerName; and make sure that the QoS Packet Scheduler is enabled, or disable ...
  72. Either the database files are corrupt or the proper versions of the Eseutil.exe and Ese.dll files are missing. If you have ...
  73. Enable case-sensitive support on the DPM server by following the steps described in http://support.microsoft.com/default.aspx?scid=kb;EN-US;938455. ...
  74. Enable the protection agent on the protected computer in DPM Administrator Console, in the Management task area, on the Agents ...
  75. End-users can not recover previous versions of files from Data Protection Manager if shadow copies are being saved locally ...