problem with policy

[mlorencak]

Hi...

Have a very strange problem, not know how to solve it.
I have set both policy to 5 weeks, then include 5 client with that policy in the same group. When I do the backup
NW sets expiration time of that tape on 10 years. Can
someone tell me why. It is true, that I have another policy
set on 10 year, but it isn't mentioned in any client or group.

Thanks in advance!

LP, Mitja

 

[605]

Just have a look which save sets are stored on that piece of media -
obviously there must at least be one with the retention policy of 10 years.

Run "mminfo -q "volume=_vol_name_" -r "client,name,ssretent" to obtain
that info.

Then separate these save sets to another pool. Different retention policies
is one of the technical reasons why you should use different pools.

 

[wallace88]

Volume expiration is different from save set expiration.

Which are you referring to that is set to 10 years?

As 605 suggested, use the mminfo command to verify the saveset's retention time. Or you can try the following:

mminfo -avot -r volume,client,ssid,ssbrowse,ssretent,name volume_name

This will also show the saveset id and also it's browse time.

 

[605]

As fas as i have been told, since a while (7.0?) the volume expiration time
will be the same as the retention date of the "last expiring save set".

 

[wallace88]

605... your description sounds more like when a volume will be a candidate for recycling.

Volume expiration is one of the information that is set and stored in an ANSI tape label when a tape is labeled prior to writing.

 

[605]

I think i found the source for my information:

Prior to NetWorker release 6.0, the volume expiration date was a default,
two-year period from the date on which the volume was most recently labeled.
As of release 6.0, NetWorker tracks volume retention time. The volume
retention time is an unconfigurable value calculated from the maximum of
retention times of all save sets in the volume.