Host-based backup of Microsoft Hyper-V VMs.
Post Reply
hbilke
Expert
Posts: 118
Liked: 5 times
Joined: Jan 14, 2017 9:05 pm
Contact:

Restore files Manager / Repo standalone / workgroup

Post by hbilke »

Ave collegae,

B&R 12.1.2.172
located in it’s own workgroup - not in domain
all backups (hyper-v and agent) are working
restore of vm-data files works
searching for files in the backup fails due to mount error / fail (FLR_) „client auth failed“

Any hints? Did a file restore before (not sure which version).

Salvete
hRy
PetrM
Veeam Software
Posts: 3874
Liked: 656 times
Joined: Aug 28, 2013 8:23 am
Full Name: Petr Makarov
Location: Prague, Czech Republic
Contact:

Re: Restore files Manager / Repo standalone / workgroup

Post by PetrM »

Hello,

Please provide a support case ID as requested when you post about a technical issue. As explained there, we cannot troubleshoot technical issues through forum posts. Any posts regarding technical issues without a case ID will eventually be deleted by forum moderators. You can also upload debug logs to our support team following the instructions provided in this KB.

Thanks!
hbilke
Expert
Posts: 118
Liked: 5 times
Joined: Jan 14, 2017 9:05 pm
Contact:

Re: Restore files Manager / Repo standalone / workgroup

Post by hbilke »

Sorry for being late. It was possible to restore the vhdx and mount this to get the files. It’s an issue hving the veeam manager in a workgroup config and doing a flr to a domain joined target. The service (user?) has no rights to open / save the file(s). I didn’t open a case - got the files via vhdx restore.

GreetNx
hRy
hbilke
Expert
Posts: 118
Liked: 5 times
Joined: Jan 14, 2017 9:05 pm
Contact:

Re: Restore files Manager / Repo standalone / workgroup

Post by hbilke »

PetrM wrote: Aug 20, 2024 6:54 pm Hello,

Please provide a support case ID as requested when you post about a technical issue. As explained there, we cannot troubleshoot technical issues through forum posts. Any posts regarding technical issues without a case ID will eventually be deleted by forum moderators. You can also upload debug logs to our support team following the instructions provided in this KB.

Thanks!
"Technical issue“ doesn’t nail it completly. Read about similar problems / descriptions in the community fora. I found a way to circumvent the problems with direct FLR restore from a setup where veeam b&r is not in the domain of the protected devices but in a workgroup. No mapping or „Copy To“ needed.
Added the target domain with an user to the credential manager (control panel) and no problems writing directly to the targets.

Cheers and have fun

hRy
Post Reply

Who is online

Users browsing this forum: No registered users and 8 guests