In this case I'm coping entire drives (F: drive) from a remote server to the local server \\\F$ F:\ - Source path followed by destination path. purge removes files and directories from the destination that do no exist in the source. sdd forces the target directories dates to be synchronized with the source directory. Emcopy 4.16 download update#ĭe - Compares both file size and last modification time when deciding to update a file, updates it if either have been changed. cm md5 - checks the file content after copying using and md5 comparison of the source and destination. o /secforce /sd - /o copies the files owner, without this the account used for the copy will be the owner. secforce overwrites the destination security settings with the source security settings (copies security settings). sd preserves security, the file isn't copied if an error occurs during security settings. r:1 /w:30 /c - /r:1 retires one time (default I believe is 100), I don't care to have it retrying all day because someone left a word document opened. If it fails it fails and I'll catch it tomorrow. w:30 is the wait time in seconds between retries. c will allow the process to continue after the retries.Answers with reference to your question numbering:ġ.a) If your EMCopy command contains the '/c' option, EMCopy will continue after any error (after retries) with the remaining files. If you leave out the '/c' it will not continue, but stop on the first (unrecoverable after retries) error. In other words, whether it stops or continues on an error is entirely up to whoever wrote the EMCopy command line. You mentioned reading that it stopped possibly what you read did not mention the 'continue' option.ġ.b) If a file is locked on the source, it cannot be copied to the target, so EMCopy leaves any previously-copied version on the target alone. EMCopy will only overwrite on the target if the file can be copied. You mentioned reading something to the contrary possibly what you read is incomplete or incorrect.Ģ.) Normally, with EMCopy (and Robocopy, and many similar tools) you run several passes. One full copy and several incremental synchronizing passes. Then take down user/application access to the source, do one final pass while no-one is using the source so that everything is fully synchronized, and then cut over to the target system.
0 kommentar(er)
