cancel
Showing results for 
Search instead for 
Did you mean: 

Veritas NetBackup Most Common Status Codes

dulda
Level 3

Veritas NetBackup most common status codes and recommended actions according to Reference Guide:

Status Code 48: client host name could not be found

Explanation: The system function gethostbyname() failed to find the client's host name.

 Recommended Action: Verify that the client name is correct in the following:

  • The NetBackup policy configuration on the master server.
  • The General tab in the following dialog boxes: NetBackup Client Properties and Specify NetBackup Machines and Policy Type (on Microsoft Windows non-target clients). To display these dialog boxes, start the Backup, Archive, and Restore interface on the client. For the General tab, click NetBackup Client Properties on the File menu; click Specify NetBackup Machines and Policy Type on the File menu.
  • The bp.conf file on UNIX and Linux clients.
  • On clients and servers, verify that the name service is set up to resolve the NetBackup client names correctly.
    On UNIX clients, verify that the client's host name is in the /etc/hosts file or the YP hosts file or NIS maps.

Status Code 58: can't connect to client

Explanation: The server was unable to connect to the client.

Recommended Action: Resolve network communication problems.

See "Resolving network communication problems" in the NetBackup Troubleshooting Guide.

Status Code 4239: Unable to find the virtual machine

Explanation: A backup or an archive operation that the backup scheduler queued was not tried because the backup window was no longer open.

Recommended Action: Do the following, as appropriate:

  • If possible, change the schedule to extend the backup window for this combination of policy and schedule so it does not occur again.
  • If the backup must be run, use the Manual Backup command on the Policy menu in the Backup Policy Management window to perform the backup. Manual backups ignore the backup window.

Status Code 196: client backup was not attempted because backup window closed

Explanation: A backup or an archive operation that the backup scheduler queued was not tried because the backup window was no longer open.

Recommended Action: Do the following, as appropriate:

  • If possible, change the schedule to extend the backup window for this combination of policy and schedule so it does not occur again.
  • If the backup must be run, use the Manual Backup command on the Policy menu in the Backup Policy Management window to perform the backup. Manual backups ignore the backup window.

Status Code 2: none of the requested files were backed up

Explanation: A backup or archive did not back up any of the files in the file list.

This status code applies primarily to automatic backups using Lotus Notes or SQL Server database agents, when all the backups that are job-related have failed. Or, an Enterprise Vault backup has failed. It should not occur for standard file system backups.

Open a NetBackup support case (as recommended in technical note TECH38838) if you encounter this error for a UNIX, Linux, or Windows file system backup, or for database agents other than SQL Server or Lotus Notes.

Recommended Action: Do the following, as appropriate:

  • The following information applies only to Lotus Notes:
    This error occurs when archive style logging is not enabled for the Lotus Domino server on UNIX. It also occurs when another backup of the transaction logs is in progress.
  • For troubleshooting guidance, such as a list of logs to gather, and for details on particular issues, refer to technical note TECH38838.

Status Code 129: Disk storage unit is full

Explanation: As NetBackup writes to the file system for the disk storage unit, runs out of space. Until more file system space is available, images of similar size or larger may fail with this error when written to this disk storage unit.

In a scheduled backup job that writes to a storage unit group (which contains this disk storage unit), the following occurs: the NetBackup scheduler requests the storage unit with the greatest available capacity when the job is retried.

For the retry, when the scheduler requests the storage unit with the greatest available capacity, note the following:

  • A tape storage unit in the storage unit group has preference over any disk storage units since tape storage units usually have more capacity.
  • If the storage unit with the most unused capacity is busy, NetBackup skips it. NetBackup then selects an available storage unit with the next largest, unused capacity.
  • If the storage unit with the greatest unused capacity is the one that lacked capacity when the job first failed, the scheduler tries it again. That storage unit may have more unused capacity now than it did when the job failed.

Recommended Action: Do the following, as appropriate:

  • Either free sufficient space or add more space to the file system for this storage unit.
  • Lower the high capacity mark for this disk storage unit. Configure the policies to access it through a storage unit group that provides alternative storage to use when this storage unit fills up. Ideally, if an image exceeds the file system's high capacity mark, it also completes successfully. This image leaves the storage unit in a full state (over the high capacity mark). The storage unit then is not assigned to other jobs until its capacity falls under its high capacity mark.
  • If the Staging attribute is set on the disk storage unit that did not have enough capacity, it may be unable to create free space. It cannot create space because the backups that are staged to the disk are not relocated (eligible to be deleted from the staging storage unit). Ensure that staging's relocation (duplication) jobs successfully copy enough images to provide sufficient free space for new backups.

Status Code 40: network connection broken

Explanation: The connection between the client and the server was broken. This status code can also appear if the connection is broken between the master and the media server during a backup.

