How to extend the expiration date on expired images after the NOexpire touchfile was created, and images are now beyond their expiration date

Article:TECH175365  |  Created: 2011-11-24  |  Updated: 2011-11-24  |  Article URL
Article Type
Technical Solution



This issue may occur after implementing the NOexpire touch file, and and allowing sufficient time pass so as to allow some images to go past their expiration date.   When this occurs, these images cannot have their expiration date extended with the bpexpdate command, using either -d or -recalculate switched, on a backupid basis, as bpdbm does not allow this action on an image whose expiration date has been reached or surpassed.   Attempts to extend the image's expiration date will result in the diagnostic message:

unable to process request


Should these circumstances arise, the following methods may be used to extend the expiration date of the backups.  Note, either method requires that the backup IDs are known.

1) Use bpexpdate to extend the expiration date of the media on which the backups reside.  This action is permissable by NetBackup, and will result in consistent images and media databases.  Note however that this will update the expiration date for ALL  images on each tape.  The media IDs can be obtained by inspecting the fragments of the individual backup IDs.  This can be done using the bpimagelist command:

   /usr/openv/netbackup/bin/admincmd/bpimagelist -backupid <backup  ID>

Once the media IDs are known, run the following bpexpdate command to update the expiration date to the desired future date:

   /usr/openv/netbackup/bin/admincmd/bpexpdate -m <media ID>  -d <date>

2) The backup images may also be expired on a bacukpid basis using the -backupid, -d 0 and -justimage switches on the bpexpdate command, after obtaining the media IDs using bpimagelist, as described in the workaround above.  Once the media IDs are known, and the backup IDs have been expired,  freeze the media to protect the backup images on them.  Then the  needed images may be recreated by the import process, after which the bpexpdate command can then be used to extend each backup ID's expiration date.



NOTE: Do not manually adjust the backup header file's retention level.  This may protect the image files, but will not protect the media on which the backups reside, and can lead to database inconsistencies, and possbily data loss, as the media can be expired by normal NetBackup processing and be overwritten.

Article URL

Terms of use for this information are found in Legal Notices