<div>
Thanks for the link to that article. <br />
<br />
If I understand it correctly, it takes a snap-shot of the entire filesystem volume and according to the article would complete the process in under 60 seconds. It dosn't explain why users still have issues up to 20 minutes later.<br />
<br />
Is there any circumstances that would cause the Shadow Copy process to take longer? Such as open or locked files? What would happen if a file is exclusively locked by another application during the Shadow Copy process?
</div>


<div>
We are currently experiencing similar issues and also the server stops responding when this happens as well. On a few occasions we had to actually restart the server before anything could be done with the locked files. <br />
<br />
Just curious, when did these issues start for you? Everything was working fine for us until about 3 weeks ago. &nbsp;Any recent Microsoft patches?
</div>


<div>
Hi wtwatts,<br />
<br />
Since this is a remote server I don't monitor it too closely. I believe the problem began shortly after it was put into production. No suprises that no one noticed during testing as it wasn't being used by a 100 super fussy users.<br />
<br />
I don't believe this server has been patched since put in production which would of been around 1 month ago. But one of my team in Sydney may of done themselves but I doubt it. <br />
<br />
You could be on the right track about the MS Patches but sorry I can't help confirm or deny that. 
</div>


<div>
<div class="content wysiwyg-content">
We currently have a scheduled task that runs Shadow copy service twice a day, 7am and 12pm on the main production file server. Users are reporting various random &quot;Can't read file&quot; errors for around 20 minutes after the scheduled task has kicked off.<br />
<br />
Errors range from &quot;Disk Is Full&quot; to &quot;Access Denied&quot; and come from a varity of different applications including Windows Explorer. All of them are trying to access files on this server. I've checked file permissions and disk space but I am convinced that it has something to do with Shadow Copy. <br />
<br />
Can anyone offer any advice?<br />

</div>
</div>


We currently have a scheduled task that runs Shadow copy service twice a day, 7am and 12pm on the main production file server. Users are reporting various random "Can't read file" errors for around 20 minutes after the scheduled task has kicked off.

Errors range from "Disk Is Full" to "Access Denied" and come from a varity of different applications including Windows Explorer. All of them are trying to access files on this server. I've checked file permissions and disk space but I am convinced that it has something to do with Shadow Copy. 

Can anyone offer any advice?


Does Shadow Copy lock files during the scheduled task?

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).