System Center Data Protection Manager 2012 R2

  1. Either stop the DPM protection agent service on %ServerName; and make sure that the QoS Packet Scheduler is enabled, or disable ...
  2. Either the database files are corrupt or the proper versions of the Eseutil.exe and Ese.dll files are missing. If you have ...
  3. Enable case-sensitive support on the DPM server by following the steps described in http://support.microsoft.com/default.aspx?scid=kb;EN-US;938455. ...
  4. Enable the protection agent on the protected computer in DPM Administrator Console, in the Management task area, on the Agents ...
  5. End-users can not recover previous versions of files from Data Protection Manager if shadow copies are being saved locally ...
  6. Ensure all volumes are online. In Disk Management Console, right-click on every DPM volume and select Properties. From the ...
  7. Ensure correct SQL data files are copied from an existing DPM SQL instance and attached to the given SQL instance. Then, ...
  8. Ensure that 'QoS Packet Scheduler' is installed in the local area connection properties of both protected and DPM server. ...
  9. Ensure that Get-DatasourceDiskAllocation and Set-DatasourceDiskAllocation are executed successfully prior to running this ...
  10. Ensure that the above server name is accessible from the DPM server. 2) Ensure that the protection agent has been installed ...
  11. Ensure that the Microsoft Online Services sign-in assistant program is installed correctly and is running. Then retry the ...
  12. Ensure that the protection group and protection group set exist, and that the protection group is not assigned to a different ...
  13. Ensure that the protection groups and protection group set exist, and that the protection groups are not assigned to a different ...
  14. Ensure that the replica is in "replica creation pending" state before recovering. For details on recovering a DPM server, ...
  15. Ensure that the SharePoint VSS writer is reporting content databases on the front-end web server. 2)Verify that the SQL Server ...
  16. Ensure that the virtual machine that you are recovering is shut down, and then retry the recovery. If the error persists, ...
  17. Ensure that the Windows Management Information (WMI) service is started. 2. Ensure that Hyper-V role is enabled on the DPM ...
  18. Ensure that the Windows Management Instrumentation (WMI) service is started. If the firewall is turned on, on %ServerName; ...
  19. Ensure that there are no pending alerts for the library. Also check whether I/E port slots have been left open; if yes, close ...
  20. Ensure that you have a valid subscription, then retry the operation after sometime. If the issue persists, contact Microsoft ...
  21. Ensure that you have run DpmSync -reallocateReplica before recovering data to the replica. For details, see the System Center ...
  22. Ensure that you have specified the correct protected computer. 2) In case you have specified the correct protected computer, ...
  23. Ensure that you have specified the correct user ID and password for the operation. Please sign in to the Windows Azure Backup ...
  24. Ensure that you signed in with an administrator account and try again. If the issue persists, register the server again. ...
  25. Ensure there are no pending disk threshold alerts active for this data source and rerun the job. DPM may have automatically ...
  26. Ensure there are no pending recovery point volume threshold alerts active for this data source and rerun the job. DPM may ...
  27. Enter a folder location with sufficient space to hold the recoverable items you anticipate to recover in parallel. You can ...
  28. Enter a passphrase to encrypt all backups from this server. Note that your existing backups will still be accessible after ...
  29. Enter the computer name of the Data Protection Manager server to be given access to end-user recovery data in Active Directory. ...
  30. Enter the domain name of the Data Protection Manager server to be given access to end-user recovery data in Active Directory. ...
  31. Enter the domain name of the protected computer for which to enable end-user recovery. For example, if the full name of the ...
  32. Error occurred while migrating data source %DatasourceName;. Check the DPM administration console for recovery point creation ...
  33. Error while deleting the previous management pack '{0}' from Operations Manager Server {1}. Delete it manually from Operations ...
  34. Error while importing the management pack '{0}' to Operations Manager Server {1}. Import the management pack manually from ...
  35. Error: Access is denied. Recommendation: You need to log on with domain user credentials to access your recovery points. ...
  36. Eseutil consistency check cannot be performed for this protection group, as eseutil.exe is not present on the DPM server. ...
  37. Eseutil.exe failed to apply logs on database files for %DatasourceType; %DatasourceName; on %AgentTargetServer; to bring ...
  38. Existing volumes do not meet the size requirements for replica and recovery point volumes for %DatasourceType; %DatasourceName; ...
  39. Expire the datasets in the tapes Data for the selected inactive protection members are marked for expiration on the tapes ...
  40. Expiry tolerance defines the maximum time for which a recovery point can lie expired on an active tape. Click Help to know ...
  41. Extracting file failed. It is most likely caused by low memory (low disk space for swapping file) or corrupted Cabinet file. ...
  42. Failed to create the protection group because a library or stand-alone tape drive has not been specified and tape protection ...
  43. Failed to obtain drive mapping information from the file DPMLA.xml. The information in this file is not formatted correctly. ...
  44. Failed to perform Test-DPMTapeData on the specified recovery point since this was created by some other DPM installation. ...
  45. Failed to update permissions used for end-user recovery on %ServerName;. Permissions update failed for the following reason: ...
  46. Failure occurred while adding one or more of the volumes involved in backup operation to snapshot set. Please check the event ...
  47. Failure to allocate disk space to the storage pool for storing the replica and the recovery points for %VolumeName; on %ServerName;. ...
  48. FailureCount; out of %Total; selected tapes cannot be marked as free because they belong to protection groups. You need to ...
  49. FailureCount; out of %Total; selected tapes cannot be marked as free. The tapes must be erased. Click Erase tape in the Actions ...
  50. FailureCount; out of %Total; tapes cannot not be erased because they contain data that is being protected. You need to stop ...
  51. File copy failed due to an I/O error. Source location: %SourceLocation; Destination location: %DestinationLocation;. (%Message;) ...
  52. File copy failed. The directory for source location %SourceLocation; or destination location %DestinationLocation; does not ...
  53. First run Get-PolicySchedule to determine the schedules that need to be specified in order to create this Protection Group. ...
  54. For a list of files that could not be backed up, review the log. If any of the deduplicated metadata files could not be backed ...
  55. For all application replica of protected DPM, recovery points on secondary DPM server will depend on the full schedule on ...
  56. For applications the recovery point is as per synchronization frequency when they support incremental, otherwise the recovery ...
  57. For disk based protection, Eseutil runs on the DPM server. For tape-based protection, Eseutil runs on the protected Exchange ...
  58. For example. if you want to recover up to 10 virtual machine backups (from online protection) in parallel and the size of ...
  59. For multiple backups that occur on the same day, the backup for the larger time period will be created. For example, if weekly ...
  60. For resolution actions and more information on the WSB error, go to http://technet.microsoft.com/en-us/library/cc734488(WS.10).aspx. ...
  61. For selecting folders you can choose commonly used folders (for example, My Documents) from the drop-down list or type in ...
  62. For the database you are recovering, specify the instance of SQL Server, the name of the recovered database, and the database ...
  63. For the members that you have specified not to format the custom volumes (in Disk Allocation Dialog earlier), the above setting ...
  64. For the members that you have specified not to format the custom volumes (in Disk Allocation Dialog earlier), the selected ...
  65. For Windows Server 2003 computers, ensure KB 942486 is installed. To download this update, go to http://go.microsoft.com/fwlink/?LinkId=148822 ...
  66. From the command prompt, type DPMAgentInstaller.exe dpmservername to install the protection agent on the protected computer. ...
  67. From the following list, select the instance of SQL Server to which each database must be recovered. By default, DPM will ...
  68. Full backup can only be performed from one copy of the database due to federated log truncation. All other copies must be ...
  69. Full backup is required for %DatasourceType; %DatasourceName; on %ServerName; as %ServiceName; service has been restarted. ...
  70. Go to the Libraries tab in the Management pane, select the tape, and click on Erase tape to erase the content of this tape. ...
  71. Helps synchronize replicas of the file system volumes. This service captures changes on the file server and sends the changes ...
  72. Helps synchronize the protected volumes. This service captures data changes, puts them in the synchronization log, and sends ...
  73. However, you can select Recover as virtual machine to any host and select the original host computer as the destination. ...
  74. HyperV role is not installed on %ServerName; . Cannot recover a virtual machine to a host where HyperV role is not installed. ...
  75. I/E port door of %Library; is now open. Place the tapes to be added in the I/E port, and then click OK. On clicking OK the ...