System Center Data Protection Manager 2012 R2

  1. Provides trends in tape utilization to assist in capacity planning and making decisions about allocating additional tapes. ...
  2. Re-run synchronization or wait for the next synchronization to occur. If the problem persists, check your domain configuration. ...
  3. Reboot %ServerName;. 2). If you have any protected data on this computer, synchronize with consistency check after %ServerName; ...
  4. Receipt of this message confirms that the SMTP server settings for Data Protection Manager enable delivery of reports and ...
  5. Recovery cannot be performed right now as some other conflicting job is running. Please go to Alerts tab in Monitoring task ...
  6. Recovery data for %DatasourceName; on %ServerName; in protection group %ProtectedGroup; resides on a volume that cannot be ...
  7. Recovery data for %DatasourceType; %DatasourceName; on %ServerName; in protection group %ProtectedGroup; resides on a volume ...
  8. Recovery failed because OS volume]\ClusterStorage is not available for write access. This folder is protected by cluster ...
  9. Recovery failed for %DatasourceType; %DatasourceName; because the overwrite flag is not set for %DbName; on %AgentTargetServer;. ...
  10. Recovery failed for %DatasourceType; %DatasourceName; on %AgentTargetServer; as the alternate storage group or the database ...
  11. Recovery failed for %DatasourceType; %DatasourceName; on %AgentTargetServer; as the specified database copy is a passive ...
  12. Recovery failed for %DatasourceType; %DatasourceName; on %AgentTargetServer; as the specified database is a recovery database. ...
  13. Recovery failed for %DatasourceType; %DatasourceName; on %AgentTargetServer; as the specified database is not a recovery ...
  14. Recovery failed for %DatasourceType; %DatasourceName; on %AgentTargetServer; as the specified storage group is a recovery ...
  15. Recovery failed for %DatasourceType; %DatasourceName; on %AgentTargetServer; as the specified storage group is not a recovery ...
  16. Recovery failed for %DatasourceType; %DatasourceName; on %AgentTargetServer; because the target database specified is in ...
  17. Recovery failed for %DatasourceType; %DatasourceName; on %ServerName; because a database with the name you specified already ...
  18. Recovery failed for %DatasourceType; %DatasourceName; on %ServerName;. Hardware snapshots of the DPM replica and recovery ...
  19. Recovery for %DatasourceType; %DatasourceName; to the latest recovery point cannot be performed because you have already ...
  20. Recovery of %DatasourceName; from staging area (%FolderPath;) to %ServerName; (Start Time %StartDateTime;) failed to recover ...
  21. Recovery of %DatasourceName; from staging area (%FolderPath;) to %ServerName; (Start Time: %StartDateTime;) failed to recover ...
  22. Recovery of %DatasourceName; from staging area (%FolderPath;) to %ServerName; (Start Time: %StartDateTime;) has completed ...
  23. Recovery of %DatasourceName; from staging area (%FolderPath;) to %ServerName; (Start Time: %StartDateTime;) has successfully ...
  24. Recovery of %DatasourceName; from staging area (%FolderPath;) to %ServerName; (Start Time: %StartDateTime;) is in progress. ...
  25. Recovery of %DatasourceName; from staging area (%FolderPath;) to %ServerName; (Start Time: %StartDateTime;) was partially ...
  26. Recovery point cannot be created on disk for data source %DatasourceName; because the protection for %ProtectedGroup; has ...
  27. Recovery point cannot be created on tape for data source %DatasourceName; because the protection for %ProtectedGroup; has ...
  28. Recovery point creation jobs for %DatasourceType; %DatasourceName; on %ServerName; have been failing. The number of failed ...
  29. Recovery point creation of data source %DatasourceName; on %ServerName; to DPM Online cannot be completed. DPM could not ...
  30. Recovery point for %DatasourceType; %DatasourceName; was created when the replica was inconsistent. Some data from this recovery ...
  31. Recovery points are not available for items that are not part of a protection group. Expand and select the nodes in the tree ...
  32. Recovery points will be created for some members in the protection group based on the express full backup schedule. To view ...
  33. Recovery points will be created for some members in the protection group based on the express full backup schedule. To view ...
  34. Recovery to %TargetServerName; that started at %StartDateTime; completed. Some jobs have successfully recovered data and ...
  35. Recovery to the original location is not supported for clients from the secondary DPM server. Select a network location for ...
  36. Reduce the frequency of Express Full backups scheduled for %DatasourceName; on %DPMServerName; to less than %MaxExchangeEFs;. ...
  37. Reduce the frequency of Express Full backups scheduled for %ServerName; on %DPMServerName; to less than %MaxPSMSSQLEFs;. ...
  38. Reduce the frequency of Express Full backups scheduled for SQL Server on %DPMServerName; to less than %MaxDPMMSSQLEFs;. 2) ...
  39. Reduce the frequency of incremental backups scheduled on %DPMServerName; to less than one every %MaxMSSQLIncrementals; hours. ...
  40. Reduce the number of backup/recovery jobs running on this production server, or wait for some backup and recovery jobs to ...
  41. Reduce the number of data sources you are protecting on %DPMServerName;. 2) Consider adding a DPM server to protect the additional ...
  42. Refer to the detailed error code in the description above. Retry this operation after the issue has been fixed. 2) If the ...
  43. Refer to the System Center 2012 R2 DPM Operations Guide for instructions on modifying the DPMLA.xml to correctly represent ...
  44. Remove all of the members that are associated with the following computers from protection groups before uninstalling the ...
  45. Remove the computers from the "Select Computers" page or provide credentials for an account that has administrator access ...
  46. Remove the existing ManagementPacks and import the following Management Packs from the ManagementPacks folder located on ...
  47. Remove the inactive protection for %ReferentialDatasourceName; in the Protection task area by selecting the data source and ...
  48. Remove the tape from the library autoloader. Consult the documentation for your hardware for instructions on troubleshooting ...
  49. Remove the tape in the slot %SlotName; by using the front panel of your library. 2) On the Libraries tab in the Management ...
  50. Remove the tapes from the library. 2. Clear duplicate barcode information from DPM. 3. Replace the barcodes on the tapes ...
  51. Replica for %DatasourceType; %DatasourceName; on %ServerName; is already consistent. Scheduled consistency check will not ...
  52. Replica volume configuration for BMR datasource failed. The replica volume for the BMR datasource %DatasourceName; cannot ...
  53. Replica volume on disk has grown to become larger than the space allocated for it on DPM Online. Increasing the size of replica ...
  54. Replicas cannot be reallocated as DPM database has not been synchronized with the environment. Run DpmSync -Sync to synchronize ...
  55. Reporting has not yet been configured on Data Protection Manager (DPM). To configure Reporting, an administrator must use ...
  56. Reporting services requires you to set a password before running any report. Set your password by clicking on the "Set reporting ...
  57. Rerun the consistency check and see if it resolves this issue. 2) Check to see if your disks are connected properly to the ...
  58. Rerun the consistency check and see if it resolves this issue. 2) If running consistency check does not resolve this issue, ...
  59. Rerunning this job will back up this data source to a new tape. If you want all data sources in this protection group to ...
  60. Rescan the disk configuration to detect the disk. If the disk is still missing, verify physical disk connections and perform ...
  61. Resolve any active 'Agent ownership required' alert for the production server. 2. Click on the link below to rerun the failed ...
  62. Restart DPM Console after verifying the following: 1. SQL Server Reporting Services is running on DPM server's SQL Server ...
  63. Restart the DPM Replication Agent service on %ServerName;. 2) If %ServerName; is configured using certificates, ensure that ...
  64. Restart the virtual disk service and try the backup operation again. If the issue persists, check the system event log for ...
  65. Restore a valid database using the steps described in the System Center 2012 R2 DPM Operations Guide, and then retry the ...
  66. Restore failed because backup metadata xml is invalid. The possible reasons for this are 1) That restore was triggered on ...
  67. Restoring the virtual machine to the original server will overwrite an existing instance of the same virtual machine present ...
  68. Retains the replica on the disk with associated recovery points and tapes for the specified retention range. You can delete ...
  69. Retry the failed tape backup job using the alert in the Monitoring task area. 2) If your copy failed because the tape backup ...
  70. Retry the operation and specify a database which is not a recovery database, or select the Recover to Recovery Database option. ...
  71. Retry the operation and specify a storage group which is not a recovery storage group, or select the Recover to Recovery ...
  72. Retry the operation. If it fails consistently, remove the protected data from the protection group and reprotect it again. ...
  73. Retry the operation. If the problem persists, the recovery point may be corrupt. Retry recovery from another recovery point. ...
  74. Retry the reporting task. If the problem persists, repair your DPM installation using the steps described in the System Center ...
  75. Retry this operation after the issue has been fixed. 2) If the error was due to insufficient resources, then it could be ...