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 Recommended Action: Verify that the class type attribute for the class is correct. Recommended Action: Check the NetBackup Problems report for clues on where and why the problem occurred. o Set the NetBackup global attribute, Maximum Jobs Per Client, to 1 (note that this limits all clients in all classes). 4. have a peek here
Examine the resulting activity log file for detailed troubleshooting information. 4. To increase the amount of information that appears in the logs, see the logging topics in Chapter 3, "Using the Logs and Reports." 2. o Check the inetd log to see if NetBackupListen is running. However, the most common cause of this error is a host name resolution problem. https://vox.veritas.com/t5/Backup-Recovery-Community-Blog/Netbackup-does-not-have-the-service-BPRD-operating-Error-25/ba-p/789783
o On NetWare target clients, check the Version entry in the bp.ini file. Status Code: 45 Top Message: request attempted on a non reserved port Explanation: An attempt was made to access a client from a nonreserved port. If the preceding steps do not resolve this problem, see "Resolving Network Communication Problems" on page 21. 61 62 63 64 65 66 67 68 69 Top Status Code: 60 Create a bpbkar activity log directory.
Status Code: 65 Top Message: client timed out waiting for the continue message from the media manager. Because system requirements vary, we can make no absolute recommendations, other than to use values great enough to provide resources to all applications. If NetBackup is under another type of account, reinstall it under an administrator account. If you continue to have problems, perform "Resolving Network Communication Problems" on page 21.
Recommended Action: 1. Status Code: 32 Top Message: could not set group id for process Explanation: Could not set the group ID of a process to the requesting user group. 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, 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: 56 Top Message: client's network is unreachable Explanation: The server got ENETUNREACH when trying to connect to the client. Then, retry the operation and check the resulting activity log. Recommended Action: Change the wildcards in the file list to specify fewer files. Then, retry the operation and check the resulting activity log.
The bpcd process compares NetBackup server list entries to the peername of the server attempting the connection and rejects the connection if the names are different. This can occur because the permissions of the command do not allow it to be executed, or there is lack of system resources such as memory and swap space. get_num_avail_drives: readline failed: socket read failed (23) get_stunits: get_num_avail_drives failed with stat 23 Loading a fresh bptm from the install media resolved the problem. 3. On Macintosh clients, check the inetd and bpcd activity logs.
Recommended Action: 1. On a Windows NT NetBackup server, set the Verbose option on the Troubleshooting tab in the NetBackup Configuration dialog box. For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log. One customer running both NetBackup and ORACLE on their Solaris server made the following changes to their /etc/system file and then rebooted the system (boot -r); the changes were found to
On aWindows master server, verify that the NetBackup Request Manager and NetBackup Database Manager services are running. On UNIX clients, check the system log (/usr/adm/messages on Solaris) for system problems. 5. Check the NetBackup Problems report for clues on where and why the failure occurred. Status Code: 21 Top Message: socket open failed Explanation: A socket open failed.
Close Box Join Tek-Tips Today! If it does, rerun the backup. The symptoms of the problem vary.
For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. This could be caused by the system being overloaded with too many processes and there is not enough physical and virtual memory. On a UNIX NetBackup master server, verify that the bprd and bpdbm processes are running. On Windows, verify that the %SystemRoot%\system32\drivers\etc\services file has the correct entries for bpcd, bpdbm, and bprd.
nbjm is unable to connect to bpcd on the media server nbpem is unable to connect to nbproxy bptm on the media server is unable to connect to nbjm on the Status Code: 72 Top Message: the client type is incorrect in the configuration database Explanation: The class type attribute in the class configuration indicates that the client is one type, but Verify that the client name is correct in: o The NetBackup class configuration on the master server. Recommended Action: 1.
Recommended Action: First, verify that the server did not crash. Recommended Action: 1. On a UNIX NetBackup server, add the VERBOSE option to the bp.conf file. Verify that the client IP address is correct in the name service that is being used.
Examine other activity logs or the progress log on the client. 7. If these logs do not provide a clue, create a bpbrm activity log on the server, retry the operation again, and check the resulting activity log. TIBCO SoftwareUsing Virtualization Technique to Increase Security and Reduce Energy Consumption in Cloud Computing QualiQode v. If you've already registered, sign in.
On a UNIX client, use the ps command to check for a client process that is using too much CPU time. 4. Invensys SystemsQualiQode v. b. o If you cannot view the report, or you get a cannot connect on socket error when trying to view it, verify again that the NetBackup Database Manager daemon (or service)
Recommended Action: 1. The following are some possible causes: · I/O error writing to the file system · Write to a socket failed. Recommended Action: If the server is a valid server, add its name to the client's server list: · On Windows NT, 98, and 95 clients, add the server on the Servers Recommended Action: 1.
Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! This error should not occur through normal use of NetBackup. Next message: [Veritas-bu] Admin console can't connect locally... If these services are not running, start them.
We are running NetBackup 5.1 on a Windows 2000 server. To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57). Possible causes are: · A process does not have permission to create the directory · The path to the directory is not valid · An IO error occurs · There was