Veritas Status Codes and Messages

maping

Status Code: 151
Message: Backup Exec operation failed

Explanation: The Global Data Manager console has reported that a Backup Exec job (backup, archive, or restore) did not complete normally.

Recommended Action: Consult the Backup Exec job history on the Backup Exec server for details.

Status Code: 152
Message: required value not set

Explanation: An incomplete request was made to the bpdbm process (NetBackup Database Manager service on Windows NT). This usually occurs because different versions of software are being used together.

Recommended Action:

1. Verify that all software is at the same version level.

2. For detailed troubleshooting information, create bpdbm and admin activity log directories and retry the operation. Check the resulting activity logs.

Status Code: 153
Message: server is not the master server

Explanation: This status code is reserved for future use.

Recommended Action: None.

Status Code: 154
Message: storage unit characteristics mismatched to request

Explanation: A backup was attempted and the storage unit selected for use had characteristics that were not compatible with the backup type.

Recommended Action:  Verify that the characteristics of the storage unit involved are appropriate for the backup attempted:

• For an NDMP class type, verify that a storage unit of type NDMP is defined and the NDMP host value matches the host name of the client. For example, if the NDMP class specifies toaster as the client, the configuration for the storage unit must specify toaster as the NDMP host.

• For a class type other than NDMP, verify that the class specifies a Media Manager or Disk type storage unit.

Status Code: 158
Message: failed accessing daemon lock file

Explanation: The process could not lock its lock file because an error was received from a system call. This lock file synchronizes process activities (for example, preventing more than one daemon from executing at a time).

Recommended Action:

1. Examine the NetBackup error log to determine why the system call failed and correct the problem. It could be a permission problem.

2. If the error log does not show the error, create an activity log directory for bprd, bpdbm, or bpsched (depending on which process encountered the error) and retry the operation. Examine the resulting activity log.

Status Code: 159
Message: licensed use has been exceeded

Explanation: This status code is reserved for future use.

Recommended Action: None.

Status Code: 160
Message: authentication failed

Explanation: A problem was encountered when two systems were attempting to authenticate one another.

Recommended Action:  See the NetBackup System administrator's Guide - UNIX for more information on the files and commands mentioned here.

1. Ensure that the authentication libraries exist:

Windows NT, 98, 95:

install_path\NetBackup\lib\libvopie.dll

install_path\NetBackup\lib\libnoauth.dll

UNIX (except HP-UX):

/usr/openv/lib/libvopie.so

/usr/openv/lib/libnoauth.so

UNIX (HP-UX only):

/usr/openv/lib/libvopie.sl

/usr/openv/lib/libnoauth.sl

Macintosh:

:System Folder:Extensions:libvopie.dll

:System Folder:Extensions:libnoauth.dll

2. Check the methods_allow.txt files on the systems that are having problems to ensure that authentication is enabled. The files are in the following locations:

Windows NT, 98, 95:

install_path\NetBackup\var\auth

UNIX:

/usr/openv/var/auth

Macintosh:

:System Folderreferences:NetBackup:var:auth

3. On the systems that are having the authentication problem, remove the remote host that is not being authenticated from the methods_allow.txt file.

For example, if hosta and hostb are having the problem, remove hosta from the file on hostb and vice versa.

Retry the operation.

• If the problem still exists, it indicates connection problems not related to authentication.

• If connections are now successful, proceed to the next step.

4. Execute bpauthsync -vopie on the master server to resynchronize the key files on the systems.

On Windows NT:

install_path\NetBackup\bin\admincmd\bpauthsync -vopie -servers

-clients

On UNIX:

/usr/openv/netbackup/bin/admincmd/bpauthsync -vopie -servers

-clients

5. Add back the names removed in step 3 and retry the operation.

6. Create activity log directories for the processes involved in authentication between NetBackup systems. These include:

• On the server, create activity log directories for bprd, bpdbm, bpcd.

• On the client, create activity log directories for bpbackup, bprestore,

bpbkar (Windows NT only).

Retry the operation and check the logs.

Status Code: 164
Message: unable to mount media because it is in a DOWN drive or misplaced

Explanation: A restore was attempted and the volume required for the restore was in a DOWN drive in a robot. Or, the slot that should contain the volume is empty.

Recommended Action:

• If volume is in a DOWN drive, remove it and place it in its designated slot. Then, retry the restore.

• If the volume is in the wrong slot, use a robot inventory option to reconcile the contents of the robot with the Media Manager volume configuration.

Status Code: 165
Message: NB image database contains no image fragments for requested backup id/copy number

Explanation: A restore was attempted and NetBackup has no record of fragments associated with the backup ID that has the files.

Recommended Action: Check the NetBackup Problems report for additional information about the error. For detailed troubleshooting information, create an activity log directory for either bpdm or bptm (whichever applies) and retry the operation. Check the resulting activity log.

Status Code: 166
Message: backups are not allowed to span media

Explanation: An end of media (EOM) was encountered while the backup image was being written. The backup was terminated because the NetBackup DISALLOW_BACKUPS_SPANNING_MEDIA option was present in bp.conf on UNIX or the registry on Windows NT. The backup will be retried automatically with a different volume if this is allowed by the backup tries attribute in the NetBackup global attribute configuration.

Recommended Action: None.

Status Code: 167
Message: cannot find requested volume pool in Media Manager volume database

Explanation: A backup to a nonrobotic drive was attempted and the tape manager (bptm) could not find or add the specified volume pool.

Recommended Action: Verify the Media Manager volume configuration.  Check the NetBackup Problems report for more information about the error.  For detailed troubleshooting information, create a bptm activity log directory and retry the operation. Check the resulting activity log.

Status Code: 168
Message: cannot overwrite media, data on it is protected

Explanation: A database backup was attempted to a volume that could not be overwritten because it contains data that NetBackup, by default, does not overwrite (tar, cpio, ANSI, and so on).

Recommended Action: Replace the volume with a new one or set the NetBackup ALLOW_MEDIA_OVERWRITE option to the appropriate value.

Status Code: 169
Message: media id is either expired or will exceed maximum mounts

Explanation: A backup or database backup was attempted and the volume selected for use has reached its maximum number of mounts as specified in the Media Manager volume configuration. For a regular backup, the volume is automatically set to the SUSPENDED state and not used for further backups.  For a NetBackup database backup, the operation terminates abnormally.

