- Posts: 21
- Liked: never
- Joined: Feb 01, 2010 7:41 pm
- Full Name: Shawn Barnhart
I have run into this on a couple of sites where backups are being run to both local disk and CIFS NAS -- two seperate jobs, local disk backup happens first and is always finished before second job starts.
Backups to local disk run fine, backups to the NAS fail kind of randomly. In one day's job, 1 or 2 of the VMs will backup and the others will fail. On the first retry, 1 or 2 VMs will backup. After that, we may not get any more successful backups (all retries result in failure) until the next scheduled job run.
As you can see in the error log, it IS a low-budget Buffalo Terastation NAS (no, I didn't choose it...) and I suspect the device is just too lame in terms of disk and network I/O to keep up with the backup server, although we did have general success with Veeam 5 to this same device.
1/24/2012 20:13:20 :: Error: Client error: The specified network name is no longer available
Failed to read data from the file [\\10.0.0.56\Veeam\VeeamDaily\DSI-Daily-Terastation\DSI-Daily-Terastation2012-01-11T105353.vbk].
Failed to backup text locally. Backup: [Prev. backups: "veeamfs:6:a4500d08-afe7-432b-85d5-0cd1adc3df6a (vm-20)\servername.org.local.vmx@\\10.0.0.56\Veeam\VeeamDaily\DSI-Daily-Terastation\DSI-Daily-Terastation2012-01-21T200042.vib";"veeamfs:6:a4500d08-afe7-432b-85d5-0cd1adc3df6a (vm-20)\servername.org.local.
- Posts: 282
- Liked: 26 times
- Joined: Nov 10, 2010 6:51 pm
- Full Name: Seth Bartlett
If my post was helpful, please like it. Sometimes twitter is quicker to hit me up if you need me.
- Veeam Software
- Posts: 5978
- Liked: 1794 times
- Joined: Jul 26, 2009 3:39 pm
- Full Name: Luca Dell'Oca
- Location: Varese, Italy
Never had this error on faster devices like ExaGrid or other mid-market NAS.
Principal EMEA Cloud Architect @ Veeam Software
vExpert 2011 -> 2020
Veeam VMCE #1
Users browsing this forum: Baidu [Spider] and 15 guests