In Disk Manager, was the new disk initialized as a dynamic disk and all 
existing volumes on the disk removed?

-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Daniel Chenault
Sent: Friday, October 3, 2014 5:53 PM
To: [email protected]
Subject: RE: [NTSysADM] FW: [dpm] DPM Event ID 32065

PS C:\Program Files\Microsoft DPM\DPM\bin> .\migratedatasourcedatafromdpm 
-dpmservername ssddpm1 -source $ds[0] -destination $disk[2] 
Set-DPMProtectionGroup : The allocation of disk space for storage pool volumes 
failed because there is not enough unallocated disk space in the storage pool.
(ID: 358)
Add more disks to the storage pool or reduce the volume size requirement.
At C:\Program Files\Microsoft DPM\DPM\bin\MigrateDatasourceDataFromDPM.ps1:129
char:23
+             Set-ProtectionGroup <<<<  $mpg
    + CategoryInfo          : NotSpecified: (:) [Set-DPMProtectionGroup], 
DlsException
    + FullyQualifiedErrorId : NotEnoughFreeSpace,Microsoft.Internal.Enterprise
   Storage.Dls.UI.Cmdlet.ProtectionCmdLets.CommitProtectionGroup

The disk I pointed at is listed in the Management tab as added to the pool. 
It's unformatted; I was under the impression DPM took care of managing it's 
allocated disks.

I could use a good book that explains DPM and not one that just shows screen 
shots and where to click.

----------------------------------------
> From: [email protected]
> To: [email protected]
> Subject: RE: [NTSysADM] FW: [dpm] DPM Event ID 32065
> Date: Fri, 3 Oct 2014 14:36:21 -0700
>
> I do; 2TB unallocated. Time to slog through...
>
> Thank you for replying.
>
> ________________________________
>> Date: Fri, 3 Oct 2014 14:32:00 -0700
>> Subject: Re: [NTSysADM] FW: [dpm] DPM Event ID 32065
>> From: [email protected]
>> To: [email protected]
>>
>> Hopefully you have a spare empty volume/drive attached to the DPM box
>>
>> http://blogs.technet.com/b/askcore/archive/2009/06/22/how-to-use-the-
>> migratedatasourcedatafromdpm-ps1-dpm-powershell-script-to-move-data.a
>> spx
>>
>> http://icttechie.wordpress.com/2013/11/14/microsoft-dpm-2012-sp1-how-
>> to-migrate-data-source-using-migratedatasourcedatafromdpm-by-icttechi
>> e/
>>
>>
>> Nathan Shelby
>> Lead Systems Engineer - Quote Wizard<https://quotewizard.com/> 
>> [email protected]<mailto:[email protected]> / 206-753-2626 Malo 
>> Periculosam Libertatem Quam Quietum Servitium
>>
>> On Fri, Oct 3, 2014 at 2:14 PM, Daniel Chenault 
>> <[email protected]<mailto:[email protected]>> wrote:
>> Getting nada on the DPM list...
>>
>> I was thrust into the added role of DPM Dude mostly kicking and screaming.
>>
>> ----------------------------------------
>>> From: [email protected]<mailto:[email protected]>
>>> To: [email protected]<mailto:[email protected]>
>>> Subject: [dpm] DPM Event ID 32065
>>> Date: Fri, 3 Oct 2014 11:56:32 -0700
>>>
>>> "Dynamic disks use a private region of the disk to maintain a 
>>> Logical
>> Disk Manager (LDM) database. The current occupany of hte LDM database 
>> is 94% which is over the DPM limit of 90%. Hence all volume creations 
>> and grows have been disabled"
>>> This is explained in the following:
>>> http://technet.microsoft.com/en-us/library/ff634234.aspx
>>>
>>> I confess I have no idea what the article means.
>>>
>>> "User Action
>>>
>>> To resolve this error, control the size of the LDM database by
>> migrating one or more data sources to a different volume.
>>> To migrate a data source to a different volume, in DPM Management
>> Shell, run the MigrateDatasourceDataFromDPM cmdlet.""
>>> Uh... okay. I looked up the syntax but still don't understand what 
>>> is
>> expected here. I'm an Exchange guy, not a DPM guy. Plain english 
>> please?
>>>
>>>
>>
>>
>>
>
>
                                          



Reply via email to