Veeam Backup & Replication 13
REST API Reference
Related documents

Restore

The Restore section defines paths and operations for performing restore.

NOTE
In this version, the REST API supports the following recovery operations:
  • Instant Recovery of a VMware vSphere VM to VMware vSphere
  • Entire VM restore of a VMware vSphere VM to VMware vSphere
  • Entire VM restore of a VMware Cloud Director VM to VMware Cloud Director
  • Restore of disks that will be registered as First Class Disks (FCD) — a type of virtual disks that can be managed independent of any VM
  • File restore from a backup or replica of a Microsoft Windows or Linux machine

Get All VM Mounts

The HTTP GET request to the /api/v1/restore/instantRecovery/vSphere/vm path allows you to get an array of VM mounts.

Available to: Veeam Backup Administrator, Veeam Restore Operator.

SecurityBearer
Request
query Parameters
skip
integer <int32>

Number of mounts to skip.

limit
integer <int32>

Maximum number of mounts to return.

orderColumn
string (EInstantViVMRecoveryMountsFiltersOrderColumn)

Sorts mounts by one of the mount parameters.

Enum: "state" "name"
orderAsc
boolean

Sorts mounts in the ascending order by the orderColumn parameter.

stateFilter
string (EInstantRecoveryMountState)

Filters mounts by mount state.

Enum: "Failed" "Mounting" "Mounted" "Dismounting"
header Parameters
x-api-version
required
string
Default: 1.1-rev1

Version and revision of the client REST API. Must be in the following format: <version>-<revision>.

Responses
200

OK

401

Unauthorized. The authorization header has been expected but not found (or found but is expired).

403

Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.

404

Not found. No object was found with the path parameter specified in the request.

500

Internal server error. The request has been received but could not be completed because of an internal error at the server side.

get/api/v1/restore/instantRecovery/vSphere/vm
Request samples 
Response samples 
application/json
{
  • "data": [
    ],
  • "pagination": {
    }
}
Start Instant Recovery
The HTTP POST request to the /api/v1/restore/instantRecovery/vSphere/vm path allows you to start Instant Recovery of a VMware vSphere VM to VMware vSphere. You can recover a VM from the specified restore point to the original location with initial VM settings, or to any location but with different settings.
Available to: Veeam Backup Administrator, Veeam Restore Operator.


SecurityBearer 
Request 
header Parameters
x-api-version
required
string
 Default:  1.1-rev1
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Request Body schema: application/json
required
restorePointId
required
string <uuid> 
ID of the restore point.


 
type
required
string (EInstantVMRecoveryModeType) 
Restore mode.


 
required
object (SecureRestoreSpec) 
Secure restore settings.


 
vmTagsRestoreEnabled
boolean
If true, Veeam Backup & Replication restores tags that were assigned to the original VM, and assign them to the restored VM.


 
nicsEnabled
boolean
If true, the restored VM is connected to the network.


 
powerUp
boolean
If true, Veeam Backup & Replication powers on the restored VM on the target host.


 
reason
string
Reason for restoring the VM.


 
Responses 
201
An InstantRecovery session has been started to start Instant Recovery. To check the progress, track the session state.


400
Bad request. This error is related to POST/PUT requests. The request body is malformed, incomplete or otherwise invalid.


401
Unauthorized. The authorization header has been expected but not found (or found but is expired).


403
Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.


404
Not found. No object was found with the path parameter specified in the request.


500
Internal server error. The request has been received but could not be completed because of an internal error at the server side.


