1-800-691-1991 | 9am - 8pm ET

How to setup SAN access for use with Veeam Backup & Replication.


This Knowledge Base provides instruction on how to setup SAN access for use with Veeam Backup & Replication.

The Direct SAN access transport mode is recommended for VMs whose disks are located on shared VMFS SAN LUNs that are connected to ESXi hosts over FC, FCoE, iSCSI, and on shared SAS storage.

In the Direct SAN access transport mode, Veeam Backup & Replication leverages VMware VADP to transport VM data directly from and to FC, FCoE and iSCSI storage over the SAN. VM data travels over the SAN, bypassing ESXi hosts and the LAN. The Direct SAN access transport method provides the fastest data transfer speed and produces no load on the production network.


Preventing Data Loss

Once a VMFS volume is presented to the Veeam VMware Backup Proxy it should always remain in an offline state and never be initialized. If by user action the volumes are ever initialized production data will be lost as the volume's partition table will be changed to GPT or MBR.

Veeam Backup & Replication prevents the Windows OS from initializing the volume automatically by changing the SAN Policy to "Offline Shared" when a server is added as a VMware Backup Proxy.

If a single server is used as both a VMware Backup Proxy using Direct SAN transport mode, and a Veeam Repository using volumes presented via iSCSI and/or FC, care must be taken when managing disks.

The instructions below describe how to setup SAN access for use with Veeam Backup & Replication.

  1. Confirm the Windows Server to which the volumes will be presented is already added as a Proxy within Veeam Backup & Replication.
  2. Connect the storage using iSCSI or FC such that the volumes appear in Disk Management.
    This step may require adjusting setting for FC zoning and iSCSI whitelisting.
    It is advisable that prior to connecting the FC cable one ensure their HBA drivers are up to date.
  3. Once connected, VMFS LUNs should appear in Windows Disk Management snap-in. They should be non-initialized without drive letters as Windows is not compatible with the VMware File System. The volume may appear as having an Offline state and should be left that way.

For more information please read the blog post on our Website:

The VMFS volume when presented to the Proxy should appear offline and never be manually initialized.

More information

The SAN Policy of a Windows OS can be checked using the DISKPART, with the command SAN.
KB ID: 1446
Product: Veeam Backup & Replication 11, Veeam Backup & Replication 10, Veeam Backup & Replication 9.5, Veeam Backup & Replication 9.0, Veeam Backup & Replication 8.0, Veeam Backup & Replication 7.0, Veeam Backup & Replication 6.5, Veeam Backup & Replication 6.1
Published: 2011-12-14
Last Modified: 2021-03-08
Languages: FR
Please rate how helpful this article was to you:
4.8 out of 5 based on 3 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.