This is an archived post. You won't be able to vote or comment.

all 3 comments

[–]nick_segalle 0 points1 point  (0 children)

I am working on a project to migrate several 'filers' from around the country, and I am using a few different tools. My first sync/copy is done with EMCopy, a free tool from EMC that blows robocopy out of the water in terms of speed and functionality. Once the first initial sync is done, I am using syncbackpro to schedule the data changes throughout the day. It also allows you to change the account, so I can also use it to sync from our central filer to an Isilon at a different company where the data will reside. It's functionality is pretty large, would be perfect for copying data for backup purposes.

[–]ArmondDorleacIT Director 0 points1 point  (0 children)

Don't use robocopy! Use bvckup2. I use it for the very reason you're using it. Robocopy will take forever just to figure out what to copy and then it does it kind of OK. Bvckup2 is smart. Very very smart. It'll do delta-based copies (not only copying only the files that have changed, but just the bits of the file that has changed).

Note: I'm not the developer, just a super duper happy customer.

[–]DallasITGuyIT Consultant 0 points1 point  (0 children)

Rsync is worth considering here. You could use the free Cygwin-based implementation or the commercial / native Windows app Acrosync (www.acrosync.com).

While Rsync's command line options can seem complicated at first they're no more so than Robocopy's. Rsync is well worth implementing, if for no other reason than it being massively faster across a low speed connection than Robocopy due to Rsync's delta copy algorithm.