Symantec NetBackup status code 0 to status code 5

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.

Below are some of the NetBackup status error codes from Status Code 0 to Status Code 5 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 0
Message: the requested operation was successfully completed
Explanation: No problems were detected with the requested operation.
Recommended Action: No action is needed, unless a database was backed up
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.

NetBackup status code: 1
Message: the requested operation was partially successful
1 Chapter
Explanation: A problem was detected that may require corrective action during
the requested operation.
Recommended Action: Check the All Log Entries report and also the progress
log (if there is one).
The following are some of the problems that can appear under status code 1:
■ A file or a directory path is more than 1023 characters long.
For NetBackup Snapshot Client, the maximum path name length is 1000
characters for snapshot backups, not 1023. When the snapshot is created, a
new mount point is added to the beginning of the file path. If the new mount
point plus the original file path exceeds 1023 characters, the backup fails with
status code 1. The progress log includes the entry
ERR-Skipping long dir path.
■ You cannot open a file.
The file may have been locked for some reason.
■ The following information applies only to UNIX and Linux systems:
NetBackup cannot get the link name of a file.
■ The following information applies only to UNIX and Linux systems:
NetBackup cannot process a sparse file.
■ A read error that was encountered in a file.
■ File is of an unknown type, or may be hidden.
■ The following information applies only to UNIX and Linux systems:
The lstat system call fails on a file that is eligible to be backed up. This error
may be a permission problem.
■ The following information applies only to UNIX and Linux systems:
A file cannot be locked that has mandatory locking enabled.
■ Asynthetic backup job may terminate with a status code 1 under the following
conditions:
■ No images were found to synthesize (status code = 607).
■ TIR information has been pruned from component images (status code =
136).
■ Image format is unsupported (status code = 79).
The synthetic backup job logs the actual status code in the NetBackup error
log. Refer to the documentation for the corresponding NetBackup error code
for the corrective action to take.
■ A BMR job may terminate with status code 1 in the following situation:
NetBackup status codes
NetBackup status codes
36
You save the BMR configuration and it returns an error even though the child
jobs completed successfully. For information, examine the Detailed Status
tab of the Job Details dialog box, or the nbjm unified log (originator ID 117).
■ A policy that contains multiple backup scripts starts a scheduled backup of a
UNIX database extension client. If it fails with a status code 1, some of the
backup scripts returned a failure status.
■ On clients using Windows Open File Backups (WOFB) to back up open or active
files, the following may occur:
Volume snapshots were not enabled successfully for the backup.
The following logging messages should appear in the bpbkar32 logs if volume
snapshots were not successfully enabled.
If multistreamed backup jobs are enabled, log messages similar to the following
appear that indicate volume snapshots were not enabled for the multistreamed
backup job:
11:05:44.601 AM: [1536.724] <4> tar_backup::V_AddToFI_XBSAObj:
INF – Volume snapshots not enabled for: D:\Directory1
If multistreamed backups were not enabled, log messages similar to the
following appear, which indicate volume snapshots were not enabled for the
non-streamed backup job:
1:59:41.229 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_CreateSnapshot: INF –
===============================
1:59:41.229 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_CreateSnapshot: INF – Attempting to
create snapshots for D:\Directory1
1:59:41.229 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_CreateSnapshot: INF – CREATE request:
C:\Program Files\VERITAS\NetBackup\bin\bpfis create -fim VSP
“D:\ Directory1”
1:59:41.799 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_ParseBpfisOutput: INF – Snapshot
creation, FIS_ID: 1058813981
1:59:41.799 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_ParseBpfisOutput: INF – Snapshot creation
EXIT STATUS 11: system call failed
1:59:41.799 PM: [2076.2088] <4>
V_Snapshot::V_Snapshot_CreateSnapshot: INF – Snapshot creation
was not successful
1:59:41.799 PM: [2076.2088] <4>
NetBackup status codes 37
NetBackup status codes
V_Snapshot::V_Snapshot_CreateSnapshot: INF –
===============================
In this case, examine the bpfis logs for error messages regarding snapshot
creation failures. More details are available on the bpfis logs.
See the NetBackup Snapshot Client Administrator’s Guide.
In the bpfis logs, the following messages may appear when snapshot creation
fails for Windows Open File Backup:
First message:
04:01:14.168 [376.2364] <32> onlfi_fi_split: VfMS error 11; see
following messages:
04:01:14.168 [376.2364] <32> onlfi_fi_split: Fatal method error
was reported
04:01:14.168 [376.2364] <32> onlfi_fi_split: vfm_freeze_commit:
method: VSP, type: FIM, function: VSP_make
04:01:14.168 [376.2364] <32> onlfi_fi_split: VfMS method error
3; see following message:
04:01:14.168 [376.2364] <32> onlfi_fi_split: snapshot services:
snapshot creation failed: invalid argument(s).
Cause: VSP was not enabled because the VSP snapshot for the backup did not
meet the specified minimum time in the Busy File Wait VSP setting.
Either increase the Busy File Timeout VSP setting (recommended setting: 300
seconds or more) or submit the backup job when the volume has less activity.
Second message:
04:17:55.571 [1636.3224] <2> onlfi_vfms_logf: snapshot services:
(null): There was an unexpected error while preparing the VSP
snapshot transaction. Dumping the parameter array to provide
more information: Error 112 from VSP_Prepare
Cause: VSP was not enabled for the backup because the client for the VSP
Snapshot Cache files does not have enough free disk space.
Free up disk space on the volumes being backed up.
Third message:
If Microsoft Volume Shadow Copy Service (VSS) is used as the Windows Open
File Backup snapshot provider and snapshot creation fails, refer to the
following: Event Viewer’s Application and System Logs for error information.
■ A snapshot error may have occurred. Also, you may have some clients that
use the Windows Open File Backup option to back up open or active files. In
this case, a log message in the bpbkar32 debug log appears, which indicates
that a snapshot error occurred.
NetBackup status codes
NetBackup status codes
38
The following is an example of a snapshot error:
8:51:14.569 AM: [1924.2304] <2> tar_base::V_vTarMsgW: ERR –
Snapshot Error while reading test.file
See the recommended actions under status code 156.
■ The granular processing operation of an Exchange Granular backup job has
failed to complete successfully. Check the bpbkar debug log for more
information. A legacy (non-VSS) backup still truncates transaction logs if the
job ends with status 1 because a granular processing operation failed. In this
situation, the backup image is suitable for database recovery.