Recommended Action: If the volume was suspended, wait until it expires and then replace it. For NetBackup database backups, replace the media.

Status Code: 171
Message: media id must be 6 or less characters

Explanation: An operation, such as using bpmedia to suspend or freeze a media ID was attempted and the media ID specified was longer than six alpha-numeric characters.

Recommended Action: Retry the command with a valid media ID.

Status Code: 172
Message: cannot read media header, may not be NetBackup media or is corrupted

Explanation: When loading a volume for a backup or restore, the tape manager (bptm), did not find the expected tape header. This can mean that a volume in a robotic device is not in the slot number shown in the Media Manager volume configuration or that a read error (I/O error) occurred.

Recommended Action:

1. If the volume is in a robot that supports barcodes, verify the robot contents by using a Media Manager robot inventory option.

2. If the volume was mounted on a nonrobotic drive, verify that the correct volume was mounted and assigned.

3. Check the NetBackup Problems report. If a fatal read error occurred, attempt the operation again using another drive, if possible.

Status Code: 173
Message: cannot read backup header, media may be corrupted

Explanation: When searching for a backup image to restore, the tape manager (bptm) could not find the correct backup ID at the position on the media where NetBackup expected it to be. This can indicate a drive hardware problem.

Recommended Action:

1. Check the NetBackup Problems report for clues as to what caused the error.

2. Try the restore on another drive if possible.

3. For detailed troubleshooting information, create an activity log directory for bptm and retry the operation. Check the resulting activity log.

Status Code: 174
Message: media manager system error occurred

Explanation: An abnormal condition occurred causing a tape manager (bptm) or disk manager (bpdm) failure. This should not occur under normal circumstances.

Note: If this occurs on a Sequent platform and you are attempting to back up more than four gigabytes of data, save all your logs and call VERITAS technical support. For other platforms perform the recommended actions described below.

Recommended Action:

1. Check the NetBackup Problems report to see if it shows the cause of the problem. If you see a Problems report message similar to "attempting to write 32767 bytes, not a multiple of 1024" save all logs and call VERITAS customer support.

2. On UNIX, if this occurs during a restore, it may be that the tape drive is incorrectly configured to write in fixed length mode when it should write in variable length mode.

Verify your drive's configuration, comparing it to what is recommended in the Media Manager Device Configuration Guide (also see Step 7 of this procedure).

If your configuration incorrectly specifies fixed length mode, change the configuration to specify variable length mode and suspend media that were written on that device. The images written to those media may be restorable (this is platform dependent), but single file restores are almost guaranteed to fail.

3. If you see the problem with only one client, verify that the client binaries are correct, especially those for bpcd.

4. Can you read or write any other images on this media?

If so, the check the following reports for clues:

• Images on Media report

• Media Contents report

5. Verify the following:

• The media by using the NetBackup image verify option.

• That you are using the correct media type for the device.

6. Check the system or console log for errors (on UNIX) or the Event Viewer Application log (on Windows NT).

7. For detailed debug information, create an activity log directory for either bptm or bpdm (whichever applies) and retry the operation. Check the resulting activity log.

If the bptm activity log shows an error similar to

00:58:54 [2304] <16>; write_data: write of 32768 bytes indicated only 29696 bytes were written, errno = 0

it may be that the tape drive is configured to write in fixed length mode rather than variable length mode, and the image being written encountered the end-of-media.

Take the corrective action suggested in Step 2.

Status Code: 175
Message: not all requested files were restored

Explanation: When restoring files from an image, the bptm or bpdm process detected a fatal error condition and terminated the restore before it completed.  This should not occur under normal circumstances.

Recommended Action:

1. Check the NetBackup Problems report and the progress log on the client for additional information about the error

2. For detailed troubleshooting information, create an activity log directory for either bptm or bpdm (whichever applies) and retry the operation. Check the resulting activity log.

Status Code: 176
Message: cannot perform specified media import operation

Explanation: The tape manager (bptm) detected an error condition when attempting to import a specific backup image. Possible reasons for this are:

• Media ID is already active in the NetBackup media database on this server

• Media ID is not in the Media Manager volume configuration

•Fatal t ape manager ( bptm) error occurred

• Total image was not obtained from Phase 1 of import

Recommended Action:

1. Check the NetBackup Problems report to find the exact cause of the failure.

2. Try the following:

• If the media ID is already active, duplicate all images on the original media ID to another volume. Then, manually expire the original media and redo the import.

• If the media ID is not present in the Media Manager volume configuration, add it.

• If a fatal bptm error occurred, verify that the Media Manager volume daemon (vmd) is active on UNIX or the NetBackup Volume Manager service is active on Windows NT.

• If the entire image is not present, perform import phase 1 on the media IDs that have the remainder of the image.

Status Code: 177
Message: could not deassign media due to Media Manager error

Explanation: The tape manager (bptm) could not successfully deassign a media ID.

Recommended Action:

1. Check the NetBackup Problems report for the cause of the problem.

2. Verify that the Media Manager volume daemon (vmd) is active on UNIX or the NetBackup Volume Manager service is active on Windows NT.

3. For detailed troubleshooting information, create an activity log directory for bptm and retry the operation. Check the resulting activity log.

Status Code: 178
Message: media id is not in NetBackup volume pool

Explanation: NetBackup attempted a backup of its databases and the media ID specified for the database backup was not in the NetBackup volume pool.  Volumes for database backups must be in the NetBackup volume pool.

Recommended Action: Check the Media Manager volume configuration to verify that the media IDs are present and in the NetBackup volume pool.

Status Code: 179
Message: density is incorrect for the media id

Explanation: An operation such as "list contents" was attempted on an invalid media ID, such as a cleaning tape. Another possibility is that a media ID in the NetBackup database backup configuration does not match the media type entered in the Media Manager volume configuration.

Recommended Action: Check the volume configuration and the NetBackup database backup configuration and correct any problems found.

Status Code: 180
Message: tar was successful

Explanation: tar returned a successful exit status.

Recommended Action: None.

maping

Status Code: 181
Message: tar received an invalid argument

Explanation: One of the parameters passed to tar was not valid. Recommended Action:

