System Center Data Protection Manager 2012 R2

  1. Disk space on the data source volumes of the protected computer is used for storing the change journal. Space allocated for ...
  2. Disk-based and tape-based protection. DPM stores the replica of the data on disks and periodic full backups are created on ...
  3. Disk-based and tape-based protection. DPM stores the replica of the data on disks and periodic full backups are created on ...
  4. Displays the recovery point status of all selected data sources. The report will show "A" (Available) if at least one good ...
  5. Do the following to troubleshoot this issue: 1) Check the spelling of the computer name. 2) Verify that Windows Server 2003 ...
  6. Do the following to troubleshoot this issue: 1) If another DPM server is currently protecting %ServerName; use that DPM server ...
  7. Do the following to troubleshoot this issue: 1) Verify that %ServerName; is online and remotely accessible from the DPM server. ...
  8. Do the following to troubleshoot this issue: 1) Verify that %ServerName; is remotely accessible from the DPM server. 2) If ...
  9. Do the following to troubleshoot this issue: 1. Verify that the credentials you entered belong to a valid domain user account, ...
  10. Do you accept all of the terms of the preceding License Agreement? If you choose No, Install will close. To install you must ...
  11. Door successfully unlocked for %LibraryType; %Library;. You can now open the library door. The door will be automatically ...
  12. Download and install Microsoft Management Console 3.0 from http://go.microsoft.com/fwlink/?LinkId=55423 or upgrade the operating ...
  13. DPM 2010 SQL End User Recovery is already installed on this system. To reinstall the application, uninstall DPM 2010 SQL ...
  14. DPM Access Manager service is unable to process the request because of an internal failure. Additional details : %ExceptionMessage; ...
  15. DPM Administrator Console can be opened only by a user belonging to a domain. Log on using a domain user account, and try ...
  16. DPM Agent on the SharePoint front-end Web server %ServerName; is not configured appropriately. DPM was unable to invoke WssCmdletWrapper ...
  17. DPM allows users in this security group to recover SQL Server databases specified in the DPM role irrespective of their permissions ...
  18. DPM attempted to move a tape to %ElementType; %ElementName; but this %ElementType; was occupied. DPM may not be in synch ...
  19. DPM attempted to move a tape to %ElementType; %ElementName; but this %ElementType; was occupied. DPM may not be in synch ...
  20. DPM Azure backup and recovery jobs use a cache volume that cannot be detected. All subsequent online protection activities ...
  21. DPM can optimize its disk allocation recommendation by calculating the size of the selected data on %VolumeName; on %ServerName;. ...
  22. DPM cannot browse %ServerName; because a protection agent is not installed on %ServerName; or the computer is restarting. ...
  23. DPM cannot browse %ServerName; either because no agent is installed on %ServerName; or because the computer is rebooting. ...
  24. DPM cannot browse %ServerName;, either because no agent is installed on %ServerName; or because the computer is rebooting. ...
  25. DPM cannot browse the contents of the virtual machine on the protected computer %ServerName;. Item level recovery is not ...
  26. DPM cannot continue protecting %DatasourceName; on %ServerName; because the volume on which this data resides on has been ...
  27. DPM cannot continue protecting the selected database because it is not part of an Availability Group anymore. Database: %DatasourceName; ...
  28. DPM cannot continue protection because SCR copy status is unhealthy for %DatasourceType; %DatasourceName; on %ServerName;. ...
  29. DPM cannot continue protection for %DatasourceType; %DatasourceName; on cluster %VirtualName; because this cluster experienced ...
  30. DPM cannot continue protection for %DatasourceType; %DatasourceName; on cluster %VirtualName; because this cluster experienced ...
  31. DPM cannot continue protection of %DatasourceType; %DatasourceName; on %ServerName; because protection agents are not upgraded ...
  32. DPM cannot continue secondary protection of this datasource because of insufficient disk space on its replica volume on the ...
  33. DPM cannot continue to protect the data on %TargetServerName; because there is not enough disk space available on one or ...
  34. DPM cannot continue with the recovery of the SharePoint Service Provider (SSP) because the SSP %DatasourceName; or the index ...
  35. DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ...
  36. DPM cannot enable e-mail subscription for reports unless SMTP details are configured in the remote SQL Server Reporting Service ...
  37. DPM cannot enable e-mail subscription for reports unless SMTP details are configured on the remote SQL Server Reporting Service ...
  38. DPM cannot enumerate the list of computers on which protection agents are installed because it cannot gain access to the ...
  39. DPM cannot protect %FileName; because there is no virtual name configured for the Resource Group to which the file belongs. ...
  40. DPM cannot protect the cluster resource group on %ServerName; because protection agents are not installed on all nodes that ...
  41. DPM cannot protect the SharePoint Search Index because DPM did not detect all of the dependent databases and Search indices ...
  42. DPM cannot protect this data source because the secondary DPM server cannot protect a local data source that is protected ...
  43. DPM cannot protect this data source. You can only select the DPM database for protection from the DPM server. To protect ...
  44. DPM cannot protect this member. On the secondary DPM server, you can only protect data sources for the primary DPM server ...
  45. DPM cannot protect this member. On the secondary DPM server, you cannot protect data sources which are not protected by the ...
  46. DPM cannot resize volumes %VolumeLabel; and %VolumeLabel; that are being used to protect %DatasourceType; %DatasourceName; ...
  47. DPM cannot show the full content of this tape as it contains a dataset which spans across multiple tapes (tapeset) and the ...
  48. DPM cannot use the volumes %VolumeLabel; for disk allocation as they are already in use by DPM. Please specify a volume that ...
  49. DPM Central Console setup skipped the creation of some default roles (used for Role Based Access Control) because they already ...
  50. DPM Central Console setup will automatically import the 'System Center 2012 R2 Data Protection Manager Scale Override' management ...
  51. DPM Central Console setup will create the following registry key to optimize Operations Manager Server performance: HKLM\SOFTWARE\Microsoft\Microsoft ...
  52. DPM could not back up some of the required files for this data source. This could be caused by intermittent failures, or ...
  53. DPM could not create online recovery point for some of the required files for this data source. This could be because of ...
  54. DPM could not enumerate SQL Server instances using Windows Management Instrumentation on the protected computer %ServerName;. ...
  55. DPM could not obtain backup metadata information for %DatasourceType; %DatasourceName; on %ServerName;. If the data source ...
  56. DPM could not obtain backup metadata information for %DatasourceType; %DatasourceName; on %ServerName;. If the data source ...
  57. DPM could not perform the requested action on the selected items. This could be because the selected item or property associated ...
  58. DPM could not perform the requested action on the selected items. This could be because the selected items or some properties ...
  59. DPM could not persist the protection group and change the server of data source. Data source: %DatasourceName; Server name:%ServerName;. ...
  60. DPM could not reserve the drive resource because one of required drive resources is not online or it needs cleaning or servicing. ...
  61. DPM could not run the backup job for the data source because the number of currently running backup and recovery jobs on ...
  62. DPM could not run the backup/recovery job for the data source because it is owned by a different DPM server. Data source: ...
  63. DPM could not run the recovery job for the data source because the number of currently running backup and recovery jobs on ...
  64. DPM could not start a recovery, consistency check, or initial replica creation job for %DatasourceType; %DatasourceName; ...
  65. DPM CPWrapper Service on the %MachineName; computer has encountered a failure and may be in an unusable state. Exception ...
  66. DPM creates the temporary folder in the same location as the SQL database log file. The temporary folder name is 'DPM_SQL_PROTECT'. ...
  67. DPM creates the temporary folder in the same location as the SQL database log file. The temporary folder name is 'DPM_SQL_PROTECT'. ...
  68. DPM data source cannot be added to the protection group because of existing settings. Create a new protection group for this ...
  69. DPM database size has exceeded the threshold limit. DPM database size: %DPMDBSize; GB DPM database location: %DPMDBLocation; ...
  70. DPM database updated. Consistency check operation will automatically run for the restored data when the client computers ...
  71. DPM detected an inconsistent replica of the data source for %ListOfDataSources;. Attempts to fix this may not have been successful. ...
  72. DPM detected multiple disks with the same disk identification number (DiskID). None of these disks will be added to the DPM ...
  73. DPM detected that server %ChosenServerName; is clustered, but could not identify the fully qualified domain name of %ServerName;. ...
  74. DPM detected that the following servers are clustered, but could not identify their fully qualified domain name: %ListofServers;. ...
  75. DPM detected that the recovery point volume for %DatasourceType; %DatasourceName; is not available on the DPM server. Protection ...