Multiple Errors after update from DPM 2012 to 2019 and SQL 2012 to 2016

Question

Hi,
I'm using DPM to make a Backup on the local Disk of 2 Servers. (Server 1 (AD) & Server 2)
DPM runs on Server 3.
I recently updated from 2012 to 2019 as well as SQL 2012 to 2016.
I uninstalled the previous version and reinstalled the mentioned newer ones.
I got a few Problems in fact.
previously I was using Disk 1 in my protection pool. however this is not possible anymore.
when I try to add it, I get an Error:
• Disk 1 is already in the storage pool.
Select a different disk to add to the storage pool.
ID: 350

Even though the storage pool is empty and there is unassigned not formatted space on the disk.
I tried using the console in the hopes of making progress on this, but no luck:

as a work around I now reduced the partition on Disk 2 and used that one for now. but it's not really what I want. now trying to remove Disk 2 from the Storage Pool, spits out another error:
• Disk 2 cannot be removed from the storage pool because it contains storage pool volumes ID 355.

Furthermore while trying to create a protection Group, I now get an Error:
• Connection to the DPM service has been lost.
Review the application event log for information about a possible service shutdown. Verify that the following services are not disabled:
DPM
DPM Replication Agent
SQLAgent$msdpm2012
MSSQL$msdpm2012
Virtual Disk Service
Volume Shadow Copy
ID: 917
Event Log:
The description for Event ID 999 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

An unexpected error caused a failure for process 'msdpm'. Restart the DPM process 'msdpm'.

