It is very possible that you came across either one of the flavors of the two error messages shown below: 2016-07-08 23:53:59.63 Logon Error: 18456, Severity:... Recommended Action: 1. If virtual memory is the problem, shut down unused applications or increase the amount of virtual memory. Check the progress report on the client for a message such as "Script exited with status code = number" (the number will vary). http://nodatasource.com/netbackup-error/netbackup-error-code-233.html
On Windows clients, verify that the NetBackup Client service is running. Verify that the system is not running out of virtual memory. If the problem is not serious and the files were backed up, you can manually delete the files. NetBackup status code: 60 Message: client cannot read the mount table Explanation: The backup process on the client did not read the list of mounted file systems. navigate here
o If you can view the report and have not found an entry related to this problem, create activity log directories for the related processes that were running when the error If rbak does not exit with a status message, NetBackup cannot determine whether the restore worked or not. Then, click Configure on the Actions menu and add the slave server to the list on the Servers tab in the NetBackup Configuration dialog box (also, see "Using the Configure -
Create a bptm activity log directory on the server. 2. Recommended Action: Verify that the server software has been installed correctly on the master server and all slave servers. If the error occurs when executing a command on the command line, verify that the parameters are valid. 3. In particular, check for a full disk partition. 2.
NBU clients running 6.x release, though it uses the vnetd daemon for incoming connections, it still requires bpcd to perform the hostname compare to authenticate the NBU server. For a Macintosh or NetWare target client, verify that the server is not trying to connect when a backup or restore is already in progress on the client. Then retry the operation and check the resulting log. Also, for UNIX, do not place Apollo and standard clients in the same class.
Then, retry the operation and check the resulting activity logs. 2. Note: If you are using bpstart_notify scripts on UNIX or Windows NT clients, verify that messages are not being written to stdout or stderr. On a UNIX or Windows NT clients, check for the following problems with the bpbkar client process. Check the All Log Entries and Problems reports to determine which system call failed and other information about the error. 2.
This can occur because the backup job was terminated or the child process was terminated by another error. http://systemmanager.ru/nbadmin.en/nbu_57.htm Status Code: 4 Top Message: archive file removal failed Explanation: The backup portion of the archive completed was successful but the delete failed. Perform "Resolving Network Communication Problems" on page 21. Note that in the above, shminfo_shmmin must be less than or equal to 100 for NetBackup processes to run. 6.
In some cases, error messages in the NetBackup log indicate a backup failure due to an error in semaphore operation; another symptom is the inability of the NetBackup Device Manager service have a peek at these guys You logged it under the Backup Exec forum! 0 Kudos Reply Either NBU Client software is Marianne Moderator Partner Trusted Advisor Accredited Certified 12-05-2011 06:11 AM Options Mark as New Bookmark Enable detailed activity logging: o On the server, create a bpbrm activity log directory. o On NetWare target and OS/2 clients the master server name is the first SERVER entry in the bp.ini file.
Recommended Action: Check the NetBackup Problems report for clues on why the failure occurred. Create a bpcd activity log directory on the client. For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. check over here The log messages were similar to the following: 01/31/96 14:05:23 ruble crabtree.null.com from client crabtree.null.com: ERR - Cannot write to STDOUT.
Retry the backup and examine the activity logs for clues on the cause of the failure. This error can occur when there is only one file in the file list and the file cannot be backed up due to an I/O error. Recommended Action: Check the NetBackup Problems report for clues on where and why the problem occurred.
The SYSTEM account cannot access network drives. Status Code: 73 Top Message: bpstart_notify failed Explanation: The bpstart_notify script returned a nonzero exit code. Simon -----Original Message----- From: veritas-bu-bounces < at > mailman.eng.auburn.edu [mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] On Behalf Of NBU Sent: Wednesday, May 06, 2009 1:55 PM To: VERITAS-BU < at > mailman.eng.auburn.edu This could be caused by the system being overloaded with too many processes and not enough physical or virtual memory.
For detailed troubleshooting information, create activity log directories for the processes that you suspect of returning this status code. Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. this content run->services.msc-->Netbackup client services Restart Netbackup client services (if they are already started ) or start netbackup servicers if they are stoped .
Status Code: 27 Top Message: child process killed by signal Explanation: A child of the process reporting this error was killed. Status Code: 59 Top Message: access to the client was not allowed Explanation: The master or slave server is trying to access the client, but the server is not recognized by Recommended Action: 1. Check the NetBackup Problems report for clues on where and why the failure occurred.
The names of the files are logged in the activity log file in the /usr/openv/netbackup/logs/bpbkar directory before bpbkar processes them. Verify that both the client and the server are operational. 2. Veritas does not guarantee the accuracy regarding the completeness of the translation. Status Code: 13 Top Message: file read failed Explanation: A read of a file or socket failed.
This problem can occur when a process tries to connect to the NetBackup request daemon (bprd) or database manager daemon (bpdbm) and the daemon is not running (On Windows NT, these Perform "Resolving Network Communication Problems" on page 21. 3. Recommended Action: 1. On a Windows NT client, set Verbose on the Troubleshooting tab in the NetBackup Configuration dialog box.
See "Resolving network communication problems" in the Troubleshooting Guide. Also delete /usr/openv/netbackup/bpbkar_path_tr so you do not generate larger log files than needed the next time you create directory /usr/openv/netbackup/logs/bpbkar. 2. The values on the Network tab are written to the services file when the NetBackup Client service starts. o The bp.ini file on OS/2 and NetWare target clients. 2.
Then, retry the operation and check the resulting activity logs. If you tell us the Client OS, we can help to troubleshoot installation and how to check what is running (or not!) on the client. On other PC clients except Macintosh, create an activity log directory for bpcd (the bpcd log is created automatically on Macintosh). A possible cause could be a high network load.
The values on the Network tab are written to the services file when the NetBackup Client service starts. On an SCO system, code 60 can occur because the mount-point path name exceeds 31 characters, which is the maximum allowed on an SCO system.