Home > Error Code > Netbackup 6.5 Error Code 23

Netbackup 6.5 Error Code 23


For example, if you see a message similar to the following in the Problems report or bpdbm activity log: 06/27/95 01:04:00 romb romb db_FLISTsend failed: system call failed (11) 06/27/95 01:04:01 Article:000090314 Publish: Article URL:http://www.veritas.com/docs/000090314 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in For example, this has been seen in conjunction with Cannot write to STDOUT when a Windows NT system that is monitoring network load has detected a high load and sent an Status Code: 55 Top Message: permission denied by client during rcmd Explanation: The UNIX client does not have the server's name in its /.rhosts file. http://windowsazure4j.org/error-code/netbackup-error-code.html

ms ^C ---- PING Statistics---- 6 packets transmitted, 6 packets received, 0% packet loss round-trip (ms) min/avg/max = 0/0/0 ========================================================== [[email protected] - /usr/openv/netbackup ] # cat bp.conf SERVER = chev1bkp2 Status Code: 65 Top Message: client timed out waiting for the continue message from the media manager. 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. NetBackup cannot delete files unless you are either the user that owns the files, a superuser on UNIX, or an administrator on Windows NT. try here

Error Code 24 In Netbackup

If necessary, reinstall the client software. 2. 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. Was this client working before or first time configuration. 0 Kudos Reply Yes, the client backup was Mack_Disouza Level 4 ‎04-24-2013 03:19 AM Options Mark as New Bookmark Subscribe Subscribe to If necessary, update the server list.

This error should not occur through normal use of NetBackup. Retry the operation and examine the logs. 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. Bpclntcmd Status Code: 28 Top Message: failed trying to fork a process Explanation: A fork of a child process failed (on UNIX) or a CreateProcess failed (on Windows NT).

On Windows NT clients, check the following: o Verify that NetBackup for Windows NT software was installed under a Windows NT administrator account. Verify that the server list specifies the correct master server. For this case, try adding or modifying the CLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT values in the server's /usr/openv/netbackup/bp.conf file. If you cannot determine the cause from the Problems report, create activity log directories for the processes that could have returned this status code.

Recommended Action: Verify that you have read access to the files. Bpclntcmd Pn Verify that the correct file list is specified for this client. 2. Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX). 3.

  • The values on the Network tab are written to the services file when the NetBackup Client service starts.
  • Verify that you have read access to the files.
  • ms 64 bytes from icmp_seq=1.
  • To display this dialog box, start the Backup, Archive, and Restore interface on the client and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on
  • The accept system call timed out after 60 seconds.

Netbackup Error Opening The Snapshot Disks Status 23

Recommended Action: 1. https://vox.veritas.com/t5/NetBackup/Backup-failing-with-error-code-23/td-p/615182 Recommended Action: Free up memory by terminating unneeded processes that consume memory. Error Code 24 In Netbackup Status Code: 22 Top Message: socket close failed Explanation: A socket could not be closed. Netbackup Error Code 25 c.

Retry the operation and check the resulting activity logs. navigate here o On other PC clients except Macintosh, create an activity log directory for bpcd (the bpcd log is created automatically on Macintosh). Check the progress log on the client for messages on why the backup failed. Create/Manage Case QUESTIONS? Clear Host Cache Netbackup

Check the NetBackup All Log Entries report to determine which directory could not be created and why it could not be created. If the backup involves a slave server, verify that these entries are correct on both the master and slave server. On a Windows NT NetBackup server (master or slave), check the Event Viewer Application log for error messages that indicate why the tape mount did not complete. Check This Out Recommended Action: 1.

Recommended Action: Examine the progress log of the archive on the client to determine if you need to retry the archive after correcting the problem. In those instances, code 0 means the backup script that started the backup ran without error. Recommended Action: 1. 1.

Then retry the operation and check the resulting activity logs. 2.

For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem General Error: Status code 23, socket read failed, during client backups or restores, or o On clients, create a bpcd activity log directory (created automatically on Macintosh clients). This can be caused by a network problem or a problem with the process reading from the socket. Writing to a full disk partition.

Status Code: 66 Top Message: client backup failed to receive the CONTINUE BACKUP message Explanation: The client bpbkar process did not receive the message from the server that indicates that the 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. For example, if a NetBackup master server has NetBackup 3.2 and the slave server has NetBackup 3.0. http://windowsazure4j.org/error-code/netbackup-7-1-error-code-23.html Thank You!

Status Code: 5 Top Message: the restore failed to recover the requested files Explanation: There were errors that caused the restore to fail. On Windows NT, verify that the recommended service packs are installed. Retry the operation and examine the resulting logs. 3. If the client software is earlier than 3.0, verify that the client is in a Standard type class.

Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. Status Code: 39 Top Message: client name mismatch Explanation: The name that the client used in a request to the NetBackup server did not match the client name configured in the If you change the server list on a UNIX master server, you must stop and then restart the NetBackup Request daemon (bprd) and NetBackup Database Manager daemon (bpdbm) for the changes Then, create an activity log directory for bpdbm, retry the operation, and check the resulting activity log.

This problem can occur during a backup or a restore. ms ^C ----csbkpms1 PING Statistics---- 6 packets transmitted, 6 packets received, 0% packet loss round-trip (ms) min/avg/max = 0/0/0 [[email protected] - /root ] # ping PING 64 byte packets If virtual memory is the problem, shut down unused applications or increase the amount of virtual memory. Recommended Action: Verify that you have permission to delete the files and that the read-only flag is not set for the files.

Because system requirements vary, we can make no absolute recommendations, other than to use values great enough to provide resources to all applications.