Hi all,
We have found the following issue (DPM 2012 RU3): when moving content database files (.ldf, .mdf) to new disks (due to lack of space), DPM is not aware of these changes until, apparently, the SharePoint protection is stopped (with retention) + redefined (otherwise, the sync jobs fail with a file not found message as it tries to get the file from the original location).
This looks specially delicate when moving the SharePoint Config database. We had a disk issue and after moving this db's transaction log file, dpm was not able to recover of this situation and we had to stop protection (preserving data), and setting a parallel SQL Server protection of the content databases as re-engaging the sharepoint protection did not recover the situation. once we had enough retention on the SQL Server protection, we removed the old sharepoint data and recreated the SharePoint PG from scratch.
A similar situation happens when removing a content database.
Have you ever moved the SharePoint config database files to other disks? How do you do this, on a DPM context?
Regards