1) If it is protected as a SQL Server database then remove the database from protection and recreate the protection group for this database. If auto-protection is configured for the SQL Server instance of this database in DPM, then recreation of protection for this database is not required as it will be treated as a new datasource and added to protection automatically. 2) If the database is part of a SharePoint farm, this alert may get resolved automatically by DPM. Alternatively, go to the Protection pane and run "Modify Protection" for the protection group containing the SharePoint farm. In the "Modify Protection Group" wizard, expand the SharePoint front-end web server node on the "Select Group Members" page and modify the protection group. Then run consistency check on the SharePoint farm.
If %ServerName; is configured to use NETBIOS, specify the NETBIOS name. Otherwise specify the DNS name of the workgroup computer. ...
If a SQL instance exists with the specified name, use Get-Datasource -ProductionServer -Inquire cmdlet to refresh the information. ...
If cluster failover has happened during backup, please retry the operation. Otherwise, increase the amount of free space ...
If cluster failover has happened during backup, please retry the operation. Otherwise, increase the amount of free space ...
If it is protected as a SQL Server database then remove the database from protection and recreate the protection group for ...
If it is protected as a SQL Server database then remove the database from protection and recreate the protection group for ...
If it is protected as a SQL Server database then remove the database from protection and recreate the protection group for ...
If no other DPM server is using the server for hosting the DPM database, uninstall the Microsoft System Center DPM Support ...
If supported, check the front panel of your library to verify that this cleaning operation completed successfully. 2) If ...