|
Hi All, I raised a call to investigate an exit status 84 error
and we resolved it by using the workaround detailed below. Problem is that it’s
totally killing the performance of a bpduplicate session, which results in me
being unable to duplicate a full backup over the weekend. Does anyone know of a
way to be informed (other than reading the next MP release notes) when a more
permanent fix is put in place? I’m assuming that the workaround is only a
temporary solution. Here’s the full Etrack Incident number and details:- -------------------------------------------------------------------------------- Etrack Incident = ET646985 Description: NDMP backups failed with a status 84 when
writing a TIR fragment. The bptm log showed an error where the
expected block position is one off. This error occurred in the function
write_data_tir(). Workaround: To avoid this issue, add the following
line to the file <installdir>/netbackup/db/config/ndmp.cfg
NDMP_MOVER_CLIENT_DISABLE This will have a minimal impact on
backups. However it will cause a significant performance
impact to dup/verify/import when using NDMP drives. -------------------------------------------------------------------------------- Cheers, Dave -- |
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