On a UNIX client:

• Ensure that the tar command in /usr/openv/netbackup/bin is the one provided by NetBackup. If you are in doubt, reinstall it.

•Check /usr/openv/netbackup/bin/version on the client to verify that the client is running the correct level software. If the software is not at the correct level, update the software per the directions in the NetBackup release notes.

On a Windows NT client, create a tar activity log directory, retry the operation, and check the log.

On a Macintosh client, check the version file that is in the bin folder in the NetBackup folder in the Preferences folder. If the software is not at the correct level, install the correct software as explained in the installation guide.

Status Code: 182
Message: tar received an invalid file name

Explanation: tar cannot write to the file that is specified with the -f parameter.

Recommended Action:

1. Create a bpcd activity log directory on the client (on a Macintosh NetBackup creates the log automatically).

2. On a Windows NT client, create a tar activity log directory.

3. Increase the logging level on the client:

• On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file.

• On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

4. Rerun the operation, check the resulting activity logs for the parameters passed to tar and call customer support.

Status Code: 183
Message: tar received an invalid archive

Explanation: The data passed to tar was corrupt.

Recommended Action:

• If the problem is with a UNIX client, create a /usr/openv/netbackup/logs/tar activity log directory on the client and rerun the operation.

a. Check the tar activity log file for error messages that explain the problem.

b. Reboot the client to see if this clears the problem.

c. When you are through investigating the problem, delete the /usr/openv/netbackup/logs/tar directory on the client.

• If the problem is with a Microsoft Windows, NetWare, or Macintosh client:

a. Create a bpcd activity log directory on the client (on a Macintosh NetBackup creates the log automatically).

b. On a Windows NT client, create a tar activity log directory.

c. Increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

d. Rerun the operation and check the resulting activity logs.

e. Reboot the client to see if it clears the problem.

Status Code: 184
Message: tar had an unexpected error

Explanation: A system error occurred in tar.

Recommended Action:

• If the problem is with a UNIX client, create a /usr/openv/netbackup/logs/tar activity log directory on the client and rerun the operation.Create a /usr/openv/netbackup/logs/tar directory on the client and rerun the operation.

a. Check the tar activity log file for error messages that explain the problem.

b. Reboot the client to see if this clears the problem.

c. When you are through investigating the problem, delete the /usr/openv/netbackup/logs/tar directory on the client.

• If the problem is with a Microsoft Windows, NetWare, or Macintosh client:

a. Create a bpcd activity log directory on the client (on a Macintosh NetBackup creates the log automatically).

b. Increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

c. On a Windows NT client, create a tar activity log directory.

d. Retry the operation and check the resulting activity logs.

e. Reboot the client to see if it clears the problem.

Status Code: 185
Message: tar did not find all the files to be restored

Explanation: There were files in the tar file list that were not in the image.

Recommended Action:

• If the problem is with a UNIX client:

a. Enable bpcd activity logging by creating the /usr/openv/netbackup/logs/bpcd directory on the client.

b. Rerun the operation, check the resulting bpcd log file for the parameters passed to tar, and call customer support.

• If the problem is with a Microsoft Windows, NetWare, or Macintosh client: a. Create a bpcd activity log directory on the client (on a Macintosh NetBackup creates the log automatically).

b. Increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports."

c. On a Windows NT client, create a tar activity log directory.

d. Retry the operation.

e. Check the resulting activity logs for the parameters passed to tar and call customer support.

Status Code: 186
Message: tar received no data

Explanation: The media manager did not send data to tar.

Recommended Action:

1. Retry the operation and check the progress log on the client for error messages that reveal the problem.

2. Verify that the tape is available and readable.

3. Verify that that the drive is in an UP state. Use the Device Monitor (on UNIX xdevadm can also be used)

4. For detailed troubleshooting information:

a. Create a bptm activity log on the server.

b. On a Windows NT client, create a tar activity log.

c. Retry the operation and check the resulting activity logs.

Status Code: 189
Message: the server is not allowed to write to the client's filesystems

Explanation: The client is not allowing writes from the server.

Recommended Action:

Perform the following to perform restores or install software from the server.

• On a UNIX client, delete DISALLOW_SERVER_FILE_WRITES from the /usr/openv/netbackup/bp.conf file.

• On a Microsoft Windows or NetWare nontarget client, select Allow Server Directed Restores on the General tab in the NetBackup Configuration dialog box. 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 page 57).

• On a Macintosh client, delete DISALLOW_SERVER_FILE_WRITES from the bp.conf file in the NetBackup folder in the Preferences folder.

• On a NetWare target client, set ALLOW_SERVER_WRITE to yes in the bp.ini file.

Status Code: 190
Message: found no images or media matching the selection criteria

Explanation: A verify, duplicate, or import was attempted and no imagesmatching the search criteria were found in the NetBackup database.

Recommended Action: Change the search criteria and retry.

Status Code: 191
Message: no images were successfully processed

Explanation: A verify, duplicate, or import was attempted and failed for all selected images.

Recommended Action: Check the NetBackup Problems report for the cause of the error. To obtain detailed troubleshooting information, create an admin activity log directory and retry the operation. Check the resulting activity log.

Status Code: 194
Message: the maximum number of jobs per client is set to 0

Explanation: The NetBackup Maximum Jobs per Client global attribute is currently set to 0. Setting the value to 0 disables backups and archives.

Recommended Action: To enable backups and archives, change the global attribute value to the desired nonzero setting.

Status Code: 195
Message: client backup was not attempted

Explanation: A backup job was in the NetBackup scheduler's worklist but was not attempted.

Recommended Action:

1. Retry the backup either immediately with a manual backup or allow the normal scheduler retries.

2. For additional information, check the All Log Entries report. For detailed troubleshooting information, create a bpsched activity log directory on the master server. After the next backup attempt, check the activity log. Some actions to perform are:

• Verify that the vmd and ltid daemons (UNIX) or the NetBackup Volume Manager and NetBackup Device Manager services (Windows NT) are running.

• Look for a problem in an earlier backup that made the media or storage unit unavailable.

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

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

Recommended Action:

• If possible, change the schedule to extend the backup window for this class and schedule combination so it does not occur again.

