VBR API Entire VM restore

[jverbeek]

Hi,

We're currently implementing the VBR API, and are trying to restore an entire VM (https://helpcenter.veeam.com/docs/backu ... toreVmware).

I see some strange behavior compared to a restore using the EM API, or EM interface.

Below is the json document we're using:

Code: Select all

{
  "objectRestorePointId" : "<restore point id>",
  "type" : "Customized",
  "restoresProxies" : {
    "autoSelection" : true,
    "proxyIds" : null
  },
  "secureRestore" : {
    "enableAntivirusScan" : false,
    "virusDetectionAction" : "Ignore",
    "enableEntireVolumScan" : false
  },
  "powerUp" : false,
  "reason" : "Restored by MyApp",
  "destinationHost" : {
    "hostName" : "<hostname>",
    "name" : "<dst cluster>",
    "type" : "Cluster",
    "objectId" : "<dst cluster objectid>"
  },
  "resourcePool" : null,
  "datastore" : {
    "datastore" : {
      "hostName" : "<hostname>",
      "name" : "<datastore>",
      "type" : "Datastore",
      "objectId" : "<datastore objectid>"
    },
    "diskType" : "Source"
  },
  "folder" : {
    "vmName" : "MyVm_restore",
    "folder" : {
      "hostName" : "<hostname>",
      "name" : "<folderName>",
      "type" : "Folder",
      "objectId" : "<folder objectid>"
    },
    "restoreVmTags" : false
  },
  "network" : null
}

Somehow it restores the VM metadata files to the datastore specified in the DatastoreSpec, but it restores the .vmdk to the original location (although it is getting renamed to the vmName in the folderSpec).

Is this working as intended? Or should we open a ticket for this.

[oleg.feoktistov]

Hi,

Reproduced the same behavior in my lab, looks like a bug. Passed to QA directly, will let you know the outcome.

Best regards,
Oleg

[jverbeek]

Hello Oleg,

Is there any news regarding this issue?

[oleg.feoktistov]

Hi,

It's confirmed as a bug, the fix is scheduled for vNext.

Best regards,
Oleg