I am trying to write a script to export a Hyper-V backup from my DPM server (DPM 2012 - no service pack).  It is my understanding that, in order to do this, I need to create a New-DPMRecoveryOption (which is then passed to Recover-RecoverableItem to export the backup).  When I try to create a New-DPMRecoveryOption, I get the following error:

New-DPMRecoveryOption : The recovery point location that you have passed is invalid. Please try again with a different value. (ID: 31050)
At C:\Users\administrator\Desktop\backup-export.ps1:15 char:29
+ $ROP = New-DPMRecoveryOption <<<<  -TargetServer host01.domain.local -RecoveryLocation CopyToFolder -HyperVDatasource -RecoveryType Recover -TargetLocation "C:\temp"
    + CategoryInfo          : NotSpecified: (:) [New-DPMRecoveryOption], DlsEx
   ception

    + FullyQualifiedErrorId : InvalidRecoveryLocation,Microsoft.Internal.EnterpriseStorage.Dls.UI.Cmdlet.RecoveryCmdLets.NewRecoveryOption

Here is the statement that is throwing the error:

$ROP = New-DPMRecoveryOption -TargetServer host01.domain.local -RecoveryLocation CopyToFolder -HyperVDatasource -RecoveryType Recover -TargetLocation "C:\temp"

I have searched and searched - every blog I come across says that this is the way to do it.  The error isn't very helpful either.  There is no "recovery point location" specified.  There is a recovery location, but according to Microsoft documentation and all of the blogs that I have read, the value that I am providing for this argument is the only value that can be provided when attempting to recover a HyperVDatasource.

For the -TargetServer argument, I have tried multiple servers (including the local server and invalid server names) but I keep getting the same error.  This leads me to believe that this is not the issue.

I have confirmed that the -TargetLocation exists.

The -RecoveryType should be correct - according to Microsoft documentation, the "Recover" value is required for reovering a HyperVDatasource.

I have tried this on one of our other DPM servers (DPM 2012 SP1) - I get the same exact error.

I am at my wits end on this issue.  I have been researching for days and cannot find a thing on Google.  When I search the error, I get 4 or 5 results and they are all useless.  What is more frustrating is I'm pretty sure it's something simple that I haven't caught yet.  Any insight would be greatly appreciated.