Users want to rely on both access and modify times (unix onepass). I noticed I could not get any info relating to atime or ctime without turning on the feature "Catalog additional file and system attributes" under the Advanced Options tab of the subclients. It collects details about such things, and now my FLA reports are a bit more usefull, but are there other ways to predict archive-able files using other reports, or is FLA "the way", or should I say, when sales/engineers folks say "you can run a report that tells you what will stub" this is what they are referring?
Anyone have any idea how much extra SQL junk is acquired/stored once this additional information is being collected? I've noticed that after enabling this collection, every archive job that runs logs this:
Error Code: [89:95] Description: Failed to map volume group to physical device. Advice: No advice. Source: tcomvault01, Process: SRMServer
I realize this may be more of a reports question but since it all stems from archiving and subsequent reporting, I'd start here.