Home > Failed To > Failed To Execute Command Usr Openv Netbackup Bin Bptm

Failed To Execute Command Usr Openv Netbackup Bin Bptm

To increase the amount of information that appears in the logs, see the logging topics in Chapter 3, "Using the Logs and Reports." On the master server create bpsched and bpbrm On all but Macintosh clients, enable bpcd activity logging as follows: Create a bpcd activity log directory on the client. To display this dialog box, start the Backup, Archive, and Restore interface on the server and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on On a UNIX system, check that /etc/services and NIS services map (if applicable) have entries for the NetBackup services: bpcd, bpdbm, and bprd. have a peek here

Also, check the All Log Entries report on the server. On UNIX clients, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file. On a UNIX NetBackup server, if you see a status code without its associated message text, you can determine the message by using the bperrcode command: /usr/openv/netbackup/bin/goodies/bperrcode [error_code] Where error_code is On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports." Retry the operation and examine the resulting https://www.veritas.com/support/en_US/article.000081783

This error can occur when a master and its slave servers or a master server and a client have different levels of NetBackup installed. 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. On UNIX clients, verify that the client's host name is in the /etc/hosts file or the YP hosts file or NIS maps. Create a bpcd activity log directory (this log is created automatically on Macintosh clients.

If the bpbrm log has entries similar to the following: bpbrm hookup_timeout: timed out waiting during the client hookup bpbrm Exit: client backup EXIT STATUS 41: network connection timed out then You may also refer to the English Version of this knowledge base article for up-to-date information. On a Windows NT system, verify that the %SystemRoot%\system32\drivers\etc\services file shows the correct entries for the NetBackup internet processes: bpcd, bpdbm, and bprd. For detailed debug information: Create a bptm activity log directory on the server.

On Windows NT, verify that the %SystemRoot%\system32\drivers\etc\services file has the correct entries for bpcd, bpdbm, and bprd. If that is not the problem and you need more information: On UNIX and Windows NT clients, enable bpbkar activity logging. If you continue to have problems, review "Resolving Network Communication Problems" on page 21 and "Verifying Host Names and Services Entries" on page 31. If virtual memory is the problem, shut down unused applications or increase the amount of virtual memory.

If you enable debug logs, you can see this error in the bptm log. The SYSTEM account cannot access network drives. Status Code: 22 Message: socket close failed Explanation: A socket could not be closed. Also, verify that the NetBackup Client Service Port Number and NetBackup Request Service Port Number on the Network tab in the NetBackup Configuration dialog box match the settings in the services

Verify that the tape is not a cleaning tape that is configured as a regular volume. I have a link of /usr/openv/netbackup/db/images pointing to /u030/netbackup/db/images on both PRODUCTION and DR server. Use your system's ps command and monitor CPU utilization to help decide which of the above conditions exist. Also, verify that the server or Windows NT administration client has a server list entry on the master server.

You may also refer to the English Version of this knowledge base article for up-to-date information. navigate here Status Code: 13 Message: file read failed Explanation: A read of a file or socket failed. Status Code: 49 Message: client did not start Explanation: The client failed to start up correctly. 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.

On Windows NT, check the Event Viewer Application log for error messages that indicate why the tape mount did not complete. If the problem is not serious and the files were backed up, you can manually delete the files. On Windows NT, 98, and 95 systems, the master server is designated as Current on the Servers tab in the NetBackup Configuration dialog box. Check This Out On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX).

Create/Manage Case QUESTIONS? Double-click System. 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.

CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical

Correct problems that you find and retry the restore. Increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports." Retry the backup and examine the resulting logs to determine Corrupt binaries are one possible cause for this error. Recommended Action: Try running wbak by hand to determine the source of the problem.

On Macintosh clients, check the inetd and bpcd activity logs. Recommended Action: Check the class file list. If this is the case then editing the catalog DR file by replacing the Site A media server used for backup with Site B master server name, you can run the this contact form On UNIX clients, check for core files in the / directory.

Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. Then, retry the operation and check the resulting activity log. On a UNIX client, use the ps command to check for a client process that is using too much CPU time. Recommended Action: Execute a df to see if the system can read the mount table.