Hello, Dwayne Jackson and Andy Nadarewistsch here. We wanted to take a minute today to detail a quick point to consider after applying Data Protection Manager (DPM 2012 R2) Update Rollup 5 (UR5) and later.
When creating a protection group after applying DPM 2012 R2 Update Rollup 5, not all data sources may display as expected.
This can occur as a result of the improved inquiry performance provided in the update. Specifically, Data Protection Manager brings speed improvements to the inquiry step in the Create/Modify Protection Group wizard. This is accomplished by the persistent caching of data sources, the pruning of unused inquiry data during nightly database cleanup, as well as a more optimized inquiry on servers that have clustered virtual machines on CSV volumes.
Because of this the behavior of the wizard has changed. The Clear Cache button is replaced with the Refresh button, and expanding a production server in the selection page now instantly obtains the data sources from the last inquiry that are cached in the database without actually triggering an inquiry on the production server. This can cause some newly added data sources to not appear until the data is refreshed.
To trigger a fresh inquiry to obtain the latest data sources (and to update the cache), you must click Refresh after you select the production server.
Note that the example scenario below is not specific to an Exchange work load – this can apply to various workloads that DPM supports.
In this scenario, we have added a second mailbox database after initial protection. As seen below, the DPM server has cached only one, named Mailbox Database NC1, even though we actually have two mailbox databases mounted.
We can also confirm from the Exchange admin center that we actually have two mailbox databases mounted.
In order to get our newly added data source to show up we need to open the DPM console and go to the Select Group Members page, then click on the DAGName\Node name and select the Refresh button. This will trigger a fresh inquiry to obtain the latest data sources and update the cache.
Be aware that in this scenario, once you expand a server node in the UI the refresh button will grayed out if the server has some data sources that are already protected. To refresh such a server, you can either:
1. Uncheck its data sources and then select the server. The refresh button will now be active, so click the Refresh button and then re-check the data sources again.
2. Refresh the server before expanding it.
As seen below, DPM now displays all of the data sources.
Dwayne Jackson | Senior Support Escalation Engineer | Microsoft GBS Management and Security Division
Andy Nadarewistsch | Senior Support Escalation Engineer | Microsoft GBS Management and Security Division
System Center All Up: http://blogs.technet.com/b/systemcenter/
Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
Data Protection Manager Team blog: http://blogs.technet.com/dpm/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The RMS blog: http://blogs.technet.com/b/rms/
App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv
The Surface Team blog: http://blogs.technet.com/b/surface/
The Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Keywords: DPM 2012 R2 Create New Protection Group data source enumeration fails, Data Sources not listed, Data Protection Manager SQL enumeration fails, Data Protection Manager Exchange enumeration fails, Data Protection Manager volume enumeration fails, Data Protection Manager Share Point enumeration fails, Data Protection Manager client enumeration fails, Data Protection Manager Hyper-V enumeration fails Data Protection Manager Virtual Machine(VM) enumeration fails,