Forum Discussion

TimWillingham's avatar
10 years ago

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

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?

  • 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.

6 Replies

  • 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.

  • 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.

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