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: 639
Explanation: The policy that was specified on the bpsynth command does not exist in the database. Either the command line or nbjm initiated the bpsynth command. If nbjm initiated it, the policy may have been deleted after nbjm started bpsynth and before bpsynth issued the database query.
Recommended Action: If bpsynth is initiated with the command line, rerun the command for an existing policy. If the problem persists after you verify the following, contact customer support and send the appropriate logs:
The synthetic backup job was scheduled or started by using the NetBackup Administration Console (manual start).
The policy exists in the bppllist command configuration.
Check the logs for nbjm, which uses unified logging (OID 117).
A complete list of required logs and configuration information is available.
See "Logs to accompany problem reports for synthetic backups" in the NetBackup Logging Reference Guide.
Click here to view technical notes and other information on the Veritas Support website about this status code.