8 Krypton

Re: Savesets not expiring - the retention time is invalid

That link is for esg106764 and is solely for snapshot backups. If your save sets are not snapshot backups this does not apply and they might be due a different issue. What this article says is:

After a VSS snapshot backup with NMM a save set "VSS:\" is created and registered in the media db. The retention time on this save set is "1/18/2038".
The VSS:/ save set is used to create the index records for the writers and volume nodes (GUI presentation objects).

The retention time for the 'VSS:\' save set is, by design, set to 1/18/2038. This save set will be deleted when the associated data save set has expired and is removed from the media database. This lifecycle is handled through nsrsnapck, which is automatically run at the start of a snapshot enabled group or is run automatically once every 24 hours, whichever comes first.

Regards,
8 Krypton

Re: Savesets not expiring - the retention time is invalid

Thanks for explaining that Parviz!
0 Kudos
Phil_1
6 Indium

Re: Savesets not expiring - the retention time is invalid

I'm very interested in this thread...
I have loads of tapes that do not expire. I cannot run a delete on the cover savesets, well I can, but they do not work.
The part "This save set will be deleted when the associated data save set has expired and is removed from the media database." seems to be a chicken/ egg situation, as they are both on the same volume, and although they are expired, they are still in the media database until the volume has been recycled. Since the cover saveset is holding the tape from being recycled, the associated saveset cannot be removed from the media database.
What we have to do is manually do the work that NetWorker is supposed to do. We manually check the older volume that should have expired, and can only relabel the volume, as this seems to fix it and remove the ssid from the indexes, which I now understand is due to this 'design'.
We do not make use of VSS (we use VSS Save operations: VSS=*off), only PowerSnap for filesystems and SQL.
We are upgrading NW server and S/N from 7.3.3 to 7.5.1. We have done this in pre-prod (with a few issues left to fix), and plan in live for next month (18th Aug).
We are planning to upgrade NetWorker client software next week in pre-prod, for all clients and modules (NME/ NMS/ PowerSnap).
Unfortunately we are 100% Win 2003 SP1 (not SP2).
We followed the NetWorker procedure generator, however there were glaring mistakes in it.

Phil
0 Kudos
8 Krypton

Re: Savesets not expiring - the retention time is invalid

Phil

I'd be very cautious about manually deleting tapes unless you are hundred percent sure you can relabel them. Networker "should" manage everything, if you get to a point where it is not then chances are you have configured something wrong, you have a misunderstanding as to how it is working, or less likely some kind of bug!

I'd suggest first of all running nsrim -V volumename against a tape you believe should be recyclable - it will check the tape against the media database and give you a summary at the end on the state of all savesets - if all savesets are not recyclable your tape will not be - you then need to determine why those savesets are not recyclable - use the mminfo command to inspect retention times of the savesets where ssrecycle=false; if it has passed out of its recycle date check that all instances of that saveset up to the next full backup have also expired - if you have a dependency it will not expire until the dependency also expires; if you manually delete it then the dependent saveset becomes invalid before its expiry - assuming when you say "at Barclays" you are in a financial institution you may be opening yourself up to fines from a regulatory body if you cannot prove you can recover data within a certain period!

One other thing I'd suggest, if you are under a lot of pressure to produce backup media every day you may be trying to do too much with too little, or you have failed to take into account data growth. You need to check if this is the case and take action before it becomes a serious problem!
0 Kudos
8 Krypton

Re: Savesets not expiring - the retention time is invalid

You say:

"The retention time for the 'VSS:\' save set is, by design, set to 1/18/2038. This save set will be deleted when the associated data save set has expired and is removed from the media database"

We are seeing this and the VSS:/ save set from the NMM clients is holding our tapes. We need to manually relable them, and we're doing that weeks after the save set is supposed to be recycled.

So what is the solution to this problem? Manually labelling tapes? hardly!

Joe
0 Kudos
8 Krypton

Re: Savesets not expiring - the retention time is invalid

Do you see 2038 retention on data or metadata for ssid?
0 Kudos
8 Krypton

Re: Savesets not expiring - the retention time is invalid

Hello,

Suddenly we have the same problems with VSS:\ save sets which has retention time 1/18/2038.

Have you found solution for that?

Thanks

0 Kudos
8 Krypton

Re: Savesets not expiring - the retention time is invalid

This is most likely due to so-called 'cover' save sets. They are created when you use the NMM module and will not expire (this time stamp is the most far away a 32bit UNIX time stamp can offer).

Run something like "mminfo -q ... -r ... sumflags" or  "mminfo -q ... -r ... ssflags". If you see the 'K' in your flags, you got one.

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

And for the next time ... please open a new thread and do not mix your request with this old one. There might not even be any relationship any longer because the NW versions are so much different.

0 Kudos