Wrong Expiration Dates Set for images.

[GulzarShaikhAUS]

Hi All,

I came accross a situation where Netbackup set wrong expiration dates on images. Please see bpimagelist output. The output are partial.

Just check the retention level mentioned which is correct. 1 week in this case and the expiration date metioned in the output is 3 weeks later date than the backup date.

C:\Program Files\Veritas\NetBackup\bin\admincmd>bpimagelist.exe -L -backupid exc
hange-dag.sipchem.local_1306677780

Client:            exchange-dag.sipchem.local
Backup ID:         exchange-dag.sipchem.local_1306677780
Policy:            Exch2010-GRT-NonExec
Policy Type:       Ms-Exchange-Server (16)
Proxy Client:      (none specified)
Creator:           root
Name1:             (none specified)
Sched Label:       Full
Schedule Type:     FULL (0)
Retention Level:   1 week (0)
Backup Time:           5/29/2011 5:03:00 PM (1306677780)
Elapsed Time:      7941 second(s)
Expiration Time:       6/19/2011 5:03:00 PM (1308492180)
Compressed:        no
Client Encrypted:  no
Kilobytes:         308783514
Number of Files:   14344
Number of Copies:  1
========================================================================================
C:\Program Files\Veritas\NetBackup\bin\admincmd>bpimagelist.exe -L -backupid exc
hange-dag.sipchem.local_1306677732

Client:            exchange-dag.sipchem.local
Backup ID:         exchange-dag.sipchem.local_1306677732
Policy:            Exch2010-GRT-NonExec
Policy Type:       Ms-Exchange-Server (16)
Proxy Client:      (none specified)
Creator:           root
Name1:             (none specified)
Sched Label:       Full
Schedule Type:     FULL (0)
Retention Level:   1 week (0)
Backup Time:           5/29/2011 5:02:12 PM (1306677732)
Elapsed Time:      82 second(s)
Expiration Time:       6/19/2011 5:02:12 PM (1308492132)
Compressed:        no
Client Encrypted:  no
Kilobytes:         165535
Number of Files:   30
Number of Copies:  1
 

[Nicolai]

Has this backup been processed by Storage Lifecycle Policies ?

[J_H_Is_gone]

Got to master server properties - Retention Levels

and verify that Retention level 0 (with the name of 1 week) is actually set to 1 week.  This can be changed but it will not change the name or number of the level.

[Marianne]

Any possibility that someone else has manually extended the image expiration date?

[GulzarShaikhAUS]

No SLP are being used. I dont think the expiration date is extended manually. Though I will check the rentention levels in Host properties but it happened for few images only.

I wanted to see if this is a known issue or a bug.

Thanks a lot guys for your vaulable suggestions.

[Yasuhisa_Ishika]

I have never heard for years such bug or issue. I assume that anyone had set 3 weeks retention for level 0. Once after backup was taken, anyone changed it back to default.

[Nicolai]

- FYI - NBU 6.5.3 had issues with the infinity retention level.

[watsons]

From admin guide:

"The expiration date for the imported items is the current date plus the retention period. For example, if a backup is imported on November 14, 2007 and its retention period is one week, the new expiration date is November 21, 2007. "

If the image has expired, and then imported again a week ago, there can be a new expiration date...

2nd thought: But your backup image looks like a Exchange data using GRT.. that has to go to disk.. not tape.

[GulzarShaikhAUS]

One more thing is in one of the image, only one fragment has this issue and other fragments have correct expiration date.

Only pasting F4 contents. Other fragments have retention level 0 and taken correctly as one week.

 ID:               O:\STU1\exchange-dag.sipchem.local_1306674748_C1_F4
 Host:             sipc-mbxdb02
 Block Size:       262144
 Offset:           0
 Media Date:            1/1/1970 3:00:00 AM (0)
 Dev Written On:   -1
 Flags:            0x0
 Media Descriptor:        sipc-mbxdb02
 checkpoint:       0
 resume num:       0
Copy number:       2
 Fragment:         1
 Kilobytes:        190023968
 Remainder:        0
 Media Type:       Media Manager (2)
 Density:          hcart3 (20)
 File Num:         2
 ID:               000164
 Host:             sipc-netbackup
 Block Size:       65536
 Offset:           347283
 Media Date:           5/30/2011 8:32:10 AM (1306733530)
 Dev Written On:   2
 Flags:            0x0
 Media Descriptor:        ?
 Expiration Time:      6/19/2011 4:12:28 PM (1308489148)
 MPX:              0
 retention_lvl:    3 weeks (2)
 Try to Keep Time:       1/1/1970 3:00:00 AM (0)
 Copy Creation Time:     5/30/2011 10:24:21 AM (1306740261)
 checkpoint:       0
 resume num:       0
 Key tag:          *NULL*
 STL tag:          *NULL*

[Anton_Panyushki]

Do these fragments have different media/destination?

Check media retention level.