anktarius Posted February 17 Share Posted February 17 (edited) Hi folks, I am a new user of your product, i was looking for a backup solution and this one seems to very interesting. I am testing with : - NFS mount - CIFS mount - Proxmox server - ESXI 7/8 servers I am able to add the CIFS mount without issue but am not able to add the NFS mount on Nakivo VM. This mount is working on the proxmox server using NFS V4, also working on my ESXI using NFS V4, i did a new NFS share using NFS V3, this is also working on Proxmox/ESXI from the same IP subnet, etc. (no Firewall etc.) NFS Mount configured in the UI is ; 192.168.2.13:/volume1/nakivo (everything else is by default) Here is the GUI error message : Quote The connection to the specified location (192.168.2.13:/volume1/nakivo) is denied due to the following reasons: - The provided account permissions are insufficient. - The traffic quota for data usage is reached on the storage side. - The selected bucket(s) is unavailable due to applied object or disabled for administrative purposes on storage side. Please check the above reasons and try again. While looking in the logs in ssh (from your docs) ; Feb 17 19:19:47 va kernel: [ 114.966395] FS-Cache: Netfs 'nfs' registered for caching Feb 17 19:19:47 va kernel: [ 114.967732] nfs: Deprecated parameter 'intr' Feb 17 19:19:47 va kernel: [ 115.062931] NFS: Registering the id_resolver key type Feb 17 19:19:47 va kernel: [ 115.062939] Key type id_resolver registered Feb 17 19:19:47 va kernel: [ 115.062940] Key type id_legacy registered Feb 17 19:19:47 va kernel: [ 115.077351] nfs: Deprecated parameter 'intr' Feb 17 19:20:02 va systemd[1]: opt-nakivo-transporter-bh\x2dmount-effea7a1\x2d4377\x2d42a4\x2db1f7\x2d4ab34c2221e4.mount: Deactivated successfully. Do you have an idea about what is wrong on the VM ? Thank you. Edited February 17 by anktarius 1 Quote Link to comment Share on other sites More sharing options...
anktarius Posted February 17 Author Share Posted February 17 It seems that i can 't edit again my post. Update : I have mounted the NFS folder directly using the CLI on the Nakivo VM to validate ; nkvuser@va:~$ sudo mount 192.168.2.13:/volume1/nakivo /mnt/test/ nkvuser@va:~$ sudo ls /mnt/test/ NakivoBackup nkvuser@va:~$ sudo touch /mnt/test/MNT_CLI nkvuser@va:~$ sudo ls /mnt/test/ MNT_CLI NakivoBackup I don't understand why it is not working from the WEBUI. By the way, it seems that the Nakivo folder is created while trying to create the repository. 1 Quote Link to comment Share on other sites More sharing options...
Official Moderator Posted February 17 Share Posted February 17 1 hour ago, anktarius said: It seems that i can 't edit again my post. Update : I have mounted the NFS folder directly using the CLI on the Nakivo VM to validate ; nkvuser@va:~$ sudo mount 192.168.2.13:/volume1/nakivo /mnt/test/ nkvuser@va:~$ sudo ls /mnt/test/ NakivoBackup nkvuser@va:~$ sudo touch /mnt/test/MNT_CLI nkvuser@va:~$ sudo ls /mnt/test/ MNT_CLI NakivoBackup I don't understand why it is not working from the WEBUI. By the way, it seems that the Nakivo folder is created while trying to create the repository. @anktarius Hello, your request was received and forwarded to our Level 2 Support Team. We will follow up with you shortly. Thank you for choosing NAKIVO Backup & Replication as your data protection solution. Quote Link to comment Share on other sites More sharing options...
anktarius Posted February 17 Author Share Posted February 17 @Official Moderator ; Thanks for your answer. Quote Link to comment Share on other sites More sharing options...
Official Moderator Posted February 18 Share Posted February 18 16 hours ago, anktarius said: @Official Moderator ; Thanks for your answer. @anktariusPlease let us know if we can arrange a remote session with the customer and our Level 2 Support Team to investigate the issue encountered online. We use the GoToMeeting application. Please let us know the (date and) time that is most convenient. We look forward to hearing from you. Quote Link to comment Share on other sites More sharing options...
anktarius Posted February 19 Author Share Posted February 19 (edited) 19 hours ago, Official Moderator said: @anktariusPlease let us know if we can arrange a remote session with the customer and our Level 2 Support Team to investigate the issue encountered online. We use the GoToMeeting application. Please let us know the (date and) time that is most convenient. We look forward to hearing from you. Hi , Sure no issue with that. Let me know if the want to get specific outputs/debug data before the meeting. It could be almost everyday as it will not take too much time i think. Can we go in MP/Mail for more details about the remote session ? Thank you Edited February 19 by anktarius Quote Link to comment Share on other sites More sharing options...
Official Moderator Posted February 19 Share Posted February 19 5 hours ago, anktarius said: Hi , Sure no issue with that. Let me know if the want to get specific outputs/debug data before the meeting. It could be almost everyday as it will not take too much time i think. Can we go in MP/Mail for more details about the remote session ? Thank you @anktarius Please, email us with a ticket number #186356: support@nakivo.com Quote Link to comment Share on other sites More sharing options...
Giovanni Panozzo Posted July 25 Share Posted July 25 I had the same problem: when mounting a NFS share from the Nakivo GUI, only the NakivoBackup directory was created, and then the GUI mount procedure failed with the same error. I solved it removing maproot/root_squash options on the NFS server. In my case it was FreeBSD 13 /etc/exports Initial /etc/exports which prevented nakivo to set permission on files: /vol1/nakivo1 -maproot=nakivouser -network=192.168.98.16/28 changed to the following working one /vol1/nakivo1 -maproot=root -network=192.168.98.16/28 1 Quote Link to comment Share on other sites More sharing options...
Official Moderator Posted July 25 Share Posted July 25 1 hour ago, Giovanni Panozzo said: I had the same problem: when mounting a NFS share from the Nakivo GUI, only the NakivoBackup directory was created, and then the GUI mount procedure failed with the same error. I solved it removing maproot/root_squash options on the NFS server. In my case it was FreeBSD 13 /etc/exports Initial /etc/exports which prevented nakivo to set permission on files: /vol1/nakivo1 -maproot=nakivouser -network=192.168.98.16/28 changed to the following working one /vol1/nakivo1 -maproot=root -network=192.168.98.16/28 @Giovanni Panozzo On behalf of the community, I want to extend my gratitude to you for your valuable contributions and for making our Forum a better place with your insightful posts. We genuinely appreciate your active involvement and look forward to more insightful discussions and solutions from you in the future. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.