Recommended Action: Do the following, as appropriate:

  • Try pinging the client from the server. If pinging is not possible, check for loose connections or other network problems.
  • Verify that the server list settings are correct on both the client and the server. If the backup involves a media server, verify that these entries are correct on both the master and the media server. For example, if a media server does not have a server list entry for the master, it does not accept connections from the master.
    • On Windows, the master server is designated on the Servers tab in the Master Server Properties dialog box.
      See "Using the Host Properties window to access configuration settings" in the NetBackup Troubleshooting Guide.
    • On UNIX and Linux systems, the master server is the first SERVER entry in the bp.conf file.
  • If you change the server list on a UNIX or Linux master server, you must stop and restart the NetBackup Request daemon (bprd) and NetBackup Database Manager daemon (bpdbm) in order for the changes to take effect. On Windows, stop and restart the NetBackup Request Manager and NetBackup Database Manager services.
  • Status code 40 can also be due to denial of a mount request by the operator.
  • This status code may occur if nbjm was unable to connect to bpbrm or to bpmount. Examine the nbjm unified log (originator ID 117) or the bpbrm or the bpmount legacy logs for more detail on the cause of the error.

Status Code 84: media write error

Explanation: The system's device driver returned an I/O error while NetBackup wrote to removable media or a disk file.

Recommended Action: Do the following, as appropriate:

  • For NetBackup Snapshot Client only:
    If the following message appears in the /usr/openv/netbackup/bptm log, and the values for key, asc, and ascq are all zero (0x0) as shown in this example message:
    tape error occurred on extended copy command, key = 0x0, asc = 
  • 0x0, ascq = 0x0
    NetBackup Snapshot Client probably does not support your host-bus adapter and its driver. The host-bus adapters that are supported in the release are listed in the NetBackup Release Notes.
  • For additional information, check the following:
    • NetBackup Problems report to determine the device or media that caused the error
    • System and error logs for the system (UNIX)
    • Event Viewer Application and System logs (Windows)
  • If NetBackup writes backups to a disk file, verify the following: The fragment size that is configured for the disk storage unit is not greater than the maximum file size that the operating system specifies.
  • On Windows, make sure that the tapes are not write protected.
  • If bpbackupdb was used to back up the NetBackup catalog to a disk path on a UNIX or Linux system, the image you try to write may be greater than the maximum file size that is specified by that operating system. Tape files do not have this limit. You may have to back up the catalog to tape.
  • If the media is tape, check for the following:
    • A defective or a dirty drive. Clean it or have it repaired (refer to the tpclean command for robotic drives).
    • The wrong media type. Verify that the media matches the drive type you use.
    • Defective media. If it is defective, use the bpmedia command to set the volume to the FROZEN state so it is not used for future backups.
    • Incorrect drive configuration. Verify the Media and Device Management and system configuration for the drive.
      For example, on UNIX the drive may be configured for fixed mode when it must be variable mode.
      See the NetBackup Device Configuration Guide for more information.
      This configuration often results in the media being frozen with the message
      too many data blocks written, check tape and drive block size 
    • configuration
      See "Frozen media troubleshooting considerations" in the NetBackup Troubleshooting Guide.

Status Code 42: network read failed

Explanation: An attempt to read data from a socket failed.

Recommended Action: Do the following, as appropriate:

  • Verify that both the client and the server are operational.
  • Resolve any network communication problems.
    See "Resolving network communication problems" in the NetBackup Troubleshooting Guide.
  • Check the Problems report for clues.

Status Code 156: snapshot error encountered

Cause
This could indicate that the client is using Windows Open File Backups to protect open or active files. The volume "snapshot" that occurs to facilitate open file backup has failed. This failure is often caused by the VSS cache file running out of allocated space.

Solution
Open file backups are not desired for the client, disable them. This will decrease the resources used by the client during backup and resolve any Status 156 errors. The default NetBackup install options are to have open file backups enabled.

To confirm if VSS open file backups are activated:
Within the NetBackup Administration Console, expand Host Properties in the right hand pane
Within Host Properties, click Master Server and then the double-click the name of the Master Server in the right pane
Click on the Client Attributes section
If the client in question is listed here, click on the client name. If it is not listed, add and click on the client name.
Click the Windows Open File Backup tab
Ensure that Enable Windows Open File Backups for this client is not selected if open file backups are not required

Another issue related to snapshot creation could be the size limit of Shadow Copies configured on the local drive.

For Volume Shadow Copy (VSS):
Use the following steps to increase the cache size when VSS is used on Windows 2003 Server clients.

In Windows, right-click on the required local drive and select Properties
In the pop up windows, click on Shadow Copies, select the appropriate drive letter, and then settings.
In the Settings dialog box, change the Maximum Size setting to either No Limit or a size large enough to suit the requirements of the installation and usage of VSS
The below screenshot is an example of setting the desired value in the size box in MB.

You can find an extended version of this article in the attached file.  Thanks for reading.

0 REPLIES 0