http://tcc.technion.ac.il/backup/VNBCodes.html#Status_Code10
Message: "the requested operation was successfully completed"
Explanation: There were no problems detected with the requested operation.
Recommended Action:
None, unless this was a database backup performed through a database extension product (for example, NetBackup for Oracle or NetBackup for SQL Server). In those instances, code 0 means the backup script that started the backup ran without error. However, you must check other status as explained in the related NetBackup manual to see if the database was successfully backed up.
Message: "the requested operation was partially successful"
Explanation: A problem that may require corrective action was detected during the requested operation.
Recommended Action:
Check the All Log Entries report and also the progress log (if there is one).
Some of the problems that can show up under Status Code 1 are:
· A file or directory path that is more than 1023 characters long.
· Could not open a file.
· On a UNIX system, NetBackup could not get the link name of a file.
· On a UNIX system, NetBackup could not process a sparse file.
· Read error encountered in a file.
· File is of an unknown type.
· On a UNIX system, the lstat system call fails on a file that is eligible to be backed up. This may be a permission problem.
· On UNIX, a file could not be locked that has mandatory locking enabled.
Message: "none of the requested files were backed up"
Explanation: A backup or archive could not back up any of the files in the file list.
Recommended Action: Verify that the files exist and you have read access to them.
· On UNIX clients, check to see if the files or directories would be excluded because of an entry in /usr/openv/netbackup/exclude_list.
· On PC clients, check the exclude list per the instructions in the user's guide for the client.
· On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to the files.
If you are backing up a network drive or a UNC (universal naming convention) path, use the Services application in the Windows NT Control Panel to verify that the NetBackup Client service does not start under the SYSTEM account. The SYSTEM account cannot access network drives.
To back up network drives or UNC paths, change the NetBackup Client service startup to log in as a user that has permission to access network drives.
Message: valid archive image produced, but no files deleted due to non-fatal problems
Explanation: The backup portion of the archive command reported problems so the files were not deleted.
Recommended Action: Examine the progress log of the archive on the client to determine if you need to retry the archive after correcting the problem. If the problem is not serious and the files were backed up, you can manually delete the files. To verify which files were backed up, use the NetBackup client-user interface in restore mode and browse the files in the archive.
A possible cause for files not being deleted is that you do not have the necessary permissions. NetBackup cannot delete files unless you are either the user that owns the files, a superuser on UNIX, or an administrator on Windows NT.
Message: archive file removal failed
Explanation: The backup portion of the archive completed was successful but the delete failed.
Recommended Action: Verify that you have permission to delete the files and that the read-only flag is not set for the files. On UNIX clients, verify that you have write permission to the directories that contain the files. Since the backup was successful, you can delete the files that were backed up (or have the system administrator delete the files if you do not have the necessary permissions).
Message: the restore failed to recover the requested files
Explanation: There were errors that caused the restore to fail.
Recommended Action:
1. Examine the progress log on the client for messages on why the restore failed. Also, check the All Log Entries report on the server.
2. On Windows NT and UNIX, check ownership and permission on directories where files will be restored.
3. Correct problems that you find and retry the restore.
Message: the backup failed to back up the requested files
Explanation: Errors caused the user backup to fail.
Recommended Action:
1. Verify that you have read access to the files. Check the progress log on the client for messages on why the backup failed. Correct problems and retry the backup.
2. On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to the files.
3. On Macintosh clients, this code can be due to multiple backups being attempted simultaneously on the same client. Some possible solutions are:
o Adjust the backup schedules.
o If the client is only in one class, set the general class attribute, Maximum Jobs per Class, to 1.
o Set the NetBackup global attribute, Maximum Jobs Per Client, to 1 (note that this limits all clients in all classes).
4. For a UNIX database extension client (for example, NetBackup for Oracle), this can mean a problem with the script that is controlling the backup.
Check the progress report on the client for a message such as "Script exited with status code = number" (the number will vary). The progress log also usually names the script.
Check the script for problems. Also, check the troubleshooting logs created by the database extension. See the NetBackup guide that came with the database extension for information on the scripts and troubleshooting logs.
Message: the archive failed to back up the requested files
Explanation: Errors caused the user archive to fail.
Recommended Action:
Verify that you have read access to the files. Check the progress log on the client for messages on why the archive failed. Correct problems and retry the archive.
On Windows NT clients, verify that the account used to start the NetBackup services has read access to the files.
Message: unable to determine the status of rbak
Explanation: On DomainOS clients, rbak is used to do restores. If rbak does not exit with a status message, NetBackup cannot determine whether the restore worked or not.
Recommended Action: Check for a new core file to see if rbak aborted. Check the ps output to see if rbak is hung. If so, kill it and try again. Check the progress log for any unusual messages from rbak.
Message: an extension package is needed but was not installed
Explanation: A NetBackup extension product is required in order to perform the requested operation.
Recommended Action: Install the required extension product.
Message: allocation failed
Explanation: Allocation of system memory failed because there is insufficient system memory available. This could be caused by the system being overloaded with too many processes and not enough physical or virtual memory.
Recommended Action: Free up memory by terminating unneeded processes that consume memory. Add more swap space or physical memory.
Message: system call failed
Explanation: A system call failed. This status code is used for a generic system call failure that does not have its own status code.
Recommended Action:
1. Check the All Log Entries and Problems reports to determine which system call failed and other information about the error.
2. A frequent cause is that the server's file system is full. For example, if you see a message similar to the following in the Problems report or bpdbm activity log:
06/27/95 01:04:00 romb romb db_FLISTsend failed: system call failed (11)
06/27/95 01:04:01 romb romb media manager terminated by parent process
06/27/95 01:05:15 romb romb backup of client romb exited with status 11 (system call failed)
On UNIX systems, run a df command on the /usr/openv/netbackup/db directory.
If the df command does not reveal the problem, check the bpdbm activity logs or do a grep for the message system call failed
in /usr/openv/netbackup/db/error/*
On Windows NT systems, verify there is room in the disk partition where NetBackup is installed.
3. Verify that the system is not running out of virtual memory. If virtual memory is the problem, shut down unused applications or increase the amount of virtual memory.
To increase virtual memory on Windows NT, 98, and 95:
a. Display the Control Panel.
b. Double-click System.
c. On the Performance tab, set Virtual Memory to a higher value.
4. Check for a semaphore problem. This error can be caused by the system not having enough semaphores allocated. This is most commonly seen on Solaris 2 servers when an RDBMS is also running.
The symptoms of the problem vary. In some cases, error messages in the NetBackup log indicate a backup failure due to an error in semaphore operation; another symptom is the inability of the NetBackup Device Manager service Media Manager device daemon, ltid, to acquire a needed semaphore (this is the NetBackup Device Manager service on Windows NT).
System requirements vary; thus, no absolute recommendations can be made. One customer running both NetBackup and ORACLE on their Solaris server made the following changes to their /etc/system file and then rebooted the system (boot -r); the changes were found to be adequate:
set semsys:seminfo_semmni=300
set semsys:seminfo_semmns=300
set semsys:seminfo_semmsl=300
set semsys:seminfo_semmnu=600
Set these attributes to a value great enough to provide resources to all applications on your system.
5. Check for a shared memory problem. This error can occur if the system cannot allocate enough shared memory. This usually occurs when you use multiplexing, which increases the shared memory requirements. A symptom is an entry similar to the following in a NetBackup log (or report) could not allocate enough shared memory
If you see this type of message, refer to the vendor documentation for your platform for instructions on increasing the amount of shared memory on your system.
Because system requirements vary, we can make no absolute recommendations, other than to use values great enough to provide resources to all applications. Although, in at least one instance, the following was found to be adequate on a Sun platform:
set shmsys:shminfo_shmmax=8388608
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmnu=600
set semsys:seminfo_semmns=300
After making the changes to the /etc/system file on the Sun platform and rebooting with boot -r, the problem was resolved. Note that in the above, shminfo_shmmin must be less than or equal to 100 for NetBackup processes to run.
6. Examine other activity logs or the progress log on the client.
7. If a backup on a Windows NT NetBackup client fails with status code 11 and the client is using Open Transaction Manager (OTM) for open file management, it is possible that the error was caused by the OTM cache file being full. If this is the case and bpbkar activity logs are turned on, a message similar to the following should appear at the end of the backup:
04/28/99 11:27:56 AM: [216]: ERR - OTM Error:0xe0001005
04/28/99 11:27:59 AM: [216]: INF - OTM Terminate - disabled for all processes
04/28/99 11:27:59 AM: [216]: FTL - Backup operation aborted!
If this error is encountered, you may need to increase either the initial OTM cache size or the maximum OTM cache size, depending on the requirements of your installation and your usage of OTM.
Message: file open failed
Explanation: An open of a file failed.
Recommended Action: Check the NetBackup Problems report. Try to determine the file and why the error occurred. A possible cause is a permission problem with the file. For detailed troubleshooting information, create an activity log directory for the process that returned this status code. Then, retry the operation, and check the resulting activity log.
Message: file read failed
Explanation: A read of a file or socket failed. Possible causes include:
· I/O error reading from the file system.
· Read of an incomplete or corrupt file.
· Socket read failing. A socket read failure can be caused by a network problem or a problem with the process that is writing to the socket.
Recommended Action:
1. Check the NetBackup Problems report for clues on where and why the problem occurred.
2. For a FlashBackup client, check the /var/adm/messages log for errors like the following:
Mar 24 01:35:58 bison unix: WARNING: sn_alloccache: cache /dev/rdsk/c0t2d0s3 full - all snaps using this cache are now unusable
This indicates that the cache partition is not large enough. If possible, increase the size of the cache partition. Or, if multiple backups are using the same cache, either reduce the number of concurrent backups by rescheduling some of them or reschedule the entire backup to a