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