When performing a restore of a thin-provisioned VMware virtual disk on an NFS data store using this proxy server, what transport mode will be used?

A Veeam proxy server is configured as follow. No modifications are allowed to the transport mode.

When performing a restore of a thin-provisioned VMware virtual disk on an NFS data store using this proxy server, what transport mode will be used?
A. Direct NFS access
B. Direct SAN access
C. Virtual appliance
D. Network

Download Printable PDF. VALID exam to help you PASS.

4 thoughts on “When performing a restore of a thin-provisioned VMware virtual disk on an NFS data store using this proxy server, what transport mode will be used?

  1. No modifications are allowed to the transport mode. Failover to Network mode is not enabled. Hence C.

  2. I think the answer is A provided the failover to network mode is enabled.

    https://helpcenter.veeam.com/docs/backup/vsphere/direct_nfs_access.html?ver=110

    The Direct NFS access is a recommended transport mode for VMs whose disks are located on NFS datastores.
    The Direct NFS access mode provides an alternative to the Network mode. When Veeam Backup & Replication processes VM data in the Network mode, it uses VMware VDDK to communicate with the ESXi host. This produces additional load on the ESXi host.

    3
    5
  3. I think C is correct. Thin-provisioned disks affects only in Direct Storage Access mode.

    Veeam Backup & Replication writes VM data to the target datastore in the Direct SAN access transport mode only if disks of a VM replica are thick-provisioned. If disks are thin-provisioned, Veeam Backup & Replication will write VM data in the Network or Virtual appliance mode

    https://helpcenter.veeam.com/docs/backup/vsphere/direct_san_access.html?zoom_highlight=thin-provisioned&ver=110

    13
  4. Is the “Failover to network mode if primary mode fails or is unavailable” option ticket in the screenshot?

    3
    2

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.