Cannot restore to original location using PowerShell

[vmm]

Hi.

We have a problem with restoring a VM to its original location using parameter -ToOriginalLocation.

When we issue the command:

Code: Select all

Start-VBRRestoreVM -RestorePoint $rrr -Server 10.242.4.26 

we can do it

But when we issue the command:

Code: Select all

Start-VBRRestoreVM -RestorePoint $rrr -Server 10.242.4.26 -ToOriginalLocation

or

Code: Select all

Start-VBRRestoreVM -RestorePoint $rrr -Server 10.242.4.26 -PowerUp $TRUE -ToOriginalLocation

we get an error:

Code: Select all

Start-VBRRestoreVM : Parameter set cannot be resolved using the specified named parameters.
At line:1 char:1
+ Start-VBRRestoreVM -RestorePoint $rrr -Server 10.242.4.26 -ToOriginalLocation
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Start-VBRRestoreVM], ParameterBindingException
    + FullyQualifiedErrorId : AmbiguousParameterSet,Veeam.Backup.PowerShell.Command.StartVBRRestoreVM

[veremin]

Since you're restoring VM to original location, try to disregard -Server parameter, as it's not needed here:

Code: Select all

Start-VBRRestoreVM -RestorePoint $rrr -ToOriginalLocation

Thanks.

[vmm]

Code: Select all

PS C:\Users\Administrator> Start-VBRRestoreVM -RestorePoint $rrr -ToOriginalLocation
Start-VBRRestoreVM : Object reference not set to an instance of an object.
At line:1 char:1
+ Start-VBRRestoreVM -RestorePoint $rrr -ToOriginalLocation
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Start-VBRRestoreVM], NullReferenceException
    + FullyQualifiedErrorId : System.NullReferenceException,Veeam.Backup.PowerShell.Command.StartVBRRestoreVM

[veremin]

Try to run the script under the account with administrative privileges.

[vmm]

Doesn't work. The issue is the same.

[veremin]

In overwhelming majority of cases it's related to lack of permissions. If running script as administrator doesn't resolve that, open a ticket with our support team and let them investigate it directly. Thanks.

[tsightler]

I probably suggest this too often, but any chance this is on Windows 2008R2 with default Powershell 2.0? I've seen a lot of strange issues like this until Powershell is upgraded to at least 3.0.