NetBackup status code: 2
Message: none of the requested files were backed up
Explanation: A backup or archive did not back up any of the files in the file list.
This status code applies primarily to automatic backups using Lotus Notes or SQL
database agents, when all the backups that are job-related have failed. Or, an
Enterprise Vault backup has failed. It should not occur for standard file system
backups.
Opena NetBackup support case (recommended in Symantec document 276903.pdf)
if you encounter this error for a UNIX, Linux, or Windows file system backup, or
for database agents other than SQL Server or Lotus Notes.
Recommended Action: Do the following, as appropriate:
■ The following information applies only to Lotus Notes:
This error occurs when archive style logging is not enabled for the Lotus
Domino server on UNIX. It also occurs when another backup of the transaction
logs is in progress.
■ For troubleshooting guidance, such as a list of logs to gather, and for details
on particular issues, refer to the Symantec support document 276903.pdf.
■ See the troubleshooting topic of the appropriate guide for a description of
troubleshooting tools:
■ NetBackup for Microsoft SQL Server Administrator’s Guide
■ NetBackup for Lotus Notes Administrator’s Guide
■ NetBackup for Enterprise Vault Agent Administrator’s Guide

NetBackup status code: 3
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 or status 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 the user that owns the
files, a superuser on UNIX, or an administrator on Windows.

NetBackup status code: 4
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 and Linux 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. (If you do not
have the necessary permissions, have the system administrator delete the files.)

NetBackup status code: 5
Message: the restore failed to recover the requested files
Explanation: Errors caused the restore to fail.
Recommended Action: Perform the following items in the order presented:
■ Ensure that the client’s server list contains entries for the master server and
any media servers that can be used during a backup or restore.
■ Examine the status or the progress log on the client for messages on why the
restore failed. Also, check the All Log Entries report on the server.
■ Check ownership and permission on directories where files are restored.
■ Correct the problems that you find and retry the restore.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *