System Center Data Protection Manager 2012 R2

  1. DPM detected that the following servers are clustered, but could not identify their fully qualified domain name: %ListofServers;. ...
  2. DPM detected that the recovery point volume for %DatasourceType; %DatasourceName; is not available on the DPM server. Protection ...
  3. DPM detected that you have selected servers that are nodes of a server cluster. You have not selected other nodes that belong ...
  4. DPM did not find a Virtual machine that is managed by Virtual Machine Manager (VMM) server. Virtual machine name: %DatasourceName;. ...
  5. DPM did not raise this alert. You can only troubleshoot DPM alerts from this link. Click OK to return to Operations Manager. ...
  6. DPM does not protect reparse points found in file systems, except for deduplication reparse points, which are protected. ...
  7. DPM does not protect reparse points found in file systems, except for deduplication reparse points, which are protected. ...
  8. DPM does not protect reparse points found in file systems, except for deduplication reparse points, which are protected. ...
  9. DPM encountered a critical error while performing an I/O operation on the tape %MediaLabel; (Barcode - %MediaBarcode;) in ...
  10. DPM encountered a critical error while trying to parse the contents of the tape %MediaLabel;. This may be because the data ...
  11. DPM encountered an error while attempting to share the data you have requested. Contact your DPM administrator to restore ...
  12. DPM encountered an error while attempting to use tape %MediaLabel; on the drive %DriveName;. This could be a problem with ...
  13. DPM encountered an error while reading from the DPM Online recovery point. Either the recovery point no longer exists or, ...
  14. DPM encountered an error while reading from the recovery point used for recovery. Either the recovery point no longer exists ...
  15. DPM encountered an error while trying to create a recovery point for one or more volumes for data source %DatasourceName; ...
  16. DPM encountered an error while trying to query the properties of the virtual machine on the Virtual Machine Manager (VMM) ...
  17. DPM failed the current backup because the previously standalone SQL database is now a part of a SQL Availability Group. Database: ...
  18. DPM failed to access the volume %VolumeName; on %AgentTargetServer;. This could be due to 1) Cluster failover during backup ...
  19. DPM failed to apply the required policies to this protection group since the recovery point limit for this DPM server has ...
  20. DPM failed to clean up data of old incremental backups on the replica for %DatasourceType; %DatasourceName; on %ServerName;. ...
  21. DPM failed to communicate with the protection agent on %ServerName; because the agent is not installed or the computer is ...
  22. DPM failed to create a copy of the tape backup for %DatasourceType; %DatasourceName; on %ServerName; because the tape backup ...
  23. DPM failed to create the backup. If you are backing up only System State, verify if there is enough free space on the protected ...
  24. DPM failed to delete the saved state of the virtual machine '%VirtualMachineName;' after recovery to the host %ServerName;. ...
  25. DPM failed to dismount the tape %MediaLabel; in drive %DriveName; for the library %Library;. This is because DPM is not synchronized ...
  26. DPM failed to erase the selected tape because the state of the %LibraryType; %Library; as seen by DPM is inconsistent with ...
  27. DPM failed to fixup VHD parent locator post backup for %DatasourceType; %DatasourceName; on %ServerName;, as operation was ...
  28. DPM failed to fixup VHD parent locator post backup for %DatasourceType; %DatasourceName; on %ServerName;. Your recovery point ...
  29. DPM failed to gather item level catalog for %FailureCount; database(s) of the SharePoint Farm %DatasourceName; on %ServerName;. ...
  30. DPM failed to mount the tape %MediaLabel; in drive %DriveName; for the library %Library;. This is because DPM is not synchronized ...
  31. DPM failed to obtain active virtual hard disk information as part of the backup for %DatasourceType; %DatasourceName; on ...
  32. DPM failed to obtain catalog information as part of the backup for %DatasourceType; %DatasourceName; on %ServerName;. Your ...
  33. DPM failed to perform the operation because too many objects have been selected. Select fewer objects and then retry this ...
  34. DPM failed to perform the tape backup for %DatasourceType; %DatasourceName; on cluster %VirtualName; because this cluster ...
  35. DPM failed to protect %DatasourceName; because DPM detected multiple front-end Web servers for the same SharePoint farm on ...
  36. DPM failed to protect the SQL database %DatasourceName; since this was part of the SharePoint Farm %ReferentialDatasourceName; ...
  37. DPM failed to provide the Windows Group %GroupName; read permissions on the replica for %DatasourceType; %DatasourceName; ...
  38. DPM failed to recatalog the contents of the tape %MediaLabel; because it encountered a critical error while attempting to ...
  39. DPM failed to recatalog the contents of the tape because it encountered a critical error while attempting to read catalog ...
  40. DPM failed to recover to the original location because either the corresponding Windows SharePoint Services Search service ...
  41. DPM failed to replicate changes for %DatasourceType; %DatasourceName; on %ServerName; due to the high amount of file system ...
  42. DPM failed to replicate the changes for the %DatasourceType; %DatasourceName;. The operation failed while DPM was attempting ...
  43. DPM failed to start tracking changes for %DatasourceType; %DatasourceName; on %ServerName; because of insufficient memory ...
  44. DPM failed to synchronize changes for %DatasourceType; %DatasourceName; on %ServerName; because the snapshot volume did not ...
  45. DPM failed to use the tape in %MediaLocationType; %MediaLocationInfo; because it appears to be a cleaning tape that is identified ...
  46. DPM failed to use the volume %VolumeLabel; to create the recovery point volume since it is not adequately sized. Volumes ...
  47. DPM failed to use the volume %VolumeLabel; to create the replica since it is not adequately sized. Volumes to be used for ...
  48. DPM failed to use volume %VolumeLabel; since this has already been selected to protect %DatasourceType; %DatasourceName; ...
  49. DPM found no recovery points which you are authorized to restore on the specified DPM server. You can restore only those ...
  50. DPM found the following databases that were created by an earlier installation of SQL Server Reporting Services: %CommaSeparatedDatabaseNames;. ...
  51. DPM has deleted DPM volume %VolumeGuid;, %VolumeLabel; because the size of the volume was modified externally using system ...
  52. DPM has detected a discontinuity in the log chain for %DatasourceType; %DatasourceName; on %ServerName; since the last synchronization. ...
  53. DPM has detected an error in the replica to recovery point volume mapping for %DatasourceName; for server %ServerName;. All ...
  54. DPM has detected an inconsistent replica of the data source during the backup of %ListOfDataSources;. This is because of ...
  55. DPM has detected that files have been deleted or moved on the protected computer. You cannot recover using Recover to original ...
  56. DPM has detected that SQL Server Reporting Services has been reconfigured to use ASP .NET Framework 2.0. Reporting Services ...
  57. DPM has detected that the cluster configuration has changed for resource group %VirtualName; and has marked the replica inconsistent. ...
  58. DPM has discovered new unsupported files or folders on one or more protected volumes. DPM will continue to protect the supported ...
  59. DPM has failed to write events to the DPM Alerts event log. Either the DPM Alerts event log has been deleted or the permissions ...
  60. DPM has failed to write events to the DPM Backup Events event log. Either the DPM Backup Events event log has been deleted ...
  61. DPM has installed some of the missing prerequisites which need a restart. SQL System Configuration Checker cannot be launched ...
  62. DPM has marked the %MediaLabel; tape as decommissioned, which means that data cannot be written to this tape in the future. ...
  63. DPM has received an improperly formed message from the DPM Protection Agent on the protected server. This problem can result ...
  64. DPM has run out of free recovery point space and will fail snapshots for %DatasourceName; in order to prevent existing recovery ...
  65. DPM has run out of free space on the recovery point volume and will fail synchronization for %DatasourceName; on %ServerName; ...
  66. DPM has run out of free space on the recovery point volume for %DatasourceName; on %ServerName;. Protection for this data ...
  67. DPM is attempting to back up or restore a deduped file, which requires Deduplication to be enabled on %AgentTargetServer;. ...
  68. DPM is attempting to backup or restore deduped files, which requires target to be a NTFS volume and deduplication should ...
  69. DPM is not synchronized with the changes on %DatasourceType; %DatasourceName; on %ServerName;. Protection cannot continue. ...
  70. DPM is not synchronized with the current state of your library. Jobs running on the %LibraryType; %Library; can potentially ...
  71. DPM is unable to configure the Windows account because the password you entered does not meet the Group Policy requirements. ...
  72. DPM is unable to continue protecting the selected database because DPM detected a mirroring session failover for this database. ...
  73. DPM is unable to continue protection for %DatasourceName; on %ServerName; because the change tracking information is corrupt ...
  74. DPM is unable to continue protection for %DatasourceName; on %ServerName; because this computer has been powered off without ...
  75. DPM is unable to continue protection for %DatasourceName; on server %ServerName; since the change tracking information is ...