Protection cannot continue because the change journal used for tracking changes for %DatasourceType; %DatasourceName; on %ServerName; is corrupt due to bad sectors on the disk.
Progress details of recovery point creation is shown below. You may close this dialog and view the progress in the Jobs tab ...
Progress details of recovery point creation is shown below. You may close this dialog and view the progress in the Jobs tab ...
Protection agent on %TargetServerName; was unexpectedly shut down during synchronization. DPM may have replicated data partially ...
Protection agents may be installed on some of the computers. Uninstall the agents on the protected computers using Add or ...
Protection cannot continue because the change journal used for tracking changes for %DatasourceType; %DatasourceName; on ...
Protection for item %ProtectableObject; is not allowed because long term protection to DPM Online is not set for protection ...
Protection for item %ProtectableObject; is not allowed because short term protection to disk is not set for protection group ...
Protection jobs cannot run successfully during the upgrade. Before starting the upgrade, verify that no critical jobs are ...
Provide an alternate name for the database to be recovered. Ensure that no database with the name you have specified already ...