failed to create vss snapshot within the 10 second write inactivity limit

Last post 07-10-2019, 12:05 PM by nvml. 2 replies.
Sort Posts: Previous Next
  • failed to create vss snapshot within the 10 second write inactivity limit
    Posted: 07-08-2019, 11:02 AM

    An older post had mentined that IntelliSnap backup snap creation failure due to 10s VSS timeout got resolved after increasing the value of the registry key - HKLM\Software\\Microsoft\Windows NT\CurrentVersion\SPP\CreateTimeout - to 1200000 (20 mins). 


    This post is added to clear any doubts regarding the above mentioned registry key. According to the microsoft document - - the FlushAndHoldWrites phase timeout of 10s is not configurable (as highlighted in the red region). 


    In many of the cases, the VSS timeout happens on intermittent basis. This would mean that the snap creation which had failed in previous attempts could succeed in the next one. The 10s VSS timout could happen even after setting the 'CreateTimeout' registry key. 



  • Re: failed to create vss snapshot within the 10 second write inactivity limit
    Posted: 07-10-2019, 7:16 AM

    Hi IntelliM

    Thank you very much for sharing the details 

    This information will be great for any users that has potential slow storage which could cause timeout delay when doing the snap creation, while using VSS



  • Re: failed to create vss snapshot within the 10 second write inactivity limit
    Posted: 07-10-2019, 12:05 PM

    Thanks intelliM for posting the clarification regarding the Windows VSS 10s time-out.

    Just to add some context here - the post being referred in this thread is the following -



    The VSS 10sec timeout is completely managed and enforced by Microsoft VSS framework and this is not a limitation imposed by backup vendors. This is to ensure that journalling is not overloaded by holding the writes for a very long period.


    To create application-consistent snapshots, the writes need to be held while taking the HW snapshots and for this, Commvault's VSS Provider based agents (like Windows FileSystem, MS-SQL, Exchange and others) issues the backup request to the VSS framework which internally holds the writers and issues the request back to Commvault's VSS Provider to create the HW snapshots. These snapshots should be created within this 10sec window and needs the control to be returned back to VSS framework to release the writers - all within this 10sec window.


    As far as I know, there is no override or any configuration to change this critical 10sec window.


    If there are any queries, I will be more glad to clarify them to my best effort.



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.
Copyright © 2020 Commvault | All Rights Reserved. | Legal | Privacy Policy