SEP and CV Archive Agent crashes Windows File System Services

Last post 06-01-2015, 1:08 PM by Stupek. 53 replies.
Page 2 of 2 (54 items)   < Previous 1 2
Sort Posts: Previous Next
  • Re: SEP and CV Archive Agent crashes Windows File System Services
    Posted: 09-18-2014, 5:23 PM

    SP8 for Simpana 10 was released today.  One of the fixes listed in release notes was:

    321. Recall operations on stub files in computers where SEP 12 is installed causes a hang on the shares.

    Doing some testing on this now; hoping this finally puts this issue to rest!

  • Re: SEP and CV Archive Agent crashes Windows File System Services
    Posted: 12-09-2014, 7:21 AM

    Hi,

    Has anyone got this successfully running with V10 SP8? We need to upgrade SEP as 11 is going out of support / updates soon so need it to work!

    Thanks

    Andy

  • Re: SEP and CV Archive Agent crashes Windows File System Services
    Posted: 12-09-2014, 11:29 PM

    Andy Kearns:

    Hi,

    Has anyone got this successfully running with V10 SP8? We need to upgrade SEP as 11 is going out of support / updates soon so need it to work!

    Thanks

    Andy

    Andy, I can confirm that Simpana 10 SP8 works with SEP12.  I have been using archiving on a new Windows Server 2012 R2 file cluster and am not seeing the dreaded stuck recall issue.  We have been running this for over a month now.

  • Re: SEP and CV Archive Agent crashes Windows File System Services
    Posted: 12-10-2014, 3:40 AM

    I can also confirm that we now have this running with no issues since they integrated the patch into SP7 & 8.

  • Re: SEP and CV Archive Agent crashes Windows File System Services
    Posted: 06-01-2015, 1:08 PM

    Hello everyone,

    Just wanted to update this thread incase anyone else is still having issues with SEP working with CV.  3 things to make sure if you are having issues.  Keep in mind that only SEP 12.1.4 and above is supported

    1. Make sure you are up to date with CV updates as there was a couple of updates that addressed this issue

    2. make sure you add the following configuration

    http://documentation.commvault.com/commvault/v10/article?p=white_paper/security/symantec_v12_file_archiver.htm

    3. add the following 2 registry keys:

    HKEY_LOCAL_MACHINE\Software\CommVault
    Systems\Galaxy\Instance<xxx>\

    key : WinFSDataMigrator

    Value : GXHSMRECALL_ENABLE_EARLY_DRIVER_NOTIFICATION

    Value Type : String ( Set it to Y)

     

    HKEY_LOCAL_MACHINE\Software\CommVault Systems\Galaxy\Instance<xxx>\

    key : WinFSDataMigrator

    Value : GXHSM_RESTUB_ENABLED

    Value Type : String ( Set it to Y)

     

Page 2 of 2 (54 items)   < Previous 1 2
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