|
|
Explanation: The client backup terminated abnormally. For example, this error occurs if a NetBackup master or media server is shut down or rebooted when a backup or restore is in progress.
Recommended Action: Do the following, as appropriate:
This error may occur if nbjm terminated while a backup job was running. Examine the unified logging files on the NetBackup server for nbjm (117) for more detail on the error. All unified logging is written to /usr/openv/logs (UNIX and Linux) or install_path\NetBackup\logs (Windows).
On UNIX and Linux clients, check for core files in the / directory.
On UNIX and Linux clients, check the system log (/usr/adm/messages on Solaris) for system problems.
This problem can sometimes be due to a corrupt binary.
On UNIX and Linux clients, use the UNIX sum command to check the bpcd, bpbkar, and tar binaries, which are located in /usr/openv/netbackup/bin on the client. Reinstall them if they are not the same as in the client directory under /usr/openv/netbackup/client on the server.
On a Windows client, check the bpinetd.exe, bpcd.exe, bpbkar32.exe, and tar32.exe files, which are located in the install_path\NetBackup\bin folder on the client.
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.