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: 332
Explanation: This error can occur while the backup process communicates with the EMM database to retrieve some information.
Recommended Action: Do the following, as appropriate:
On UNIX, verify that the NetBackup Volume Manager (vmd) is running. On Windows, verify that the NetBackup Volume Manager service is running.
See the process-specific error log directory for more details.
UNIX:
/usr/openv/netbackup/logs/process_name
Windows:
install_path\NetBackup\logs\process_name
For example, if you get this error while running a Vault command (such as vltcontainers or vltopmenu), look at the following logs to learn why:
/usr/openv/netbackup/logs/vault
Note:
The log file cannot be created unless the appropriate log directory (for example,
/usr/openv/netbackup/logs/vault
) is already created.
Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.