I've been using DPM for a few years. I was running System Center DPM 2012 R2 with Rollup 6 on Windows 2008 R2 SP1. I decided it was time to upgrade to Windows 2012 R2. I started with a new server and installed Windows 2012 R2 on it, then installed the same version of DPM on it. I then started moving each protected server, one-by-one, onto the new DPM server. I basically followed these steps:
1. On the old DPM server, stop protection of the member and disable the agent.
2. On the protected server, run the command SetDpmServer.exe -dpmServerName MyDPMServerName.
3. On the new DPM server, use the DPM Management Shell to attach the protected server to the new DPM server.
4. Create a new protection group on the new DPM server and add the protected server to the group.
This all went very well until I got to the SharePoint farm. I followed the above steps for both the Web Front End server and the SQL server. I added the SQL databases to the new DPM server, then realized this was a mistake. I needed to add the SP Farm to the DPM server first. So I removed the SQL databases from DPM protection and tried to protect the farm. That's when I got this error: "DPM cannot protect this SharePoint farm as it cannot detect the configuration of the dependent SQL databases. (ID: 32008)" I've done a lot of searching and found that a lot of people have run into this issue. I tried the three steps described on the error page, and I've done a variety of other things, too. I've verified that the SharePoint VSS writer is running and stable on the WFE server. I've run the command ConfigureSharePoint.ext -EnableSharePointProtection. I've registered the SharePoint VSS writer. I've checked that the SharePoint VSS writer is running under FarmAdmin creds. Etc.
Just to reiterate, DPM protection of the SharePoint Farm was working perfectly normally under the old DPM server. Now that I'm trying to migrate it to a new DPM server (same version of DPM, new version of OS, new server has a different name than the old DPM server) protection of the SharePoint Farm is no longer working.