• If the backup must be run, use the Manual Backup command on the Class menu in the Backup Policy Management window to perform the backup.  Manual backups ignore the backup window.

• If the backup must be run, use the NetBackup administration interface command for manual backups to perform the backup. Manual backups ignore the backup window.

Status Code: 197
Message: the specified schedule does not exist in the specified class

Explanation: A user backup or archive request has specified the exact class and schedule to use when performing a backup. The class exists but does not contain the schedule.

On Microsoft Windows and NetWare nontarget clients, you can specify a class or schedule on the Backups tab in the NetBackup Configuration dialog box. 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 page 57).

On UNIX and Macintosh clients, you can specify a class or schedule by using the bp.conf options, BPBACKUP_CLASS or BPBACKUP_SCHED. • On NetWare target clients, you can specify a class or schedule in the bp.ini file.

Recommended Action:

Check the client progress log (if available) to determine the class and schedule that were specified.
Check the configuration on the master server to determine if the schedule is valid for the class. If the schedule is not valid, either add the schedule to the class configuration or specify a valid schedule on the client.
Status Code: 198
Message: no active classes contain schedules of the requested type for this client

Explanation: A user backup or archive has been requested, and this client is not in a class that has a user backup or archive schedule.

Recommended Action:

Determine if the client is in any class that has a schedule of the appropriate type (either user backup or archive).

• If the client is in such a class, check the general class attributes to verify that the class is set to active.

• If the client is not in such a class, either add a schedule of the appropriate type to an existing class that has this client or create a new class that has this client and a schedule of the appropriate type.

Status Code: 199
Message: operation not allowed during this time period

Explanation: A user backup or archive has been requested and this client is not in a class that has a user backup or archive schedule with an open backup window. This error implies that there is an appropriate class and schedule combination for this client.

Recommended Action: Determine the classes to which this client belongs that also have a schedule of the appropriate type (either user backup or archive).

If possible, retry the operation when the backup window is open.

If the backup window is not open during appropriate time periods, adjust a backup window for a schedule in one of the classes.

Status Code: 200
Message: scheduler found no backups due to run

Explanation: When checking the class and schedule configuration, the NetBackup scheduler process (bpsched) did not find any clients to back up.  This could be due to:

• No backup time windows are open (applies only to full and incremental schedules).

• Classes are set to inactive.

• The clients were recently backed up and are not due for another backup (based on Frequency setting for the schedules).

• Classes do not have any clients.

Recommended Action: Usually, this message can be considered informational and does not indicate a problem. However, if you suspect a problem:

1. Examine the NetBackup All Log Entries report to see if there are any messages in addition to one indicating that the scheduler found nothing to do.

2. Examine the class configuration for all classes or the specific class in question and determine if any of the reasons mentioned in the Explanation section above apply.

3. To obtain detailed troubleshooting information, create a bpsched activity log directory on the master server and retry the operation. Check the resulting activity log.

maping

Status Code: 201
Message: handshaking failed with server backup restore manager

Explanation: A process on the master server encountered an error when communicating with the media server (either the master or a slave server). This error means that the master and media server processes were able to initiate communication, but encountered difficulties in completing them. This problem can occur during a backup, restore, or media list in a single or multiple server configuration.

Recommended Action:

1. Determine the activity that encountered the handshake failure by examining the NetBackup All Log Entries report for the appropriate time period. If there are slave servers, determine if:

• The handshake failure was encountered between the master and a slave server.

or

• Only the master server was involved.

2. If necessary, create the following activity log directories for the following:

• bpcd on the NetBackup media server (either master or slave).

• If the error was encountered during a backup operation, bpsched on the master server.

• If the error was encountered during a restore operation, bprd on the master server.

• If the error was encountered during a media list operation, admin in the NetBackup logs/admin directory on the master server.

3. Retry the operation and examine the resulting activity logs for information on why the error occurred.

Status Code: 202
Message: timed out connecting to server backup restore manager

Explanation: A process on the master server timed out while trying to initiate communications with the media server (either the master or a slave server).  This problem can occur during a backup or restore in either a single or multiple server configuration.

Recommended Action: Determine which activity encountered the connection timeout failure by examining the All Log Entries report for the appropriate time period. If there are slave servers, determine if the timeout occurred between the master and a slave or if only the master was involved.

1. Verify that the schedule specifies the correct storage unit.

2. Execute the ping command from one host to another by using the following combinations:

• From the master server, ping the master and all slave servers by using the host names found in the storage unit configuration.

• From each of the slave servers, ping the master server by using the host name specified in the NetBackup server list. On a UNIX server, this is the first SERVER entry in the bp.conf file. On a Windows NT server, the master is designated as the Current server on the Servers tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the server and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).

3. Verify that the master server can communicate with bpcd on the host that has the storage unit.

After each backup, the scheduler checks the storage unit to see how many drives are available (in case the backup caused a drive to be automatically downed). If bpsched cannot communicate with bpcd, it sets the number of available drives in that storage unit to 0 and further backups to that storage unit fail.

The available drives remain at 0 until the scheduler is initialized again.  Therefore, even if bpcd seems to be operating correctly now, check the bpsched and bpcd activity logs (see below) for records of an earlier failure.

4. See "Testing Slave Server and Clients" on page 18 and "Resolving Network Communication Problems" on page 21.

5. If necessary, create activity log directories for the following processes and retry the operation. Then, check the resulting activity logs on the master server:

• If the error occurred during a backup operation, check the bpsched activity logs. Also, check the bpcd activity logs.

• If the error occurred during a restore operation, check the bprd activity logs.

Status Code: 203
Message: server backup restore manager's network is unreachable

Explanation: A process on the master server could not connect to a particular host on the network when trying to initiate communication with the media server for a particular operation. This problem can occur during a backup or restore in either a single or multiple server configuration.

Recommended Action: Determine which activity encountered the network unreachable failure by examining the All Log Entries report for the appropriate time frame. If there is more than one NetBackup server (that is, one or more slave servers) determine if the network unreachable failure was encountered between the master and a slave server or if only the master server was involved. Execute the ping command from one host to another by using the following combinations:

1. From the master server, ping the master and all slave servers by using the host names in the storage unit configuration.

