01-22-2014 09:56 AM
I'm using NB 7.5.0.3 on Solaris. I have some tapes that were somehow set to expire in december 16th 2013 but they contain images that have a retention period of 2 years and the tapes were first mounted in around december 5th 2013! I tried to change the media expiration dates with bpexpdate and it just says "unable to process request". As it so happens, we did a reboot of our server this morning and it didn't change anything... Anyone ever had a similar problem?
Thanks!
Solved! Go to Solution.
01-22-2014 10:28 AM
Media expiration (mediaDB) is different from image retention. (imageDB)
vmchange command changes volume information in the Enterprise Media Manager database. Expiration option with vmchange tells EMM that this volume is now expired, which means it can not be used further. Expiration with vmchange will not expire the images and release the media.
MEDIADB:
vmchange -exp 0 -m 0123L3 (will change media 0123L3 to be based off image retention or - as shown below.)
This would mean someone may be placing a "hard date" on media/tape 0123L3 usage. Should be letting the length of retention of image dictate that. By default its set to 0.
NOTE: Execute (replace mediaid)
nbemmcmd -listmedia -mediaid 0123L3
Will show you two entries
a. Media expiration (should be - (.. just a - for the entry)
b. Image expiration should be a date for Images to expire
Many confuse these 2.
ImageDB:
The bpexpdate command allows the expiration date and time of backups to be changed
in the NetBackup image catalog. (imageDB)
bpexpdate -m 0123L3 -d 0 (will expire all images IF hard date on mediadb has not passed)
01-22-2014 10:08 AM
Forgot to mention that I did a bpimage -cleanup and it didn't cleanup those tapes. I wasn't aware that the date wasn't set properly at first.
01-22-2014 10:28 AM
Media expiration (mediaDB) is different from image retention. (imageDB)
vmchange command changes volume information in the Enterprise Media Manager database. Expiration option with vmchange tells EMM that this volume is now expired, which means it can not be used further. Expiration with vmchange will not expire the images and release the media.
MEDIADB:
vmchange -exp 0 -m 0123L3 (will change media 0123L3 to be based off image retention or - as shown below.)
This would mean someone may be placing a "hard date" on media/tape 0123L3 usage. Should be letting the length of retention of image dictate that. By default its set to 0.
NOTE: Execute (replace mediaid)
nbemmcmd -listmedia -mediaid 0123L3
Will show you two entries
a. Media expiration (should be - (.. just a - for the entry)
b. Image expiration should be a date for Images to expire
Many confuse these 2.
ImageDB:
The bpexpdate command allows the expiration date and time of backups to be changed
in the NetBackup image catalog. (imageDB)
bpexpdate -m 0123L3 -d 0 (will expire all images IF hard date on mediadb has not passed)
01-22-2014 10:33 AM
Please show us output of this command for one of these tapes:
nbemmcmd -listmedia -mediaid <media-id>
Any chance this media is under SLP control?
01-22-2014 10:45 AM
Here's the output for one of the tapes where I tried to set the expiration date for december 16th 2015 and it didn't work, SUPPOSEDLY!!!