File Server Resource Manager

Last post 06-25-2019, 6:41 AM by Genesh Subhash. 10 replies.
Sort Posts: Previous Next
  • File Server Resource Manager
    Posted: 05-14-2019, 10:30 AM

    What are the advanced fixes for backup failure of FSRM on windows servers other than deleting old snapshots, adding to content filters?


    GS
  • Re: File Server Resource Manager
    Posted: 06-03-2019, 11:12 AM
    • Aplynx is not online. Last active: 10-18-2019, 2:25 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,724

    Is this an issue with the System State? Typically this failure will occur if the option is enabled but not setup. So the OS will flag the VSS writer as having data, but nothing will be there for the BackupAndReadAPI to grab. The clbackup.log will show this on the client. If this is what the log shows, I'd recommend filtering the FSRM. 

     

    FsBackupTw::BackupComponentTemplate(636) - Backing up [File Server Resource Manager] 

    CDefaultWriterBackup::GatherWriterExcludes(1673) - Exclude file count [0] for writer [GUID]

    CDefaultWriterBackup::BackupWriter(991) - FSRM Global Configuration has 3 files/folders, 0 logs, and 0 databases

    CsSnapRequestor::GetSnapshotPathA() - Call GetSnapshotPath(pwszInPath.c_str(), strPath, bGetFullPath) [FAILED, throwing CV exception] - Code = 0x80004005, Description = E_FAIL

    CDefaultWriterBackup::BackupFileDesc(601) - Failed to translate source path to snap path [C:\System Volume Information\SRM\Settings\].

    CDefaultWriterBackup::BackupFileDesc(661) - hr - [FAILED] 0x80004005

    CDefaultWriterBackup::BackupWriter(1026) - BackupFileDesc(args, comp.p, CVFILE_NORMAL, cFiles, files) - [FAILED] 0x80004005

    FsBackupTw::BackupComponentTemplate(650) - Failed to backup [File Server Resource Manager] Either SocketLinkedList, SocketObject or CriticalSectionObject is null

  • Re: File Server Resource Manager
    Posted: 06-10-2019, 11:28 AM

    Thanks, Error Below.

    Error Code: [6:64]
    Description: System state backup of component [File Server Resource Manager;] failed.

    I have reviewed the logs and i have the same issue which you have mentioned above.

    I have filtered FSRM and we dont have the error now. Is there any other way were we can fix this. Any idea why this is suddenly an issue ?


    GS
  • Re: File Server Resource Manager
    Posted: 06-10-2019, 11:58 AM
    • Aplynx is not online. Last active: 10-18-2019, 2:25 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,724

    I'm assuming now you have an FSRM VSS writer when running vssadmin list writers. This would only be active when FSRM is enabled. The failure comes when CV queries the writers and makes an API call for their output during the system state. You'll want to review the machine and see what happened to make that change. 

  • Re: File Server Resource Manager
    Posted: 06-17-2019, 4:21 AM

    Liam,

    I have ran a full backup which completed sucessfully

    4264  35f8  06/14 21:55:56 1269242 PrintReport(1804) - File Server Resource Manager        Writer                              Successful

     

    However the following incremental failed to backup FSRM

    7156  32cc  06/15 22:37:54 1269814 PrintReport(1804) - File Server Resource Manager        Writer                              Failed

     

    We couldnt find any issues at server OS level.


    GS
  • Re: File Server Resource Manager
    Posted: 06-19-2019, 11:40 AM
    • Aplynx is not online. Last active: 10-18-2019, 2:25 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,724

    This is in no way a critical component for a restore so again I'd recommend filtering the object, however what do the full and incremental say under the backing up the FSRM higher up in the clbackup.log?

  • Re: File Server Resource Manager
    Posted: 06-21-2019, 8:50 AM

    Liam,

     

    12332 2d64  06/17 21:59:25 1270855 CsSnapRequestor::GetSnapshotPathA() - Call GetSnapshotPath(pwszInPath.c_str(), strPath, bGetFullPath)  [FAILED, throwing CV exception] - Code = 0x80004005, Description = E_FAIL
    12332 2d64 06/17 21:59:25 1270855 CDefaultWriterBackup::BackupFileDesc(728) - Failed to translate source path to snap path [H:\System Volume Information\SRM\].
    12332 2d64 06/17 21:59:25 1270855 CDefaultWriterBackup::BackupFileDesc(788) - hr - [FAILED] 0x80004005
    12332 2d64 06/17 21:59:25 1270855 CDefaultWriterBackup::BackupWriter(1161) - BackupFileDesc(args, comp.p, CVFILE_NORMAL, cFiles, files) - [FAILED] 0x80004005
    12332 2d64 06/17 21:59:25 1270855 FsBackupTw::BackupComponentTemplate(1436) - Failed to backup [File Server Resource Manager]

     

    We have disabled shadow copies for H drive and FSRM completed sucessfully. Any suggessions? 


    GS
  • Re: File Server Resource Manager
    Posted: 06-21-2019, 9:25 AM
    • Aplynx is not online. Last active: 10-18-2019, 2:25 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,724

    VSS is saying it can't snap the H: drive. Is this a cluster? 

  • Re: File Server Resource Manager
    Posted: 06-21-2019, 9:33 AM

    No, the server is a VM


    GS
  • Re: File Server Resource Manager
    Posted: 06-21-2019, 9:38 AM
    • Aplynx is not online. Last active: 10-18-2019, 2:25 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,724

    There was an issue accessing this path at the time of the backup that failed, that didn't occur on the backup that completed. 

    [H:\System Volume Information\SRM\
  • Re: File Server Resource Manager
    Posted: 06-25-2019, 6:41 AM

    Thanks Liam,

    We have seen the same issue with other servers as well. But most of them are intermittent. Is this AV related or due to any MS patches? Disabling snapshot is a permanent fix?


    GS
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