Error 64: Failed to flush buffers / Network name...

[guiy2k_TS]

Hi,

Support case # 00495800
I got this issue since Monday on our Backup Infrastructure: I dont know why this happens. I tried to recreate the Backup task, delete all stuff related to that backup job, but nothing. Every time the same error.
The most of our VMs will be backuped fine. But 2 of our Production VMs wont: What can i do to fix this issue: The CIFS Share is on our NetApp Filer:

Our System: VMWARE 5.1 latest Patch Level with. vCenter 5.1 on DELL R410 and R710 Servers
Veeam B&R: 7.0 R2 latest Patch Level on a W2k8R2 latest Patch Level
CIFS Share: provided by our NetApp FAS Filer

Code: Select all

25.12.2013 22:33:25 :: Processing 'Q9GTK_2nd AD Controller_CRL' Error: Client error: Der angegebene Netzwerkname ist nicht mehr verfügbar. Error code: 64
Failed to flush file buffers. File: [\\serverfqdn\Z_Backup_Storage$\Q9GTK_2\Q9GTK2013-12-25T223306.vbk].
Failed to backup text locally. Backup: [veeamfs:0:0b6f513c-0581-4184-b6ec-e36bf3d82cd3 (vm-4391)\summary.xml@\\serverfqdn\Z_Backup_Storage$\Q9GTK_2\Q9GTK2013-12-25T223306.vbkVBK: 'veeamfs:0:0b6f513c-0581-4184-b6ec-e36bf3d82cd3 (vm-4391)\summary.xml

THX a lot!
bye Rene´

[Gostev]

I will take a guess that either something broke on the actual filer, or this is a networking issue. Thanks.

[guiy2k_TS]

Hi,
the filer is fine, because the most of the VMs can be backuped. I only use one CIFS Share for backing up all VMs. And 5 of them, i cant backup anymore. The crazy thing is, after i setup a local stroage share on my veeam Server for backup, the affected VMs can be backuped fine... so no problem, no error. But why the most of our VMs can be backuped fine to the SAME NetApp Share... and this 5 couldnt?

[guiy2k_TS]

After a little bit of deep diving with WireShark i found out, that the routing metrics are going bad and the FW was blocking MS-DS 445 TCP and all NetBIOS Ports to the B&R Servers and to the NetApp Filer... i have two network cards connected to the VMs..AdminLAN and "normal" Network...
After i setup the metrics by hand, one IP static, other with DHCP (266 and 10) the connection with Veeam B&R works fine and i could backup the affected VMs again. So i was very happy about that, because since monday i got no backup from 2 Prod VMs. All Vms are now safe.