Windows 2008 r2 file copy hangs

On doing some reading there was some issues with broadcom nics and also TOE etc - though I'm under the impression that a lot of this has been dealt with in R2. Does anyone have any suggestions of where to start or is anyone having similar problems?

Saturday, February 27, AM. Hi, In order to isolate the issue, please perform the following suggestions: 1. Best Regards, Vincent Hu. Monday, March 1, AM. Hi Vincent, Thanks for the reply For now the issue seems to have gone away after rebooting both VM's and host - subsequent file copies have been OK I was in a bit of a panic when writing the original post - should have gone back to 1st principles and rebooted before writing - it has been a long and painful few weeks!

I haven't had the issue with other VM's - though this is only a few weeks into the build. The other change I have made today was applying the hotfix for hyper-v on Nehalem processors after one of the hosts blue screened again - looked a bit deeper this time - I don't think this is related but a change all the same.

I'll keep an eye on it and report back if the issue happens again. I was under the impression that a lot of the TCP offloading issues had been resolved in R2 - are there still many reported issues? I tried many variations as it was unclear exactly where to disable physical NIC, VM guest etc - did tests using all combinations that I could come up with.

At this point it's all switched back on - this was after reading about the chimney features etc in R2. Hi, Please take your time. Three vms and other tasks from the host means the drives access will be a bottleneck. A drobo would do the job pretty well It sounds like the host simply can't handle the amount of IO.

You didn't say what type of drives but I would also suspect that they do not support NCQ which would help a little. Clearly you have an IO bottleneck. The optiplex as configured would not be able to handle large IO loads since I believe the 2 disks share the same bus the onboard is a port multiplier.

I've tried to use desktops in the past as server and run into similar headaches to the point where now I'll just pick up a cheap server. Server chipsets are almost always multilane sata controllers. I also found a thread with a tool for adjusting them here.

It's like process explorer but better. Start a file copying and then begin sorting through the data displayed looking for anything that looks odd. What was it's peak? Check explorer. Here's what mine looked like while copying a VM folder containing several, various sized vmdk files. I watched and saw that it dropped to zero as it finished each file. Does explorer. Does another process spike instead? AV scanning the copy process?

Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Learn more. Windows Server R2 grinds to a screeching halt during file copy operations Ask Question. Asked 10 years, 9 months ago.

Active 8 years, 6 months ago. Viewed 7k times. Improve this question. What kind of processor are you using? At this point, the volume for which a schedule has been defined will have a small clock image superimposed over the volume icon and will indicate that 0 bytes of shadow copy storage have been used.

The next step is to enable shadow copies on the volume by selecting the volume from the list and clicking on the Enable button. The volume in the list will update to display the date and time of the next scheduled copy and provide a summary of the current level of storage space used for the shadow copies.

To initiate a manual shadow copy now, or at any other time, simply select the volume to be copied from the list in the Shadow Copy properties panel and click on the Create Now button. To restore an entire volume, access the Shadow Copy property panel either from Computer Management as outline above, or by running vssuirun from a command prompt with elevated privileges.

Once loaded, select the desired volume followed by a snapshot from which to restore from the Shadow copies of selected volume list and click on the Revert Now This will revert all shared folders on the selected volume to their state at the point that the selected shadow copy was made.

It is important to note that restoration of entire volumes is not possible on system volumes since this would, in all probability, severely interfere with the current system state.

A significant amount of Shadow Copy functionality can be accessed via the command line using the vssadmin tool, which is the focus of this section. In order to obtain information about shadow copies configured on a system, use vssadmin list shadows :. To obtain information about how shadow copy storage is allocated to shadow copies, use the vssadmin list shadowstorage :.

The above command is particularly useful for comparing used and available space for shadow copy storage. Shadow Copy for a volume may also be enabled from the command-line using vssadmin , the syntax for which is:.

A manual shadow copy of an enabled volume may be triggered from the command prompt at any time by running vssadmin as follows:. Specific shadow copies may also be deleted from the command line either by specifying that the oldest snapshot is to be deleted or by referencing the specific snapshot by its Shadow Copy Id which can be obtained from the vssadmin list shadows command.

For example, to delete the oldest shadow snapshot:. The restoration of a shadow from a specific snapshot can be achieved from the command line using the vssadmin revert command combined with the Shadow Copy ID of the required snapshot.

Finally, Shadow Copying on a volume may be disabled via the command prompt using the vssadmin delete shadowstorage command, although the command will only work once all snapshots associated with the volume have been deleted from the shadow storage. Assuming there are no existing shapshots, the following example will disable shadow copy on the volume represented as the e: drive:. Once shadow copy has been configured for volumes on the server, the next step is to learn how to access the previous version of files from client systems.

However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix.

For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:. If you do not see your language, it is because a hotfix is not available for that language.

For more information about how to obtain a Windows 7 or Windows Server R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:. The global version of this hotfix installs files that have the attributes that are listed in the following tables.