Home > Error Code > Veritas Netbackup Error Codes

Veritas Netbackup Error Codes


On the server, create a bpbrm activity log directory. SearchDisasterRecovery Dell Services elevates Alabama city's DR plan with the cloud After a massive tornado touched down across the state, the city of Opelika, Ala., looked to the cloud to get Status Code 114 ==================== unimplemented error code This error should not occur. Dell EMC gives the green light for Isilon All-Flash arrays Dell EMC shows off Isilon All-Flash scale-out NAS array at first Dell EMC World; also extends EMC management and data protection http://pdctoday.com/error-code/veritas-netbackup-error-codes-list.php

Girish Sharma 466 views 17:01 Tech Tuesday: Tips & Best Practices for Managing NetBackup Storage Lifecycle Policies - Duration: 1:04:29. Status Code 122 ==================== specified device path does not exist The NetBackup internal catalogs were backed up in the following manner: by using the bpbackupdb command line and by specifying a Status Code 152 ==================== required value not set An incomplete request was made to the bpdbm process (on UNIX), or the NetBackup Database Manager service (on Windows). With a UNIX client, the email was not sent to an email address specified with USEMAIL in the client's bp.conf file.

Netbackup Error Codes And Solutions

Status Code 209 ==================== error creating or getting message queue When a NetBackup process attempts to create an internal message queue construct for inter-process communication, an error occurs. If the file list contains UNC (Universal Naming Convention) names, ensure they are properly formatted. 71 72 73 74 75 76 77 78 Top Status Code: 70 Top We'll send you an email containing your password. If you continue to have problems, perform "Resolving Network Communication Problems" on page 21.

  1. Status Code 60 ==================== client cannot read the mount table The backup process on the client did not read the list of mounted file systems.
  2. Status Code 275 ==================== a session is already running for this vault This error occurs when you start a session for a vault and another session is already running for this
  3. a.
  4. o On NetWare target clients, check the Version entry in the bp.ini file.
  5. If the error occurs during a backup, pay attention to what is being backed up.
  6. It is possible that updates have been made to the original version after this document was translated and published.
  7. TechStorey 6,999 views 9:15 NETBACKUP 7.7.3 - Duration: 17:01.

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 Recommended Action: Check the NetBackup Problems report for clues on where and why the problem occurred. Please visit the Veritas support web site, and refer to Technote number 262225 for further information. 10:09:56.571 [1146] <16> bpbkar Exit: ERR - bpbkar FATAL exit status = 142: file does Netbackup 7.7 Status Codes This error can also occur if the wrong parameters are used when you run a command line.

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 Published on Aug 18, 2015Troubleshooting NetBackup Name Resolution or Communication or Status 58 error. No Yes 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 https://www.veritas.com/support/en_US/article.DOC8599 Sorry, we couldn't post your feedback right now, please try again later.

Recommended Action: 1. 1. Important Error Codes In Veritas Netbackup Possible causes include: * An I/O error occurred during a read from the file system. * Read of an incomplete file or a corrupt file. * Socket read failure. Status Code 283 ==================== error(s) occurred during vault report generation Vault encountered errors during the report generation phase. NetBackup cannot delete files unless you are either the user that owns the files, a superuser on UNIX, or an administrator on Windows NT.

Netbackup Error Codes Pdf

Check the level of network activity. For a regular backup, the volume is automatically set to the SUSPENDED state and not used for further backups. Netbackup Error Codes And Solutions o On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file. Veritas Netbackup Error Codes List A symptom is an entry similar to the following in a NetBackup log (or report) could not allocate enough shared memory If you see this type of message, refer to the

Status Code 35 ==================== cannot make required directory Could not create a required directory. http://pdctoday.com/error-code/wep-error-codes.php Retry the operation and examine the resulting logs. 3. 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 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 Netbackup Error Codes And Resolution

On Windows, the server list contains no entries. Then, retry the operation and check the resulting activity log. This email address is already registered. check over here Create/Manage Case QUESTIONS?

On Windows NT, verify that the recommended service packs are installed. Veritas Netbackup Error Codes Pdf Status Code 218 ==================== failed reading policy database information During the periodic checking of the NetBackup configuration, nbpem did not read the backup policy configuration. If wildcards are used, verify there are matching bracket characters ([ and ]).

Status Code 267 ==================== cannot find the local host name A Vault job obtains the local host name through an OS call.

Check the NetBackup Problems report for clues on where and why the failure occurred. 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 bpcd and bprd settings in 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. Netbackup Error Code 1 Status Code 75 ==================== client timed out waiting for bpend_notify to complete The bpend_notify script on the client takes too long.

This status code is used for a generic system call failure that does not have its own status code. The values on the Network tab are written to the services file when the NetBackup Client service starts. On a Windows NT NetBackup server, set the Verbose option on the General tab in the Master Server Properties dialog box (see "Using the Configure - NetBackup Window" on page 57). this content If you change the server list on a Windows NT master server, stop and then restart the NetBackup Request Manager and NetBackup Database Manager services.

o On UNIX, and Macintosh systems, the master server is the first SERVER entry in the bp.conf file. Status Code: 58 Top Message: can't connect to client Explanation: The server was unable to connect to the client. UNIX: /usr/openv/netbackup/vault/sessions/vault_name/session.last Windows: install_path\NetBackup\vault\sessions\vault_name\session.last Status Code 266 ==================== cannot find robot, vault, or profile in the vault configuration NetBackup cannot find the specified profile name or triplet robot_name/vault_name/profile_name on the Vault