Veritas NetBackup™ Release Notes
- About NetBackup 8.3.0.1
- New features, enhancements, and changes
- NetBackup 8.3.0.1 new features, changes, and enhancements
- Operational notes
- NetBackup installation and upgrade operational notes
- NetBackup administration and general operational notes
- NetBackup administration interface operational notes
- NetBackup Bare Metal Restore operational notes
- NetBackup Cloud operational notes
- NetBackup with Veritas CloudPoint operational notes
- NetBackup deduplication operational notes
- NetBackup internationalization and localization operational notes
- NetBackup for NDMP operational notes
- NetBackup Snapshot Client operational notes
- NetBackup virtualization operational notes
- Appendix A. About SORT for NetBackup Users
- Appendix B. NetBackup installation requirements
- Appendix C. NetBackup compatibility requirements
- Appendix D. Other NetBackup documentation and related documents
Errors are shown in the jobs detail when NetBackup attempts to expire images from non-WORM capable storage
NetBackup routinely attempts to remove expired backups from the catalog and subsequently on storage. In cases where backups are WORM-locked on storage beyond the catalog expiration time, attempts to delete the data from storage causes the job to complete with partial-success. The job completes with a status (1) with a per-image error code of 2060069 reported in the job details. Each cleanup cycle attempts to remove the backup until storage successfully allows the deletion of the WORM-locked images.
Workaround:
To remove the WORM images from the cleanup cycle, perform one of the following as appropriate:
Run a manual import to get the WORM images back into catalog.
Use the nbdelete -purge_deletion_list -backupid command to remove the WORM image backup IDs from deletion worklist. This command does not delete these images from storage, so you have to delete the images manually from storage.