It seems that there is a bit of a bug in the Hyper-V export function if the destination for the export is receiving data slower than the source is sending it. The export function will continue to cache the export in all available memory until the server stops responding due to memory being exhausted.
Prior to running any export processes on a production server this hotfix should be applied.
Examples where the problem hits is when the export is being run to a USB hard disk that runs at 30MB/Second or across a slower LAN link to another server.
Hat Tip: Tim Barrett of No Geek Left Behind.
Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book
*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.
No comments:
Post a Comment