PSRemoting Start-VBRInstantRecovery error, v7

[pizzim13]

I am having an issue executing an instant recovery via PowerShell remoting. I have only tested this in v7. The following command works as excepted when run locally

Code: Select all

Start-VBRInstantRecovery -RestorePoint $VBRRSPoint -VMName $VMIRName -Server $VMHost -ResourcePool $RSPool

The instant recovery job starts and the vm is registered in vCenter. The variables are loaded with the same objects in both the local and remote session

When run remotely, the job starts and then fails. This is the error from the remote console

Code: Select all

PSMessageDetails      : 
Exception             : Veeam.Backup.Common.CAppException: There is no instant recovery session with ID '566ed67c-e835-4dfa-a27c-c5401d541e47'.
                           at Veeam.Backup.PowerShell.Model.InstantRecovery.Get(Guid id)
                           at Veeam.Backup.PowerShell.Command.StartVBRInstantRecovery.Execute()
                           at Veeam.Backup.PowerShell.PSCmdletLogged.ProcessRecord()
                           at System.Management.Automation.CommandProcessor.ProcessRecord()
TargetObject          : 
CategoryInfo          : NotSpecified: (:) [Start-VBRInstantRecovery], CAppException
FullyQualifiedErrorId : Veeam.Backup.Common.CAppException,Veeam.Backup.PowerShell.Command.StartVBRInstantRecovery
ErrorDetails          : 
InvocationInfo        : System.Management.Automation.InvocationInfo
ScriptStackTrace      : at <ScriptBlock>, <No file>: line 1
PipelineIterationInfo : {}

This is the error from the Veeam job log: (I X'd out identifying info)

Code: Select all

5/29/2015 10:08:36 AM          Starting VM "XXX-XXXX_IR" recovery
5/29/2015 10:08:42 AM          Connecting to host "XXXX.XXX.XXX"
5/29/2015 10:09:24 AM Error    Checking if vPower NFS datastore is mounted on host
5/29/2015 10:09:24 AM Error    Failed to publish VM XXX-XXXX_IR Error: The RPC server is unavailable
                               RPC function call failed. Function name: [InvokerTestConnection]. Target machine: [XXX.XXX.XXX.XXX].

Anyone else ever try this?

[pizzim13]

Scratch that. Appears to be a networking issue, not PowerShell.