+5Hello everyone!
I performed an Instant Restore, but most of the time, I need to manually unmount the NFS datastore. However, sometimes Veeam does not automatically remove these datastores after the jobs have finished running, so I have to remove them manually.
Is there anything I can do to fix this?
Best answer by regnor
📯And here we are with the latest release of VBR: 12.3.1139
- Automatically disconnect vPower NFS datastores after Instant VM Recovery sessions are completed, reduce alarms or misleading capacity planning calculations caused by disconnected vPower NFS datastores. To configure, create the following registry value on the backup server:
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: vPowerNFSUnmountDatastore
Value Type: DWORD (32-bit) Value
Value Data: 1
+20Unfortunately no. This behavior has been happening for several years (since IR has been around). Some will suggest to just leave the Datastore to make IR restores for the next restore go a lil quicker. Personally, I don’t like seeing “rogue” Datastores in my vSphere environment so, like you, I manually remove them.
Unless Veeam has come up with a process like Snapshot Hunter, to remove them, which I’m sure they haven’t, there’s no fix. You can ping Veeam support though to verify.
Best.
+3Not any way I’m aware of to have it perform a cleanup. Our team just moves the datastore into a folder called “_DONOTUSE”, and that way it’s a little more out of sight.
+5Unfortunately no. This behavior has been happening for several years (since IR has been around). Some will suggest to just leave the Datastore to make IR restores for the next restore go a lil quicker. Personally, I don’t like seeing “rogue” Datastores in my vSphere environment so, like you, I manually remove them.
Unless Veeam has come up with a process like Snapshot Hunter, to remove them, which I’m sure they haven’t, there’s no fix. You can ping Veeam support though to verify.
Best.
Yeah, I dont like too to see that datastoes. However, I’ll check at Veeam support to very. Thanks !!
+5Not any way I’m aware of to have it perform a cleanup. Our team just moves the datastore into a folder called “_DONOTUSE”, and that way it’s a little more out of sight.
My fear is that someone might use the NFS datastore incorrectly. Here, I have many backups environments to manage, and this poses a significant risk.
+3Not any way I’m aware of to have it perform a cleanup. Our team just moves the datastore into a folder called “_DONOTUSE”, and that way it’s a little more out of sight.
My fear is that someone might use the NFS datastore incorrectly. Here, I have many backups environments to manage, and this poses a significant risk.
Doesn’t the datastore become inaccessible after unpublishing the Instant Recovery? And if the DS is sitting in a folder called “Do Not Use”, I hope someone might think twice about using it, perhaps ask some questions.
+5I have an NFS datastore running in my environment, with no active Instant Restore sessions, and I can create a VM there.
Renaming it might be useful—I’ll use that tip.
+3I have an NFS datastore running in my environment, with no active Instant Restore sessions, and I can create a VM there.
Renaming it might be useful—I’ll use that tip.
That is interesting/concerning. When you create a VM, does it it consume disk space in your Instant Recovery Write Cache folder?
I could see why this could be a risk of someone inadvertently creating a VM there, and it going down when the mount server gets rebooted.
+5I have an NFS datastore running in my environment, with no active Instant Restore sessions, and I can create a VM there.
Renaming it might be useful—I’ll use that tip.
That is interesting/concerning. When you create a VM, does it it consume disk space in your Instant Recovery Write Cache folder?
I could see why this could be a risk of someone inadvertently creating a VM there, and it going down when the mount server gets rebooted.
Yes, this consumes space from both the mount server and the write cache folder.
This could cause a lot of problems, so I’d like to know if there’s anything I can do to prevent it.
+14By design the Veeam vPower NFS datastore stays connected after an Instant Recovery. The reason for this has been that future restores will be faster as the connection is already existing. It will show as disconnected as soon as you restart your mount server.
Until now there is no solutions besides either ignoring the datastore or manually unmounting it. So there’s nothing Veeam Support can do about this. But there’s a change planned for a future release and as soon as it’s available I’ll update this topic.
+9Just an idea, you could change permissions within vSphere to this mount, that only your Veeam Service account can work with it, for other users/accounts use read/only.
Also, there’s a script from Niels Engelen out there, where you can dismount it https://github.com/nielsengelen/veeam-powershell.
+20That would be a welcomed feature Max. Looking fwd to seeing that come to fruition!
+3Glad to see a new feature on the horizon for this. Even something as simple as a checkbox on the the repository settings like "Automatically unmount vPower NFS share when not in use" or something to that effect.
+5Just an idea, you could change permissions within vSphere to this mount, that only your Veeam Service account can work with it, for other users/accounts use read/only.
Also, there’s a script from Niels Engelen out there, where you can dismount it https://github.com/nielsengelen/veeam-powershell.
This feature would be really great! I appreciate the ideas and information. In the meantime, I'll keep removing it manually while applying all the suggestions.
+14📯And here we are with the latest release of VBR: 12.3.1139
- Automatically disconnect vPower NFS datastores after Instant VM Recovery sessions are completed, reduce alarms or misleading capacity planning calculations caused by disconnected vPower NFS datastores. To configure, create the following registry value on the backup server:
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: vPowerNFSUnmountDatastore
Value Type: DWORD (32-bit) Value
Value Data: 1
+3That’s awesome! Is that feature addition due to this thread? If so that is some great turnaround time.
+5📯And here we are with the latest release of VBR: 12.3.1139
- Automatically disconnect vPower NFS datastores after Instant VM Recovery sessions are completed, reduce alarms or misleading capacity planning calculations caused by disconnected vPower NFS datastores. To configure, create the following registry value on the backup server:
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: vPowerNFSUnmountDatastore
Value Type: DWORD (32-bit) Value
Value Data: 1
Really happy to know that! I'll upgrade my environment today and won't be afraid of performing an NFS restore anymore.😁
+5That’s awesome! Is that feature addition due to this thread? If so that is some great turnaround time.
If it was because of this post, it just reinforces how important the community is. I'm happy to be a part of it.
Thanks, everyone!
+14
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
