by RyGy7 » Fri Jul 24, 2015 3:41 pm people like this post
So I have setup several desktops to use veeam endpoint and its been working great so far. But i've recently encountered a problem at about the same time each day. The backup destination is simply an old win7 computer with tons of storage. Here is what i see;
veeam client logs errors in the win event of 'network not found'
the destination veeam storage drops packets just pinging the client & the network utilization bounces up n down 15% - 40%
after a few re-tries and an hour all is good again. This is happening to about 5 clients that are running at that time. Now of course i could stagger better but I was wondering if anyone has tips to help the bandwidth on the destination PC.
by Vitaliy S. » Mon Jul 27, 2015 10:06 am people like this post
Shawn, have you tried to check Windows Event log for this Win 7 server? Also have you tried to reduce the number of concurrently launched backup jobs? It seems like that target storage NIC card is overloaded when all jobs are running at the same time.
by RyGy7 » Tue Jul 28, 2015 2:49 pm people like this post
Unfortunately the event logs show nothing. I would have assumed so as well, but nothing in application / system / HW events / or windows network profile. I have 5 machines backing up to this which I will begin to stagger (hope i don't bang up against other machine times..lol)
What makes this just slightly odd to me is that it was not an issue until I altered the IP address on the server. Since then i have rebooted and flushed DNS. Also the backups eventually succeed so it is a flooding issue, just didn't think 5 machines was too much. I disabled tcp offloading last week but clearly didn't help.
by RyGy7 » Thu Jul 30, 2015 3:09 pm 1 person likes this post
Issue resolved!! Another Admin expanded our dhcp scope last week. Which then extended into the IP address of my backup destination. I had concerns that duplicate IP's were an issue but I was unable to prove it in the times i brought down the box. Turned out to be a Samsung phone...woopsie!