windows system comes to restore the backup function using the underlying ShadowCopy (shadow volume) technique.
The technology uses a copy on write mode when each time a new IO, the old data is copied out and then write new IO
Recently error "Event ID 36, User Imposed Limit" when invoking the interface, after a survey found. When the shadow volume error "User Imposed Limit", most likely create a shadow volume of disk space you do not need expansion.
reference:
How to Fix VolSnap 36 Error User Imposed Limit – Volume Snapshot
VolSnap 36 event ID may show up as error:
Volume Snapshot Driver, Diff Area health issuesEvent ID 36
Source volsnapThe shadow copies of volume C: were aborted because the shadow copy storage could not grow due to user imposed limit or a related message.
Basically VolSnap 36 is an error event that signals an issue with the diff area being used by VSS.
It could be：
a low limit for the diff area, see http://backupchain.com/i/how-to-fix-volsnap-25-error
a disk I/O issue
a bad sector on disk: use chkdsk X: /b to check for bad blocks (may require a reboot)
system load is too high for the diff area to grow fast enough
a corrupt file system issue. Use Chkdsk with /r option, better use /b to also check for bad sectors
The most common cause is #1. Use the solution in the article linked above; however, checking the other potentialities may also be a good idea if the disk hasn’t been checked in a while.
公号 [ 同叔练级之路 ]
Certainty of death. Small chance of success.
