1 Rookie
•
6 Posts
0
883
October 22nd, 2021 08:00
Volume expiration wrong - (bad year)
Hello,
could someone please explain to me how is it possible that some volumes have a completely false expiration date?
I would like to force recycling but first I would prefer to understand what is the cause.
If I do "Show Save Set" in some of these Volumes with wrong expiration like volume L60067 (7/22/54) it contains Save Set with expiration in the range from April to June 2018.
In other cases like L60078 (expiration 09/21/57) i have much more recent Save Sets (July - August 2021).
Thanks for the support.
No Events found!
bingo.1
2.4K Posts
0
October 24th, 2021 02:00
'savetime' is absolute not the parameter you should look at. 'savetime' refers to the backup time/date, not to the expiration date of a save set. What you need to check is the save set retention time (ssretent). So your mminfo command should look similar to this one:
mminfo -q "volume=L60067,ssretent>01/01/2030" -r "client,name,level,savetime,ssbrowse,ssretent,ssid,cloneid"
Set the date to your appropriate value.
Then use the nsrmm command to correct the retention date as follows:
nsrmm -y -e <new_retention_time> -S <ssid/cloneid>
Please see the command line reference for more details.
bingo.1
2.4K Posts
0
October 23rd, 2021 08:00
Your screenshots are nice. However, the important information is missing. If you sort your lists by the retention time you will most likely see at least one save set which has a 'wrong' retention year (we have no idea what you consider the right one).
And of course we do not know why these save sets have been assigned a wrong retention date. Could be a software error but also a configuration/handling mistake.
And do not forget that one single save set is sufficient to rule the game ... to control the volume expiration.
PiloZ
1 Rookie
•
6 Posts
0
October 23rd, 2021 14:00
I thank you for the answer.
Unfortunately, looking at every save set, there isn't even one with the wrong expiration.
Look at these commands:
mminfo -av -r "volume,volretent" | grep L60067
L60067 07/22/54
mminfo -q "volume=L60067" -r "savetime,volume" | grep -v "/18 L60067"
date volume
mminfo -q "volume=L60067" -r "savetime,volume" | grep "/18 L60067" | wc -l
13734
If i check the most recent volumes, the expiration date is correct (a sign that at the moment it is working well).
In your opinion, given that each saveset of the volume L60067 is from 2018, don't I have to worry about recycling the volume?
Thanks again for the help
PiloZ
1 Rookie
•
6 Posts
0
October 24th, 2021 03:00
Great, now i understand my mistake and I found the saveset with wrong expiration.
I have recently been using NetWorker for work and did not know mminfo yet
Thank you so much!