Veritas NetBackup™ Status Codes Reference Guide
- NetBackup status codes
- NetBackup status codes
- NetBackup KMS status codes
- NetBackup status codes
- Media Manager status codes
- Media Manager status codes
- Media Manager status codes
- Device configuration status codes
- Device configuration status codes
- Device configuration status codes
- Device management status codes
- Device management status codes
- Device management status codes
- Robotic status codes
- Robotic status codes
- Robotic status codes
- Robotic error codes
- Robotic error codes
- Robotic error codes
- Security services status codes
- Security services status codes
- Security services status codes
- NetBackup alert notification status codes
NetBackup status code: 206
Explanation: The master server tries to start a process on another server (or itself) but does not appear in the NetBackup server list on that server. On a UNIX or Linux server, the master is the first SERVER entry in the bp.conf
file. On a Windows server, the master is designated on the tab in the Master Server Properties dialog box.
See "Using the Host Properties window to access configuration settings" in the NetBackup Troubleshooting Guide.
Recommended Action: Do the following, as appropriate:
Verify that the master server appears as a server in its own server list as well as being listed on all media servers.
If you change the master server list, stop and restart the NetBackup Database Manager (bpdbm) and NetBackup Request Daemon (bprd) to ensure that all appropriate NetBackup processes use the new server entry.
If necessary, create debug log directories for bprd and retry the operation. Then, check the resulting debug logs on the master server:
If the error occurred during a backup operation, check the nbpem, nbjm, and nbrb logs by using the vxlogview command.
If the error occurred during a restore operation, check the bprd debug logs.
Click here to view technical notes and other information on the Veritas Technical Support website about this status code.