post/api/v1/restore/instantRecovery/vSphere/vm
Request samples 
application/json
{
  • "restorePointId": "af75ddaa-d680-4c50-ac82-07834a007707",
  • "type": "OriginalLocation",
  • "vmTagsRestoreEnabled": true,
  • "secureRestore": {
    },
  • "nicsEnabled": false,
  • "powerUp": true,
  • "reason": "Instant Recovery to VMware vSphere"
}
Response samples 
application/json
{
  • "sessionType": "InstantRecovery",
  • "state": "Working",
  • "id": "2e0bf225-91b3-4005-8524-6f7971e9ac4f",
  • "name": "apache05",
  • "jobId": "9239c712-3c0e-49e9-ae4d-c9c6267504e0",
  • "creationTime": "2024-03-07T19:31:23.07555+01:00",
  • "endTime": null,
  • "progressPercent": 0,
  • "result": {
    },
  • "resourceId": "2e0bf225-91b3-4005-8524-6f7971e9ac4f",
  • "resourceReference": "/api/v1/restore/instantRecovery/vmware/vm/2e0bf225-91b3-4005-8524-6f7971e9ac4f",
  • "parentSessionId": null,
  • "usn": 0
}
Get VM Mount
The HTTP GET request to the /api/v1/restore/instantRecovery/vSphere/vm/{mountId} path allows you to get a VM mount that has the specified mountID.
Available to: Veeam Backup Administrator, Veeam Restore Operator.


SecurityBearer 
Request 
path Parameters
mountId
required
string <uuid> 
Mount ID.


 
header Parameters
x-api-version
required
string
 Default:  1.1-rev1
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Responses 
200
OK


401
Unauthorized. The authorization header has been expected but not found (or found but is expired).


403
Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.


404
Not found. No object was found with the path parameter specified in the request.


500
Internal server error. The request has been received but could not be completed because of an internal error at the server side.


get/api/v1/restore/instantRecovery/vSphere/vm/{mountId}
Request samples 
Response samples 
application/json
{
  • "state": "Mounted",
  • "id": "32441b29-d55c-4b20-801a-c1b17cd75d55",
  • "sessionId": "32441b29-d55c-4b20-801a-c1b17cd75d55",
  • "spec": {
    },
  • "vmName": "apache04",
  • "errorMessage": ""
}
Stop VM Publishing
The HTTP POST request to the /api/v1/restore/instantRecovery/vSphere/vm/{mountId}/unmount path allows you to stop publishing the recovered VM and remove it from the destination host.
Available to: Veeam Backup Administrator, Veeam Restore Operator.


SecurityBearer 
Request 
path Parameters
mountId
required
string <uuid> 
Mount ID.


 
header Parameters
x-api-version
required
string
 Default:  1.1-rev1
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Responses 
200
An InstantRecovery session has been started to stop publishing the VM. To check the progress, track the session state.


400
Bad request. This error is related to POST/PUT requests. The request body is malformed, incomplete or otherwise invalid.


401
Unauthorized. The authorization header has been expected but not found (or found but is expired).


403
Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.


404
Not found. No object was found with the path parameter specified in the request.


500
Internal server error. The request has been received but could not be completed because of an internal error at the server side.


post/api/v1/restore/instantRecovery/vSphere/vm/{mountId}/unmount
Request samples 
Response samples 
application/json
{
  • "sessionType": "InstantRecovery",
  • "state": "Working",
  • "id": "2e0bf225-91b3-4005-8524-6f7971e9ac4f",
  • "name": "apache05",
  • "jobId": "9239c712-3c0e-49e9-ae4d-c9c6267504e0",
  • "creationTime": "2024-03-07T19:31:23.07555+01:00",
  • "endTime": null,
  • "progressPercent": 0,
  • "result": {
    },
  • "resourceId": "2e0bf225-91b3-4005-8524-6f7971e9ac4f",
  • "resourceReference": "/api/v1/restore/instantRecovery/vmware/vm/2e0bf225-91b3-4005-8524-6f7971e9ac4f",
  • "parentSessionId": null,
  • "usn": 0
}
Start VM Migration
The HTTP POST request to the /api/v1/restore/instantRecovery/vSphere/vm/{mountId}/migrate path allows you to start VM migration from the specified mount.
Available to: Veeam Backup Administrator, Veeam Restore Operator.


