Forum Discussion
This is more than likley a difference in "tuning" values, between what you had in the old Master, and what you have since the upgrade..
One thing that may help to prove this is to do a backup with "set hist=n" as the first line of the includes/selections list, this will treat the backup as a single large dump, and not "index" every file in it, thus proving that the data can be read / written and that its the data being sent regarding the individual files that is the problem.
https://www.veritas.com/support/en_US/doc/24427212-127304472-0/id-SF940177686-127304472
NOTE with the "hist=n" setting you will NOT be able to individual file restores, you have to recover the entire volume, but it will help rule out the need to tune things...
Looking at OLD questions regarding a similar issue https://vox.veritas.com/t5/NetBackup/NDMP-XDR-DECODE-ERR/td-p/442148
this could also be due to JUMBO frames.
Regards
Simon
- VeritasNB5 years agoLevel 2
Thank you Simon for your reply and ideas regarding this situation. I would like to be able to recover single files so set hist=n is not an option. The ndmp backups a netapp with esx server and if 1 server needs to be restored then the entire is being restored. I can not find the jumbo frames on windows server 2016 > nic > properties > configure > advanced.
**** Post edited to remove unrelated URL ****
Related Content
- 10 months ago
- 4 months ago
- 7 months ago
- 6 months ago