This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 99%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
We have implemented VSS volume on our Windows Server, scheduled to run twice daily. However, we've encountered an issue where one of the scheduled snapshots is intermittently missing. This occurs randomly, with no discernible pattern —sometimes at 7:00 AM and other times at 12:00 PM.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi,
Please open Task Scheduler, select the shadow copy volume task and switch to the History tab. Check the time the task completed and see if there are any errors. If the previous instance of the task is not competed, a new instance will not be started.
Best Regards,
Ian Xue
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Dear Ian,
I have checked the log and VSS task reported as completed.
However, when I look at the Windows Event Logs, I observe that there are different error messages for different volumes
Volume Shadow Copy Service error: The shadow copy could not be committed - operation timed out. Error context: DeviceIoControl(\?\Volume{6ba7ecf3-fa0f-4991-bace-f39479f057e7} - 00000000000001A0,0x0053c010,0000006FD57B3C50,0,0000006FD57B7C90,4096,[0]).
VssAdmin: Unable to create a shadow copy: Another shadow-copy creation is in progress, so the current shadow copy cannot be created. There are a number of common scenarios causing this problem: * If Shadow Copies of Shared Folders is set up, ensure that no two volumes have schedules that lie within five minutes of each other. * If automatic backup of any form is scheduled, ensure that the backup schedule does not overlap with the schedule used for Shadow Copies of Shared Folders. Generally, retrying the operation after a few minutes or changing the schedule of an automatic task should fix this problem.
VssAdmin: Unable to create a shadow copy: Another shadow-copy creation is in progress, so the current shadow copy cannot be created. There are a number of common scenarios causing this problem: * If Shadow Copies of Shared Folders is set up, ensure that no two volumes have schedules that lie within five minutes of each other. * If automatic backup of any form is scheduled, ensure that the backup schedule does not overlap with the schedule used for Shadow Copies of Shared Folders. Generally, retrying the operation after a few minutes or changing the schedule of an automatic task should fix this problem. Command-line: 'C:\Windows\system32\vssadmin.exe Create Shadow /AutoRetry=15 /For=\?\Volume{a0cc4744-768e-11e6-812f-06ebb66c8722}'.
Besides, does backup software like Veeam impact the creation of VSS Volume and cause the problem? Do they use the same VSS services?
Thanks
