I am trying to add a NFS Repo to B&R and having some issues. Here is a summary:
B&R v12.2
Storage device is a UGREEN NAS with NFS enabled
Shared folder on the NAS is called Backup, but apparently the UGREEN must referenced by Volume1\SharedFolder
I installed the NFS client on the V&R machine for testing and can mount/map the shared drive via command line. That looks like this:
mount "\\<NAS-IP>\Volume1\Backup" Z:
That successfully maps the drive and I can interact with it.
Now... when I try to a NFS repo, I enter the Shared Folder as:
<NAS-IP>:/Volume1/Backup
However, Veeam won't connect and I get an error "Failed to connect to the NFS shared folder"
The only thing I can think is that Veeam doesn't like the shared folder having 2 layers - Volume1 and Backup. Otherwise, I am not sure why it won't connect.
Any help is appreciated.
-
- Service Provider
- Posts: 108
- Liked: 8 times
- Joined: Jan 19, 2022 4:48 pm
- Contact:
-
- Veeam Software
- Posts: 2838
- Liked: 650 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Adding NFS Repo
Hi NorthGuard,
Sorry to hear about the challenges; do you have a Support Case opened for this issue yet? We will not be able to troubleshoot this over the forums, so please open a Support Case and let Support review the behavior. Be sure to include logs for Support to review (reproduce the issue, note the date/time of the reproduce, and when exporting logs, use the 3rd radio button and select the Veeam server itself to export logs from)
Please share your case number here once created.
As for this:
> The only thing I can think is that Veeam doesn't like the shared folder having 2 layers - Volume1 and Backup. Otherwise, I am not sure why it won't connect.
I'm not aware of any limitations or issues with this -- there may be a requirement to set at least read permissions on the parent folder (Volume1) as well, but it's best to review with Support.
Sorry to hear about the challenges; do you have a Support Case opened for this issue yet? We will not be able to troubleshoot this over the forums, so please open a Support Case and let Support review the behavior. Be sure to include logs for Support to review (reproduce the issue, note the date/time of the reproduce, and when exporting logs, use the 3rd radio button and select the Veeam server itself to export logs from)
Please share your case number here once created.
As for this:
> The only thing I can think is that Veeam doesn't like the shared folder having 2 layers - Volume1 and Backup. Otherwise, I am not sure why it won't connect.
I'm not aware of any limitations or issues with this -- there may be a requirement to set at least read permissions on the parent folder (Volume1) as well, but it's best to review with Support.
David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: Semrush [Bot] and 22 guests