On Windows NT clients, verify that the account used to start the NetBackup services has read access to the files. b. Recommended Action: None, unless this was a database backup performed through a database extension product (for example, NetBackup for Oracle or NetBackup for SQL Server). Status Code: 61 Top Message: wbak was killed Explanation: The wbak process on the Apollo was killed. http://nodatasource.com/netbackup-error/status-41-netbackup.html
o Verify that the Windows NT TCP/IP service specifies the domain server that resolves names for the subnet that contains the NetBackup servers. STEP 2:Click the "Quick Scan" button. Recommended Action: 1. Recommended Action: 1. Go Here
o Check the inetd log to see if NetBackupListen is running. These clients can handle only one NetBackup job at a time. On the Performance tab, set Virtual Memory to a higher value. 4. Recommended Action: 1.
When you are through investigating the problem, delete the /usr/openv/netbackup/logs/bpbkar directory, since the log files can become quite large and are not deleted automatically. Check the IP address for the client. b. o On Windows NT, 98, and 95 systems, the master server is designated as Current on the Servers tab in the NetBackup Configuration dialog box.
Status Code: 25 Top Message: cannot connect on socket Explanation: A process timed out while connecting to another process for a particular operation. Register Hereor login if you are already a member E-mail User Name Password Forgot Password? Submit your e-mail address below. We'll email youwhen relevant content isadded and updated.
b. see it here Thank You! Netbackup Status Code 239 Oracle On UNIX clients, check the system log (/usr/adm/messages on Solaris) for system problems. 5. When this condition exists the NetBackup servers and Windows NT clients may be able to ping one another, but the server is still unable to access the Windows NT client. 3.
Then, retry the operation and check the resulting activity logs. 2. http://nodatasource.com/netbackup-error/netbackup-error-code-233.html Enable detailed activity logging on the client: o Create bpcd and bpbkar (UNIX or Windows NT only) activity log directories. Recommended Action: Free up memory by terminating unneeded processes that consume memory. Status Code: 44 Top Message: network write failed Explanation: An attempt to write data to a socket failed.
Set up activity logging: a. Send me notifications when members answer or reply to this question. Recommended Action: 1. check over here Recommended Action: Activate the required policy, correct the client name, or add the client to a policy that meets your needs.
Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. One instance when this code appears is if a NetBackup master or slave server is shut down or rebooted when a backup or restore is in process. Retry the operation and examine the resulting logs. 5.
On other PC clients except Macintosh, create an activity log directory for bpcd (the bpcd log is created automatically on Macintosh). This has been seen to occur during backups when directories have thousands of unmodified files; it has also been seen when backing up file systems or directories that reside on optical Correct problems and retry the archive. But the backup does not run, failing with an error 236.
Perform "Resolving Network Communication Problems" on page 21. 4. What are the steps which need to be performed in $ORACLE_HOME for enabling the RMAN backups with netbackup or TSM tape library software ? c. http://nodatasource.com/netbackup-error/netbackup-error-code-245.html o •The bpbkar client process is not hung, but due to the files and directories it is scanning, it has not replied to the server within CLIENT_READ_TIMEOUT or CLIENT_CONNECT_TIMEOUT.
The bpbkar activity log on the client will show a message similar to the following: bpbkar build_nfs_list: FTL - cannot statfs net Errno: 42406 To eliminate these errors for future backups, For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. It is possible that updates have been made to the original version after this document was translated and published.