| Senior Support Escalation Engineer
Hi Everyone, Dwayne Jackson here again with a quick tip for you in case you ever run into an issue where SQL Server instance auto-protection for Data Protection Manager is not enabled during DPM Secondary Protection. Please ensure your symptoms align with the items noted below.
1. Existing DPM Secondary Protection is configured for the SQL Server instance.
2. SQL Server instance auto-protection is working as expected from the Primary DPM server. SQL Server instance auto-protection enables DPM to automatically identify and protect SQL Server databases that are added to instances of SQL Server.
From the Secondary DPM Server, newly added databases to the SQL Server Instance are not automatically added to be protected.
If you experience this issue, complete the following steps to enable SQL Server instance auto-protection on the Secondary DPM Server.
1. From the Secondary DPM Server, modify the protection group in question.
2) From the
Select Group Members
step, expand the appropriate SQL Server.
3) Select the SQL instance (i.e. check the box next to the SQL instance) then right-click it.
4) Next click on the pop-up window that says
Turn on auto protection
as shown below.
Here is what it should look like on auto protection has been turned on:
For additional information regarding SQL Server instance auto-protection, please see the following: