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.aspx
http://icttechie.wordpress.com/2013/11/14/microsoft-dpm-2012-sp1-how-to-migrate-data-source-using-migratedatasourcedatafromdpm-by-icttechie/ Nathan Shelby Lead Systems Engineer – Quote Wizard <https://quotewizard.com/> [email protected] / 206-753-2626 Malo Periculosam Libertatem Quam Quietum Servitium On Fri, Oct 3, 2014 at 2:14 PM, Daniel Chenault <[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] > > To: [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? > > > > > > >