2. From each of the slave servers, ping the master server host by using the host name specified in the NetBackup server list. On a UNIX server, this is the first SERVER entry in the bp.conf file. On a Windows NT server, the master is designated as the Current server on the Servers tab in the NetBackup Configuration dialog box. 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).

3. See "Testing Slave Server and Clients" on page 18 and "Resolving Network Communication Problems" on page 21.

4. If necessary, create activity log directories for the following processes and retry the operation. Then, check the resulting activity logs on the master server:

• If the error occurred during a backup, check the bpsched activity logs.

• If the error occurred during a restore, check the bprd activity logs.

Status Code: 204
Message: connection refused by server backup restore manager

Explanation: The media server refused a connection on the port number for bpcd. This error can be encountered during a backup or restore.

Recommended Action: Execute the ping command from one host to anotherby using the following combinations:  Note: Also, see "Resolving Network Communication Problems" on page 21.

From the master server, ping the master and all slave servers by using the host names in the storage unit configuration.
From each of the slave servers, ping the master server by using the name specified in the NetBackup server list. On a UNIX server, this is the first SERVER entry in the bp.conf file. On a Windows NT server, the master is designated as the Current server on the Servers tab in the NetBackup Configuration dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the server and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57).
On UNIX servers, verify that the bpcd entries in /etc/services or NIS on all the servers are identical. Verify that the media server is listening on the correct port for connections to bpcd by running one of the following commands (depending on platform and operating system):

netstat -a | grep bpcd
netstat -a | grep 13782 (or the value specified during the install)
rpcinfo -p | grep 13782 (or the value specified during the install)

On UNIX servers, you may have to change the service number for bpcd in /etc/services and the NIS services map and send SIGHUP signals to the inetd processes on the clients.
/bin/ps -ef | grep inetd
kill -HUP the_inetd_pid
or
/bin/ps -aux | grep inetd
kill -HUP the_inetd_pid

Note: On a Hewlett-Packard UNIX platform, use inetd -c to send a SIGHUP to inetd.
On Windows NT servers:
Verify that the bpcd entries are correct in:
%SystemRoot%\system32\drivers\etc\services
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 settings in the services file. 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).  The values on the Network tab are written to the services file when the NetBackup Client service starts.
Stop and restart the NetBackup services.
See "Testing Slave Server and Clients" on page 18 and "Resolving Network Communication Problems" on page 21.
If necessary, create activity log directories for the following processes and retry the operation. Then, check the resulting activity logs on the master server:
If the error occurred during a backup operation, check the bpsched activity logs.
If the error occurred during a restore operation, check the bprd activity logs.
Status Code: 205
Message: cannot connect to server backup restore manager

Explanation: A process on the master server could not connect to a process on a host on the network while trying to initiate communication with the server that has the storage unit for a particular operation. This problem can occur during a backup or restore in either a single or multiple server configuration. This can also occur when the scheduler process (bpsched) is building its list of available storage units to use during backups.

Recommended Action: Execute the ping command from one host to another by using the following combinations:

Note: Also, see "Resolving Network Communication Problems" on page 21.

From the master server, ping the master and all slave servers by using the host names in the storage unit configuration.
From each of the slave servers, ping the master server by using the name specified in the NetBackup server list. On a UNIX server, this is the first SERVER entry in the bp.conf file. On a Windows NT server, the master is designated as the Current server on the Servers tab in the NetBackup Configuration dialog box. 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).
On a UNIX server, verify that the bpcd entry in /etc/services or NIS on all the servers are identical. Verify that the media server is listening on the correct port for connections to bpcd by running one of the following commands (depending on platform and operating system):

netstat -a | grep bpcd
netstat -a | grep 13782 (or the value specified during the install)
rpcinfo -p | grep 13782 (or the value specified during the install)

On Windows NT servers:  
Verify that the bpcd entries are correct in the services file:
%SystemRoot%\system32\drivers\etc\services
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 settings in the services file. 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).  The values on the Network tab are written to the services file when the NetBackup Client service starts.
Stop and restart the NetBackup services.
See "Testing Slave Server and Clients" on page 18 and "Resolving Network Communication Problems" on page 21.
Create a bpcd activity log directory on the server that has the storage unit and retry the operation. Then, check for additional information in the resulting activity log.
Status Code: 206
Message: access to server backup restore manager denied

Explanation: The master server is trying to start a process on another server (or itself) and the master server does not appear in the Netbackup server list on that server. On a UNIX server, the master is the first SERVER entry in the bp.conf file. On a Windows NT server, the master is designated as the Current server on the Servers tab in the NetBackup Configuration dialog box.

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).

Recommended Action:

Verify that the master server appears as a server in its own server list as well as being listed on all slaves.

If you change the server list on a master server, stop and restart the NetBackup database manager and request daemons (UNIX) or the NetBackup Database Manager and NetBackup Request Manager services (Windows NT).
If necessary, create activity log directories for the following processes and retry the operation. Then, check the resulting activity logs on the master server:
If the error occurred during a backup operation, check the bpsched activity logs.
If the error occurred during a restore operation, check the bprd activity logs.
Status Code: 207
Message: error obtaining date of last backup for client

Explanation: An error occurred when the backup scheduler (bpsched) tried to obtain the date of the last backup for a particular client, class, and schedule combination.

Recommended Action:

Verify that the NetBackup database manager (bpdbm) process (NetBackup Database Manager service on Windows NT) is running.
Examine the All Log Entries report for the appropriate time frame to gather more information about the failure.
For detailed troubleshooting information, create activity log directories for bpsched and bpdbm on the master server and retry the operation. Then, check the resulting activity logs.
Status Code: 208
Message: failed reading user directed file list

Explanation: An error occurred when the backup scheduler (bpsched) attempted to read the list of files requested for a user backup or archive. This error indicates either a client-server communication problem, or a system problem on the master server where the NetBackup scheduler process (bpsched) is running.

Recommended Action: For detailed troubleshooting information, create activity log directories for bpsched and bprd on the master server and retry the operation. Then, check the resulting activity logs.

Status Code: 209
Message: error creating or getting message queue

Explanation: An error occurred when the backup scheduler (bpsched) attempted to create an internal message queue construct for interprocess communication. This error indicates a problem on the master server and is most likely due to a lack of system resources for System V interprocess communication.

