Incompatibility using SyncToy with WHS on large files RRS feed

  • General discussion

  • It appears that the way SyncToy copies files, and the way WHS advertises available storage space can result in a situation where large files fail to complete a copy. 

    This failure is a combination of:
    1) SyncToy sees all the available space on the combined drive pool (not just the physical drive targeted)
    2) When SyncToy starts the copy process, WHS selects the physical drive based on the size of the file being saved - which apparently is just 64K that is then "gown" as data is transferred (according to Ken W in the post linked below)

    The result is that while a large file (like a Blu-ray ISO) may be 50GB, WHS will commence saving it to a physical drive with less available space than is actually required as it "thinks" the file being transferred is only 64K.

    The original thread on this is at the WHS forum http://social.microsoft.com/Forums/en-US/whssoftware/thread/a40bfdd9-2cc6-4289-b00e-0e98de16ff8f but I thought it best to also post the info here in the hope the WHS / SycToy devs may be interested.


    Sunday, March 8, 2009 10:43 AM