SecurityBearer 
Request 
path Parameters
mountId
required
string <uuid> 
Mount ID.


 
header Parameters
x-api-version
required
string
 Default:  1.1-rev1
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Request Body schema: application/json
required
required
object (InventoryObjectModel) 
Inventory object properties.


 
object (InventoryObjectModel) 
Inventory object properties.


 
object (InventoryObjectModel) 
Inventory object properties.


 
object (InventoryObjectModel) 
Inventory object properties.


 
sourceProxyIds
Array of strings <uuid> 
Array of source backup proxies.


 
targetProxyIds
Array of strings <uuid> 
Array of target backup proxies.


 
VeeamQMEnabled
boolean
If true, the Veeam Quick Migration mechanism is used. Otherwise, Veeam Backup & Replication will use VMware vMotion for migration.


 
DeleteSourceVmsFiles
boolean
If true, Veeam Backup & Replication will delete source VM files upon successful migration.


 
Responses 
200
A QuickMigration session has been started to migrate the VM. To check the progress, track the session state.


400
Bad request. This error is related to POST/PUT requests. The request body is malformed, incomplete or otherwise invalid.


401
Unauthorized. The authorization header has been expected but not found (or found but is expired).


403
Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.


404
Not found. No object was found with the path parameter specified in the request.


500
Internal server error. The request has been received but could not be completed because of an internal error at the server side.


post/api/v1/restore/instantRecovery/vSphere/vm/{mountId}/migrate
Request samples 
application/json
{
  • "destinationHost": {
    },
  • "folder": {
    },
  • "resourcePool": {
    },
  • "datastore": {
    },
  • "sourceProxyIds": [
    ],
  • "targetProxyIds": [
    ],
  • "VeeamQMEnabled": true,
  • "DeleteSourceVmsFiles": false
}
Response samples 
application/json
{
  • "sessionType": "QuickMigration",
  • "state": "Starting",
  • "id": "8228661b-861e-40c4-8133-8a97700f4dfa",
  • "name": "Quick Migration Job",
  • "jobId": "a00aa837-2c85-40c9-ae98-8b089dabc9b5",
  • "creationTime": "2024-03-07T21:16:08.216977+01:00",
  • "endTime": null,
  • "progressPercent": 0,
  • "result": null,
  • "resourceId": null,
  • "resourceReference": null,
  • "parentSessionId": null,
  • "usn": 0
}
Restore Entire VMware vSphere VM
The HTTP POST request to the /api/v1/restore/vmRestore/vSphere path allows you to perform entire VM restore of a VMware vSphere VM to VMware vSphere. You can restore a VM from the specified restore point to the original location with initial VM settings, or to any location but with different settings.
Available to: Veeam Backup Administrator, Veeam Restore Operator.


SecurityBearer 
Request 
header Parameters
x-api-version
required
string
 Default:  1.1-rev1
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Request Body schema: application/json
required
restorePointId
required
string <uuid> 
ID of the restore point.


 
type
required
string (EEntireVMRestoreModeType) 
Restore mode.


 
object (RestoreProxySpec) 
Backup proxies for VM data transport.


 
object (SecureRestoreSpec) 
Secure restore settings.


 
powerUp
boolean
If true, Veeam Backup & Replication powers on the restored VM on the target host.


 
reason
string
Reason for restoring the VM.


 
quickRollback
boolean
If true, Veeam Backup & Replication performs incremental restore.


 
Responses 
201
Restore session has been created. To check the progress, track the session state.


400
Bad request. This error is related to POST/PUT requests. The request body is malformed, incomplete or otherwise invalid.


401
Unauthorized. The authorization header has been expected but not found (or found but is expired).


403
Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.


404
Not found. No object was found with the path parameter specified in the request.


500
Internal server error. The request has been received but could not be completed because of an internal error at the server side.