Recommended Action: Create a bpsched activity log directory on the master server and retry the operation. Then, determine the type of system failure by examining the error message in the bpsched activity log.

On UNIX servers, also gather the output of the ipcs -a command to see what system resources are currently in use.

Status Code: 210
Message: error receiving information on message queue

Explanation: An error occurred when one of the backup scheduler (bpsched) processes attempted to receive a message from another bpsched process on an internal message queue construct. This error indicates a problem on the master server and is likely due to problems with or a lack of system resources for System V interprocess communication.

Recommended Action: Create a bpsched activity log directory on the master server and retry the operation. Then, determine the type of system failure by examining the error message in the bpsched activity log on the master server.  On UNIX servers, also gather the output of the ipcs -a command to see what system resources are currently in use.

Status Code: 211
Message: scheduler child killed by signal

Explanation: A backup scheduler (bpsched) child process, which interacts with the backup restore manager (bpbrm) on the media server, was terminated. This can occur because of system administrator action.

Recommended Action: Create an activity log directory for bpsched on the master server and retry the operation. Then, to determine the cause of the child termination, examine the messages in the bpsched activity log.

Status Code: 212
Message: error sending information on message queue

Explanation: The backup scheduler (bpsched) encountered an error when attempting to attach to an already existing internal message queue construct for interprocess communication. This error indicates a problem on the master server and is likely due to a lack of system resources for System V interprocess communication.

Recommended Action: Create a bpsched activity log directory on the master server and retry the operation. Then, determine the type of system failure by examining the error message in the bpsched activity log.   On a UNIX server, also, gather the output of the ipcs -a command to see what system resources are currently in use.

Status Code: 213
Message: no storage units available for use

Explanation: The NetBackup scheduler process (bpsched) did not find any of its storage units available for use. Either all storage units are unavailable or all storage units are configured for "on demand only" and the class and schedule does not require a specific storage unit.

Recommended Action:

Examine the Backup Status and All Log Entries report for the appropriate time period to determine the class or schedule that received the error.
Verify that the storage unit's drives are not down or waiting for media from a previous operation that did not complete.
Examine the storage unit configuration to verify that all the storage units do not have their "Concurrent Jobs" attribute set to 0.
Verify that the robot number and host name in the storage unit configuration matches the Media Manager device configuration.
Determine if all storage units are set to "On Demand Only" for a class and schedule combination that does not require a specific storage unit. If this is the case, either specify a storage unit for the class and schedule combination or turn off "On Demand Only" for a storage unit.
If the storage unit is on a UNIX NetBackup slave server, it could indicate problem with bpcd. Check /etc/inetd.conf on the slave server to verify that the bpcd entry is ok.  If the storage unit is on a Windows NT NetBackup slave server, verify that the NetBackup Client service has been started on the Windows NT NetBackup slave server.
For detailed troubleshooting information, create a bpsched activity log directory on the master server and retry the operation. Then, check the resulting activity log.
Status Code: 214
Message: regular bpsched is already running

Explanation: The NetBackup scheduler (bpsched) performs periodic checking of the class and schedule configuration to determine if there are new backups due. Error 214 indicates that when a new instance of NetBackup starts, it finds that a scheduler process is already checking the class and schedule configuration.

Recommended Action: Usually, no action is required for this condition.  However, NEVER kill bpsched before doing some checking. For example, bpsched could be calling bpdbm (NetBackup Database Manager service on Windows NT) to clean up and compress the databases. To determine what the running bpsched is currently doing, examine the bpsched activity log on the master server. If necessary, enable bpsched activity logging by creating a bpsched activity log directory on the master server and retrying the operation.  To check for backups do the following:

On a UNIX master server:

Check for active or queued backups by using the job monitor.
Check for active bp processes with bpps. This reveals if there are bpbrm or bptm processes running and a backup is active.
If there is no reason for bpsched to be running, then use kill -HUP to terminate it.
On a Windows NT NetBackup master server:

Status Code: 215
Message: failed reading global config database information

Explanation: During the periodic checking of the NetBackup configuration, the NetBackup scheduler process (bpsched) was unable to read the global configuration parameters.

Recommended Action:

On a UNIX master server, verify that the NetBackup database manager (bpdbm) process is running. On a Windows NT master server, verify that the NetBackup Database Manager service is running.
Attempt to view the global configuration settings by using the the NetBackup administration interface.
For detailed troubleshooting information, create activity log directories for bpsched and bpdbm on the master server and retry the operation. Then, check the resulting activity logs.
Status Code: 216
Message: failed reading retention database information

Explanation: During its periodic checking of the NetBackup configuration, the NetBackup scheduler process (bpsched) could not read the list of retention levels and values.

Recommended Action:

On a UNIX master server, verify that the NetBackup database manager (bpdbm) process is running. On a Windows NT master server, verify that the NetBackup Database Manager service is running.
For detailed troubleshooting information, create activity log directories for bpsched and bpdbm on the master server and retry the operation. Then, check the resulting activity logs.
Status Code: 217
Message: failed reading storage unit database information

Explanation: During its periodic checking of the NetBackup configuration, the NetBackup scheduler process (bpsched) could not read the storage unit configuration.

Recommended Action:

On a UNIX server, verify that the NetBackup database manager (bpdbm) process is running. On a Windows NT server, verify that the NetBackup Database Manager service is running.
Attempt to view the storage unit configuration by using the NetBackup administration interface.
For detailed troubleshooting information, create activity logs for bpsched and bpdbm on the master server and retry the operation. Then, check the resulting activity logs.   Ensure that the correct master server is being specified for the connection.
Status Code: 218
Message: failed reading class database information

Explanation: During the periodic checking of the NetBackup configuration, the NetBackup scheduler process (bpsched) could not read the class (backup policy) configuration.

Recommended Action:

On a UNIX server, verify that the NetBackup database manager (bpdbm) process is running. On a Windows NT server, verify that the NetBackup Database Manager service is running.
Attempt to view the class configuration by using the NetBackup administration interface.
For detailed troubleshooting information, create activity log directories for bpsched and bpdbm on the master server and retry the operation. Then, check the resulting activity logs.  Ensure that the correct master server is being specified for the connection.
Status Code: 219
Message: the required storage unit is unavailable

