Standalone backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE)
Post Reply
Gligom
Lurker
Posts: 1
Liked: never
Joined: Jun 20, 2019 8:39 pm
Full Name: ClaudiuS
Contact:

Error on file restore [Case 03627933]

Post by Gligom » Jun 20, 2019 8:46 pm

Hi,
When i try to restore files i get this error "Input string was not in a correct format", i click ok and the application close, can't restore any file.
I have a Support Case opened (03627933), but i use free edition so no guaranties that i will receive an answer.
Thank you!

Dima P.
Product Manager
Posts: 11405
Liked: 983 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: Error on file restore [Case 03627933]

Post by Dima P. » Jun 21, 2019 12:16 pm

Hello and welcome to the community Gligom.

I've asked support team to pay attention to your case, as log analysis is required to understand the root cause of this issue. Let us know how the investigation goes. Cheers!

grumpyoldtechie
Lurker
Posts: 1
Liked: 1 time
Joined: Jun 26, 2019 4:25 am
Full Name: Arnold Greyling
Contact:

Re: Error on file restore [Case 03627933]

Post by grumpyoldtechie » Jun 26, 2019 5:18 am 1 person likes this post

Hi

I had the same issue restoring from a Synology 816 NAS SMB share to a Windows Server 2019 virtual machine.
In addition the backups failed intermittently with an error that one of the backup files could not be opened for reading.

The Synology log showed:

Code: Select all

../source3/smbd/smb2_read.c:259: [2019/06/25 14:32:54.285557, all 0, pid=27174] smb2_sendfile_send_data
  smb2_sendfile_send_data: sendfile failed for file vermeersa_dc001_backup/vermeersa_dc001_backup2019-06-25T133039.vbk (Connection reset by peer) for client ipv4:192.168.31.15:64698. Terminating
This indicated to me the problem wasn't the Veeam software but an issue between Server 2019 and the Synology.
The issue seemed to occur as soon as large files were accessed on the Synology.

After a lot of wild goose chases on Google an some experimenting I found that the following settings on the advanced SMB settings in the Synology solved the problem:

Maximum SMB protocol: SMB3
Minimum SMB protocol: SMB2
Enable Opportunistic locking: On
Enable smb2 lease: On
Transport Encryption mode: Force (I suspect this is the important one)

I hope this helps

Post Reply

Who is online

Users browsing this forum: No registered users and 11 guests