Yes, we're researching reducing SAVSECDTA time. That will involve
switching to authorization lists (which we should be doing anyway), but
that project hasn't been scheduled yet. This IFS issue is a different
issue that has been happening infrequently for some time now. And
looking at the logs, I don't understand it at all.
We've got this in our backup:
Auxiliary Weekly Incremental Full Retain
Save List Storage Activity Media Media Object
Item Type Pool Device MTWTFSS Policy Policy Detail
*LINK *ALLAVL IIIIIFI DAILY DAILY *YES
But from what I can tell, the system did a complete IFS save on 3/23,
3/27, 3/30, 4/06, 4/10, 4/13 and today, 4/17. I only base that on the
number of IFS objects saved (2 million vs a few thousand). I cannot
tell from the logs which type BRMS attempted. Weirdly, it doesn't seem
to me that it is EVER doing a complete IFS backup on Saturdays (3/21,
3/28, 4/4, 4/11).
4/13 was unusual in that it was an ad-hoc mid-month save during the
day. The rest all occured during our overnight processing, in which the
IFS *LINK portion usually kicks off around 2AM (unless SAVSECDTA goes long).
On 4/17/2020 7:49 AM, Rob Berendt wrote:
Weren't you working on another issue with your IFS? Did you perhaps fire off some mass authority correction? Like convert to using authority lists or anything?
Rob Berendt
midrange.com
