I am running redundant backups on 3 Windows 7 Pro computers located at 3 different sites over MPLS. Call them sites 1,2 and 3. Each computer backs up the same files from the originating computers (located at all 3 sites) in sequence; i.e. there is generally no overlap between backup jobs on any one computer and/or on the MPLS.
The backup computer at Site 2 was recently changed up from XP to Windows 7.
This ONE SITE backup computer, before Windows 7 and now with it, occasionally generates errors:
"the specified network name is no longer available"
That is, it only happens at Site 2 and I've only seen it happen on backup jobs from Site 1 (Site 3 has but one small backup job so the opportunity to see this is much more limited).
This happens in the middle of a backup and the rest of the message makes it obvious that the individual filename is known.
None of the other backup computers has this kind of error.
Another site, which has to back up the exact same files from the same source computers, has none of these errors.
The site with errors is geographically further away but the MPLS is all on fiber.
All of the computers are accessed using UAC so no name service at all; i.e. \\[ipaddress]\....
I very much doubt that there are any settings that could be affecting this. I'm rather left with wondering about hardware - thus the recent swap-out of the computer. Yet these errors continue to occur on occasion.
I'm looking for good ways to narrow down the possibilities.
The hardware chain is:
- backup computer
- local switch
- main switch
- MPLS router
MPLS fiber system
- at least one switch
- MPLS router (which also serves the Site 3 backups without errors)
So, everything is common with Site 3 at this point.....
Not that I suspect the hardware necessarily but where else to look.
And, how to look?
I can run Wireshark on the Site 2 LAN switch ports ........