post/api/v1/restore/vmRestore/vSphere
Request samples 
application/json
{
  • "restorePointId": "8c843d10-6d0f-4abe-b898-e1ba18b94f68",
  • "type": "OriginalLocation",
  • "restoreProxies": {
    },
  • "secureRestore": {
    },
  • "powerUp": true,
  • "reason": "string",
  • "quickRollback": true
}
Response samples 
application/json
{
  • "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  • "name": "string",
  • "jobId": "9d222c6d-893e-4e79-8201-3c9ca16a0f39",
  • "sessionType": "Infrastructure",
  • "creationTime": "2019-08-24T14:15:22Z",
  • "endTime": "2019-08-24T14:15:22Z",
  • "state": "Stopped",
  • "progressPercent": 0,
  • "result": {
    },
  • "resourceId": "026d60bb-63a8-407e-bf67-01dcfc6022e6",
  • "resourceReference": "string",
  • "parentSessionId": "b1d7834e-fe2f-4cad-b0e5-ff5c5615f344",
  • "usn": 0
}
Restore Entire VMware Cloud Director VM
The HTTP POST request to the /api/v1/restore/vmRestore/cloudDirector path allows you to perform entire VM restore of a VMware Cloud Director VM to VMware Cloud Director. You can restore a VM from the specified restore point to the original location with initial VM settings, or to any location but with different settings.
Available to: Veeam Backup Administrator, Veeam Restore Operator.


SecurityBearer 
Request 
header Parameters
x-api-version
required
string
 Default:  1.1-rev1
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Request Body schema: application/json
required
restorePointId
required
string <uuid> 
ID of the restore point.


 
type
required
string (EEntireVMRestoreModeType) 
Restore mode.


 
object (RestoreProxySpec) 
Backup proxies for VM data transport.


 
object (SecureRestoreSpec) 
Secure restore settings.


 
powerUp
boolean
If true, Veeam Backup & Replication powers on the restored VM on the target host.


 
reason
string
Reason for restoring the VM.


 
quickRollback
boolean
If true, Veeam Backup & Replication performs incremental restore.


 
Responses 
201
A RestoreVm session has been created. To check the progress, track the session state.


400
Bad request. This error is related to POST/PUT requests. The request body is malformed, incomplete or otherwise invalid.


401
Unauthorized. The authorization header has been expected but not found (or found but is expired).


403
Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.


404
Not found. No object was found with the path parameter specified in the request.


500
Internal server error. The request has been received but could not be completed because of an internal error at the server side.


post/api/v1/restore/vmRestore/cloudDirector
Request samples 
application/json
{
  • "restorePointId": "8c843d10-6d0f-4abe-b898-e1ba18b94f68",
  • "type": "OriginalLocation",
  • "restoreProxies": {
    },
  • "secureRestore": {
    },
  • "powerUp": true,
  • "reason": "string",
  • "quickRollback": true
}
Response samples 
application/json
{
  • "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  • "name": "string",
  • "jobId": "9d222c6d-893e-4e79-8201-3c9ca16a0f39",
  • "sessionType": "Infrastructure",
  • "creationTime": "2019-08-24T14:15:22Z",
  • "endTime": "2019-08-24T14:15:22Z",
  • "state": "Stopped",
  • "progressPercent": 0,
  • "result": {
    },
  • "resourceId": "026d60bb-63a8-407e-bf67-01dcfc6022e6",
  • "resourceReference": "string",
  • "parentSessionId": "b1d7834e-fe2f-4cad-b0e5-ff5c5615f344",
  • "usn": 0
}
Get All FCD Mounts
The HTTP GET request to the /api/v1/restore/instantRecovery/vSphere/fcd path allows you to get an array of FCD mounts.
Available to: Veeam Backup Administrator, Veeam Restore Operator.


