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:


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).

Before:



After:

This issue will be addressed in one of the future updates for v8