Home > Error Code > Symantec Netbackup Status Codes

Symantec Netbackup Status Codes

Contents

The following are some possible causes: I/O error writing to the file system Write to a socket failed. That storage unit may have more unused capacity now than it did when the job failed. Should I use disk for archives? Status Code: 65 Top Message: client timed out waiting for the continue message from the media manager. http://nodatasource.com/error-code/netbackup-error-codes-pdf.html

The SYSTEM account cannot access network drives. Check for a semaphore problem. Status Code 244 ==================== Status code not available. Perform "Resolving Network Communication Problems" on page 21. 3.

Symantec Netbackup Status Codes

Retry the operation and examine the resulting logs. 5. Status code 40 can also be due to the operator denying a mount request. Recommended Action: Try running wbak by hand to determine the source of the problem.

You could also try -- regardless of whether the system is physical or virtual -- a simple reboot. 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 Status Code 215 ==================== failed reading global config database information During the periodic checking of the NetBackup configuration, nbproxy was unable to read the global configuration parameters. Netbackup Error Codes And Resolution b.

Recommended Action: 1. Netbackup Error Codes And Solutions o Create a bpcd activity log directory (this log is created automatically on Macintosh clients. This error can also occur if the wrong parameters are used when you run a command line. Load More View All Manage Gold standard of data protection methods goes through sea of change Four data copy management misconceptions that affect your business Five common Backup Exec errors and

NetBackup executes client processes with the group ID of the requesting user. Netbackup 7.7 Status Codes Status Code 145 ==================== daemon is already running Another copy of the process is running. 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. On Windows NT and UNIX, check ownership and permission on directories where files will be restored. 3.

  • Status Code 21 ==================== socket open failed A socket was not opened.
  • Status Code: 7 Top Message: the archive failed to back up the requested files Explanation: Errors caused the user archive to fail.
  • If the server is a valid server, verify that it is in the server list on the client.
  • 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).
  • This error is usually due to a mistake in the specification of media IDs for NetBackup catalog backups.
  • Status Code 239 ==================== the specified client does not exist in the specified policy The specified client is not a member of the specified policy.
  • Status Code 32 ==================== could not set group id for process Could not set the group ID of a process to the requesting user group.

Netbackup Error Codes And Solutions

The values on the Network tab are written to the services file when the NetBackup Client service starts. http://backup.technion.ac.il/codes There are a couple of things you can do in this situation. Symantec Netbackup Status Codes If the error occurs during a backup, pay attention to what is being backed up. Netbackup Error Codes Pdf An overloaded network can cause this error. 5.

Status Code 246 ==================== no active policies in the configuration database are of the correct client type A user backup request was not satisfied because no active policies were the type have a peek at these guys See the NetBackup guide that came with the database extension for information on the scripts and troubleshooting logs. Verify that the client and servers are operational and connected to the network. 3. Status Code 132 ==================== user is not validated to use the server from this client None Status Code 133 ==================== invalid request One of two explanations exist. * A request was Veritas Netbackup Error Codes List

court dismisses Symantec lawsuit against Veeam Veritas Backup Exec 16 backs up Microsoft Azure, Windows Server 2016 Commvault CEO: We're ahead of Veritas in data management platform race Load More View Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Status Code 102 ==================== failed closing mail pipe The process that sends mail could not close the pipe to the server. check over here This error can occur because of the following: * No process listening activity occurs on the bpcd port * The number of connections to the bpcd port is more than the

SearchCloudStorage Hitachi Content Intelligence searches, analyzes data Hitachi Content Intelligence, built into Hitachi Content Portfolio object storage, extracts data and metadata from repositories ... Important Error Codes In Veritas Netbackup Status Code 228 ==================== unable to process request An inconsistency exists in the catalog or a request was made that would be improper to satisfy. This error indicates that the client and server were able to initiate communications, but encountered difficulties and the communications did not complete.

Recommended Action: Verify that the requested volume is available and the required device is in an UP state.

Veritas does not guarantee the accuracy regarding the completeness of the translation. Set up activity logging: a. This status code can indicate a drive hardware problem. Netbackup Error Code 1 Status Code 196 ==================== client backup was not attempted because backup window closed A backup or an archive operation that the backup scheduler queued was not attempted because the backup window

Recommended Action: 1. If there are slave servers involved, create a bpbrm activity log directory on them. 4. 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. http://nodatasource.com/error-code/veritas-netbackup-error-codes-list.html Sorry, we couldn't post your feedback right now, please try again later.

Check the permissions on the command to be executed. 3. NetBackup runs client processes as the requesting user. Create bpbrm and bpdbm activity log directories on the server and retry the operation. 4. Status Code 19 ==================== getservbyname failed A call to getservbyname() failed.

If nbjm received a negative error number, status 114 is issued. Recommended Action: 1. Please provide a Corporate E-mail Address. On UNIX, the /usr/openv/netbackup/bp.conf file does not exist.

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 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. o Verify that the Windows NT TCP/IP service specifies the domain server that resolves names for the subnet that contains the NetBackup servers. Status Code 234 ==================== communication interrupted This status code is an intermediate one that usually precedes another status code and is associated with a problem in network communication.

Status Code 254 ==================== server name not found in the NetBackup configuration This error should not occur through normal use of NetBackup. Recommended Action: Try to ping the client from the server. This may be due to: An overloaded system Insufficient swap space or physical memory Too many processes running on the system. Get Symantec's explanation of how to fix this issue.