The names of the files are logged in the activity log file in the /usr/openv/netbackup/logs/bpbkar directory before bpbkar processes them. Status Code: 9 Message: an extension package is needed but was not installed Explanation: A NetBackup extension product is required in order to perform the requested operation. If possible, increase the size of the cache partition. o •The bpbkar client process is hung on a file that has mandatory locking set. Source
o On UNIX, and Macintosh systems, the master server is the first SERVER entry in the bp.conf file. Verify that there is space in the file system that contains the NetBackup databases. 3. If necessary, update the server list. On Windows NT, verify that the recommended service packs are installed.
Recommended Action: 1.Â Â Â Â Â Examine the progress log on the client for messages on why the restore failed. Recommended Action: 1. 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
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 - Status Code: 31 Top Message: could not set user id for process Explanation: Could not set the user ID of a process to that of the requesting user. Recommended Action: 1.Â Â Â Â Â Check the NetBackup Problems report for clues on where and why the failure occurred. Verify that the client IP address is correct in the name service that is being used.
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. Veritas does not guarantee the accuracy regarding the completeness of the translation. The default for the CLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT is 300 seconds if unspecified. https://vox.veritas.com/t5/NetBackup/Restore-failed-with-25-for-windows-2008-client/td-p/451147 The system returned: (22) Invalid argument The remote host or network may be down.
Recommended Action: Verify that the files exist and you have read access to them. · On UNIX clients, check to see if the files or directories would be excluded because of Not the answer you're looking for? 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 On Sun Solaris, verify that all operating system patches are installed (see the Operating Notes section of the NetBackup Release Notes - UNIX). 5.
Recommended Action: Try the backup again. http://orkut.google.com/c42551282-tdf8ad8822dae4932.html If NetBackup is under another type of account, reinstall it under an administrator account. If the problem is not serious and the files were backed up, you can manually delete the files. Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred.
Recommended Action: 1. http://birdsallgraphics.com/error-bpbrm/error-bpbrm-pid.php Check the level of network activity. Are normal backups working for this client? On Macintosh clients, check the inetd and bpcd activity logs.
Direct the output of the wbak command to /dev/null to avoid filling up your file system and use the following parameters: -l -nhi -pdtu -stdout -nwla and -full or -af date Such an increase in response time is typically seen in environments with volume databases containing over 25000 pieces of media or issues with network communications with the media servers, and can Status Code: 27 Top Message: child process killed by signal Explanation: A child of the process reporting this error was killed. have a peek here Check the NetBackup Problems report for clues on why the failure occurred. 2.
An overloaded network can cause this error. 5. Enable detailed activity logging: o Create a bpbkar activity log directory (UNIX or Windows NT only). Heathrow to Gatwick and traffic jam Can Homeowners insurance be cancelled for non-removal of tree debris?
If you cannot determine the cause from the Problems report, create activity log directories for the processes that returned this status code. On UNIX clients, use the UNIX sum command to check the bpcd, bpbkar, and tar binaries, located in /usr/openv/netbackup/bin on the client. Also, see "Verifying Host Names and Services Entries" on page 31. 4. For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code.
Verify that software is installed on the client and it is the correct version. Some possible solutions are: oÂ Â Â Â Â Â Â Adjust the backup schedules. Kindly suggest ... Check This Out Recommended Action: 1.Â Â Â Â Â Verify that the correct version of software is running on the client and the server. 2.Â Â Â Â Â Enable detailed activity logging: oÂ Â Â Â Â Â Â On the server, create a bpbrm activity
The SYSTEM account cannot access network drives. This could be caused by the system being overloaded with too many processes and there is not enough physical and virtual memory. A socket read failure can be caused by a network problem or a problem with the process that is writing to the socket. This problem can also occur if a NetBackup process was terminated through Task Manager or another utility.
Chances are this is a known problem http://www.symantec.com/business/support/index?page=content&id=TECH77071 An Emergency Engineering Binary (EEB) to enable Oracle 11.2 for NetBackup 6.5.5 is available at the following link: http://support.veritas.com/docs/346033 For NetBackup 6.5.4: http://support.veritas.com/docs/346592 A socket read failure can be caused by a network problem or a problem with the process that is writing to the socket. What should I do? The values on the Network tab are written to the services file when the NetBackup Client service starts.
Or, if multiple backups are using the same cache, either reduce the number of concurrent backups by rescheduling some of them or reschedule the entire backup to a time when the To verify which files were backed up, use the NetBackup client-user interface in restore mode and browse the files in the archive. Correct problems that you find and retry the restore. o On NetWare target clients, check the Version entry in the bp.ini file.
The getservbyname() function uses the name of the service to find a service entry in the services file (or NIS services map on UNIX if it is configured). 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. On a UNIX or Windows NT client, create the bpbkar activity log directory on the client. 2. Recommended Action: 1.
Note: Also, use the above procedure for other, "unknown" bpbkar hangs. c. o The bp.ini file on OS/2 and NetWare target clients. 2.