cancel
Showing results for 
Search instead for 
Did you mean: 

Images not being set to expired at the right date and I can't change it

C_Moisan
Level 4

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!

1 ACCEPTED SOLUTION

Accepted Solutions

Alan_Blackwell
Not applicable
Employee Accredited Certified

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)

 

View solution in original post

4 REPLIES 4

C_Moisan
Level 4

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.

Alan_Blackwell
Not applicable
Employee Accredited Certified

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)

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

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?

C_Moisan
Level 4

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!!!

 

root@chopin:/u09/gestion/bin> nbemmcmd -listmedia -mediaid Q18020
NBEMMCMD, Version: 7.5.0.3
====================================================================
Media GUID:                     055394ba-5276-11e3-8000-8c1bc9445f29
Media ID:                       Q18020
Partner:                        -
Media Type:                     DLT
Volume Group:                   Voute_Qc_LTO5
Application:                    Netbackup
Media Flags:                    1
Description:                    ---
Barcode:                        Q18020L5
Partner Barcode:                --------
Last Write Host:                bellini
Created:                        11/21/2013 11:27
Time Assigned:                  12/02/2013 08:09
First Mount:                    12/03/2013 01:48
Last Mount:                     12/03/2013 01:48
Volume Expiration:              -
Data Expiration:                12/16/2015 00:00
Last Written:                   12/02/2013 08:09
Last Read:                      -
Robot Type:                     NONE
Robot Control Host:             -
Robot Number:                   -
Slot:                           -
Side/Face:                      -
Cleanings Remaining:            -
Number of Mounts:               1
Maximum Mounts Allowed:         0
Media Status:                   FULL MPX
Kilobytes:                      1754979584
Images:                         430
Valid Images:                   430
Retention Period:               1
Number of Restores:             0
Optical Header Size Bytes:      1024
Optical Sector Size Bytes:      0
Optical Partition Size Bytes:   0
Last Header Offset:             0
Adamm Guid:                     00000000-0000-0000-0000-000000000000
Rsm Guid:                       00000000-0000-0000-0000-000000000000
Origin Host:                    NONE
Master Host:                    chopin
Server Group:                   UNRESTRICTED_SHARING_GROUP
Upgrade Conflicts Flag:
Pool Number:                    7
Volume Pool:                    Vault
Previous Pool Name:             Scratch
Vault Flags:                    -
Vault Container:                -
Vault Name:                     -
Vault Slot:                     -
Session ID:                     -
Date Vaulted:                   -
Return Date:                    -
Media on Hold:                  0
====================================================================
Command completed successfully.
root@chopin:/u09/gestion/bin>
 
I just saw now that it does in fact show as 2015 in the volume group lists... So, it seems that NB is full of it and tells me it can'r process my request when in fact it did... ;) Thanks , I guess we can close this thread, I will mark Alan's post as the solution since he showed me a new command!