Hey guys,
Are there any internal components in veeam software for NAS repository?
I recently faced an error in customer environment where the backup copy job resulted in an error saying “Can’t call Remote Procedure Call for NfsIsExist “
Solved
Veeam-NFS
Best answer by MicoolPaul
Hi,
Youve got errors here that can be grouped up, though you’ve only got part of the details posted here so I can’t give you exact details for some of this:
From the report: Connecting to IP address 10.15.99.162:6160 failed. This is the port used by the Veeam installer service, indicating connection issues deploying components, I’d need to see more detail on the surrounding logs to confirm what’s being deployed at that point in time. But if you can confirm what roles are deployed to this server, that would help.
From the Svr.VeeamInstaller.Log:
It’s claiming a file is missing, I can’t see the full path to know what this is, but it could be Veeam’s installer service attempting to copy a file to run, being unable to copy and then failing to execute the file as a result. Check that this path is valid and the account credentials being used for this server have permissions to access the resource.
From Svc.VeeamInstallerDLL.log:
Error code 10048 means a port conflict, you’ve already got something using the same port that it intends to use. It references NFS so I’d assume this is relating to another service using port 6161 which is the backup repository port, unless this server is also an NFS share in which case it could be port 111 or port 2049.
I suggest on this server getting an output of netstat when no backup jobs are running and look for these ports being in use.
I hope this helps!
+17You can configure a repository on a NFS share. It is perhaps not the most advisable solution, but it works.
Do you have some more information about the error? Some logfiles?
Jochen (Joe) Meixner | Veeam Vanguard 2024 | Veeam Legend 2021 - 2024 | Veeam Certified Architect (VMCA) | Twitter: @JoMeix | BlueSky: @jmeixner.bsky.social
1 person likes this
The repository was in unavailable state. So it showed can’t connect to target repository.
+17Sorry, with this little information it is hard to say anything about this. Could be a network or permission issue.
Did you open a support case with Veeam?
+21Anandu wrote:
The repository was in unavailable state. So it showed can’t connect to target repository.
That would do it and cause the error. Glad you figured it out.
Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
+23Hi
Check the following:
- Are you targeting the NFS share as an IP address or a DNS record? Are they correct and connectable from both VBR server and gateway server?
- Have you confirmed firewall communication is okay between VBR and gateway server? Have you then confirmed firewall okay between gateway server and NFS?
- Have you tried manually using an NFS client from the gateway server to confirm it works?
Michael Paul - Opinions are my own and do not necessarily reflect the opinion of Veeam | https://micoolpaul.com | Mastodon: @micoolpaul@masto.nu | Bluesky: @micoolpaul.com
Hi Guys,
I had the same problem with
1 person likes this
+23Tommy Armando wrote:
Hi Guys,
I had the same problem with
Without seeing any logs, it’s really hard to say.
I’ve seen randomness with NFS and case sensitivity on the server but case insensitivity on the client.
The logs should state why it was canceled
Michael Paul - Opinions are my own and do not necessarily reflect the opinion of Veeam | https://micoolpaul.com | Mastodon: @micoolpaul@masto.nu | Bluesky: @micoolpaul.com
MicoolPaul wrote:
Tommy Armando wrote:
Hi Guys,
I had the same problem with
Without seeing any logs, it’s really hard to say.
I’ve seen randomness with NFS and case sensitivity on the server but case insensitivity on the client.
The logs should state why it was canceled
Hii
From the report
Error: Failed to call RPC function 'NfsIsExist': The remote procedure call was cancelled. RPC function call failed. Function name: [DoRpcWithBinary]. Target machine: [10.15.99.162:6160].
From the Svc.VeeamInstaller.log
[22.07.2022 09:37:42.735] < 15848> dpl | ERR |Failed to execute DoRpcWithBinary. Command name: 'DoSerialRpc'.
[22.07.2022 09:37:42.735] < 15848> dpl | >> |The system cannot find the file specified.
[22.07.2022 09:37:42.735] < 15848> dpl | >> |Failed to open fs item \\?\C:\Users\Supri
[22.07.2022 09:37:42.735] < 15848> dpl | >> |--tr:Error code: 0x00000002
[22.07.2022 09:37:42.735] < 15848> dpl | >> |--tr:Failed to complete RPC request. Method: [FcGetItemInfo], In XML: []
[22.07.2022 09:37:42.735] < 15848> dpl | >> |--tr:Failed to invoke RPC request
[22.07.2022 09:37:42.735] < 15848> dpl | >> |--tr:Failed to call DoRpc. CmdName: [DoSerialRpc] inParam: [].
[22.07.2022 09:37:42.735] < 15848> dpl | >> |An exception was thrown from thread [15848].
From the Svc.VeeamInstallerDll.log
[21.07.2022 22:04:12.332] < 19036> nfs | ERR |[NFS41] connect failed with error: 10048
1 person likes this
+23Hi,
Youve got errors here that can be grouped up, though you’ve only got part of the details posted here so I can’t give you exact details for some of this:
From the report: Connecting to IP address 10.15.99.162:6160 failed. This is the port used by the Veeam installer service, indicating connection issues deploying components, I’d need to see more detail on the surrounding logs to confirm what’s being deployed at that point in time. But if you can confirm what roles are deployed to this server, that would help.
From the Svr.VeeamInstaller.Log:
It’s claiming a file is missing, I can’t see the full path to know what this is, but it could be Veeam’s installer service attempting to copy a file to run, being unable to copy and then failing to execute the file as a result. Check that this path is valid and the account credentials being used for this server have permissions to access the resource.
From Svc.VeeamInstallerDLL.log:
Error code 10048 means a port conflict, you’ve already got something using the same port that it intends to use. It references NFS so I’d assume this is relating to another service using port 6161 which is the backup repository port, unless this server is also an NFS share in which case it could be port 111 or port 2049.
I suggest on this server getting an output of netstat when no backup jobs are running and look for these ports being in use.
I hope this helps!
Michael Paul - Opinions are my own and do not necessarily reflect the opinion of Veeam | https://micoolpaul.com | Mastodon: @micoolpaul@masto.nu | Bluesky: @micoolpaul.com
1 person likes this
Got this same error, in my case, loggin into the NAS (QNAP) file inconsistency error came up, after letting the system fix this everything came back fine.
1 person likes this
Comment
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.