Weekly full backup of itself fails with a status 41 and sometimes status 89. Other backups in the environment work fine. Any suggestions outside of network load?
I guess my confusion is that Status 41 is usually indicative of network naming and communication issues, and my problem is a master server backup of *itself*. It can backup other network clients just fine.
The jobs are dying mid/late backup, so a connection can be made (to itself). I'll look through bpbkar/bpcd and see if there anything indicative.
Add the sporadic Status 89's, and my guess is network/CPU load, but is there anything else worth checking?
NetBackup treats every server the same. It does not do a short cut just because the server doing the backup happens to be the same as the one being backed up. It checks and validates each server before it backs it up, to do this it goes out onto the network. So to the server being backed up and to the server doing the backup they seem to be completely differant servers. Of course the data transfer is done internally.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.