SecurityBearer 
Request 
query Parameters
skip
integer <int32> 
Number of mounts to skip.


 
limit
integer <int32> 
Maximum number of mounts to return.


 
orderColumn
string (EVmwareFcdInstantRecoveryMountsFiltersOrderColumn) 
Sorts mounts by one of the mount parameters.


 Enum: "state" "name"  
orderAsc
boolean
Sorts mounts in the ascending order by the orderColumn parameter.


 
stateFilter
string (EInstantRecoveryMountState) 
Filters mounts by mount state.


 Enum: "Failed" "Mounting" "Mounted" "Dismounting"  
header Parameters
x-api-version
required
string
 Default:  1.1-rev1
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Responses 
200
OK


401
Unauthorized. The authorization header has been expected but not found (or found but is expired).


403
Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.


404
Not found. No object was found with the path parameter specified in the request.


500
Internal server error. The request has been received but could not be completed because of an internal error at the server side.


get/api/v1/restore/instantRecovery/vSphere/fcd
Request samples 
Response samples 
application/json
{
  • "data": [
    ],
  • "pagination": {
    }
}
Start Instant FCD Recovery
The HTTP POST request to the /api/v1/restore/instantRecovery/vSphere/fcd path allows you to start Instant FCD Recovery from the restore point to the destination cluster.
Specify the destination cluster in the destinationCluster parameter of the request body as a model of the VMware vSphere object. For details on how to get the cluster model, see Get Inventory Objects.
Available to: Veeam Backup Administrator, Veeam Restore Operator.


SecurityBearer 
Request 
header Parameters
x-api-version
required
string
 Default:  1.1-rev1
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Request Body schema: application/json
required
restorePointId
required
string <uuid> 
ID of the restore point.


 
required
object (InventoryObjectModel) 
Inventory object properties.


 
required
Array of objects (VmwareFcdInstantRecoveryDiskSpec) 
Array of disks for restore.


 
object (VmwareFcdWriteCacheSpec) 
Write cache for recovered disks.


 
Responses 
201
Instant FCD Recovery has been started. To check the progress, track the session state.


400
Bad request. This error is related to POST/PUT requests. The request body is malformed, incomplete or otherwise invalid.


401
Unauthorized. The authorization header has been expected but not found (or found but is expired).


403
Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.


404
Not found. No object was found with the path parameter specified in the request.


500
Internal server error. The request has been received but could not be completed because of an internal error at the server side.


post/api/v1/restore/instantRecovery/vSphere/fcd
Request samples 
application/json
{
  • "restorePointId": "8c843d10-6d0f-4abe-b898-e1ba18b94f68",
  • "destinationCluster": {
    },
  • "disksMapping": [
    ],
  • "writeCache": {
    }
}
Response samples 
application/json
{
  • "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  • "name": "string",
  • "jobId": "9d222c6d-893e-4e79-8201-3c9ca16a0f39",
  • "sessionType": "Infrastructure",
  • "creationTime": "2019-08-24T14:15:22Z",
  • "endTime": "2019-08-24T14:15:22Z",
  • "state": "Stopped",
  • "progressPercent": 0,
  • "result": {
    },
  • "resourceId": "026d60bb-63a8-407e-bf67-01dcfc6022e6",
  • "resourceReference": "string",
  • "parentSessionId": "b1d7834e-fe2f-4cad-b0e5-ff5c5615f344",
  • "usn": 0
}
Get FCD Mount
The HTTP GET request to the /api/v1/restore/instantRecovery/vSphere/fcd/{mountId} path allows you to get information about the mounted vPower NFS datastore, such as restore session ID, mount state, instant FCD recovery settings and disks that will be recovered.
Available to: Veeam Backup Administrator, Veeam Restore Operator.


SecurityBearer 
Request 
path Parameters
mountId
required
string <uuid> 
Mount ID.


 
header Parameters
x-api-version
required
string
 Default:  1.1-rev1
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Responses 
200
OK


401
Unauthorized. The authorization header has been expected but not found (or found but is expired).


