Highlighted

custom error messages in netbackup

Hi, anyone know if I can customize the error message for a certain error code.

For example: bpstart_notify failure causes "error 73: bpstart_notify failed". instead, I wanted to in the job details what logs to look for when that happens. Is it possible? I mean is there any way that i can alter the error message for a certain error code

2 Solutions

Accepted Solutions
Accepted Solution!

Not possible. But you can

Not possible. But you can click on the troubleshooting icon and it will tell you.

View solution in original post

Accepted Solution!

Found it is best to create

Found it is best to create the logging from inside the script to tell what the problem is with the script, all netbackup get is an exit code which is either zero or nonzero.

That requires logging into the client to troubleshoot, but you would probably have to do that anyway to correct the problem. Alternatively you setup a share or mailing of the log.

 

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

View solution in original post

3 Replies
Accepted Solution!

Not possible. But you can

Not possible. But you can click on the troubleshooting icon and it will tell you.

View solution in original post

Seems you need a better

Seems you need a better understanding of the NBU process flow. If you know which processes run on a client, you would know which logs are needed.
Accepted Solution!

Found it is best to create

Found it is best to create the logging from inside the script to tell what the problem is with the script, all netbackup get is an exit code which is either zero or nonzero.

That requires logging into the client to troubleshoot, but you would probably have to do that anyway to correct the problem. Alternatively you setup a share or mailing of the log.

 

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

View solution in original post