Explanation: The class or schedule for the backup requires a specific storage unit, which is currently unavailable. This error also occurs for other attempts to use the storage unit within the current backup session.

Recommended Action:  Examine the Backup Status and All Log Entries report for the appropriate time period to determine the class or schedule that received the error. Then, examine the specific class and schedule configuration to determine the required storage unit.

Verify that the schedule specifies the correct storage unit and the storage unit exists.
Verify that the Media Manager device daemon (ltid) is running (if the server is UNIX) or the NetBackup Device Manager service is running (if the server is a Windows NT system). Use bpps on UNIX and the Activity Monitor on Windows NT.
Verify that the Number of Drives attribute for the storage unit is not set to 0.
If the storage unit is a tape or optical disk, verify that at least one of the drives is in the UP state. Use the Device Monitor (on UNIX xdevadm can also be used).
Verify that the robot number and host in the storage unit configuration matches what is specified in the Media Manager device configuration.  
Verify that the master server can communicate with the bpcd process on the server that has the storage unit.
Verify that bpcd is listening on the port for connections.
On a UNIX server, executing
netstat -a | grep bpcd
should return something similar to the following:
*.bpcd *.* 0 0 0 0 LISTEN
Do this on the server where the storage unit is connected.
On a Windows NT NetBackup server, executing
netstat -a
prints out several lines of output. If bpcd is listening, one of those lines is similar to the following:
TCP myhost:bpcd 0.0.0.0:0 LISTENING
Do this on the server where the storage unit is connected.
If bpcd seems to be operating correctly, create bpsched and bpcd activity log directories and retry the operation. Check the resulting activity logs for records of an earlier failure.
After each backup, the scheduler checks the storage unit to see how many drives are available (in case the backup caused a drive to be automatically downed). If bpsched cannot communicate with bpcd, it sets the number of available drives in that storage unit to 0 and further backups to that storage unit during this backup session will fail. The number of available drives remains at 0 until the scheduler is initialized again.
c. If the cause of the problem is not obvious, perform some of the steps in "Resolving Network Communication Problems" on page 21.
Status Code: 220
Message: database system error

Explanation: The bpdbm process (NetBackup Database Manager service on Windows NT) could not create a directory path for its configuration databases due to the failure of a system call. This is usually due to a permission problem or an "out of space" condition.

Recommended Action: Create an activity log directory for bpdbm and retry the operation. Check the resulting activity log for information.

maping

Status Code: 221
Message: continue

Explanation: This status code is used in coordinating communication between various NetBackup processes and normally does not occur. If the logs show that it is associated with a subsequent error, it usually indicates a communication problem. In this case, concentrate your troubleshooting efforts on the subsequent error.

Recommended Action: Determine the cause of the status code that follows this one.

Status Code: 222
Message: done

Explanation: This status code is used in coordinating communication between various NetBackup processes and is normally not seen. If the error logs show that it is associated with a subsequent error, it usually indicates a communication problem. In this case, concentrate your troubleshooting efforts on the subsequent error.

Recommended Action: Determine the cause of the status code that follows this one.

Status Code: 223
Message: an invalid entry was encountered

Explanation: A request to the bpdbm process (NetBackup Database Manager service on Windows NT) had invalid or conflicting information. This is usually a result of using software from different versions together, but can also be caused by incorrect parameters on a command.

Recommended Action: Verify that all NetBackup software is at the same version level and the command parameters are specified correctly. If neither of these is the problem, obtain detailed troubleshooting information by creating a bpdbm activity log directory and retrying the operation. Check the resulting activity log.

Status Code: 224
Message: there was a conflicting specification

Explanation: A request to the bpdbm process (NetBackup Database Manager service on Windows NT) had conflicting information. This is usually a result of using software from different version levels together.

Recommended Action: Verify that all NetBackup software is at the same version level. If that is not the problem, obtain detailed troubleshooting information by creating bpdbm and admin activity log directories and retrying the operation. Check the resulting activity logs.

Status Code: 225
Message: text exceeded allowed length

Explanation: A request containing text that exceeds a buffer size was made to the bpdbm process (NetBackup Database Manager service on Windows NT).  This is usually a result of using software from different version levels together.

Recommended Action: Verify that all NetBackup software is at the same version level. If that is not the problem, create activity log directories for bpdbm and admin. Then, retry the operation and examine the resulting activity logs.

Status Code: 226
Message: the entity already exists

Explanation: The configuration already has an entity with the same name or definition. For example, you see this status if you try to add a new class when an existing class has the same name or definition (attributes, clients, and so on).

Recommended Action: Correct your request and re-execute the command.

Status Code: 227
Message: no entity was found

Explanation: The item requested was not in the database. For example, the entity could be a file or class information.

Recommended Action: A common cause for this problem is a query that has no matching images. Specify different parameters or options for the operation and try it again.

Status Code: 228
Message: unable to process request

Explanation: An inconsistency exists in the database or a request was made that would be improper to satisfy.

Recommended Action:

If this involves a slave server, verify that its server list specifies the correct master server. On a UNIX server, the master server is the first SERVER entry in the bp.conf file. On a Windows NT server, the master is designated as the Current server on the Servers tab in the NetBackup Configuration dialog box. 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).

For detailed troubleshooting information, create a bpdbm activity log directory and retry the operation. Then, check the resulting activity log.

Status Code: 229
Message: events out of sequence - image inconsistency

Explanation: A request was made which, if satisfied, would cause the image database to become inconsistent.

Recommended Action: Obtain detailed troubleshooting information by creating an activity log directory for bpdbm. Then, retry the operation, save the resulting activity log, and call customer support.

Status Code: 230
Message: the specified class does not exist in the configuration database

Explanation: The specified class name does not exist.

Recommended Action: Correct your parameters or options and retry the operation.

Status Code: 231
Message: schedule windows overlap

Explanation: The start and duration times specified for one day of the schedule overlap with another day of the schedule.

Recommended Action: Correct the schedule to eliminate the overlapping backup windows.

Status Code: 232
Message: a protocol error has occurred

Explanation: This is an intermediate status code that usually precedes another status code. It indicates that either the bpdbm process (NetBackup Database Manager service on Windows NT) or the process communicating with it has received unexpected information.

