![]() ![]() A common method is to send just the differences between file_A and file_B down the link and then use such list of differences to reconstruct the file on the remote end. Now assume that file_A and file_B are quite similar, and to speed things up, you take advantage of this similarity. To make it more efficient, you could compress file_A before sending it, but that would usually only gain a factor of 2 to 4. If file_A is large, copying it onto file_B will be slow, and sometimes not even possible. Now imagine that the two files are on two different servers connected by a slow communications link, for example, a dial-up IP link. The obvious method is to copy file_A onto file_B. You wish to update file_B to be the same as file_A. Imagine you have two files, file_A and file_B. Rsync is a tool was created by Andrew Tridgell and Paul Mackerras who were motivated by the following problem: This article provides some further information about rsync, and an explanation of what happened in that story. ![]() However, what most of us forget is to understand what rsync really is, and how is it used, and the most important in my opinion is, where it come from. The friend believed that rsync is a magic tool that should just “sync” the file as it is. They could not understand why the file they copied was 10GB on site A but but it became 100GB on-site B. Some years ago, a friend who used to work on my team needed to copy virtual machine templates from site A to site B. ![]() The problem is when we run things without understanding them. We all do it, and the copy-and-paste itself is not a problem. I think "-ignore-existing" would be the switch you want in your rssync command.There is a notion that a lot of people working in the IT industry often copy and paste from internet howtos. Thanks for your willingness to read through this. Can you give me an idea of a script you would use for my situation? Thanks for your willingness to read through know this thread is way old, Pre-Pandemic one might say, but I'm now dealing with something similar and your approach seems like something that would be beneficial to me. What I feel is my problem now is, if I use RSYNC to move all sub folders under each external drive's 2022 folder but some of those folders are already on the NAS, how do I do it so it moves only new files and folders into the combined folder and skips over any files that are already on the nas and the latest version? I have sporadically been moving one to two folders at a time from each drive into the single 2022 destination folder. My goal is for my destination folder on the NAS to have all 2022 folders from each drive copied into a single 2022 destination folder. On each drive I have a 2022 folder, then inside that folder on one drive might be folders -21, then the other drive might have -11, and the third drive has several other 2022 project folders. The way I have organized their directory structure is by Year, then by project, then raw files along with folder(s) broken out by the concepts of edited, Full-Res, Low-Res, Watermarked Low-Res, etc. Can you give me an idea of a script you would use for my situation?īasically, I'm a photographer I have three 2TB external drives where I store all of the photos from each photoshoot and event that I photograph. Know this thread is way old, Pre-Pandemic one might say, but I'm now dealing with something similar and your approach seems like something that would be beneficial to me. ![]()
0 Comments
Leave a Reply. |