403
Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.


404
Not found. No object was found with the path parameter specified in the request.


500
Internal server error. The request has been received but could not be completed because of an internal error at the server side.


get/api/v1/restore/instantRecovery/vSphere/fcd/{mountId}
Request samples 
Response samples 
application/json
{
  • "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  • "sessionId": "f6567dd8-e069-418e-8893-7d22fcf12459",
  • "state": "Failed",
  • "spec": {
    },
  • "errorMessage": "string",
  • "mountedDisks": [
    ]
}
Stop FCD Publishing
The HTTP POST request to the /api/v1/restore/instantRecovery/vSphere/fcd/{mountId}/dismount path allows you to stop publishing the recovered FCDs and remove the disks from the datastore.
Available to: Veeam Backup Administrator, Veeam Restore Operator.


SecurityBearer 
Request 
path Parameters
mountId
required
string <uuid> 
Mount ID.


 
header Parameters
x-api-version
required
string
 Default:  1.1-rev1
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Responses 
200
The disks have been unmounted. To check the progress, track the session state.


400
Bad request. This error is related to POST/PUT requests. The request body is malformed, incomplete or otherwise invalid.


401
Unauthorized. The authorization header has been expected but not found (or found but is expired).


403
Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.


404
Not found. No object was found with the path parameter specified in the request.


500
Internal server error. The request has been received but could not be completed because of an internal error at the server side.


post/api/v1/restore/instantRecovery/vSphere/fcd/{mountId}/dismount
Request samples 
Response samples 
application/json
{
  • "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  • "name": "string",
  • "jobId": "9d222c6d-893e-4e79-8201-3c9ca16a0f39",
  • "sessionType": "Infrastructure",
  • "creationTime": "2019-08-24T14:15:22Z",
  • "endTime": "2019-08-24T14:15:22Z",
  • "state": "Stopped",
  • "progressPercent": 0,
  • "result": {
    },
  • "resourceId": "026d60bb-63a8-407e-bf67-01dcfc6022e6",
  • "resourceReference": "string",
  • "parentSessionId": "b1d7834e-fe2f-4cad-b0e5-ff5c5615f344",
  • "usn": 0
}
Start FCD Migration
The HTTP POST request to the /api/v1/restore/instantRecovery/vSphere/fcd/{mountId}/migrate path allows you to start migration of FCDs from the specified mount.
In the request body specify FCD migration configuration:
     
  • Disks for migration
    •  
  • Target datastore
    •  
  • Storage policy that will be applied to the migrated disks
 For details on how to get models of the datastore and storage policy, see Get Inventory Objects.
Available to: Veeam Backup Administrator, Veeam Restore Operator.


SecurityBearer 
Request 
path Parameters
mountId
required
string <uuid> 
Mount ID.


 
header Parameters
x-api-version
required
string
 Default:  1.1-rev1
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Request Body schema: application/json
required
required
object (InventoryObjectModel) 
Inventory object properties.


 
mountedDiskNames
Array of strings
Array of disks that will be migrated to the targetDatastore associated with the storagePolicy.


 
object (InventoryObjectModel) 
Inventory object properties.


 
Responses 
200
FCD Migration has been started. To check the progress, track the session state.


400
Bad request. This error is related to POST/PUT requests. The request body is malformed, incomplete or otherwise invalid.


401
Unauthorized. The authorization header has been expected but not found (or found but is expired).


403
Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.


404
Not found. No object was found with the path parameter specified in the request.


500
Internal server error. The request has been received but could not be completed because of an internal error at the server side.


