Unable to start VM migration using Start VM Migration API

[lahari]

Hi Team,

I am trying to complete the migration of data to production using API once Instant recovery is started. I have collected the restore point ID and started instant recovery which is successful. I have got Mount ID using Get VM mount API.
Starting the VM migration by providing Mount ID and below mentioned details but I am receiving 400 bad request with error message as :
{
"errorCode": "UnknownError",
"message": "Object reference not set to an instance of an object.\r\n",
"resourceId": null
}
API guide followed : https://helpcenter.veeam.com/docs/backu ... eryMigrate


API :

Code: Select all

[size=50]curl --location 'https://172.xx.xx.xx:xxxx/api/v1/restore/instantRecovery/vSphere/vm/ed0eef9f-023c-4fa1-a71c-a66fe42f9639/migrate' \
--header 'Authorization: bearer eyJhbGciOiJSUzUxMiIsImtpZCI6IjdCOEZFQkNBRDYzQTYyRENGOUY5QTBFM0JCNzQ2Mjg0QUIwMUMyODYiLCJ0eXAiOiJKV1QifQ.eyJ1bmlxdWVfbmFtZSI6ImFkbWluaXN0cmF0b3IiLCJuYmYiOjE3MTQzODM2MzEsImV4cCI6MTcxNDM4NzIzMSwiaWF0IjoxNzE0MzgzNjMxLCJhdWQiOiJhY2Nlc3MifQ.p0Wn0GzSROEPlpiwMsXuHAYrMv25aWI6K_qy9zJgzR1Pv7NcDWnSfvr-WLRlk1aqyESnlYybKFZ6PUDpmsoF3MveudBRtuHzJTAgYUhiRSDA9-fYaL1a3ug10LqtU6qRq4tnhFuSf9ofhngJd8SO9tUVcZ6SuS5g4f6T9rhdMFhi2Il4dM9ZkINMfBHRm0zRuQoD-03OwGI02h-mxvcq1qcFeET2nsBE-PchXnoivUA_K5515_Te5VUCgHHGZWwcKfZjy5PMLcGO6QevJ4lLqCBcXOV5MqdPL8FMSPhYq7w805KFPsM22yGbykAWgAIOV49UKjnkdL3R6sxyphBSrQ' \
--header 'Content-Type: application/json' \
--header 'x-api-version: 1.1-rev1' \
--data '{
    "destinationHost": {
      "type": "Datastore",
      "hostName": "h22-1-vm1.lab.archivas.com",
      "name": "Veeam Proxy 2",
	  "urn": "vmomi",
      "objectId": "vm-11317",
      "platform": "VMware",
      "size": "N/A"
    },
    "folder": {
      "type": "Datastore",
      "hostName": "h22-1-vm1.lab.archivas.com",
      "name": "Veeam Proxy 2",
	  "urn": "vmomi",
      "objectId": "vm-11317",
      "platform": "VMware",
      "size": "N/A"

    },
    "resourcePool": {
      "type": "Datastore",
      "hostName": "h22-1-vm1.lab.archivas.com",
      "name": "Veeam Proxy 2",
	  "urn": "vmomi",
      "objectId": "vm-11317",
      "platform": "VMware",
      "size": "N/A"

    },
    "datastore": {
      "type": "Datastore",
      "hostName": "h22-1-vm1.lab.archivas.com",
      "name": "Veeam Proxy 2",
	  "urn": "vmomi",
      "objectId": "vm-11317",
      "platform": "VMware",
      "size": "N/A"

    },
    "sourceProxyIds": [],
    "targetProxyIds": [],
    
    "VeeamQMEnabled": true,
    "DeleteSourceVmsFiles": false
  }'
[/size]

[david.domask]

Hi Nakka,

Sounds like an unexpected behavior and it's best checked by the Support Team. Please open a case and show the same situation that you did here, and please export logs from the VBR server using the 3rd radio option after reproducing the issue. Please note the date and time of your reproduce test for the Support Team as well as including your code above and the logs as requested.