BAR not displacing new expiry date after extending expiry date

[Dollypee]

Netbackup version: 7.1.0.4

OS: Win 2k3, R2, 64bit

after running bpexpidate command to extend expiry date of backup id, BAR is still displacing initial expiration date of the backup image. However,checking the client on image on disks report, i could see that the new expiration date has been modified to new date. I'm just curious why the new date isn't displaying on the backup sets on BAR. Please i need your help.

[Manigandan_r]

Hi Dolly,

You have only extended the image expiration date so the image will exists.

If you want the media expiration date to be extended you have to use the below command

 bpexpdate -m media_id -d date x  (X denotes number of days you want extend i.e, 1 or 2...) 

[Manigandan_r]

Hi dolly,

the command can be more specific

 bpexpdate -m media_id -d MM/DD/YYYY

[Marianne]

Please show us a screenshot of what you see?

I don't see expiration date in my Java BAR GUI. The columns I have are:
Name  Backup Date  Size (Bytes)  Modified  Schedule Type  Policy   Image Format  Data Mover

*** EDIT ***

I have just checked Windows Admin Console as well - Expiration date does not show in BAR GUI.
Columns are:
Name   Time Backed Up   Attributes  Size  Time Modified

[mph999]

Not sure this is quite correct - from a quick test, my media expirely date is automatically updated when I increse the expire time of the backupid

Here is my backup image, retention of 1 day so expires Aug 8

IMAGE nbmaster00 0 0 8 nbmaster00_1375866968 test 0 *NULL* root Full 0 12 1375866968 86 1375953368 0 0 534208 2501 1 1 0 test_1375866968_FULL.f *NULL* *NULL* 0 1 0 0 0 *NULL* 0 0 0 0 0 0 0 *NULL* 0 0 0 *NULL* 887 0 0 299911 0 0 *NULL* *NULL* 0 0 0 0 *NULL* *NULL*

HISTO -1 -1 -1 -1 -1 -1 -1 -1 -1 -1

FRAG 1 1 534208 0 2 6 1 E01001 nbmaster00 65536 2 1375866968 1 0 *NULL* 1375953368 0 65548 0 0 0 1 0 1375867054 0 *NULL* *NULL*

root@nbmaster00 data $ bpdbm -ctime 1375953368

1375953368 = Thu Aug  8 02:16:08 2013

Here is the tape it is on 

 id     rl  images   allocated        last updated      density  kbytes restores

           vimages   expiration       last read         <------- STATUS ------->

--------------------------------------------------------------------------------

E01001  12      1   08/07/2013 02:16  08/07/2013 02:16   hcart      534208     0

                1   08/08/2013 02:16        N/A

I extend the image to 1 week

root@nbmaster00 data $ bpexpdate -backupid nbmaster00_1375866968 -d 08/14/2013 09:00:00

Are you SURE you want to change nbmaster00_1375866968

to expire on Wed 14 Aug 2013 09:00:00 AM PD y/n (n)? y

And the 'tape' expire time is automatically updated ...

 id     rl  images   allocated        last updated      density  kbytes restores

           vimages   expiration       last read         <------- STATUS ------->

--------------------------------------------------------------------------------

E01001  12      1   08/07/2013 02:16  08/07/2013 02:16   hcart      534208     0

                1   08/14/2013 09:00        N/A

[Dollypee]

=> Marianne, actually, to see time expires of a backup image from BAR, 1st ensure it's set to show from the colum layout. now click on view ----> uncheck "Show Netbackup History as a Timeline". This will let you see date/time your backup sets will expires. Please see attachment.

=> mph999, actually from my image on disk report from activity monitor, i could see the backup image has the new expiration date/time. My worry is just that, why is this not reflecting from "Time expires" on the BAR. I have done this before and i see it taking effect almost immediately on the BAR. I would like to know the command you ran to get the image on tape above.

I forgot to mention my storage unit is datadomain.

Thanks.

[Marianne]

Have you tried to close the GUI and open it again?

I have found that Java and Windows console don't always refresh soon enough.

[Dollypee]

I have done that. I went a step further restarting " Netbackup remote manager and monitor service". Previous date remain as it is. 

[mph999]

Commands were bpimagelist -l and bpmedialist

M

[Marianne]

You now need to tell us how image retention was changed. Seems the change was not successful?

Check image expiration from cmd with:

bpimagelist -client <client-name> -d 08/06/2013 -L

[Dollypee]

Marianne, I just felt you have a very huge point here. Here how's i extended the expiration date bpexpdate.

Backup was taken on 07/31/2013.

D:\Program Files\Veritas\NetBackup\bin\admincmd>bpexpdate.exe -backupid xxxxx_1234  -copy 1 -d 1/31/2014 12:00:00

Are you SURE you want to change xxxx_1234 copy 1
to expire on    1/31/2014 12:00:00 PM y/n (n)? y

But from bpimagelist, am still seeing initial expiration date: 8/21/2013

bpimagelist.exe -client XYZ -d 07/31/2013 -L

Client:            XYZ
Backup ID:         xxxx_1234
Policy:            xxxxxxxx
Policy Type:       Standard (0)
Proxy Client:      (none specified)
Creator:           root
Name1:             (none specified)
Sched Label:       Daily_Incr
Schedule Type:     INCR (1)
Retention Level:   3 weeks (7)
Backup Time:          7/31/2013 10:36:25 PM (1375324585)
Elapsed Time:      19606 second(s)
Expiration Time:      8/21/2013 10:36:25 PM (1377138985)
Compressed:        no
Client Encrypted:  no
Kilobytes:         734784256
Number of Files:   11
Number of Copies:  3
Number of Fragments:   7
 

Please help..

[Andy_Welburn · Accepted solution]

Number of Copies:  3

Look further down in the output - there are additional details specific to each copy. You *should* find that the correct expiration has been applied to the actual copy.

[Dollypee]

Thank you all. I can verify the correct expiration date has been applied to the actual copy. Thank you.