This is an archive version of the document. To get the most up-to-date information, see the current version.POST /vAppRestorePoints/{ID}?action=restore
Starts the full VM restore process from the vApp restore point having the specified ID.
Request
To start the full vApp restore, send the POST HTTP request to the /vAppRestorePoints/{ID}/?actions=restore URL.
HTTP Request
Request Headers
The request contains the following headers:
Header | Required | Description |
|---|---|---|
X-RestSvcSessionId | True | The request requires authorization. In the header, the client must send a session ID copied from the server reply to the request creating a new logon session. For details, see Authentication and Security. |
Content-Type | True | Identifies the format of the request body message. Possible values:
|
Accept | False | Identifies the format of the response. Possible values:
If the request does not contain the header, the server will return the response in the XML format. |
Request Body
In the request body, the client must send the parameters for the full vApp restore process. The body of the request must conform to the XML Schema Definitionem_rest_ of Veeam Backup Enterprise Manager REST API.
The request body must contain the following elements:
Element | Type | Description | Modifiable | Min/Max Occurrence |
|---|---|---|---|---|
PowerOnAfter | Boolean | Specifies if VMs in the vApp must be powered on after the restore process is complete. | Yes | 1/1 |
HierarchyRoot | UidType | UID of the host on which the vApp must be restored, for example: urn:veeam:HierarchyRoot:2dcfebc9-eb06-4d3b-a639-c1cfa8483621. | Yes | 1/1 |
OrgVdcRef | HierarchyObj | Reference to the OrgVdc to which the vApp must be restored. The reference can be constructed manually or obtained with the lookup service. For details on using the lookup, see Virtual Infrastructure Lookup. | Yes | 1/1 |
vAppNewName | String | Name of the restored vApp. If this parameter is not specified, the initial vApp name will be used. | Yes | 0/1 |
VmsRestore | vCloudVmRestoreParametersInfo | Defines VM-specific parameters. | No | — |
VM restore parameters are provided in the following format:
<VmsRestoreParameters> |
"VmsRestoreParameters": { "Vm": { "VmRestorePointUid": "urn:veeam:VmRestorePoint:48c8cd65-d5fa-4ca6-8a98-d3fde641086e", "VmNewName": "VM1", "DatastoreRef": "urn:vCloud:Datastore:fa099d3b-7376-49b1-884c-bb6fa47c7b1e.urn:vcloud:datastore:68d9f62d-f3c1-4842-8ad6-9b7faca3c92a", "OrgVdcStorageProfileRef": "urn:vCloud:OrgVdcStorageProfile:fa099d3b-7376-49b1-884c-bb6fa47c7b1e.urn:vcloud:vdcstorageprofile:1afeb3cc-bc4f-4e0f-b092-a3f8bbe70adc", "LinkedCloneVmTemplateRef": "" } } |
You can define the following restore parameters for VMs:
Element | Type | Description | Modifiable | Min/Max Occurrence |
|---|---|---|---|---|
VmRestorePointUid | UidType | UID of the restore point from which the VM must be restored, for example: urn:veeam:VmRestorePoint:48c8cd65-d5fa-4ca6-8a98-d3fde641086e. | Yes | 1/1 |
VmNewName | String | Name of the restored VM. If this parameter is not specified, the VM is restored with its initial name. | Yes | 0/1 |
DatastoreRef | HierarchyObjRefType | Reference to the datastore on which VM files must be placed. You can construct the reference manually or use the lookup service to retrieve the reference. | Yes | 0/1 |
OrgVdcStorageProfileRef | HierarchyObjRefType | Reference to the OrgVdc profile to be used for the restored VM. You can construct the reference manually or use the lookup service to retrieve the reference. | Yes | 0/1 |
LinkedCloneVmTemplateRef | HierarchyObjRefType | (For linked clone VMs) Reference to the template that was used to create the VM. You can construct the reference manually or use the lookup service to retrieve the reference. | Yes | 0/1 |
<?xml version="1.0" encoding="utf-8"?> |
{ "VCloudVAppRestoreSpec": { "PowerOnAfterRestore": false, "HierarchyRootUid": "urn:veeam:HierarchyRoot:2dcfebc9-eb06-4d3b-a639-c1cfa8483621", "OrgVdcRef": "urn:vCloud:OrgVdc:2dcfebc9-eb06-4d3b-a639-c1cfa8483621.urn:vcloud:vdc:1d0bf8ae-8eac-4772-b675-5a4cf06fcbc1", "VAppNewName": "vApp2", "VmsRestoreParameters": [ { "VmRestorePointUid": "urn:veeam:VmRestorePoint:b3755195-80bc-4149-937b-4d58d6caac34", "VmNewName": "VM1", "DatastoreRef": "urn:vCloud:Datastore:2dcfebc9-eb06-4d3b-a639-c1cfa8483621.urn:vcloud:datastore:68d9f62d-f3c1-4842-8ad6-9b7faca3c92a", "OrgVdcStorageProfileRef": "urn:vCloud:OrgVdcStorageProfile:2dcfebc9-eb06-4d3b-a639-c1cfa8483621.urn:vcloud:vdcstorageprofile:1afeb3cc-bc4f-4e0f-b092-a3f8 bbe70adc", "LinkedCloneVmTemplateRef": "" }, { "VmRestorePointUid": "urn:veeam:VmRestorePoint:3acc4a1d-8a11-4119-b361-291e2d785dde", "VmNewName": "VM2", "DatastoreRef": "urn:vCloud:Datastore:2dcfebc9-eb06-4d3b-a639-c1cfa8483621.urn:vcloud:datastore:68d9f62d-f3c1-4842-8ad6-9b7faca3c92a", "OrgVdcStorageProfileRef": "urn:vCloud:OrgVdcStorageProfile:2dcfebc9-eb06-4d3b-a639-c1cfa8483621.urn:vcloud:vdcstorageprofile:1afeb3cc-bc4f-4e0f-b092-a3f8 bbe70adc", "LinkedCloneVmTemplateRef": "" } ] } } |
The server returns the following response to the client.
A successfully completed operation returns response code 202 Accepted.
Header | Description |
|---|---|
Content-length | The length of the response body. |
Content-type | The media type and syntax of the request body message. Possible values:
|
Request: POST https://localhost:9398/api/vAppRestorePoints/f139af13-0d49-49c1-bf88-8b2d0db621e3?action=restore
Request Headers: X-RestSvcSessionId NDRjZmJkYmUtNWE5NS00MTU2LTg4NjctOTFmMDY5YjdjMmNj
Request Body: <?xml version="1.0" encoding="utf-8"?>
Response: 202 Accepted
Response Body: <Task xmlns="http://www.veeam.com/ent/v1.0" Type="Task" Href="https://localhost:9398/api/tasks/task-1"> |
Request: GET https://localhost:9398/api/tasks/task-1
Request Header: X-RestSvcSessionId NDRjZmJkYmUtNWE5NS00MTU2LTg4NjctOTFmMDY5YjdjMmNj
Response: 200 OK
Response Body: <Task xmlns="http://www.veeam.com/ent/v1.0" Type="Task" Href="https://localhost:9398/api/tasks/task-1"> |
