System Center Data Protection Manager 2012

  1. Status: %AlertStatus; Description: The disk %DiskName; cannot be detected or has stopped responding. All subsequent protection ...
  2. Status: %AlertStatus; Protection Group: %ProtectedGroup; Description: DPM discovered one of the following changes: a. New ...
  3. Status: %AlertStatus; Protection Group: %ProtectedGroup; Description: DPM discovered one of the following changes: a. New ...
  4. Status: %AlertStatus; Protection Group: %ProtectedGroup; Description: DPM discovered one of the following changes: a. New ...
  5. Status: %AlertStatus; Volume: %VolumeName; Computer: %ServerName; Description: Network bandwidth usage throttling not working. ...
  6. Status: %AlertStatus; Volume: %VolumeName; Computer: %ServerName; Description: Network bandwidth usage throttling not working. ...
  7. Status: %AlertStatus; Volume: %VolumeName; Computer: %ServerName; Description: Network bandwidth usage throttling not working. ...
  8. Status: %AlertStatus; Volume: %VolumeName; Computer: %ServerName; Description: Used disk space for recovery point volume ...
  9. Status: %AlertStatus; Volume: %VolumeName; Computer: %ServerName; Description: Used disk space for recovery point volume ...
  10. Status: %AlertStatus; Volume: %VolumeName; Computer: %ServerName; Description: Used disk space for recovery point volume ...
  11. Status: %AlertStatus; Volume: %VolumeName; Computer: %ServerName; Description: Used disk space on replica volume exceeds ...
  12. Status: %AlertStatus; Volume: %VolumeName; Computer: %ServerName; Description: Used disk space on replica volume exceeds ...
  13. Status: %AlertStatus; Volume: %VolumeName; Computer: %ServerName; Description: Used disk space on replica volume exceeds ...
  14. Subscription to Windows Azure Online Backup has expired. Your subscription would be cancelled if the subscription is not ...
  15. Synchronization for replica of %DatasourceName; on %ServerName; failed because the replica is not in a valid state or is ...
  16. Synchronization frequency specified is invalid. You can only set synchronization frequency to 1, 2, 4, 6, 12 or 24 hours. ...
  17. Synchronization start time can be used to optimize performance of a protection group and secondary protection of another ...
  18. Synchronization with consistency check will occur for all protected data on {0}. Synchronization may affect server performance ...
  19. Tape in %Location; cannot be recataloged. Perform the following before retrying this cmdlet: If the tape is marked as free, ...
  20. Tape in %Location; cannot be recataloged. Perform the following before retrying this cmdlet: If the tape is marked as free, ...
  21. Tape in %Location; cannot be recataloged. Perform the following before retrying this cmdlet: If the tape is marked as free, ...
  22. The %DatasourceName; data source on the %ServerName; server is being protected directly on the secondary DPM server. To switch ...
  23. The %ElementType; %ElementName; did not contain a tape when DPM expected it to. DPM might not be in synch with the state ...
  24. The %Name; service is running under %Credentials; credentials. We recommend that the service run under the NT Authority\NETWORK ...
  25. The %ObjectId; object id specified is not a valid GUID. Please refer to MSDN documentation for valid GUID string formats. ...
  26. The %Prerequisite; installation failed. All changes made by the %Prerequisite; installation to the system were rolled back. ...
  27. The 32-bit version of Microsoft System Center Data Protection Manager is not supported on a 64-bit computer. You need to ...
  28. The ability to add members to this protection group is temporarily disabled while initial synchronization of one or more ...
  29. The agent operation failed because DPM detected a more recent version of the DPM protection agent (version %AgentVersion;) ...
  30. The agent operation failed because server %ServerName; is part of a cluster. DPM does not support protection of clustered ...
  31. The agent operation failed on %ServerName; because DPM could not communicate with the DPM protection agent. The computer ...
  32. The agent operation failed on %ServerName; because DPM could not communicate with the DPM protection agent. The computer ...
  33. The agent operation failed on %ServerName; because DPM could not communicate with the DPM protection agent. The computer ...
  34. The alert would remain active for next 24 hours and within this period if the required tapes are not brought back to library ...
  35. The allocation of disk space for storage pool volumes failed because there is not enough unallocated disk space in the storage ...
  36. The alternate SQL instance name is either empty or invalid. Provide a valid alternate SQL instance name to use for the recovery ...
  37. The available memory on the computer is less than the DPM minimum memory requirement. The minimum memory requirement is %MinimumMemoryRequired; ...
  38. The backup failed as the total size of the data that has been backed up has exceeded the quota limit for your organization. ...
  39. The backup frequency for long-term protection needs to be equal to or greater than the backup frequency for short-term protection. ...
  40. The backup frequency for long-term protection needs to be equal to or greater than the backup frequency for short-term protection. ...
  41. The backup frequency for long-term protection needs to be equal to or greater than the backup frequency for short-term protection. ...
  42. The backup frequency for long-term protection needs to be equal to or greater than the backup frequency for short-term protection. ...
  43. The backup job failed because a recovery point on which it depends has been deleted by remove-RecoveryPoint cmdlet or by ...
  44. The backup job failed because DPM detected that some databases of the Exchange Server Storage Group instance %DatasourceName; ...
  45. The backup job failed because DPM detected that the %DatasourceName; instance of SQL Server 2000 on %ServerName; has been ...
  46. The backup job was not completed successfully because DPM detected that the virtual machine has migrated from the configured ...
  47. The backup schedule specified cannot be used. Backup schedules can only be configured to run every half an hour starting ...
  48. The backup to tape job completed, but the catalog was not built correctly for %DatasourceType; %DatasourceName; on %ServerName;. ...
  49. The barcode on the tape %MediaLabel; in %MediaLocationType; %MediaLocationInfo; appears to have changed since the last time ...
  50. The certificate %CertificateName; with serial number %CertificateSerialNumber; issued by %CertificateIssuer; will expire ...
  51. The certificate has Enhanced Key Usage (EKU) enabled but either Server Authentication EKU or Client Authentication EKU is ...
  52. The certificate provided with thumbprint %InputParameterTag; on the personal machine store of machine %MachineName; does ...
  53. The certificate provided with thumbprint %InputParameterTag; on the personal machine store of machine %MachineName; does ...
  54. The certificate provided with thumbprint %InputParameterTag; on the personal machine store of machine %MachineName; does ...
  55. The change journal size can only be modified by a DPM administrator working on the Administrator console. Contact your DPM ...
  56. The cleaning operation for drive %DriveName; on library %Library; took longer than expected. The cleaning operation may have ...
  57. The client-side components should be installed on the machine where you will be launching the Operations Manager Console. ...
  58. The computer %DPMServerName; is either not a DPM server or it does not support centralized management and troubleshooting. ...
  59. The computer %ServerName; hosts the SQL Server database for this DPM computer. If the operating system of %ServerName; is ...
  60. The computer name you entered was invalid. Please enter the name of the Data Protection Manager computer that should be given ...
  61. The computer processor speed does not meet the DPM minimum configuration requirements. The minimum required processor speed ...
  62. The computer running DPM has deleted volume %VolumeGuid;, %VolumeLabel; from DPM disk %NTDiskNumber; because it was not a ...
  63. The computers listed are in the same domain as the DPM server. To add a computer from a different domain, type the fully ...
  64. The configuration of the pre-backup script or the post-backup script XML for %DatasourceType; %DatasourceName; is incorrect. ...
  65. The consistency check failed to trigger for client datasource as client initialization is pending. This will happen automatically ...
  66. The consistency check resulted in the following changes to SQL Server Agent schedules: Schedules added: %SchedulesAdded; ...
  67. The current backup operation failed because the number of data transfer failures was more than %FailureCount; Specified files ...
  68. The current operation failed due to an internal service error %InputParameterTag;]. Please retry the operation after sometime. ...
  69. The current recovery operation failed because the number of data transfer failure was more than %FailureCount; Specified ...
  70. The current selections will be reset and you will need to select them again. Click "Yes" to reset or "No" to keep the current ...
  71. The data format of the online backup service and the Windows Azure Online Backup Agent do not match. Please install the latest ...
  72. The Data Protection Manager (DPM) program files and database files have been installed on this computer at the following ...
  73. The Data Protection Manager (DPM) program files and database files have been installed on this computer at the following ...
  74. The Data Protection Manager (DPM) program files and database files have been installed on this computer at the following ...
  75. The Data Protection Manager (DPM) program files and database files have been installed on this computer at the following ...