https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxODk1IiwiaGFzaCI6IjUyYzA3NjkzLTZjNjctNDYzNi05Y2Y1LWRmODNkNTIzMzExNyJ9
1-800-691-1991 | 9am - 8pm ET
EN

Direct-SAN Transport mode – Requirements and Troubleshooting

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.
KB ID:
1895
Product:
Veeam Backup & Replication
Version:
6.x, 7.x, 8.x, 9.x
Published:
2014-06-11
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 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.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later