post/api/v1/restore/instantRecovery/vSphere/fcd/{mountId}/migrate
Request samples 
application/json
{
  • "mountedDiskNames": [
    ],
  • "targetDatastore": {
    },
  • "storagePolicy": {
    }
}
Response samples 
application/json
{
  • "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  • "name": "string",
  • "jobId": "9d222c6d-893e-4e79-8201-3c9ca16a0f39",
  • "sessionType": "Infrastructure",
  • "creationTime": "2019-08-24T14:15:22Z",
  • "endTime": "2019-08-24T14:15:22Z",
  • "state": "Stopped",
  • "progressPercent": 0,
  • "result": {
    },
  • "resourceId": "026d60bb-63a8-407e-bf67-01dcfc6022e6",
  • "resourceReference": "string",
  • "parentSessionId": "b1d7834e-fe2f-4cad-b0e5-ff5c5615f344",
  • "usn": 0
}
Start File Restore
The HTTP POST request to the /api/v1/restore/flr path allows you to start file restore from a backup or replica of a Microsoft Windows or Linux machine. The operation starts a file restore session and mounts the machine file system to a mount point.
Available to: Veeam Backup Administrator, Veeam Restore Operator.


SecurityBearer 
Request 
header Parameters
x-api-version
required
string
 Default:  1.1-rev1
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Request Body schema: application/json
required
restorePointId
required
string <uuid> 
ID of the restore point that you want to restore files from.


 
type
required
string (EFlrType) 
Restore type.


 
required
object (FlrAutoUnmountModel) 
Settings for automatic unmount of the file system.


 
reason
string
Reason for restoring files.


 
credentialsId
string <uuid> 
ID of the credentials record used to connect to the source machine. The credentials will be used to compare files from backup and the source machine.


 
Responses 
201
File system has been mounted.


400
Bad request. This error is related to POST/PUT requests. The request body is malformed, incomplete or otherwise invalid.


401
Unauthorized. The authorization header has been expected but not found (or found but is expired).


403
Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.


500
Internal server error. The request has been received but could not be completed because of an internal error at the server side.


post/api/v1/restore/flr
Request samples 
application/json
{
  • "restorePointId": "5777a78d-62f6-40a3-a7e3-8b56a56e58c0",
  • "type": "Linux",
  • "autoUnmount": {
    },
  • "reason": "File restore",
  • "helperHost": {
    }
}
Response samples 
application/json
{
  • "type": "Linux",
  • "sessionId": "1dc723e8-12a0-4480-bc34-6cb117d3d4a1",
  • "properties": {
    },
  • "sourceProperties": {
    }
}
Unmount File System
The HTTP POST request to the /api/v1/restore/flr/{sessionId}/unmount path allows you to unmount the file system from a mount point and stop a file restore session that has the specified sessionId.
Available to: Veeam Backup Administrator, Veeam Restore Operator.


SecurityBearer 
Request 
path Parameters
sessionId
required
string <uuid> 
ID of the restore session.


 
header Parameters
x-api-version
required
string
 Default:  1.1-rev1
Version and revision of the client REST API. Must be in the following format: <version>-<revision>.


 
Responses 
201
Restore session has been stopped.


401
Unauthorized. The authorization header has been expected but not found (or found but is expired).


403
Forbidden. The user sending the request does not have adequate privileges to access one or more objects specified in the request.


404
Not found. No object was found with the path parameter specified in the request.


500
Internal server error. The request has been received but could not be completed because of an internal error at the server side.


post/api/v1/restore/flr/{sessionId}/unmount
Request samples 
Response samples 
application/json
{
  • "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  • "name": "string",
  • "jobId": "9d222c6d-893e-4e79-8201-3c9ca16a0f39",
  • "sessionType": "Infrastructure",
  • "creationTime": "2019-08-24T14:15:22Z",
  • "endTime": "2019-08-24T14:15:22Z",
  • "state": "Stopped",
  • "progressPercent": 0,
  • "result": {
    },
  • "resourceId": "026d60bb-63a8-407e-bf67-01dcfc6022e6",
  • "resourceReference": "string",
  • "parentSessionId": "b1d7834e-fe2f-4cad-b0e5-ff5c5615f344",
  • "usn": 0
}