Yea, Data Domain want us to upgrade to 5.0.2.3 also but they cannot pinpoint
any reason for the code 84. Right now we are staying at 5.0.1.7 as the media
write errors are very very few now. I even asked datadomain to give the
solution id that specifically addresses the media write error in the
:[Veritas-bu] Status 84 - plugin error
Sent by:veritas-bu-boun...@mailman.eng.auburn.edu
We had the same problem, media write errors. Seems to happen with long
running jobs most of the time. We ugpraded the Data domain code and OST
code which increased the timeouts to 3hrs from data domain
Hi Jack,
i'll second rsavage. we had to upgrade to 5.0.1.7 and use the symantec patch
for 2008 servers as well which definitely helped. We worked for a few weeks
before we got a hold of the right person at DD to figure this out. DD support
has been great but they need to do a better job
We had the same problem, media write errors. Seems to happen with long running
jobs most of the time. We ugpraded the Data domain code and OST code which
increased the timeouts to 3hrs from data domain. We also noticed are long
running jobs in which most of the 84 errors were coming from were
We've been having jobs fail with a status 84 seemingly at random. These
jobs are being written to a DataDomain 890 configured as an OST target for
the backups. Both of the media servers in the environment (one AIX and one
Windows) are seeing these failures. Since NetBackup is reporting a
We have seem similar issues when we exceed the max streams on the DD
system. Synth jobs take up 3 streams, duplication jobs take up 2
streams, so you need to be careful with the max jobs on the storage
unit. If this is happening you will see messages logged in your daily
autosupports (No
