NetBackup status code: 191
Message: no images were successfully processed
Explanation: One of the following has occurred:
A verify, duplicate, Auto Image Replication, automatic import, or import was tried and failed for all selected images.
If the STS_EFILESYSTEM error code appears (error 2060063) for BasicDisk or AdvancedDisk, the file system is not configured correctly. The Allocation Unit Size of the NTFS file system is too small for the BasicDisk or AdvancedDisk data writes. Or, the maximum fragment size that NetBackup configures is too large.
If a backup or duplicate job is configured with a retention level greater than 25 and the storage unit specified in the policy is managed by a media server that runs a version of NetBackup previous to NetBackup 8.0, the backup jobs associated with the policy fail.
Recommended Action: Do the following, as appropriate:
Check the NetBackup Problems report for the cause of the error. To obtain detailed troubleshooting information, create an admin debug log directory and retry the operation. Check the resulting debug log.
If the backup or duplicate job failed for a policy configured with a retention level greater than 25, you can either upgrade the media server to NetBackup 8.0 or later or set the retention level between 0 and 25. Note that the retention period for level 25 is always set to expire immediately and this value cannot be changed.
If the error was encountered during duplication of backups, check the duplication progress log to help determine the root cause of the problem.
An Auto Image Replication job may cause this error. If the storage lifecycle policy names or data classifications do not match the originating domain and the target domain, the import job fails. Failed imports appear in the Problems report when it is run on the target master server. The image is expired and deleted during catalog cleanup. Note that the originating domain does not track failed imports.
More information is available about troubleshooting this problem:
For more information on troubleshooting this problem, please see the About Troubleshooting Auto Image Replication topic of the NetBackup Troubleshooting Guide.
An automatic import job may cause this error. This job is an import job that shows a storage lifecycle policy name.
More information is available about troubleshooting this problem:
For more information on troubleshooting this problem, please see the About Troubleshooting Auto Image Replication topic of the NetBackup Troubleshooting Guide.
If a Vault job encountered the error responsible for the duplication, check the duplicate.log files in your sidxxx directories to determine the root cause:
UNIX: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where xxx is the session ID)
Reduce the maximum fragment size on the storage unit that writes to this file system. This value is typically less than 20 GB. But you may need to adjust the maximum fragment size as necessary until the STS_EFILESYSTEM errors no longer occur. The value is based on how much data that the storage unit writes to the image.
To change this value, in the NetBackup Administration Console, in the left pane, expand NetBackup Management > Storage. Then in the right pane, double-click the storage unit for this file system. In the Change Storage Unit dialog box, change the value of the Maximum Fragment Size to 20480 MB (20 GB) by checking the Reduce fragment size to checkbox and entering the new value.
Increase the Allocation Unit Size by reconfiguring the file system. This usually requires that you format the file system, so this action may not be a feasible for an existing file system. Consider this when you create a new file system for BasicDisk images or AdvancedDisk images. Because setting this value is different on each OS file system, refer to the appropriate OS or file system documentation for instructions.
Ensure that the Logical Storage Unit (LSU) name or the Domain Volume name has less than 50 ASCII characters, including a hyphen (-) and an underscore (_), and that the name does not have a blank space.
Click here to view technical notes and other information on the Veritas Technical Support website about this status code.