Recommended Action: Create an activity log directory for bpdbm. Then, retry the operation, save the activity log, and call customer support.

Status Code: 233
Message: premature eof encountered

Explanation: This is an intermediate status code that usually precedes another status code and is associated with a problem in network communication.

Recommended Action: During a restore, this means that tar (on the client) received a stream of data that was not what it expected. If this is a new configuration, verify that the tape drive is configured for variable mode (see the Media Manager Device Configuration Guide).

If the communication failure is not due to an interrupt on a client system, save all error information and call customer support.

Status Code: 234
Message: communication interrupted

Explanation: This is an intermediate status code that usually precedes another status code and is associated with a problem in network communication. A process, either server or client, received an interrupt signal.

Recommended Action: Save all error information and call customer support.

Status Code: 235
Message: inadequate buffer space

Explanation: This code usually indicates a mismatch between server and client software versions.

Recommended Action:

1. Verify that all NetBackup software is at the same version level. Update earlier versions of NetBackup software.

On UNIX NetBackup servers and clients, check the /usr/openv/netbackup/bin/version file.
On Windows NT NetBackup servers, check the install_path\NetBackup\version.txt file or the About NetBackup command on the Help menu.
On Microsoft Windows clients, check the About NetBackup command on the Help menu.
On NetWare target clients, check the Version entry in the bp.ini file.  If the client software is earlier than 3.0, verify that the client is in a Standard type class.
On Macintosh clients, check the version file in the bin folder in the NetBackup folder in the Preferences folder.
2. If the problem persists, save all error information and call customer support.

Status Code: 236
Message: the specified client does not exist in an active class within the configuration database

Explanation: A client name was not specified or the specified client does not exist.

Recommended Action: Activate the required class, correct the client name, or add the client to a class that meets your needs. After making the correction, retry the operation.

Status Code: 237
Message: the specified schedule does not exist in an active class in the configuration database

Explanation: The specified schedule does not exist in the NetBackup configuration.

Recommended Action: Activate the required class, correct the schedule name, or create a schedule in a class that meets your needs. After making the correction, retry the operation.

Status Code: 238
Message: the database contains conflicting or erroneous entries

Explanation: The database has an inconsistent or corrupted entry.

Recommended Action: Obtain detailed troubleshooting information for bpdbm (NetBackup Database Manager service on Windows NT) by creating an activity log directory for it. Then, retry the operation, save resulting activity log, and call customer support.

Status Code: 239
Message: the specified client does not exist in the specified class

Explanation: The specified client is not a member of the specified class.

Recommended Action: Correct the client name specification, specify a different class, or add the required client name to the class. After making the correction, retry the operation.

Status Code: 240
Message: no schedules of the correct type exist in this class

Explanation: The appropriate schedule was not found in the specified class.  For example, a user backup specified a class name but no user backup schedule exists in that class.

Recommended Action: Specify a different class or create a schedule of the needed type in the class. After making the correction, retry the operation.

Status Code: 241
Message: the specified schedule is the wrong type for this request

Explanation: The schedule that was specified for an immediate manual backup is not for a full nor an incremental backup. It must be one of these.

Recommended Action: Specify only full or incremental schedules for manual backups. If one does not exist in the class, create one.

Status Code: 242
Message: operation would cause an illegal duplication

Explanation: Processing the request would cause a duplicate database entry.  This is usually due to a mistake in specifying media IDs for NetBackup database backups.

Recommended Action: Check the error reports to determine the specific duplication that would occur. Correct the settings for the operation and retry it.

Status Code: 243
Message: the client is not in the configuration

Explanation: The specified client name was not in the database.

Recommended Action: Either correct the client name or add the client to the desired class.

Status Code: 244
Message: main bpsched is already running

Explanation: A bpsched process tried to become the main backup scheduler but another process is currently in this mode.

Recommended Action: None.

Status Code: 245
Message: the specified class is not of the correct client type

Explanation: A user backup specified a class that is not the type required for the client.

Recommended Action: Retry the operation by specifying a class that is the correct type for the client. If such a class does not exist, create one.

Status Code: 246
Message: no active classes in the configuration database are of the correct client type

Explanation: A user backup request was not satisfied because no active classes were the type required for the client.

Recommended Action: Create or activate an appropriate class so the user backup request can be satisfied.

Status Code: 247
Message: the specified class is not active

Explanation: Backups for the specified class are disabled because the class is inactive.

Recommended Action: Activate the class and retry the operation.

Status Code: 248
Message: there are no active classes in the configuration database

Explanation: No active class was found that would satisfy the request.

Recommended Action: Activate the appropriate class and retry the operation.

Status Code: 249
Message: the file list is incomplete

Explanation: The server timed out while waiting for the client to finish sending the file list, or a sequencing problem occurred.

Recommended Action: Obtain additional information by first creating activity logs and then attempting to recreate the error. The activity logs to create are as follows:

On the server, bptm, bpbrm, and bpdbm.
On UNIX and Windows NT clients, bpbkar.
On other clients, bpcd.
To increase the amount of information included in the logs. See "Activity Logs on PC Clients" on page 67.

Status Code: 250
Message: the image was not created with TIR information

Explanation: This is an internal error and should not be seen by customers. Recommended Action: Obtain detailed troubleshooting information by creating activity logs for bptm and bpdbm on the server. Then, retry the operation and check the resulting activity logs.

Status Code: 251
Message: the tir information is zero length

Explanation: For a true-image backup, the client sent no file information to the master server. NetBackup discovered this condition when it attempted to write the TIR information to media.

Recommended Action:

1. Check the file list for the class and the exclude and include lists on the client to verify that the client has files that are eligible for backup. For example, this status code can appear if the exclude list on the client excludes all files.

2. To obtain detailed troubleshooting information, create activity logs for bptm and bpdbm on the server. Then, retry the operation and check the resulting activity logs.

Status Code: 254
Message: server name not found in the bp.conf file

Explanation: This error should not occur through normal use of NetBackup.

Recommended Action: Save all error information and call customer support.

fugangyun

晕，楼主辛苦了。

netbackup文档中，排错那一章有比这个更详细的代码。

wuhao1001

感谢楼主.

bj5i5j

谢谢分享

maping

顶上去