recalled files not stubbing back out

Last post 06-05-2018, 10:48 AM by Manoj_Pradhan. 1 replies.
Sort Posts: Previous Next
  • recalled files not stubbing back out
    Posted: 06-05-2018, 9:46 AM

    Wondering where to look exactly to figure out why 1000's of files which were recalled are not stubbing back out again. Which logs are required to diagnose the "lack of stubbing or disk cleanup" and are more verbose logging levels needed to really see where the decisions are being made on a per-file basis? I've looked at the FileScan and CXHSMStub logs but am not seeing anything useful:

    These are Linux (RHEL7.4) machines running XFS and the disk cleanup rules do not seem to be honored at all. V11 SP10

    CXHSMStub::DoStub() - Nothing to stub.
    CXHSMStub::DoStub() - [292655] Successfully archived 0 file(s) and skipped/failed 0 file(s)

    We've even tried touching the atimes on a bunch of candidate files(setting it back in time) to see if that did anything (which isn't the case anyways since we are using LVM snaps to preserve them during backups).

    Set the % min free space to 0, no change, it is not the disk usage preventing cleanup, that is certain.

    We have about 45TB to recall and restub but at this pace it will take a year unless we can figure out where they are getting skipped. The disk cleanup does not seem to work as "predictable" as it did in v10 at all.

    thanks

  • Re: recalled files not stubbing back out
    Posted: 06-05-2018, 10:48 AM

    Hello, 

     

    there are several reasons why this might have happened. Can you open up a support case, we would check to find the exact reason. 

     

    Thanks,

    Manoj

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