PS - NTdoc, is there file size that's too much for kix to handle that you feel robocopy would work better? I was quite pleased that a 2gb file was moved between network shares as fast as it was by kix . . when copied via windows drag and drop it took close to an hour to move :(. I know I have users with 10gb+ PST's...is there a breaking point for kix's move funtion?
There is no KiXtart limit (KiXtart will use the underlying OS APIs). The reason for using ROBOCOPY or similar tools on very large files is because of the restart options.
More of a problem on slower WAN connections, it provides the option when your 10 GB copy fails at 9.5 GB to resume and copy the last 0.5 GB instead of starting from scratch. It can also be configured to automatically retry interrupted / failed copies so that for example if network connection dropped for a couple of minutes the copy would continue when it came back.
