Veeam drops network connectivity on restore

[Grammo]

Hi there.

Im new on the forum, we have a veeam backup server running, and some of our backups arent working probaly.

When i try to restore guest files from our fileserver, it mounts the server perfect, but when i start to restore the files, it stops around 30% of the restore, and then stop all network connectivity.
It completes the backup without any errors.

Ive had a similar problem with out exchange backup, we had a period of 4 days where we couldnt mount the server, it stopped at 18%. After this it took a full backup and it have run ever since.

Our storage location is a Synology RS2414rp device connected with FC.

I have tried to find a solution, but im running my head against the wall.

[Vitaliy S.]

Hi Martin,

What's your suppport case ID? Have you tried moving backup files to another repository and then running the restore?

Thanks!

[Grammo]

I havent made a support ticket yet. I wanted to ask in the forum at first.

I havent tried moving my data, because i have only seen the problem, with a few files, with out exchange it was a few rollbacks that failed, not them all. So i thought it migt was something similar with our fileserver.

I have thougt about if it could be caused, due to us using reverse incremental, and it fails in that job, maybe a incremental would help us with the problem?

I have just tried to restore some files, 48,1 MB, and it stopped at 91% 47.1 mb and my transferrate dropped tp 130-180 kb/s

Im gonna create a ticket for this issue.

[Grammo]

Fun fact! Or not really, but i just tested again, and i used the "restore" function, and the restore of my file, stopped at 91%

Then i tried to use a Copy To, and placed it locally on my veeam, and then copy/pasted it to the networklocation on my fileserver afterwards, and it worked like a charm.

[veremin]

I have thougt about if it could be caused, due to us using reverse incremental, and it fails in that job, maybe a incremental would help us with the problem?

Nope, backup mode used by source job has nothing to with the described issue. Opening a ticket sounds like the best idea, indeed.

[Grammo]

I have made a support case. ID: 00823356

[veremin]

Thanks for posting the case number. Let's wait and see what your support engineer say, once logs are analyzed.