I finally tried changing parameters on the target XP machine, and this "fixed" the problem. Increase lanman size parameter from 1 to 3 (HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Size) at first, this seemed to lengthen the time to failure, then I wasn't so sure.Upgrade router firmware I tried bypassing the router instead.Upgrade the NIC driver mine was up to date.Disable various TCP offloading parameters (checksum offload, large send offload) the specific parameters varied per-NIC my NIC didn't have any of the listed options.Disable TCP chimney offload (netsh int tcp set global chimney=disabled) no apparent effect.Disable TCP autotuning (netsh int tcp set global autotuninglevel=disabled) no apparent effect.Disable remote differential compression no apparent effect.I tried the various solutions people recommended, without success. Microsoft has apparently known about this for years and (I assume) doesn't know how to fix it. For some people, network transfers work, but slowly for others they fail altogether. I found that many people have reported similar problems there are widespread problems copying large files across the network from both Vista and Windows 7. I have five other (XP) computers backing up to the same target XP machine with no problem. I couldn't copy large files from Windows 7 to my XP machine across the network. However, in addition to backups failing, file copies were also failing. Ghost was successfully creating the remote file and was sending data for a while before the backup would fail. For the benefit of others having this problem, I will outline what it was and what it wasn't.įirst, I had no problem mapping the remote drive, and Ghost was connecting ok to the target drive using a UNC path and credentials. Thanks.ĭaveH - Thanks for the good questions. Just for reference, this is how it looked at 12 minutes into the backup pretty normal I think: This is Task Manger showing the state just after I paused VProSvc.exe: Here's a screenshot after I paused it at 20 minutes, just before it got full enough to freeze Windows. There aren't any processes obviously using the memory when it is filling up, but if I use Process Explorer to pause VProSvc.exe, the memory stops filling. The event log shows the following, but I think it is just a symptom, with the core problem being full memory:Įrror EC8F17B7: Cannot create recovery points for job: Drive Backup of OS (C:\).Įrror EBAB03F1: Error performing inpage operation.Įrror EBAB03F1: The specified network name is no longer available. This is Ghost 15 (15.6) on Windows 7 Ultimate 64 bit with 6GB memory. I can backup the C drive to a local USB drive without errors. When I try to backup the C drive across the network, it only runs successfully for about 20 minutes and then suddenly starts filling memory, causing Windows to freeze for a few minutes until the backup finally fails.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |