System Center Data Protection Manager 2012

  1. DPM could not perform the requested action on the selected items. This could be because the selected item or property associated ...
  2. DPM could not perform the requested action on the selected items. This could be because the selected item or property associated ...
  3. DPM could not perform the requested action on the selected items. This could be because the selected items or some properties ...
  4. DPM could not perform the requested action on the selected items. This could be because the selected items or some properties ...
  5. DPM could not perform the requested action on the selected items. This could be because the selected items or some properties ...
  6. DPM could not persist the protection group and change the server of data source. Data source: %DatasourceName; Server name:%ServerName;. ...
  7. DPM could not reserve the drive resource because one of required drive resources is not online or it needs cleaning or servicing. ...
  8. DPM could not run the backup job for the data source because the number of currently running backup and recovery jobs on ...
  9. DPM could not run the backup/recovery job for the data source because it is owned by a different DPM server. Data source: ...
  10. DPM could not run the recovery job for the data source because the number of currently running backup and recovery jobs on ...
  11. DPM could not start a recovery, consistency check, or initial replica creation job for %DatasourceType; %DatasourceName; ...
  12. DPM could not start a recovery, consistency check, or initial replica creation job for %DatasourceType; %DatasourceName; ...
  13. DPM could not start a recovery, consistency check, or initial replica creation job for %DatasourceType; %DatasourceName; ...
  14. DPM CPWrapper Service on the %MachineName; computer has encountered a failure and may be in an unusable state. Exception ...
  15. DPM creates the temporary folder in the same location as the SQL database log file. The temporary folder name is 'DPM_SQL_PROTECT'. ...
  16. DPM creates the temporary folder in the same location as the SQL database log file. The temporary folder name is 'DPM_SQL_PROTECT'. ...
  17. DPM creates the temporary folder in the same location as the SQL database log file. The temporary folder name is 'DPM_SQL_PROTECT'. ...
  18. DPM creates the temporary folder in the same location as the SQL database log file. The temporary folder name is 'DPM_SQL_PROTECT'. ...
  19. DPM creates the temporary folder in the same location as the SQL database log file. The temporary folder name is 'DPM_SQL_PROTECT'. ...
  20. DPM creates the temporary folder in the same location as the SQL database log file. The temporary folder name is 'DPM_SQL_PROTECT'. ...
  21. DPM data source cannot be added to the protection group because of existing settings. Create a new protection group for this ...
  22. DPM data source cannot be added to the protection group because of existing settings. Create a new protection group for this ...
  23. DPM data source cannot be added to the protection group because of existing settings. Create a new protection group for this ...
  24. DPM database size has exceeded the threshold limit. DPM database size: %DPMDBSize; GB DPM database location: %DPMDBLocation; ...
  25. DPM database size has exceeded the threshold limit. DPM database size: %DPMDBSize; GB DPM database location: %DPMDBLocation; ...
  26. DPM database size has exceeded the threshold limit. DPM database size: %DPMDBSize; GB DPM database location: %DPMDBLocation; ...
  27. DPM database updated. Consistency check operation will automatically run for the restored data when the client computers ...
  28. DPM detected an inconsistent replica of the data source for %ListOfDataSources;. Attempts to fix this may not have been successful. ...
  29. DPM detected multiple disks with the same disk identification number (DiskID). None of these disks will be added to the DPM ...
  30. DPM detected that server %ChosenServerName; is clustered, but could not identify the fully qualified domain name of %ServerName;. ...
  31. DPM detected that the following servers are clustered, but could not identify their fully qualified domain name: %ListofServers;. ...
  32. DPM detected that the recovery point volume for %DatasourceType; %DatasourceName; is not available on the DPM server. Protection ...
  33. DPM detected that you have selected servers that are nodes of a server cluster. You have not selected other nodes that belong ...
  34. DPM detected that you have selected servers that are nodes of a server cluster. You have not selected other nodes that belong ...
  35. DPM did not find a Virtual machine that is managed by Virtual Machine Manager (VMM) server. Virtual machine name: %DatasourceName;. ...
  36. DPM did not raise this alert. You can only troubleshoot DPM alerts from this link. Click OK to return to Operations Manager. ...
  37. DPM does not protect reparse points found in file systems, except for deduplication reparse points, which are protected. ...
  38. DPM does not protect reparse points found in file systems, except for deduplication reparse points, which are protected. ...
  39. DPM does not protect reparse points found in file systems. if you have selected volumes or folders in this protection group, ...
  40. DPM does not protect reparse points found in file systems. if you have selected volumes or folders in this protection group, ...
  41. DPM does not protect reparse points found in file systems. if you have selected volumes or folders in this protection group, ...
  42. DPM does not protect reparse points found in file systems. if you have selected volumes or folders in this protection group, ...
  43. DPM encountered a critical error while performing an I/O operation on the tape %MediaLabel; (Barcode - %MediaBarcode;) in ...
  44. DPM encountered a critical error while trying to parse the contents of the tape %MediaLabel;. This may be because the data ...
  45. DPM encountered an error while attempting to share the data you have requested. Contact your DPM administrator to restore ...
  46. DPM encountered an error while attempting to use tape %MediaLabel; on the drive %DriveName;. This could be a problem with ...
  47. DPM encountered an error while reading from the DPM Online recovery point. Either the recovery point no longer exists or, ...
  48. DPM encountered an error while reading from the recovery point used for recovery. Either the recovery point no longer exists ...
  49. DPM encountered an error while trying to create a recovery point for one or more volumes for data source %DatasourceName; ...
  50. DPM encountered an error while trying to query the properties of the virtual machine on the Virtual Machine Manager (VMM) ...
  51. DPM failed the current backup because the previously standalone SQL database is now a part of a SQL Availability Group. Database: ...
  52. DPM failed to access the volume %VolumeName; on %AgentTargetServer;. This could be due to 1) Cluster failover during backup ...
  53. DPM failed to access the volume %VolumeName; on %AgentTargetServer;. This could be due to 1) Cluster failover during backup ...
  54. DPM failed to access the volume %VolumeName; on %AgentTargetServer;. This could be due to 1) Cluster failover during backup ...
  55. DPM failed to apply the required policies to this protection group since the recovery point limit for this DPM server has ...
  56. DPM failed to clean up data of old incremental backups on the replica for %DatasourceType; %DatasourceName; on %ServerName;. ...
  57. DPM failed to communicate with the protection agent on %ServerName; because the agent is not installed or the computer is ...
  58. DPM failed to create a copy of the tape backup for %DatasourceType; %DatasourceName; on %ServerName; because the tape backup ...
  59. DPM failed to create the backup. If you are backing up only System State, verify if there is enough free space on the protected ...
  60. DPM failed to delete the saved state of the virtual machine '%VirtualMachineName;' after recovery to the host %ServerName;. ...
  61. DPM failed to dismount the tape %MediaLabel; in drive %DriveName; for the library %Library;. This is because DPM is not synchronized ...
  62. DPM failed to erase the selected tape because the state of the %LibraryType; %Library; as seen by DPM is inconsistent with ...
  63. DPM failed to fixup VHD parent locator post backup for %DatasourceType; %DatasourceName; on %ServerName;, as operation was ...
  64. DPM failed to fixup VHD parent locator post backup for %DatasourceType; %DatasourceName; on %ServerName;. Your recovery point ...
  65. DPM failed to gather item level catalog for %FailureCount; database(s) of the SharePoint Farm %DatasourceName; on %ServerName;. ...
  66. DPM failed to mount the tape %MediaLabel; in drive %DriveName; for the library %Library;. This is because DPM is not synchronized ...
  67. DPM failed to obtain active virtual hard disk information as part of the backup for %DatasourceType; %DatasourceName; on ...
  68. DPM failed to obtain catalog information as part of the backup for %DatasourceType; %DatasourceName; on %ServerName;. Your ...
  69. DPM failed to perform the operation because too many objects have been selected. Select fewer objects and then retry this ...
  70. DPM failed to perform the tape backup for %DatasourceType; %DatasourceName; on cluster %VirtualName; because this cluster ...
  71. DPM failed to protect %DatasourceName; because DPM detected multiple front-end Web servers for the same SharePoint farm on ...
  72. DPM failed to protect the SQL database %DatasourceName; since this was part of the SharePoint Farm %ReferentialDatasourceName; ...
  73. DPM failed to provide the Windows Group %GroupName; read permissions on the replica for %DatasourceType; %DatasourceName; ...
  74. DPM failed to recatalog the contents of the tape %MediaLabel; because it encountered a critical error while attempting to ...
  75. DPM failed to recatalog the contents of the tape because it encountered a critical error while attempting to read catalog ...