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

Veeam Backup & Replication
Last Modified:


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

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.


Rate the quality of this KB article: 
4.7 out of 5 based on 3 ratings

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: