VOLRETENT value already past current date and not yet expired
Hi folks,
I am unable to understand why I am getting this strange behaviour from Networker: Normally, when a volume's volretent has expired, the value I get under volretent when I do an mminfo is
expired. However, for some reason I can not understand, some volumes we have, already has a past date value on the volretent field, and yet it is not marked as expired!
# date
Wed Jun 7 16:19:25 SGT 2006
# mminfo -a -q 'barcode=EB0213' -r 'barcode,volretent'
barcode expires
EB0213 06/05/06
Has anyone experienced this kind of incident? Is this a bug?
However, if this is the case, how come it only affects some volumes (or save sets, not sure yet)? Does this mean that something happened when this specific volume was used such that savegrp did not finished its task and ran nsrim, thus this discrepancy? Our backups has been running on a daily basis, and yet, some of this volumes seems to have been not yet corrected.
The volume will go into an expired state when nsrim runs, which is once a day when a group completes, or when Networker is started, or when you run it manually.
Maybe there are full backup savesets on volume which have an incremental depending on it and therefore volume is not marked as expired yet. Check it out.
Primoz answer is probably the one here - if some latter incremental or level saveset relies on an earlier backup to be able your data to be recovered completely there will be a dependency on that saveset.
Try running nsrim -X manually and see if it recycles your volumes; if not it is probably a dependency causing this.
Some 3 years ago I opened a RFE during 7.0 beta and asked for nsrtree command. I called it that way as I wanted it to see dependency in txt graphic like tree command would give you dir output in DOS. This can be achieved with a bit more complex script too, but I hope EMC will implement this one day.
rlchua
12 Posts
298
0
Posted June 7th, 2006 02:00
However, if this is the case, how come it only affects some volumes (or save sets, not sure yet)? Does this mean that something happened when this specific volume was used such that savegrp did not finished its task and ran nsrim, thus this discrepancy? Our backups has been running on a daily basis, and yet, some of this volumes seems to have been not yet corrected.