OK, after weeks of failed backups (that one directory only) I *FINALLY* got a successful backup this morning.
The change of the day: a new(er) version of Symantec Endpoint Protection. It seems there was a bug introduced in an updated version of SEP that would cause hangs when copying files across the network under SMB2.
The one system I was having trouble with is a laptop I have remote work access installed on and therefore requires SEP. An SEP update around the 11.0.5xxx range introduced the error. SEP released a fix (version 11.06300.803 or higher), but work hadn't pushed through a newer version yet, but I found I could manually go out and pull down 11.07xxx from the corp website*
This lead to my first successful backup in well over a week! The last real test will be overnight today to see if the backup runs unattended successfully.
Notes:
I know this probably doesn't help a single person, but if anyone else has very odd network copy problems start looking at anything that might conflict with SMB2 (it seems it does happen). There is a way to force SMB1 on Windows if you can't figure out the conflicting program.
SEP fix details: http://www.symantec.com/business/suppor ... TECH139768
How to force SMB1 for those that may or may not care: http://www.nathanmino.com/2011/03/09/tr ... dows-72008
*Fun fact, all of this broken/fixed versioning happened in 2010. Seem the corporate version of SEP stays back several levels. Leastwise the one my work requires if I want access from home.
The change of the day: a new(er) version of Symantec Endpoint Protection. It seems there was a bug introduced in an updated version of SEP that would cause hangs when copying files across the network under SMB2.
The one system I was having trouble with is a laptop I have remote work access installed on and therefore requires SEP. An SEP update around the 11.0.5xxx range introduced the error. SEP released a fix (version 11.06300.803 or higher), but work hadn't pushed through a newer version yet, but I found I could manually go out and pull down 11.07xxx from the corp website*
This lead to my first successful backup in well over a week! The last real test will be overnight today to see if the backup runs unattended successfully.
Notes:
I know this probably doesn't help a single person, but if anyone else has very odd network copy problems start looking at anything that might conflict with SMB2 (it seems it does happen). There is a way to force SMB1 on Windows if you can't figure out the conflicting program.
SEP fix details: http://www.symantec.com/business/suppor ... TECH139768
How to force SMB1 for those that may or may not care: http://www.nathanmino.com/2011/03/09/tr ... dows-72008
*Fun fact, all of this broken/fixed versioning happened in 2010. Seem the corporate version of SEP stays back several levels. Leastwise the one my work requires if I want access from home.