Home > Netbackup Error > Netbackup Error Code 126

Netbackup Error Code 126

Verify that the client name is correct in: o The NetBackup class configuration on the master server. Compare the NetBackup version level on the server to that on the clients: o On UNIX NetBackup servers and clients, check the /usr/openv/netbackup/bin/version file. On a UNIX master server, add a SERVER = slave_server_name to the bp.conf file. Check the NetBackup Problems report for clues on why the failure occurred. 2. http://nodatasource.com/netbackup-error/netbackup-error-code-233.html

Then, retry the operation and check the resulting activity log. If you are backing up a network drive or a UNC (universal naming convention) path, use the Services application in the Windows NT Control Panel to verify that the NetBackup Client Recommended Action: Change the wildcards in the file list to specify fewer files. Since the backup was successful, you can delete the files that were backed up (or have the system administrator delete the files if you do not have the necessary permissions). https://www.veritas.com/support/en_US/article.000090934

The SYSTEM account cannot access network drives. On a UNIX client, use the ps command to check for a client process that is using too much CPU time. 4. The symptoms of the problem vary.

  1. Status Code: 41 Top Message: network connection timed out Explanation: The server did not receive any information from the client for too long a period of time.
  2. Error Message NB database backup header is too large, too many paths specified Solution Troubleshooting:Run nbemmcmd -listhosts -nbservers -verbose and make sure that NetBackupVersion reflects the correct version of NetBackup on
  3. Enable detailed activity logging: o On the server, create a bpbrm activity log directory.
  4. Check the progress report on the client for a message such as "Script exited with status code = number" (the number will vary).

Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Services Overview On UNIX clients, check the system log (/usr/adm/messages on Solaris) for system problems. 5. Recommended Action: Try running wbak by hand to determine the source of the problem.

A possible cause could be a high network load. Retry the operation and check the resulting activity logs for detailed troubleshooting information. Then, retry the operation and check the resulting activity log. If you cannot determine the cause from the Problems report, create activity log directories for the processes that returned this status code.

If necessary, reinstall the client software. 2. Verify that the server list specifies the correct master server. On Macintosh clients, this code can be due to multiple backups being attempted simultaneously on the same client. Correct problems that you find and retry the restore.

This error should not occur through normal use of NetBackup. Then, create an activity log directory for bpdbm, retry the operation, and check the resulting activity log. On the server, create a bpbrm activity log directory. To increase virtual memory on Windows NT, 98, and 95: a.

Are you running cold catalog backups - I think you are With cold catalog backups you can specify the filelist to backup, I think - in which case you must have have a peek at these guys See the NetBackup guide that came with the database extension for information on the scripts and troubleshooting logs. This can be caused by a network problem or a problem with the process reading from the socket. Writing to a full disk partition. Then retry the operation and check the resulting activity logs. 2.

Perform "Resolving Network Communication Problems" on page 21. 3. Correct the vmd security configuration by adjusting the authentication configuration, the AUTHORIZATION_REQUIRED entry, and SERVER entries. Also, for UNIX, do not place Apollo and standard clients in the same class. check over here NetBackup executes client processes with the group ID of the requesting user.

The SYSTEM account cannot access network drives. Run bpauthsync -vopie on the master server to synchronize the key files on the systems again. Recommended Action: 1.

For UNIX servers, verify that the bpcd port number on the server (either NIS services map or in /etc/services) matches the number in the client's services file. 3.

ERROR The requested URL could not be retrieved The following error was encountered while trying to retrieve the URL: Connection to failed. Check the level of network activity. Check the NetBackup Problems report for clues on where and why the failure occurred. c.

NetBackup cannot delete files unless you are either the user that owns the files, a superuser on UNIX, or an administrator on Windows NT. Status Code: 57 Top Message: client connection refused Explanation: The client refused a connection on the port number for bpcd. If the server is a valid server, verify that it is in the server list on the client. this content Recommended Action: Verify that the server software has been installed correctly on the master server and all slave servers.

This status code is used for a generic system call failure that does not have its own status code. If there are slave servers involved, create a bpbrm activity log directory on them. 4. On a UNIX or Windows NT client, create the bpbkar activity log directory on the client. 2. On the Performance tab, set Virtual Memory to a higher value. 4.

also could you let us know does the backup failure for catalog backups? Status Code: 36 Top Message: failed trying to allocate memory Explanation: Allocation of system memory failed. For detailed debug information: 1. This problem can sometimes be due to a corrupt binary.

Recommended Action: Check the class file list. See the NetBackup Security and Encryption Guide for information on vmd security. a. For this case, add the following to the client's bp.conf file: VERBOSE and as root on the client execute: touch /usr/openv/netbackup/bpbkar_path_tr mkdir /usr/openv/netbackup/logs/bpbkar Then retry the operation.

In some cases, error messages in the NetBackup log indicate a backup failure due to an error in semaphore operation; another symptom is the inability of the NetBackup Device Manager service o On Windows NT NetBackup servers, check the install_path\netbackup\version.txt file or the About NetBackup command on the Help menu.