peshkova - Fotolia
While Symantec NetBackup is relatively easy to configure and use, problems can and sometimes do occur. This article discusses five common NetBackup status codes and how to solve them.
NetBackup status code: 1
Message: The requested action was partially successful
In my opinion, this is one of the most frustrating NetBackup status codes. This is a non-specific error that basically says, "Something went wrong, but I'm not going to tell you what it was."
Unfortunately, there is no magical fix for this error. The only way to correct this particular condition is to figure out what the error means. The best way to do that is to look through the backup logs for any hint as to what might be causing the problem.
If the error occurs during a backup, pay attention to what is being backed up. This problem can occur if NetBackup tries to open a locked file or if the file path is more than 1,000 characters long. In some cases, 1,023-character file paths are allowed, but try to keep the path under 1,000 characters if possible.
NetBackup status code: 2
Message: None of the requested files were backed up
This particular problem is almost always related to a security issue. Specifically, NetBackup generates this error when it does not have read access to the data it is trying to back up.
On Windows machines, the NetBackup Client service makes use of a service account that must have read access to the data being backed up. One common problem is that the NetBackup Client service is sometimes configured to use the SYSTEM account. While this account should work fine for backing up local data, it does not have access to network drives.
Visit Symantec's website to read its recommended action.
NetBackup status code: 5
Message: The restore failed to recover the requested files
Nothing raises an administrator's stress level like an error code indicating that a backup cannot be restored. Fortunately, this message does not always mean a fatal condition has occurred.
This is one of the NetBackup status codes that often relates to a security or configuration issue. You should begin the troubleshooting process by checking the logs for any further explanation of why the restore failed. It is also a good idea to check the resource you are backing up to ensure the NetBackup client has permission to write data to the location where the data is being restored.
You should also check the client's server list to verify that it contains an entry for the master server and any media server that might potentially be used during the recovery operation.
Read Symantec's advice on how to solve this status code.
NetBackup status code: 10
Message: Allocation failed
This NetBackup error code means the system lacks sufficient memory for the operation to complete. There are a couple of things you can do in this situation.
If the problem occurs on a virtual machine (VM), try shutting down the VM and allocating additional memory to it. Keep in mind that if the VM is running a 32-bit operating system it will never be able to use more than 4 GB of RAM.
You could also try -- regardless of whether the system is physical or virtual -- a simple reboot. Rebooting the system will often reclaim memory from unused processes.
If all else fails, use the Windows Task Manager to determine if there are any unnecessary processes running on the system. You may be able to free up some memory by terminating such processes.
NetBackup status code: 12
Message: File open failed
This NetBackup status code sounds like a read error, but it occurs when a disk storage unit attempts to write data to the root device of the NetBackup server, which can also happen with media servers.
If the path for the disk storage unit absolutely must reside at the root level, you can force the operation by opening the Administration Console, going to the Change Storage Unit dialog box and selecting the "This directory can exist on the root file system or system disk" checkbox.
Errors associated with NetBackup status codes can often be traced to permissions issues, resource allocation issues, or other simple configuration or logistical issues.
Get Symantec's explanation of how to fix this issue.
NetBackup errors with Active Directory
Deploying Instant Recovery for VMware
Symantec NetBackup 7.6 offers faster VMware VM protection