Searching on Windows shares has been a frustrating situation. If your Macs fall asleep with documents open from the SMB share, you are in a world of hurt.ĥ: Be prepared to not be able to find anything. Connect to a server, let the mac sleep, on wake it can renegotiate the connection to the server volume (usually). Get cozy with the nf file.Ĥ: Don't let your Macs sleep. 10.10 has huge issues with file ID enumeration and periodic deadlock issues. 10.9 was a train wreck with Windows Clustered servers. Your Mac OS version will have varying degrees of success. From rampant file ID numeration, to slow directory reading, to hung Finder. Make sure it can both see paths that exceed the API limit and also that it is capable of restoring data in paths that exceed the length.ģ: SMB is still a nightmare. 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. So if you want up-to-date BSD userland components, you need to install them yourself.Īs I said, in my case, I used MacPorts to install rsync, but every other package manager available for OS X will have rsync, so use whichever one you prefer.Apologies in advance if this has ended up in the wrong section of the forum, hoping someone could point me in the right direction. The reason for this seems to be Apple's fear of GP元 licensing, which applies to the newer versions of this and other programs. Now, here is the default rsync I use, which was installed via MacPorts:Īs you can see, not only is the bundled version out of date, but it hasn't had the required patches applied to insure metadata preservation. I'm on Lion, and here is is what the output from the system rsync reveals: Yes, it would be wise to compile your own copy of rsync, not only because the version included with any GUI program may not preserve all metadata, but because even the copy included with OS X itself doesn't preserve all metadata(!).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |