Skip to main content
  • EN

We have several backup and replication jobs running on Veeam Backup and Replication build 10.0.1.4524 and have started receiving errors with all of the jobs failing. These error messages vary from “ Error: The network path was not found. Agent failed to process method {FileSystem.Exists}.” to

“Could not perform threshold check for backup location “\\..." due to space info retrievement fail!
Error: Failed to call RPC function 'FcCreateDir': The network path was not found. Cannot create folder. Folder path: e\\..].
Job has failed. See logs for details.”

When troubleshooting, we receive a warning while rescanning the repository stating that it is missing. We are able to SSH into the NAS backup repository and I am able to sign into the NAS and see all of the permissions and correct network paths. Is there anything more we can do to fix this issue or somewhere specific to look?

You say, you can SSH in to your NAS, but the error message looks like a SMB path.
Are you able to reach the share on which your repository resides on the NAS via SMB like configured in Veeam?

 

And your VBR version is very old, you should consider to update to version 12 or at least version 11.

Also check the account used to connect to the repo within Veeam - did the password possibly change and needs updating?  Also, like Joe mentioned test the SMB path from another system and definitely upgrade Veeam.  😋

Hi @BradShaver 

are you able to SSH into NAS from Veeam B&R Server and from Veeam proxy to? 

have you tried using the DNS/Host name and the IP address?

 

@JMeixner Running Test-Path comes back false for the network path, but that could come from missing credentials since the NAS is not part of the domain. However, nothing was changed on either end outside of the error we ran into previously that I mention below. Regardless of the read/write error that we ran into the network paths and credentials all remained the same.

@Chris.Childerhose That was the second test we did in troubleshooting, we double checked the credentials and made new ones using the exact login used to sign into the NAS moments before.

@Andanet We can SSH from the other servers, including the B&R server and the proxy servers.

The issue seems to have started when we ran into a read/write problem with the storage pool on the NAS but that has since been fixed after running a check file system option. There is also plenty of storage space remaining in the storage pool. 

OK, as we don’t know the complete path.

  • DNS resolution is Ok?
  • Any changes to firewalls? Perhaps some ports were blocked?
  • Or just the standard - did you try to restart the NAS and the VBR Server?

@JMeixner No change in firewalls, both servers have been restarted, and DNS resolution is ok. The Gateway and other IPv4 settings are all the same as before the errors started and match what they should be configured to. SMB is also enabled and set to the highest version available. I’ve also double checked the security settings and see that the connections are allowed on the NAS. 

Do you have another server you could test moving to v12 or at least v11?  Just wondering if either version might “fix” the issue.  Other than that, a support case would be next.

If you can access to the NAS issue is inside It. Can you try to create another shared folder and add it as a new repository?

Thank you all for the help in troubleshooting, after confirming that I could add the same exact path as a NFS repository to the Veeam installation we discovered that after a firmware update the SMB version was lowered on the NAS appliance, after raising it to the required version we were able to reconnection and rescan the repository. Looking forward to not receiving any job failures tonight.

Comment


Terms & Conditions