|
|
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."
The following information applies only to UNIX and Linux systems:
The following information applies only to UNIX and Linux systems:
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 synthetic backup job may terminate with a status code 1 under the following conditions:
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:
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> 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:
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.
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.
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 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.
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
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.