Join the Conversation

To sign in, use your existing MySonicWall account. To create a free MySonicWall account click "Register".

Quest Rapid Recovery and SentinelONE 4.1.6.118 VSS Error's

I was auto updated to S1 version 4.1.5.97 and started getting VSS error's on agent backups in Rapid Recovery. Found article about known issue's. Followed steps to upgrade to S1 Version 4.1.6.118. Calls with support to fix backend issues. Finally thought I had it squared away but now I am still receiving random VSS error's when backup is trying to be performed.

VSS Copy snapshot of 'C:\; D:\; EFI System Partition 1 on disk 0; Recovery Partition 0 on disk 0' on 'FS1' failed due to VSS error: FlushWritesTimeout


Is anyone successfully using Rapid Recovery and S1 version 4.1.6.118?


I have multiple systems with this setup and it starting to get frustrating.

Category: Capture Client
Reply

Answers

  • ThomTurnerThomTurner Newbie ✭

    @Bret

    We get similar issues with SQL backups, you're not alone. How did your issue get resolved?

  • BretBret Newbie ✭

    @ThomTurner It hasn't.

  • BretBret Newbie ✭

    Week and half later and still no updates from support.

  • MicahMicah admin

    Hello @Bret, I'm sorry to hear about this inconvenience. Let me PM you and get the case number that you are working on so I can escalate internally.

    Kind Regards,

    🖐️ Sr. Manager, Web and Digital, SonicWall. Say "hi" by tagging me at @micah.

  • skesarwaskesarwa SonicWall Employee
    edited March 11

    @Bret

    Could you please help me with output of "vssadmin list writers" from CMD.

    Are you seeing issue with "Writer name: 'VSS Metadata Store Writer' or "Writer name: 'Shadow Copy Optimization Writer'".

    Can you get me more details.

  • BretBret Newbie ✭

    Yes this issue is with S1 4.1.6.118. It is happening on multiple systems in different client environments with the common factor Capture Client 3.1.4 S1 4.1.6.118. Moving to this version of S1 has fixed the issue of the backup failing every time it is trying to run. Now it fails a couple of times a day with the following errors:

    Rapid Recovery Error:

    The transfer failed: 'There was a problem with the VSS subsystem on '10.10.1.253'.'

    DoSnapshotSet failed with error: 'The system was unable to flush I/O writes. This can be a transient problem. It is recommended to wait ten minutes and try again, up to three times.'

    VSS Copy snapshot of '(Volume Labeled 'System Reserved'); C:\; D:\' on '10.10.1.253' failed due to VSS error: FlushWritesTimeout



    Windows Event Viewer Error:


    The flush and hold writes operation on volume C: timed out while waiting for file system cleanup.

    The flush and hold writes operation on volume \\?\Volume{34202054-0000-0000-0000-100000000000} timed out while waiting for file system cleanup.



    Here is the info requested from one of that is having the issue:

    It does not specify which writer is having the issue.


    Writer name: 'Task Scheduler Writer'

      Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}

      Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}

      State: [1] Stable

      Last error: No error


    Writer name: 'VSS Metadata Store Writer'

      Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}

      Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}

      State: [1] Stable

      Last error: No error


    Writer name: 'Performance Counters Writer'

      Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}

      Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}

      State: [1] Stable

      Last error: No error


    Writer name: 'System Writer'

      Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

      Writer Instance Id: {8512d12f-0bfa-4f4c-a6e2-d04900e57da8}

      State: [1] Stable

      Last error: No error


    Writer name: 'Shadow Copy Optimization Writer'

      Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

      Writer Instance Id: {21c0ef5a-70d0-4ec7-aa06-7a0148ed1f4a}

      State: [1] Stable

      Last error: No error


    Writer name: 'ASR Writer'

      Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

      Writer Instance Id: {20fb1739-a295-438b-8abf-1f6dcd8e4fff}

      State: [1] Stable

      Last error: No error


    Writer name: 'WMI Writer'

      Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

      Writer Instance Id: {518252b2-c1b9-47d6-b0e6-a533cff20553}

      State: [1] Stable

      Last error: No error


    Writer name: 'Registry Writer'

      Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

      Writer Instance Id: {ca9274ef-d5fc-4e2e-a051-90abc38c247b}

      State: [1] Stable

      Last error: No error


    Writer name: 'DFS Replication service writer'

      Writer Id: {2707761b-2324-473d-88eb-eb007a359533}

      Writer Instance Id: {82085b66-eff9-4ac1-baff-421f2f94995c}

      State: [1] Stable

      Last error: No error


    Writer name: 'Microsoft Hyper-V VSS Writer'

      Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

      Writer Instance Id: {dca6cdbc-6f07-49be-94ea-d8947b22c8c5}

      State: [1] Stable

      Last error: No error


    Writer name: 'COM+ REGDB Writer'

      Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

      Writer Instance Id: {ff4994e6-15b6-4a6d-8852-cbd2ab11f2e3}

      State: [1] Stable

      Last error: No error


    Writer name: 'NTDS'

      Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}

      Writer Instance Id: {7ac3d781-13f6-4e83-b2f2-50f5c808cd1f}

      State: [1] Stable

      Last error: No error

Sign In or Register to comment.