NetBackup Status Codes: 5 Common Troubleshooting Fixes Guide 2025

Veritas NetBackup stands as a cornerstone in enterprise data protection, managing backups across diverse environments from physical servers to virtual machines. However, even robust systems encounter hiccups, manifesting as status codes that halt operations. These errors, while initially daunting, often stem from straightforward issues like configuration mismatches, resource constraints, or permission glitches. This comprehensive guide delves into the most recurrent NetBackup status codes, offering actionable diagnostics and resolutions drawn from official documentation and proven practices. By mastering these troubleshooting techniques, administrators can minimize downtime and maintain data integrity.

Understanding NetBackup Status Codes

NetBackup communicates issues through numeric status codes, each signaling specific failure modes. Unlike generic error messages, these codes provide clues for targeted fixes. Common culprits include partial successes, file access denials, resource shortages, and snapshot failures. Before diving into specifics, establish a baseline troubleshooting workflow: verify system compatibility, review logs, check disk space, and confirm process health. Official Veritas resources emphasize starting with the NetBackup Troubleshooting Guide, which outlines sequential checks from OS validation to daemon monitoring.

Effective diagnosis hinges on unified logging. Enable verbose mode via the Administration Console or command line to capture detailed traces. Commands like bperror -S -r list recent errors, while vxlogview parses unified logs. Always cross-reference with the Status Codes Reference Guide for context-specific advice.

Resolving Partial Backup Success (Status Code 11)

Status code 11 indicates that a job completed but not fully as intended—some files backed up, others skipped. This vagueness frustrates admins, but logs reveal the root cause, often locked files, path length excesses, or corruption.

• Examine Backup Logs: Locate the job’s detailed log in /usr/openv/netbackup/logs/ (Unix) or install_path\netbackup\logs\ (Windows). Search for ‘partial’ or file-specific failures.
• Path Length Check: NetBackup supports up to 1023 characters for standard paths, dropping to 1000 for snapshots. Use find / -name "*" -type f | awk '{print length($0)}' | sort -n | tail on Unix to identify offenders.
• Handle Locked Files: Databases or active applications lock files. Schedule backups during quiescence or employ agents for consistent snapshots.
• Corruption Detection: Run filesystem checks like fsck or chkdsk. Retry after repairs.

If persistent, increase logging verbosity with vxlogcfg -a -p nb -o Default -s DebugLevel=6 and reproduce the issue.

Tackling Zero Files Backed Up (Status Code 2)

Code 2 signals no files were successfully backed up, rare for filesystem jobs but common in database scenarios like SQL Server or Oracle via agents. Batch file failures in policies trigger this, especially with multiple streams.

Diagnostic Steps:

1. Query policies: bppllist -U on the master server reveals configurations.
2. Navigate to install_path\veritas\netbackup\bin\admincmd and execute bpplclients policy_name for client details.
3. Test agent connectivity: Use bptestnetconn from master to client.
4. For SQL: Confirm RMAN scripts or batch files execute sans errors via command line.

Resolution often involves splitting multi-batch policies or verifying credentials. Retest with manual backups from the console.

Overcoming Instant Recovery Failures (Status Code 5)

Status 5 plagues VMware instant recoveries, where VMs fail to power on post-restore. Culprits include vSphere misalignments, wrong resource pools, or permission barriers.

• vSphere Validation: Confirm VM compatibility with host clusters. Check datastore space and network mappings.
• Resource Pool Assignment: In restore jobs, specify correct pools; mismatches cause activation halts.
• Server Lists: Ensure client properties list primary and media servers accurately.
• Permissions Audit: NetBackup service accounts need vSphere roles like Datastore.Browse.

Logs in vmware logs under job IDs pinpoint issues, e.g., ‘mount failed’ indicates config errors. Post-fix, verify with test restores.

Addressing Memory Allocation Issues (Status Code 100)

Code 100 screams insufficient RAM—NetBackup processes starve during allocation. VMs exacerbate this, capped at 4GB for 32-bit guests.

1. Monitor Usage: Use top, Task Manager, or bpps to spot high-memory daemons like bpbkar.
2. VM Tweaks: Power off, allocate more vRAM via hypervisor console.
3. Swap Space: Extend paging files; low swap mimics RAM exhaustion.
4. Process Limits: Adjust ulimit on Unix or registry tweaks on Windows.

For chronic cases, profile with nbemmcmd reports and scale hardware.

Solving File Open Denials (Status Code 122)

122 arises when storage units target root devices, forbidden for safety. Media servers echo this.

• Storage Unit Review: In Admin Console, edit units; avoid root paths unless critical.
• Root Override: Check ‘Allow root filesystem’ if unavoidable, but prefer /backup mounts.
• Permissions: Ensure nbuser owns paths: chown nbuser:nbuser /storage/path.

Migrate to dedicated volumes for best practice.

General Troubleshooting Best Practices

Beyond specifics, adopt these habits:

• Compatibility First: Reference NetBackup Master Compatibility List quarterly.
• Log Mastery: Automate rotations; use OpsCenter for analytics.
• Disk Vigilance: Monitor /usr/openv partitions; alert at 80% full.
• Process Checks: Script bpps -x for daemon health.

Integrate with monitoring tools like Nagios for proactive alerts.

Frequently Asked Questions

What if logs show no obvious errors?

Increase verbosity and retry; consult Veritas support with support.log bundles.

How to prevent status code 11 recurrence?

Implement path normalization scripts and exclusive backup windows.

Is status code 2 always database-related?

Primarily, but check for empty directories or access denials in filesystems.

Can I ignore code 100 on high-RAM servers?

No—per-process limits persist; tune individually.

What’s the safest fix for code 122?

Relocate storage units off root partitions entirely.