System Center Data Protection Manager 2012
- The number of free tapes in the %LibraryType; %Library; is less than or equals the threshold value of %ThresholdValue;. You ...
- The operation attempted cannot be performed at this time because maximum number of parallel backup jobs are already running. ...
- The operation attempted cannot be performed at this time because maximum number of parallel restore jobs are already running. ...
- The operation failed because DPM failed to access the shadow copy on %AgentTargetServer;. This could be due to 1) Cluster ...
- The operation failed because DPM failed to access the shadow copy on %AgentTargetServer;. This could be due to 1) Cluster ...
- The operation failed because DPM failed to access the shadow copy on %AgentTargetServer;. This could be due to 1) Cluster ...
- The Operation failed since DPM was unable to access the file/folder %FileName; on %AgentTargetServer;. This could be due ...
- The Operation failed since file/folder %FileName; was not accessible. This could be due to the file/folder being corrupt ...
- The parameter set that you have specified is incorrect. Specify only short-term disk along with long-term Online or long-term ...
- The parameter set that you have specified is incorrect. Specify only short-term disk and long-term Online policy objective. ...
- The parameter set that you have specified is incorrect. Specify only short-term disk and long-term tape policy objectives. ...
- The parent instance of at least one of the SQL databases selected is auto-protected. Unless you turn-off auto-protection ...
- The path to the SQL temporary folder for %DatasourceType; %DatasourceName; on %ServerName; is too long. This can cause backup ...
- The protected volume %VolumeName; on %ServerName; could not be accessed. The volume may have been removed or dismounted, ...
- The protection agent could not be removed from %ServerName;. The computer may no longer have an agent installed or may no ...
- The protection agent could not be removed from %ServerName;. The computer may no longer have an agent installed or may no ...
- The protection agent could not be removed from %ServerName;. The computer may no longer have an agent installed or may no ...
- The protection agent installation failed because another version of the protection agent is already installed on %ServerName;. ...
- The protection agent installation failed because the files needed to install the protection agent (version %AgentVersion;) ...
- The protection agent installation failed. The credentials you provided do not have administrator privileges on %ServerName;. ...
- The protection agent installation failed. There was an error in reading the files needed to install the protection agent ...
- The protection agent is incompatible with the version of DPM that is installed on this computer. All subsequent protection ...
- The protection agent is incompatible with the version of DPM that is installed on this computer. All subsequent protection ...
- The protection agent on %ServerName; is not compatible with the DPM version. The protection agent version is %AgentVersion;, ...
- The protection agent operation failed because DPM could not communicate with the Protection Agent service on %ServerName;. ...
- The protection agent operation failed because it could not access the protection agent on %ServerName;. %ServerName; may ...
- The protection agent uninstall is unavailable because the DPM server is currently communicating with the protection agents ...
- The protection agent upgrade failed because %ServerName; has a more recent version of the protection agent (version %AgentVersion;) ...
- The protection agent upgrade is unavailable because the DPM server is currently communicating with the protection agents ...
- The protection group configuration has changed and therefore this job cannot be re-run. On the Jobs tab in the Monitoring ...
- The recovery failed for %DatasourceType; %DatasourceName; on %ServerName; because a mirroring session exists for this database. ...
- The recovery jobs for %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, are in progress. ...
- The recovery jobs for %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, have completed. ...
- The recovery jobs for %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, have successfully ...
- The recovery jobs for %DatasourceName; that started at %StartDateTime;, with the destination of %TargetServerName;, have ...
- The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
- The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
- The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
- The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
- The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
- The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
- The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
- The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %ServerName;, ...
- The recovery jobs for %DatasourceType; %DatasourceName; that started at %StartDateTime;, with the destination of %TargetServerName;, ...
- The recovery point window defines the granularity of time in which you expect a minimum of one good recovery point for each ...
- The recovery points for application replicas on the secondary DPM server use the express full backup schedule and synchronization ...
- The recovery target location %FolderPath;, does not exist or cannot be accessed. Please verify the recovery target location ...
- The recovery to the latest point in time failed. During a recovery to the latest point in time, DPM tries to do a tail log ...
- The recovery to the latest point in time has failed. During a recovery to the latest point in time, DPM tries to do a SQL ...
- The replica for %DatasourceName; on %ServerName; is currently being synchronized with consistency check. A consistency check ...
- The replica for %DatasourceType; %DatasourceName; is currently being synchronized with consistency check. A consistency check ...
- The replica for %DatasourceType; %DatasourceName; on %ServerName; is not created. Replica creation job is scheduled to run ...
- The replica for %DatasourceType; %DatasourceName; on %ServerName; is not created. You have chosen to create the replica manually. ...
- The replica is inconsistent for %DatasourceType; %DatasourceName; on %ServerName; due to a CCR failover. A synchronization ...
- The replica of %DatasourceName; on %ServerName; is being created. After the initial copy is made, only incremental changes ...
- The replica of %DatasourceName; on %ServerName; is inconsistent with the protected data source. All protection activities ...
- The replica of %DatasourceName; on %ServerName; is inconsistent with the protected data source. All protection activities ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is being created. After the initial replica is created, ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is inconsistent with the protected data source. All protection ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is inconsistent with the protected data source. All protection ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is inconsistent with the protected data source. All protection ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM detected ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM error ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM has ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM has ...
- The replica of %DatasourceType; %DatasourceName; on %ServerName; is not consistent with the protected data source. DPM has ...
- The replica on the DPM server for %DatasourceType; %DatasourceName; on %ServerName; is inconsistent with the protected data ...