09-04-2017 03:49 AM - edited 09-04-2017 03:50 AM
09-04-2017 04:27 AM
You didn't provide much information, so I can give you a very vague answer.
Stop the NetBackup services and remove the lock file it might be talking about.
Search the VERITAS folder for *.lock. It is probable a good idea to search the KB for the lock files before deciding to delete it.
09-04-2017 05:37 AM
Please show us all text in the Job Details of failed job.
Herewith explanation of status 158: https://www.veritas.com/support/en_US/article.000118927
Message: failed accessing daemon lock file
Explanation: The process cannot lock its lock file because an error was received from a system call. This lock file synchronizes process activities (for example, it prevents more than one daemon from running at a time).
Recommended Action: Do the following, as appropriate:
Examine the NetBackup error log to determine why the system call failed. Then correct the problem. It may be a permission problem.
If the error log does not show the error, create a debug log directory for bprd or bpdbm (depending on which process encountered the error). Increase the unified logging level if nbpem, nbjm, or nbrb encountered the error. Use the vxlogcfg command as explained in the following topic:
See "About unified logging" in the NetBackup Logging Reference Guide.
Retry the operation and check the resulting debug log.
If you search Google for
NetBackup status 158
You will find a number of possible reasons for this error.
PS:
Are you aware that NBU 7.6 reached EOSL 7 months ago?