Test, test, and test some more with all your tools, including your backup software. If you are coming from a system that supported longer paths (like OS X and *nix operating systems) than you will want to review the length of your file paths. In this day of unicode many parts of Windows can only handle a max file system path of 256 characters. For details, see here (v=vs.85).aspxĢ: Maximum path length. Look for files that start and end with the space character. You must do a review of file and folder names BEFORE trying to migrate. So can *********REALY IMPORTANT FILE!!!!!! Yes there are spaces in the from and end. Mac users on Mac storage will can use any character they want other than : and /. Been through this a lot (sigh).ġ: Naming. Looking forward to hearing your feedback, definitely let me know of any "gotchas" or things I need to take into consideration during the planning stage. Be reliable for transferring large date - currently around ~18TB be able to provide a meaningful summary for piece of mind when the transfer is completed (kind of like ChronoSyncs log) support resuming if the transfer fails / pauses support copying file attributes from MAC-to-Windows world This is what I'm looking for in an app to manage the transfer: We have a paid version of ChronoSync that we use to run our nightly backups to other external NAS devices - I see this has come up in a few Google searches.Ģ others products that are popping up in my research are arRsync and SuperDuper - can anyone comment or recommend these products? I'm wondering what the best application to manage the transfer of data might be? In Windows environments I've used Robocopy or FTP and the likes but not really familiar on the Mac side of things when it comes to data migrations. We are in the process of planning a large data migration (~18TB) from the mac formatted NAS device, onto a Windows Server (using NetApp as the storage solution / VM datastore) ![]() I work for a company that currently stores its files on an OS X Journaled NAS device, connected to a Mac Mini via lightning cable, and the mac connects into the network via ethernet. If this takes a lot longer than for your source disk, your target disk could be the bottleneck.Apologies in advance if this has ended up in the wrong section of the forum, hoping someone could point me in the right direction. To verify that this is the problem, on any os with a bash, just type time ls -Ral > filelist.txt (diverting the output to a file since putting out data on the screen is way slower). ![]() The -delete option can also cause a slow rsync, if retrieving the complete file-list of the target location is slow (which is probable for an external, rotating USB disk). Maybe a tool like iotop (in the case your on Linux, similar tools are available for almost all platforms) can help you identify the bottleneck. Your usb drive might be your bottleneck, as retrieval of the size and timestamp will create a lot of jumps in the inode table. If you just have a few files, this will obviously be faster than for many files. ![]() If they differ, copy the file from the source to the destination Compare it with the size and mtime of the copy in the destination locationĬ. Get the size and the mtime (modification timestamp)ī. ![]() Build a file-list of the source location.Ī. This will cause a rather slow rsync caused by the design of the rsync protocol. I am assuming you have a lot of files, no matter their sizes in the location you are copying from. If they don't match your situation, please clarify your question and I'll happily update my answer. As I don't exactly know your system, I am making a few assumptions here.
0 Comments
Leave a Reply. |