Rep 52266 the in Process Reports Server Failed to Start
- Home
- Storage & Backup
- Data Backup
Hi Everyone,
We recently set up Veeam Backup Agent for Windows on a few of our PC's.
All seem to be working perfectly fine, except for a couple that we received errors messages for as the backups failed. We have set these ones up the exact same was as the other ones so not sure what the error message actually means or why there even is an error.
These errors are below -
Failed to backup []
Error: Shared memory connection was closed. Agent failed to process method {FileBackup.SyncDirs}. Exception from server: An unexpected network error occurred. Failed to write data to the file [].
Error: The network path was not found. --tr:Error code: 0x00000035 --tr:FC: Failed to check whether file or folder . --tr:Failed to call DoRpc. CmdName: [FcIsExists]. The network path was not found.
Unable to perform threshold check for location "": failed to query backup repository disk space
Error: The network path was not found. --tr:Error code: 0x00000035 --tr:FC: Failed to check whether file or folder '' exists. --tr:Failed to call DoRpc. CmdName: [FcIsExists].
Any ideas what these errors mean?
Thank you.
What VAW edition are you using ?
What type of network are running on these machines and/or your backup repository ?
......
The more common issue is that you have configured backup of a few machines to run at same time such that the network or the backup repository network is too congested such that these machines cannot see the backup repository. Other issues maybe that the backup repository IO is too busy to respond to these machines.
This is what I have and seen....150 PCs and 120 lappy backing up (personal files only) to a Synology NAS with only 1 LAN (RAID 5 12x4TB HDD)....all set to run at 6pm.
In the beginning, there were many failures as the network gets too congested and the NAS box gets too busy also....at most 5 machines can backup (each machine have at least 100GB of files for example). The machines will be powered off after backup and skip backup when powered on.
The next day only 8 machines backup successfully (the 5 from day 1 with 3 more)...the following day only 12 (8 from previous days with 4 more)....the previous days successfully backup machines started to use increment backup instead of full.
What we changed....NAS to use RAID 10 & use all 4 NIC ports (teamed)....PCs to run at 6pm & lappy to run at 7pm.
The outcome became obvious to the issues....especially on first day....backup jobs got delayed to almost 1am but all was successful...mainly due to NAS slow in writing but there was no cannot find NAS issue as probably the NIC teaming prevented the "network path not found" error
- ROM
- CPU
- RAM
- GPU
8 Replies
Brand Representative for Veeam Software
Seems like backup repository wasn't accessible in the time of backup. What did you configure as a backup target? Network share? Can you try to access it (and write some data) on it from that Windows PC and using the same credentials you provided agent with?
What VAW edition are you using ?
What type of network are running on these machines and/or your backup repository ?
......
The more common issue is that you have configured backup of a few machines to run at same time such that the network or the backup repository network is too congested such that these machines cannot see the backup repository. Other issues maybe that the backup repository IO is too busy to respond to these machines.
This is what I have and seen....150 PCs and 120 lappy backing up (personal files only) to a Synology NAS with only 1 LAN (RAID 5 12x4TB HDD)....all set to run at 6pm.
In the beginning, there were many failures as the network gets too congested and the NAS box gets too busy also....at most 5 machines can backup (each machine have at least 100GB of files for example). The machines will be powered off after backup and skip backup when powered on.
The next day only 8 machines backup successfully (the 5 from day 1 with 3 more)...the following day only 12 (8 from previous days with 4 more)....the previous days successfully backup machines started to use increment backup instead of full.
What we changed....NAS to use RAID 10 & use all 4 NIC ports (teamed)....PCs to run at 6pm & lappy to run at 7pm.
The outcome became obvious to the issues....especially on first day....backup jobs got delayed to almost 1am but all was successful...mainly due to NAS slow in writing but there was no cannot find NAS issue as probably the NIC teaming prevented the "network path not found" error
hi Andrew,
we have 9 pcs backing up to a sinology NAS.
They are all scheduled to begin at the same time.
The target is just a network share and not a backup repository.
The backups are not failing every time.
Those error messages are from two different PCs
Could the problem be our NAS cant handle 9 PCs all trying to start a backup at the same time?
Hi Adrian, thank you for your reply! we are using the free VAW 3.0.2.1170 edition.
we are running a 1GB network on the PC's.
Its sounds like it would be worth trying running the backups at different times to reduce the load on the NAS device.
Brand Representative for Veeam Software
Tyler got it. I bet the NAS appears to be a bottleneck for those tasks. Try to cascade them, schedule with a bit of delay and there you go.
ccampbell5 wrote:
Hi Adrian, thank you for your reply! we are using the free VAW 3.0.2.1170 edition.
we are running a 1GB network on the PC's.
Its sounds like it would be worth trying running the backups at different times to reduce the load on the NAS device.
That means the network is so congested at the NAS such that other PCs are not getting a network response....from your error messages and the symptoms.
BTW, instead of calling it a NAS....we use the term backup repository (can mean NAS, cloud etc) as to differentiate that a NAS is usually a file server while a backup repository is mainly used for storing backup data sets....although a NAS can server both (or many purposes).
Also do note how VAW "free" works also as this can be another cause of backup loads (but this is unavoidable)...VAW uses Full backup in the initial backup then incremental backups until the retention period is reached. After that, VAW "free" will then run as "reverse increment" such that a daily increment backup is taken but then a daily synthetic full backup is created. So each backup job would have 3 parts...(1) take daily increment backup (2) create daily synthetic full (3) delete oldest backup.
Hi Everyone,
We tested out staggering the times yesterday and looking at the backup reports that we received for yesterdays backups, this seemed to solve our issue!
We received no error messages on any of the PCs and they all ran successfully.
This topic has been locked by an administrator and is no longer open for commenting.
To continue this discussion, please ask a new question.
Rep 52266 the in Process Reports Server Failed to Start
Source: https://community.spiceworks.com/topic/2229040-veeam-backup-errors
0 Response to "Rep 52266 the in Process Reports Server Failed to Start"
Post a Comment