8 Krypton

Re: Savesets not expiring - the retention time is invalid

I don't remember the details, but in 7.4.4.3 some of the issues with clretent have been resolved - can you try that patch? Or even 7.4.4.4....
0 Kudos
8 Krypton

Re: Savesets not expiring - the retention time is invalid

I'll take a look at the release notes and see if we can justify an upgrade; I have a call logged with EMC so I will see if they can also offer advice on this.
0 Kudos
8 Krypton

Re: Savesets not expiring - the retention time is invalid

I've returned to looking at this one - some more interesting information. So looking at one of these tapes:

nsrim -V A92944

returns:

Cross check completed successfully

A92944: 384 GB used, 233 save sets, full, 9 browsable save sets, 224 recyclable save sets
62173:nsrim: nsrim has finished at Mon Jun 22 11:47:56 2009.

mminfo -q volume=A92944 -r client,name,savetime,level,ssbrowse,ssretent,clretent,ssflags,clflags|grep -v clretent|wc -l

224
mminfo -q volume=A92944 -r client,name,savetime,level,ssbrowse,ssretent,clretent,ssflags,clflags|grep vrEF|wc -l

223
mminfo -q volume=A92944 -r client,name,savetime,level,ssbrowse,ssretent,clretent,ssflags,clflags|grep -v vrEF

client name date lvl browse retent clretent ssflags clflg
s-cc-rwp01 E:\ 02/23/09 full 03/23/09 03/23/09 03/23/09 vrEiF E

So the "9 browsable savesets" which seem to be stopping this tape recycling do not get listed as being in the media database.
0 Kudos
8 Krypton

Re: Savesets not expiring - the retention time is invalid

So what I am going to look at now is deleting the tape and scanning in then running the same queries again...
0 Kudos
8 Krypton

Re: Savesets not expiring - the retention time is invalid

Scanning the tape back in discovered an interesting result; the savesets returned by mminfo matched the recyclable tapes but the nsrim -V volume seemed to be referencing ana additional 9 browsable savesets that were not listed in the mminfo output.

I'm now running a media scavenge on this box and seeing what results this gives.
0 Kudos
8 Krypton

Re: Savesets not expiring - the retention time is invalid

Ran the media scavenge successfully; looked at tape A92944 again - ran nsrim -V then checked the savesets:

Cross check completed successfully

A92944: 45 GB used, 67 save sets, read-only, 9 browsable save sets, 58 recyclable save sets


124 root@bkpsrv30:->mminfo -q volume=A92944|wc -l
59
125 root@bkpsrv30:-


We still appear to be referencing the phantom savesets....?
0 Kudos
8 Krypton

Re: Savesets not expiring - the retention time is invalid

Try to add -av so that lines goes

mminfo -av -q volume=A92944|wc -l
0 Kudos
8 Krypton

Re: Savesets not expiring - the retention time is invalid

I already did but no luck - it turns out one of the savesets still has a browse/retention of 2045 still - I am trying to recall the workaround for this but here is some strange behaviour:

ssid clone id retent clretent
1570960368 1235416048 06/24/09 07/31/45

nsrmm -e "24 June 2009" -S 1570960368/1235416048

1570960368 1235416048 01/19/38 07/31/45

nsrmm -e "1 day" -S 1570960368/1235416048

1570960368 1235416048 01/19/38 06/25/09

nsrmm -e "today" -S 1570960368/1235416048

1570960368 1235416048 06/24/09 07/31/45

nsrmm -e "24 June 2009" -S 1570960368/1235416048

1570960368 1235416048 06/24/09 07/31/45

nsrmm -e "1 day" -S 1570960368


retention policy expiration `Thu Jun 25 15:53:19 2009' must be later than browse policy expiration `Tue Jan 19 04:12:28 2038'

ssid clone id retent clretent browse

1570960368 1235416048 06/24/09 07/31/45 01/19/38

nsrmm -w "1 day" -S 1570960368

retention policy expiration `Wed Jun 24 00:00:00 2009' must be later than browse policy expiration `Thu Jun 25 15:57:41 2009'
0 Kudos
8 Krypton

Re: Savesets not expiring - the retention time is invalid

nsrmm -e "2 day" -S 1570960368/1235416048
nsrmm -w "1 day" -S 1570960368/1235416048


1570960368 1235416048 01/19/38 06/26/09 06/25/09

nsrmm -w "1 day" -e "2 day" -S 1570960368

1570960368 1235416048 06/26/09 06/26/09 06/25/09

nsrmm -w "yesterday" -e "today" -S 1570960368

1570960368 1235416048 06/24/09 06/26/09 06/23/09
0 Kudos
8 Krypton

Re: Savesets not expiring - the retention time is invalid

Well, you really did a mess, didn't you :D Did you used any customer expiration time for these during backups? Clock was ok? Oh sorry, not backups, but cloning... these savesets are cloned, right? I do understand 2038 limit, but I have no idea how you managed to get 2045 for clretent :D

I know how I can get 2038 mess with PowerSnap, but not sure what is the situation there. Is there anything common to savesets which exhibit this issue?

It's interesting issue and trick would be to figure out what has caused it in first place and conditions surrounding it. Did you talk to the support?
0 Kudos