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. What type of network are running on these machines and/or your backup repository ? tr:Error code: 0x00000035 -tr:FC: Failed to check whether file or folder '' exists. Unable to perform threshold check for location "": failed to query backup repository disk spaceĮrror: The network path was not found. tr:Error code: 0x00000035 -tr:FC: Failed to check whether file or folder. Exception from server: An unexpected network error occurred. 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.Įrror: Shared memory connection was closed.
Veeam backup repository windows#
Nothing in the article would lead to any correlation that "NAS are riskier" than other things.We recently set up Veeam Backup Agent for Windows on a few of our PC's.Īll seem to be working perfectly fine, except for a couple that we received errors messages for as the backups failed. If the issue was a firmware bug, then it is QNAP specific. If the failed drive is replaced, it will use the same calculations to repopulate the drive with corrupted data." If the errors come from URE, then the issue affects all systems regardless of what they are. Here is the quote: "He found that if a drive fails in a RAID 5 array, the QNAP device will resort to recalculating the missing data, causing errors in calculations and corrupting data. Go watch his VeeamON 2017 preso, he spent sometime talking about why this is a problem. Just like Anton said, it's a NAS problem. Thanks for the replies, and - I would have just chalked it up to a QNAP problem and using RAID5 (in this scenario made no sense to me) but like you said, he mentions an entire "category" of technology.
Should I reconsider my plan and start looking for an actual server to fill with local storage as my next backup said in Synology NAS for Veeam Backup said in Synology NAS for Veeam Backup Repository:
Veeam backup repository download#
I do this because it would take quite awhile to download all the backups from S3 in the event of a disaster. I also manually copy all backups to USB hard drives every weekday and take them offsite every weeknight.
Veeam backup repository full#
The only one I don't do that with is the "huge" file server, that is currently 2.4TB for a full backup. I also have external (separate from Veeam) tasks that run copies to an AWS S3 bucket to get the backups offsite almost immediately after the jobs finish. I am using OBR10 (not RAID5 like the QNAP article mentioned). I replaced the drive and it rebuilt just fine. I have never experienced an issue with mine except I did have a drive fail when a larger than normal backup occurred and maxed the storage capacity. I started questioning this statement and found many posts by Veeam reps on SW that don't seem to have any qualms with them and in the SMB, Synology (also QNAP and ReadyNAS) are very popular for this use case. This is why for cheap backup targets, we've always been recommending using a physical Windows or Linux server with a bunch of disks instead." As I keep repeating at my breakout sessions, usage of low end NAS is by far the number one reason of corrupt backups and failed recoveries that we're seeing in support. Indeed, we had quite a few customers impacted by this issue – we just could not "separate" this particular one from a bunch of other issues causing corrupted backups with this sort of devices. "Here's one more nail into the coffin of low end NAS usage > QNAP critical data corruption. Anyway, he mentioned a QNAP data corruption issue and how low end NAS devices are not recommended. If you aren't familiar with it, Anton Gostev (Vice President, Product Management at Veeam Software) sends a brief weekly message about things that mostly relate to Veeam, VMware and Hyper-V but also other things that he finds interesting. I have been using a Synology NAS (first, an 1812+, currently an 1813+) as a Veeam backup repository for about 5 years and was about to pull the trigger on the Synology DS3617xs until I saw last weeks' Veeam Community Forums Digest.