Problem Details:
<FatalServiceError><__System><ID>19</ID><Seq>4361</Seq><TimeCreated>25.01.21 06:37:27</TimeCreated><Source>DpmThreadPool.cs</Source><Line>163</Line><HasError>True</HasError></__System><ExceptionType>MissingMethodException</ExceptionType><ExceptionMessage>Method not found: 'Int32 Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.PrmCatalog.CreateReplicaInstance(System.Guid, System.Guid, Microsoft.Internal.EnterpriseStorage.Dls.XsdClasses.StorageManager.StorageType, UInt64, System.Collections.Generic.List1&lt;System.Guid&gt;, System.String, Boolean)'.</ExceptionMessage><ExceptionDetails>System.MissingMethodException: Method not found: 'Int32 Microsoft.Internal.EnterpriseStorage.Dls.PRMCatalog.PrmCatalog.CreateReplicaInstance(System.Guid, System.Guid, Microsoft.Internal.EnterpriseStorage.Dls.XsdClasses.StorageManager.StorageType, UInt64, System.Collections.Generic.List1<System.Guid>, System.String, Boolean)'.
at Microsoft.Internal.EnterpriseStorage.Dls.Rhl.ReplicaAreaSetManagerHelper.CreateReplicaInDb(Guid datasourceId, UInt64 replicaSize, List1 dataSourcesOnReplica, String storageNodeServerName, Boolean migrationScenario) at Microsoft.Internal.EnterpriseStorage.Dls.Rhl.ReplicaAreaSetManager.Allocate(Guid dataSourceId, List1 dataSourcesOnReplica, String storageNodeServerName, String replicaAreaSetName, String replicaMountPointName, UInt64 replicaSize, String shadowCopyMountPointName, UInt64 shadowCopySize, String replicaGuid, String shadowCopyGuid, Boolean formatRequested, Boolean isCustom, Boolean isDiskMigration)
at Microsoft.Internal.EnterpriseStorage.Dls.StorageManager.DiskManager.AllocateStorage(String containerId, Guid storageId, StorageParams storageParams)
at Microsoft.Internal.EnterpriseStorage.Dls.StorageManager.StorageManager.AllocateStorage(String containerId, Guid storageId, StorageType storageType, StorageParams storageParams)
at Microsoft.Internal.EnterpriseStorage.Dls.Intent.DataSourceTranslator.PerformReplicaAllocation(Boolean isCustom, ProtectedObjectType[] protectedObjects)
at Microsoft.Internal.EnterpriseStorage.Dls.Intent.DataSourceTranslator.ValidateAndPerformReplicaAction(ProtectedObjectType[] protectedObjects, Boolean isReplicaProtectionTypeChanged, Dictionary`2 reallocateStorageMap)
at Microsoft.Internal.EnterpriseStorage.Dls.Intent.ProtectedGroupTranslator.ValidateAndPerformReplicaAction()
at Microsoft.Internal.EnterpriseStorage.Dls.Intent.ProtectedGroupTranslator.PrepareForTranslation()
at Microsoft.Internal.EnterpriseStorage.Dls.Intent.ProtectedGroupTranslator.TranslateGroup(IMCatalogType IMCatalogXmlPassed, String intentCatalogXml, String oneTimePasscode)
at Microsoft.Internal.EnterpriseStorage.Dls.Engine.CIntentServices.ConfigureProtectedGroup(UInt16* bstrIMCatalogXml)
at Microsoft.Internal.EnterpriseStorage.Dls.Engine.CCoreServices.ConfigureProtectedGroup(CCoreServices* , UInt16* bstrIMCatalogXml, tagSAFEARRAY** exceptionResult)</ExceptionDetails></FatalServiceError>

Answer 1

Hi,
Have you updated to the latest Rollup 2 of DPM 2019:
https://support.microsoft.com/en-us/topic/update-rollup-2-for-system-center-2019-data-protection-manager-6fe0b459-36be-6dd7-5073-0badee0c817a
Please check the doc on Add Modern Backup Storage to DPM:
https://learn.microsoft.com/en-us/system-center/dpm/add-storage?view=sc-dpm-2019

DPM 2019 accepts volumes/disks for storage. Once you add a volume, DPM formats the volume to ReFS to use the new features of Modern Backup Storage. Volumes cannot reside on a dynamic disk, use only a basic disk.

For disk 1, maybe you can try to use diskpart and clean command to re-initialized the disk, then add it again to Storage Pool.
diskpart
list disk
select disk 1
clean

For disks cannot be removed, you need to open the console, go to Protection. Click on All - it will show some with Inactive protection. Right-click on the group/member and remove the data. This will remove the data from the disk.

According to error id 917 and 999, please try the following steps:
In SQL Management studio, run a check on the database just to be sure everything was ok with that – locate the MSDPM DB and open a query, run:
DBCC CHECKDB;
GO

Check the database is synced with the DPM clients, to do this open a DPM Management Shell and run:
.DPMSync.exe -sync

Thanks for your time!
Best Regards,
Mico Mi

---

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Thanks for replying,
here my feedback on those different steps:

Hi,
Have you updated to the latest Rollup 2 of DPM 2019:
https://support.microsoft.com/en-us/topic/update-rollup-2-for-system-center-2019-data-protection-manager-6fe0b459-36be-6dd7-5073-0badee0c817a
Please check the doc on Add Modern Backup Storage to DPM:
https://learn.microsoft.com/en-us/system-center/dpm/add-storage?view=sc-dpm-2019

DONE. I also updates SSMS to the newest version.

DPM 2019 accepts volumes/disks for storage. Once you add a volume, DPM formats the volume to ReFS to use the new features of Modern Backup Storage. Volumes cannot reside on a dynamic disk, use only a basic disk.
For disk 1, maybe you can try to use diskpart and clean command to re-initialized the disk, then add it again to Storage Pool.
diskpart
list disk
select disk 1
clean

All my Disks apart from the System Volume are dynamic... so I can’t just diskpart them as I have Virtual machines and other services running on those. I can check with the Client if they are willing to add a dedicated Disk for DPM. I don’t see any other way if Dynamic Disks are not allowed.
It worked in DPM 2012 though, has this change been implemented since? Or is it just not recommended but worked anyway?

For disks cannot be removed, you need to open the console, go to Protection. Click on All - it will show some with Inactive protection. Right-click on the group/member and remove the data. This will remove the data from the disk.

NO Protection Groups are present. It just says “No Protection group has been created and points me to the wizzard.

According to error id 917 and 999, please try the following steps:
In SQL Management studio, run a check on the database just to be sure everything was ok with that – locate the MSDPM DB and open a query, run:
DBCC CHECKDB;
GO

DONE – No Errors

Check the database is synced with the DPM clients, to do this open a DPM Management Shell and run:
.DPMSync.exe -sync

DONE

RESULT:

Still can’t add disk 1 to storage pool
Still can’t remove Disk 2 from storage pool.
Creating Protection group -> still crashes with Error 917. And MMC crashes.
It gives a success on the first Allocate replica job, then crashes, shows no Protection group and has created 2 “DPM-vol” partitions on Disk 2: which I need to delete manually in Disk Management as they don’t show up in DPM anywhere.

Regards,
J.

Answer 3

Hi,

thanks for the reply.

that's what I feared... I will discuss this with the client in order to get a dedicated physical volume and then see if this resolves the issues.

regards,

J.