FLA or another way to predict stubbing / archival candidates?

Last post 04-01-2014, 5:51 PM by jjbiv. 1 replies.
Sort Posts: Previous Next
  • FLA or another way to predict stubbing / archival candidates?
    Posted: 04-01-2014, 3:03 PM

    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?Undecided

    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 Angel [A] 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.

     

    thanks

     

  • Re: FLA or another way to predict stubbing / archival candidates?
    Posted: 04-01-2014, 5:51 PM

    You might also take a look at the System Discovery Tool if you'd rather gather this data once and then view the results outside of CommVault (via the CV cloud website).  No worries about adding extraneous data to the database this way Smile

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy