Video Screencast Help

Lots of status code 14/83/87/213/2074 after upgrade from 7.5.0.6 to 7.6.0.2

Created: 25 Jul 2014 • Updated: 25 Jul 2014 | 6 comments
This issue has been solved. See solution.

Yesterday I posted about status code 2106 after this upgrade which Symantec was able to resolve.  Now however, many of the clients are getting the subject errors.  Has anyone else had this experience with this upgrade?

Operating Systems:

Comments 6 CommentsJump to latest comment

INT_RND's picture

I would guess all those errors share a root cause on the destination disk pool. Do all those jobs share one disk pool? What kind of disk is it?

This article might help:

http://www.symantec.com/business/support/index?page=content&id=HOWTO35836

TimWillingham's picture

Yes, all clients write to the same MSDP pool which is SAN storage with great performance.  We didn't have this many failures before the upgrade.

INT_RND's picture

Did you encounter any errors during the database conversion step at the end of the upgrade?

Check your conversion logs:

http://www.symantec.com/business/support/index?page=content&id=TECH213745

INT_RND's picture

If the MSDP volume is okay then it's possible you are running in to issues with client-side dedupe. The clients must all be upgraded to the same patch level. To test this theory you can disable client side dedupe for a policy and manually run that policy. 

It's always best practice to keep master/media/client software at the same patch level. In this case the dedupe fingerprints need to be in the same format.

SOLUTION
TimWillingham's picture

Unfortunately, that appear to be the case.  I upgraded 2 of the clients that were having problems and upgrading them resolve the failures.