I always have a copy installed on my workstation, and at least 1 of my serversĮxplorer? You've got to be kidding (or trolling) I learnt of it during my Amiga days, in what seems like a lifetime ago. Stangely, not a lot of sysadmins know about DOpus.
Emcopy do copy systems zip#
It also has tabbed browsing (you can save groups of tabs), duplicate file finding, built in Zip management, custom toolbar command creation, file/folder listing and printing. I can attest to it's incredibly reliable performance, error handling and insanely flexible advanced features.Īside from being able to copy vast quantities of data, handle errors, log all actions, migrate NTFS properties, automatically unprotect restricted files and re-copy files if the source is modified, it also has built-in FTP, an advanced synchronisation feature (useful for mopping up failed files after you've fixed the problem that stopped them being copied), and a truly unparralelled batch renaming system which among other things, can use Regular Expressions. Personally, I swear by Directory Opus, by GPsoftware. I think what the primus is saying is that /de copies any file that has a different modification time, not just a newer one.Large file transfers are always a challenge That way I can take a week to get all the data moved from one file system to the other, and every day I can emcopy with the /de switch and the only thing that is going to get copied over is newer data. What I need is for emcopy to look at the source and destination and only copier files that are newer on the source. “ The message displayed when EMCOPY is run with no arguments is correct: “Copy the source files when the last modification is not the same as the destination file's modification time or when files size are different.”In the next EMCOPY release, the readme.txt file which comes with EMCOPY will be updated to reflect this behavior. With EMCOPY 4.00, the readme.txt file that comes with EMCOPY is incorrect when it says that the file will be transferred when “LAST MODIFICATION time greater than the existing target copy or the files that have the same LAST MODIFICATION time and a difference in the size. The /de option of EMCOPY was introduced in order to copy the file from source to destination in case the previous copy was interrupted in the middle of transferring data (in that case, the file date is more recent on the destination and /d will not re-transfer the file). Here is what the primus says:Īn additional note regarding EMCOPY documentation:ĮMCOPY readme.txt file has documentation error regarding /de option. Any suggestions?īergec, I am reading that Primus, but I dont think I understand what it is saying. It would be great to have a more reliable tool that didnt continously fail all day long. Here is an example of the command syntax I use. So I have to babysit the process all day long and keep restarting it. Each time it seems to copy a little more than it did last time, but then it stops again. I have to restart it, then it runs for a while and then stops again. I see a lot of "unable to browse" errors start occuring and then it just stops. What usually happens is for whatever reason emcopy just stops. Running all 5 at the same time seems to give me a lot of problems, so I usually only one one or two at a time. So I am trying to run emcopy from 5 different command prompt windows, each copy to/from a seperate file system. Emcopy while it does work most of the time seems to give me problems any time I try to use it.The way we have our data is it is spread across 5 different file systems. I found a tool called Beyond Compare which worked well, but come to find out, it didnt retain the "file created date" property of the file, so that messed up deduplication.
It has to keep all the file and folder permissons and properties intact. I have approximately 5-6 Tb of data I need to copy from a Celerra NS502G to a NS480.