System Center Data Protection Manager 2012 R2

  1. The parameter set that you have specified is incorrect. Specify only short-term disk and long-term Online policy objective. ...
  2. The parameter set that you have specified is incorrect. Specify only short-term disk and long-term tape policy objectives. ...
  3. The parent instance of at least one of the SQL databases selected is auto-protected. Unless you turn-off auto-protection ...
  4. The path to the SQL temporary folder for %DatasourceType; %DatasourceName; on %ServerName; is too long. This can cause backup ...
  5. The protected volume %VolumeName; on %ServerName; could not be accessed. The volume may have been removed or dismounted, ...
  6. The protection agent could not be removed from %ServerName;. The computer may no longer have an agent installed or may no ...
  7. The protection agent installation failed because another version of the protection agent is already installed on %ServerName;. ...
  8. The protection agent installation failed because the files needed to install the protection agent (version %AgentVersion;) ...
  9. The protection agent installation failed. The credentials you provided do not have administrator privileges on %ServerName;. ...
  10. The protection agent installation failed. There was an error in reading the files needed to install the protection agent ...
  11. The protection agent is incompatible with the version of DPM that is installed on this computer. All subsequent protection ...
  12. The protection agent is incompatible with the version of DPM that is installed on this computer. All subsequent protection ...
  13. The protection agent on %ServerName; is not compatible with the DPM version. The protection agent version is %AgentVersion;, ...
  14. The protection agent operation failed because DPM could not communicate with the Protection Agent service on %ServerName;. ...
  15. The protection agent operation failed because it could not access the protection agent on %ServerName;. %ServerName; may ...
  16. The protection agent uninstall is unavailable because the DPM server is currently communicating with the protection agents ...
  17. The protection agent upgrade failed because %ServerName; has a more recent version of the protection agent (version %AgentVersion;) ...
  18. The protection agent upgrade is unavailable because the DPM server is currently communicating with the protection agents ...
  19. The protection group configuration has changed and therefore this job cannot be re-run. On the Jobs tab in the Monitoring ...
  20. The recovery failed for %DatasourceType; %DatasourceName; on %ServerName; because a mirroring session exists for this database. ...
  21. The recovery jobs for %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, are in progress. ...
  22. The recovery jobs for %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, have completed. ...
  23. The recovery jobs for %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, have successfully ...
  24. The recovery jobs for %DatasourceName; that started at %StartDateTime;, with the destination of %TargetServerName;, have ...
  25. The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
  26. The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
  27. The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
  28. The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
  29. The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %TargetServerName;, ...
  30. The recovery point window defines the granularity of time in which you expect a minimum of one good recovery point for each ...
  31. The recovery points for application replicas on the secondary DPM server use the express full backup schedule and synchronization ...
  32. The recovery target location %FolderPath;, does not exist or cannot be accessed. Please verify the recovery target location ...
  33. The recovery to the latest point in time failed. During a recovery to the latest point in time, DPM tries to do a tail log ...
  34. The recovery to the latest point in time has failed. During a recovery to the latest point in time, DPM tries to do a SQL ...
  35. The replica for %DatasourceName; on %ServerName; is currently being synchronized with consistency check. A consistency check ...
  36. The replica for %DatasourceType; %DatasourceName; is currently being synchronized with consistency check. A consistency check ...
  37. The replica for %DatasourceType; %DatasourceName; on %ServerName; is not created. Replica creation job is scheduled to run ...
  38. The replica for %DatasourceType; %DatasourceName; on %ServerName; is not created. You have chosen to create the replica manually. ...
  39. The replica is inconsistent for %DatasourceType; %DatasourceName; on %ServerName; due to a CCR failover. A synchronization ...
  40. The replica of %DatasourceName; on %ServerName; is being created. After the initial copy is made, only incremental changes ...
  41. The replica of %DatasourceName; on %ServerName; is inconsistent with the protected data source. All protection activities ...
  42. The replica of %DatasourceName; on %ServerName; is inconsistent with the protected data source. All protection activities ...
  43. The replica of %DatasourceType; %DatasourceName; on %ServerName; is being created. After the initial replica is created, ...
  44. The replica of %DatasourceType; %DatasourceName; on %ServerName; is inconsistent with the protected data source. All protection ...
  45. The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...
  46. The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...
  47. The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...
  48. The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM error ...
  49. The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM has ...
  50. The replica on the DPM server for %DatasourceType; %DatasourceName; on %ServerName; is inconsistent with the protected data ...
  51. The replicas for one or more of the volumes being protected are missing. This may be a result of one or more disks in the ...
  52. The reporting components could not be installed. You can still continue to protect, monitor and recover data. Click on the ...
  53. The requested changes to the protection group %ProtectedGroup; will initiate an immediate consistency check on the following: ...
  54. The rescan operation checks for new libraries attached to the DPM server and refreshes the state of currently attached libraries. ...
  55. The search string should use UNC Format if the protected computer is not specified. If the search is intended on a folder, ...
  56. The selected data cannot be recovered to the DPM server %ServerName; because the replica is not in "replica creation pending" ...
  57. The selected data sources are protected by the primary DPM server %InputParameterTag;. This DPM server is protecting the ...
  58. The selected data sources cannot be added to the same protection group. A protection group must have either client data sources ...
  59. The selected data sources were previously protected by the primary DPM server %InputParameterTag;. Performing this operation ...
  60. The selected data will be copied to the specified location. You can monitor the progress of the copy job(s) on the Jobs tab ...
  61. The selected database has one or more FILESTREAM data groups. You cannot recover such database to the pre configured file ...
  62. The selected datasource(s) cannot be configured for copy backup because it is either a standalone MailBox DB or a DR replica ...
  63. The selected drive is the only functioning drive in the library. Disabling it would fail all the protection jobs that are ...
  64. The selected tape is currently being recataloged. The contents of this tape can be viewed only after the recatalog operation ...
  65. The selected tapes cannot be erased because they belong to protection groups. You need to stop protection of the associated ...
  66. The selected tapes cannot be marked as free because they belong to protection groups. You need to stop protection of the ...
  67. The selected volume %VolumeName; cannot be protected as it does not have a drive letter or a mount point. DPM only protects ...
  68. The server %PSServerName; does not have a DPM protection agent installed or is not protected by the DPM server %ServerName;. ...
  69. The server registration certificate could not be retrieved from the local certificate store. Verify that a valid certificate ...
  70. The server registration certificate for this server is no longer valid and cannot be used to authenticate this server with ...
  71. The service %Name; is running under %Credentials; credentials. It should be running under domain user credentials or Local ...
  72. The service might be installing an update or be in the process of being recovered. Please try the operation again after a ...
  73. The service version of the azure backup service and the Windows Azure Backup Agent do not match. Please install the latest ...
  74. The Setup Wizard completed successfully, but the Reporting components could not be installed (you can retry installing Reporting ...
  75. The Setup Wizard completed successfully, but the Reporting components installation was cancelled ( you can install Reporting ...