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

Veeam doesn't clean up temporary datastore in vSphere after restore from NetApp storage snapshot


After completing one of the restore options available for NetApp storage snapshot, you may notice that the temporary datastore under the name "snap-<id>-<original datastore name>" is still mounted on the ESXi hosts with inactive status. See the screenshot below for an example:
User-added image

After a manual rescan of the storage adapter on each host, the temporary datastore is removed.


This is a known issue. Veeam assigns a clone of the LUN to the entire initiator group instead of a dedicated host selected in the Restore wizard. However, during unmount Veeam requests a rescan of the storage adapter only on the host which was selected in the Restore wizard.


You may create dedicated initiator groups for each ESXi host and explicitly add the initiator name of the ESXi host. Make sure to define the same OS type for those groups as the main group, otherwise you won't be able to add an initiator name (the group will be created empty).


User-added image

User-added image

More information

This issue will be addressed in one of the future updates for v8
Veeam Backup & Replication
Last Modified:
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.

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.