Hello,

I am facing the following error while trying to add a drive to a protection group :

Dynamic disks use a private region of the disk to maintain a Logical Disk Manager database. The current occupancy of LDM database is 93% which is over the DPM limit of 90%.Hence, all volume creations and grows have been disabled.

Can someone help?

Thanks and Regards,

Hi Preethi,

Logical Disk Manager or LDM is a hidden partition that stores the dynamic disk database, which contains information about all dynamic disks and volumes installed on the computer. The LDM database can only store 2960 records before it can no longer create or extend volumes. This is a limitation within Windows Server.

My suggestion to you is to add a another disk to your DPM Disk Pool and migrate datasources from the over-committed disk to the new disk using the MigrateDatasourceDataFromDPM-script.

Here is a guide how to use the script: How to Use The Migratedatasourcedatafromdpm.Ps1 DPM Powershell Script to Move Data

Kind Regards
Markus Eliasson

• Marked as answer by PreethiC 17 hours 40 minutes ago

Hi Preethi,

Logical Disk Manager or LDM is a hidden partition that stores the dynamic disk database, which contains information about all dynamic disks and volumes installed on the computer. The LDM database can only store 2960 records before it can no longer create or extend volumes. This is a limitation within Windows Server.

My suggestion to you is to add a another disk to your DPM Disk Pool and migrate datasources from the over-committed disk to the new disk using the MigrateDatasourceDataFromDPM-script.

Here is a guide how to use the script: How to Use The Migratedatasourcedatafromdpm.Ps1 DPM Powershell Script to Move Data

Kind Regards
Markus Eliasson

• Marked as answer by PreethiC Monday, September 07, 2015 1:56 PM

Hi Preethi,

Logical Disk Manager or LDM is a hidden partition that stores the dynamic disk database, which contains information about all dynamic disks and volumes installed on the computer. The LDM database can only store 2960 records before it can no longer create or extend volumes. This is a limitation within Windows Server.

My suggestion to you is to add a another disk to your DPM Disk Pool and migrate datasources from the over-committed disk to the new disk using the MigrateDatasourceDataFromDPM-script.

Here is a guide how to use the script: How to Use The Migratedatasourcedatafromdpm.Ps1 DPM Powershell Script to Move Data

Kind Regards
Markus Eliasson

• Marked as answer by PreethiC Monday, September 07, 2015 1:56 PM

Markus, as far as I know the LDM database is global. Adding a disk will not help.

Preethi: If you run into this issue I would suggest to search for the most fragmented volume and decide if it is possible to shrink or even better delete it (deleting meaning losing recovery points!). This will free extents in the LDM database. If you can add another disk, add the disk and recreate the volume which was deleted. This volume will be created on the new disk in one piece, unfragmented, i.e. only using very little entries in the LDM database (I think 3 entries are needed). You should then consider migrating datasource per datasource from the old to the new disk(s) in order to "defragment" the volumes and reducing the amount of used entries in the LDM database. But be careful: During migration the number of database entries needed is temporarily higher till the old recovery points expire. This is a very tidious and time consuming operation. You have to avoid at all costs to go to 95% or higher...

• Marked as answer by PreethiC 17 hours 40 minutes ago

Hi,

Sorry if I was unclear in my reply! Adding a disk will help you with the process of using the MigrateDatasourceDataFromDPM-script. When a migration occurs it will consolidate all "extended"-volume records into only one record.

With an "extended"-record I refer to when a recovery point or replica volume have "auto-grown" in DPM or manually got extended.

Kind Regards
Markus Eliasson

Markus, as far as I know the LDM database is global. Adding a disk will not help.

Preethi: If you run into this issue I would suggest to search for the most fragmented volume and decide if it is possible to shrink or even better delete it (deleting meaning losing recovery points!). This will free extents in the LDM database. If you can add another disk, add the disk and recreate the volume which was deleted. This volume will be created on the new disk in one piece, unfragmented, i.e. only using very little entries in the LDM database (I think 3 entries are needed). You should then consider migrating datasource per datasource from the old to the new disk(s) in order to "defragment" the volumes and reducing the amount of used entries in the LDM database. But be careful: During migration the number of database entries needed is temporarily higher till the old recovery points expire. This is a very tidious and time consuming operation. You have to avoid at all costs to go to 95% or higher...

• Marked as answer by PreethiC Monday, September 07, 2015 1:56 PM

Markus, as far as I know the LDM database is global. Adding a disk will not help.

Preethi: If you run into this issue I would suggest to search for the most fragmented volume and decide if it is possible to shrink or even better delete it (deleting meaning losing recovery points!). This will free extents in the LDM database. If you can add another disk, add the disk and recreate the volume which was deleted. This volume will be created on the new disk in one piece, unfragmented, i.e. only using very little entries in the LDM database (I think 3 entries are needed). You should then consider migrating datasource per datasource from the old to the new disk(s) in order to "defragment" the volumes and reducing the amount of used entries in the LDM database. But be careful: During migration the number of database entries needed is temporarily higher till the old recovery points expire. This is a very tidious and time consuming operation. You have to avoid at all costs to go to 95% or higher...

• Marked as answer by PreethiC Monday, September 07, 2015 1:56 PM