Represents a mount point resource having the specified ID.

Mount points are specific Veeam Backup Enterprise Manager objects that provide access to VM replica guest OS files. The /vmReplicaPoints/{ID}/mounts/{ID} resource becomes available only after the client performs file-level restore for the VM by sending the POST HTTP request to the /vmReplicaPoints/{ID}/mounts resource. To learn more, see (POST) /vmReplicaPoints/{ID}/mounts.

During the restore process, Veeam Backup & Replication mounts VM disks to the Veeam backup server. As a result, the VM guest OS files can be accessed through the mount point by the following path: C:\VeeamFLR\<vm-name>. The client can browse the VM replica guest file system, get the necessary files and folders and restore them.

The /vmReplicaPoints/{ID}/mounts/{ID} resource is available only within the currently existing logon session. After the logon session expires, all created mount points become inaccessible.

Resource URL


Related Resources



The following methods are supported for the /vmReplicaPoints/{ID}/mounts/{ID} resource:

Resource Representation

The /vmReplicaPoints/{ID}/mounts/{ID} resource has a resource representation of the following type:

<VmReplicaPointMount xmlns="http://www.veeam.com/ent/v1.0" Type="VmReplicaPointMount" Href="https://localhost:9398/api/vmReplicaPoints/623cbbec-c8ff-4cf4-96be-d433f3b775c7/mounts/1">
   <Link Rel="Delete" Type="VmReplicaPointMount" Href="https://localhost:9398/api/vmReplicaPoints/623cbbec-c8ff-4cf4-96be-d433f3b775c7/mounts/1" />
   <DirectoryEntry Type="DirectoryEntry" Href="https://localhost:9398/api/vmReplicaPoints/623cbbec-c8ff-4cf4-96be-d433f3b775c7/mounts/1/Volume$0:">
   <DirectoryEntry Type="DirectoryEntry" Href="https://localhost:9398/api/vmReplicaPoints/623cbbec-c8ff-4cf4-96be-d433f3b775c7/mounts/1/C:">
   <DirectoryEntry Type="DirectoryEntry" Href="https://localhost:9398/api/vmReplicaPoints/623cbbec-c8ff-4cf4-96be-d433f3b775c7/mounts/1/E:">


I want to report a typo

There is a misspelling right here:


I want to let the Veeam Documentation Team know about that.