A customer has a physical proxy configured for Direct Storage Access without failover to network mode. The backup fails. What could be the issue?
A. The disks being processed are IDE and/or SATA
B. The datastores are properly zoned and exposed to the proxy server but in read-only mode
C. The storage is not added into the storage infrastructure, inside the backup and replication console
D. Write access has not been enabled on the SAN
E. One or more of the VM disk(s) are on Wols
|
Download Printable PDF. VALID exam to help you PASS. |
 |
E. One or more of the VM disk(s) are on Wols
Limitations for the Direct SAN Access Mode
The Direct SAN access transport mode can be used to restore only thick VM disks.
You cannot use the Direct SAN access mode in the following cases:
For VMs residing on vSAN. You can use Virtual appliance and Network transport modes to process such VMs. For details on vSAN restrictions, see VDDK 5.5 Release Notes.
If at least one VM disk is located on a VVol.
For Veeam Cloud Connect Replication because in this scenario Veeam Backup & Replication always creates VM replicas with thin disks.
For incremental restore due to VMware limitations. Either disable CBT for VM virtual disks for the duration of the restore process or select another transport mode for incremental restore.
For backing up VM templates.
https://helpcenter.veeam.com/archive/backup/100/vsphere/direct_san_access.html