Operational Defect Database
BugZero found this defect 3631 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb1895
Direct-SAN Transport mode – Requirements and Troubleshooting
Last update date:
10/27/2021
Affected products:
Veeam Backup & Replication
Affected releases:
8.0
Fixed releases:
No fixed releases provided.
Description:
Challenge
Direct-SAN transport fails or configuration assistance is needed.
Solution
You must disable automount in diskpart on the proxy that the volumes are presented to, to ensure that VMFS volumes are not modified. (http://kb.vmware.com/kb/2002227) Requirements: Only VMFS type datastores are supported. The volume for each datastore containing a VM that is intended to be backed up over Direct-SAN must be presented to the Backup Proxy. The volume must appear in Disk Management within the Backup Proxy Server. Known Issues: As the number of volumes presented to the Backup Proxy increases the delay for starting of the VM task may increase. This is due to the job scanning each volume. This can be mitigated by manually specifying in the Backup Proxy setting which datastores are connected. Under certain circumstances volumes may not be automatically discovered and necessitate manually specifying which datastores are connected in the Backup Proxy settings.
More Information
Veeam Backup & Replication User Guide - Data Backup in Direct SAN Access Mode How to setup Direct-SAN Access vee.am/kb1446 Direct SAN access tips for iSCSI VMFS volumes and backup proxies
