Skip to main content
  • EN
  • Community
  • Community
  • Discussion Boards
  • Error: Failed to call RPC function 'HvGetVolumesByPaths': The file or directory is not a reparse point. Failed to retrieve reparse point data.

Hello, well, the fun never ends.

I moved a VM named ‘user01-Virtual-Machine agent_vserver03’ from one folder to another folder on the same drive letter V:
The vm itself runs fine, no issues.

Now, the backup fails.

I tried to search about the error and for 'HvGetVolumesByPaths', but foud nothing at all.
Error: Failed to call RPC function 'HvGetVolumesByPaths': The file or directory is not a reparse point. Failed to retrieve reparse point data. 

I re-scaned the hyper-v server, ‘VSERVER03’ but nothing changed.
Note: this is a homelab, i am willing to delete and re-do whatever.
But, no idea what to try next.
 

Maybe I should the following, but hoping there is a less drastic solution?

  1. export vm
  2. delete vm
  3. import vm
  4. in VBR, re-scan the standalone hyperv server
  5. re-create a backup job and backup copy job

 

 

Did you try removing the server from the backup job and then add it back?  I would assume this was tried.

@Chris.Childerhose “Did you try removing the server from the backup job and then add it back?  I would assume this was tried.“

No, as that is even more drastic, then my proposed possible solution.
No idea what “unknown unknown” problems that could trigger.

Have you ever done that?

No idea really on my end as well. Only thing I could find was this Forums post:

https://forums.veeam.com/microsoft-hyper-v-f25/question-about-backup-when-vhd-is-on-a-ram-disk-t83969.html

Not sure that applies, since your issue appears to have occurred after a VM move. Question - how did you move the VM? Did you use the Move function within Veeam, or did you cut/paste it in a new directory manually? If manually, it seems like you probably have a metadata file still referencing the VM from its original location, which makes sense. Not entirely sure how you should proceed other than contacting Support for suggestions. If you attempt what you shared, just make sure you take a current config DB backup of VBR and make sure your VM backups are current.

@Chris.Childerhose “Did you try removing the server from the backup job and then add it back?  I would assume this was tried.“

No, as that is even more drastic, then my proposed possible solution.
No idea what “unknown unknown” problems that could trigger.

Have you ever done that?

It is drastic and would run a full backup but to me it is the only way to fix it other than contacting support.

OK, thanks to all for the suggestions.

In the end, I decided to try my approach first, as it was less risky than removing and re-adding the standalone hyper-v server and if need be, try that.

Luckily, my approach worked perfectly!

  1. Export the vm from hyperv server.
  2. Delete the vm from hyperv server.
  3. Delete the backup job and backup copy job from VBR.
  4. Import the vm to hyperv server, making sure to create a new ID.
  5. Re-create the backup job and backup copy job using VBR.
  6. Run the backup job and backup job job using VBR.
  7. Live Long and Prosper.

Ok @asdffdsa6132 ...sounds good. Glad you got it sorted. Thanks for sharing what worked for you. 

OK, thanks to all for the suggestions.

In the end, I decided to try my approach first, as it was less risky than removing and re-adding the standalone hyper-v server and if need be, try that.

Luckily, my approach worked perfectly!

  1. Export the vm from hyperv server.
  2. Delete the vm from hyperv server.
  3. Delete the backup job and backup copy job from VBR.
  4. Import the vm to hyperv server, making sure to create a new ID.
  5. Re-create the backup job and backup copy job using VBR.
  6. Run the backup job and backup job job using VBR.
  7. Live Long and Prosper.

That is quite the solution but the one I suggested would have been faster.  😂 

@Chris.Childerhose  “That is quite the solution but the one I suggested would have been faster.  😂”

yes, I am the happy new father of a “quite the solution” ;wink

In retrospect, your proposed solution was too cryptic for me to understand.

Can you please explain it in more detail, for the next forum member with the same issue?

 

@Chris.Childerhose  “That is quite the solution but the one I suggested would have been faster.  😂”

yes, I am the happy new father of a “quite the solution” ;wink

In retrospect, your proposed solution was too cryptic for me to understand.

Can you please explain it in more detail, for the next forum member with the same issue?

 

I just meant to edit the job and remove the VM.  Then edit it a second time to add back.

@Chris.Childerhose at some point, i created a new backup job for the vm and that still did not work. so that is why i did my drastic approach.

thanks, hopefully, that will work for other forum members.

 

@Chris.Childerhose at some point, i created a new backup job for the vm and that still did not work. so that is why i did my drastic approach.

thanks, hopefully, that will work for other forum members.

 

Not a problem at all.  Glad to give input and that you fixed the issue.

Comment


Terms & Conditions