System Center 2012 R2 Data Protection Manager cannot be installed on the same computer as System Center 2012 Data Protection Manager
Synchronization for replica of %DatasourceName; on %ServerName; failed because the replica is not in a valid state or is ...
Synchronization frequency specified is invalid. You can only set synchronization frequency to 1, 2, 4, 6, 12 or 24 hours. ...
Synchronization start time can be used to optimize performance of a protection group and secondary protection of another ...
Synchronization with consistency check will occur for all protected data on {0}. Synchronization may affect server performance ...
System Center 2012 R2 Data Protection Manager cannot be installed on the same computer as System Center 2012 Data Protection ...
Tape in %Location; cannot be recataloged. Perform the following before retrying this cmdlet: If the tape is marked as free, ...
The %DatasourceName; data source on the %ServerName; server is being protected directly on the secondary DPM server. To switch ...
The %ElementType; %ElementName; did not contain a tape when DPM expected it to. DPM might not be in synch with the state ...
The %Name; service is running under %Credentials; credentials. We recommend that the service run under the NT Authority\NETWORK ...