Comprehensive data protection for all workloads
Post Reply
ocarreras
Lurker
Posts: 2
Liked: never
Joined: Jul 22, 2020 5:39 pm
Full Name: Oscar Munoz Carreras
Contact:

Restore problem cant mount restore point

Post by ocarreras »

Case #04297415

Hello,
I have this problem for restore (WINDOWS GUEST FILE RESTORE) I using community edition lastest version.

Code: Select all

7/22/2020 1:44:31 PM FILE LEVEL RESTORE STARTED 
7/22/2020 1:44:41 PM USING GEBA-FSSP.AR.GESTAMP.COM AS MOUNT SERVER 
7/22/2020 1:44:42 PM RESTORING FROM BACKUP REPOSITORY 1 
7/22/2020 1:44:42 PM INTERACTIVE MODE 
7/22/2020 1:44:43 PM MOUNTING RESTORE POINT 
[b]7/22/2020 2:25:45 PM ERROR SESSION BECAME ORPHANED. 
7/22/2020 2:25:45 PM ERROR RESTORE JOB IS FAILED: RESTORE SESSION CLOSED UNEXPECTEDLY.[/b]
Egor Yakovlev
Product Manager
Posts: 2579
Liked: 708 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Location: Prague, Czech Republic
Contact:

Re: Restore problem cant mount restore point

Post by Egor Yakovlev »

Hi Oscar,
checked the case, but it only has a single screenshot attachment - can you please upload exported product logs (you can attach them to the case via my.veeam.com). It is hard to guess what caused File-level recovery service outage there.
/Thanks!
ocarreras
Lurker
Posts: 2
Liked: never
Joined: Jul 22, 2020 5:39 pm
Full Name: Oscar Munoz Carreras
Contact:

Re: Restore problem cant mount restore point

Post by ocarreras »

Thanks! Egor I uploaded logs. i my first time with a veeam problem
Egor Yakovlev
Product Manager
Posts: 2579
Liked: 708 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Location: Prague, Czech Republic
Contact:

Re: Restore problem cant mount restore point

Post by Egor Yakovlev »

Thanks for the logs, interesting reading. Cannot say for sure what causes it(I see some file system access errors) - so let's hear from support engineer!
Does that error pop at the start of the FLR Session? Or during file transfer?
Meanwhile, you can try extending default session timeout(30 mins) to something higher - let's say 2 hours - via registry key [HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\InactiveFLRSessionTimeout] give it a value of "7200" and restart Veeam server or its VeeamBackup service(make sure no jobs are running!).

By the way, what is the source of FLR session? I see some physical cluster protected and it gives errors upon rescan with CNO not found...just wondering.

/Thanks!
Post Reply

Who is online

Users browsing this forum: Bing [Bot], Google [Bot], Semrush [Bot] and 309 guests