Why doesn't Power NFS mount get disconnected?

[electricd7]

Hello,

I am fairly new to Veeam, but tried to search first and came up empty. I recently did an Instant Recovery of a VM as a test in our environment. This went just fine, and once the VM was up and running via the Power NFS mount, I did a storage vMotion to production storage. I then went into the Veeam server and dismounted the VM listed in Instant Recovery. This seemed to go without issue as well except it gave me a warning about the VM being migrated. Once it was done, the VM disappeared from Veeam, and continued to run in vSphere as expected. My question is why was the VeeamBackup NFS mount left connected to the host? Is this expected behavior? I would have expected as part of the cleanup process that this mount would have gotten disconnected from the host. Is there a way to force this so that my other users don't do something silly like try and svmotion a machine to this mount? Thanks in advance!

ED7

[Gostev]

Hello, this is normal. Mounting datastore from scratch is not a quick process at all, and really affect how that "instant" VM recovery is, so we just leave it mounted. You can use vCenter permissions to restrict users from doing silly stuff they are not supposed to. Thanks!

[electricd7]

Ok thanks for the quick response. Would there be any adverse affect on Veeam if as part of our nightly VMware script we dismounted that datastore from each host so long as it wasn't in use (ie, if empty dismount)? It would just get re-mounted the next time we do an instant recovery, right?

[Gostev]

Yep. No problems at all.

[JoshF]

How do you guys deal with Ghost NFS devices that need the ESXi management services restarted in order to remove them?