System Center Data Protection Manager 2012

  1. The library %Library; requires all drives to be empty in order to lock or unlock the door. However, the drive %DriveName; ...
  2. The limit for the frequency of incremental backups of SQL Server databases on a SQL Server that has more than %MaxSQLDbsForIncr; ...
  3. The maximum number of data sources that a DPM server can protect is %MaxDataSources;. If you exceed this limit, DPM server ...
  4. The maximum number of disaster recovery (DR) data sources that a DPM server can protect is %MaxDataSources;. If you exceed ...
  5. The members that have been co-located in the selected DPM volume is given below, these cannot be changed as DPM based upon ...
  6. The minimum system requirements required to perform a successful Bare Metal Recovery is specified in BMRSystemRequirements.txt ...
  7. The missing disk contains protection group members. To continue protecting these members, you must allocate them to another ...
  8. The number of DPM licenses purchased and used are shown below. If you have purchased more licenses than shown below, type ...
  9. The number of drives reported for this library is different from the number of drives detected by DPM. If any drives are ...
  10. The number of drives reported for this library is different from the number of drives detected by DPM. If any drives are ...
  11. The number of free tapes in the %LibraryType; %Library; is less than or equals the threshold value of %ThresholdValue;. You ...
  12. The operation attempted cannot be performed at this time because maximum number of parallel backup jobs are already running. ...
  13. The operation attempted cannot be performed at this time because maximum number of parallel restore jobs are already running. ...
  14. The operation failed because DPM failed to access the shadow copy on %AgentTargetServer;. This could be due to 1) Cluster ...
  15. The operation failed because DPM failed to access the shadow copy on %AgentTargetServer;. This could be due to 1) Cluster ...
  16. The operation failed because DPM failed to access the shadow copy on %AgentTargetServer;. This could be due to 1) Cluster ...
  17. The Operation failed since DPM was unable to access the file/folder %FileName; on %AgentTargetServer;. This could be due ...
  18. The Operation failed since file/folder %FileName; was not accessible. This could be due to the file/folder being corrupt ...
  19. The parameter set that you have specified is incorrect. Specify only short-term disk along with long-term Online or long-term ...
  20. The parameter set that you have specified is incorrect. Specify only short-term disk and long-term Online policy objective. ...
  21. The parameter set that you have specified is incorrect. Specify only short-term disk and long-term tape policy objectives. ...
  22. The parent instance of at least one of the SQL databases selected is auto-protected. Unless you turn-off auto-protection ...
  23. The path to the SQL temporary folder for %DatasourceType; %DatasourceName; on %ServerName; is too long. This can cause backup ...
  24. The protected volume %VolumeName; on %ServerName; could not be accessed. The volume may have been removed or dismounted, ...
  25. The protection agent could not be removed from %ServerName;. The computer may no longer have an agent installed or may no ...
  26. The protection agent could not be removed from %ServerName;. The computer may no longer have an agent installed or may no ...
  27. The protection agent could not be removed from %ServerName;. The computer may no longer have an agent installed or may no ...
  28. The protection agent installation failed because another version of the protection agent is already installed on %ServerName;. ...
  29. The protection agent installation failed because the files needed to install the protection agent (version %AgentVersion;) ...
  30. The protection agent installation failed. The credentials you provided do not have administrator privileges on %ServerName;. ...
  31. The protection agent installation failed. There was an error in reading the files needed to install the protection agent ...
  32. The protection agent is incompatible with the version of DPM that is installed on this computer. All subsequent protection ...
  33. The protection agent is incompatible with the version of DPM that is installed on this computer. All subsequent protection ...
  34. The protection agent on %ServerName; is not compatible with the DPM version. The protection agent version is %AgentVersion;, ...
  35. The protection agent operation failed because DPM could not communicate with the Protection Agent service on %ServerName;. ...
  36. The protection agent operation failed because it could not access the protection agent on %ServerName;. %ServerName; may ...
  37. The protection agent uninstall is unavailable because the DPM server is currently communicating with the protection agents ...
  38. The protection agent upgrade failed because %ServerName; has a more recent version of the protection agent (version %AgentVersion;) ...
  39. The protection agent upgrade is unavailable because the DPM server is currently communicating with the protection agents ...
  40. The protection group configuration has changed and therefore this job cannot be re-run. On the Jobs tab in the Monitoring ...
  41. The recovery failed for %DatasourceType; %DatasourceName; on %ServerName; because a mirroring session exists for this database. ...
  42. The recovery jobs for %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, are in progress. ...
  43. The recovery jobs for %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, have completed. ...
  44. The recovery jobs for %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, have successfully ...
  45. The recovery jobs for %DatasourceName; that started at %StartDateTime;, with the destination of %TargetServerName;, have ...
  46. The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
  47. The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
  48. The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
  49. The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
  50. The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
  51. The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
  52. The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
  53. The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
  54. The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %TargetServerName;, ...
  55. The recovery point window defines the granularity of time in which you expect a minimum of one good recovery point for each ...
  56. The recovery points for application replicas on the secondary DPM server use the express full backup schedule and synchronization ...
  57. The recovery target location %FolderPath;, does not exist or cannot be accessed. Please verify the recovery target location ...
  58. 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 ...
  59. 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 ...
  60. The replica for %DatasourceName; on %ServerName; is currently being synchronized with consistency check. A consistency check ...
  61. The replica for %DatasourceType; %DatasourceName; is currently being synchronized with consistency check. A consistency check ...
  62. The replica for %DatasourceType; %DatasourceName; on %ServerName; is not created. Replica creation job is scheduled to run ...
  63. The replica for %DatasourceType; %DatasourceName; on %ServerName; is not created. You have chosen to create the replica manually. ...
  64. The replica is inconsistent for %DatasourceType; %DatasourceName; on %ServerName; due to a CCR failover. A synchronization ...
  65. The replica of %DatasourceName; on %ServerName; is being created. After the initial copy is made, only incremental changes ...
  66. The replica of %DatasourceName; on %ServerName; is inconsistent with the protected data source. All protection activities ...
  67. The replica of %DatasourceName; on %ServerName; is inconsistent with the protected data source. All protection activities ...
  68. The replica of %DatasourceType; %DatasourceName; on %ServerName; is being created. After the initial replica is created, ...
  69. The replica of %DatasourceType; %DatasourceName; on %ServerName; is inconsistent with the protected data source. All protection ...
  70. The replica of %DatasourceType; %DatasourceName; on %ServerName; is inconsistent with the protected data source. All protection ...
  71. The replica of %DatasourceType; %DatasourceName; on %ServerName; is inconsistent with the protected data source. All protection ...
  72. The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...
  73. The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...
  74. The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...
  75. The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...