![]() This modifies rsyncâs "quick check" algorithm for finding files ![]() ![]() To mirror a directory with storage connected to the same machine, this is what I use. For people new to Unix, it is just easier to say "don't, ever" then try to explain when it is ok. Running almost all GUI tools with sudo/root is a bad idea for a number of reasons. For backing up a single HOME, this might not matter too much, but if there is more than 1 userid or any system files, forget it. rsync for backups has a number of limitations, especially if the file systems between the source and target are different. ![]() I've never had luck with GUI back tools, and actually, for rsync to be more than a way to mirror or mirror and add files makes learning a real backup tool make more and more sense. If you mount it using a GUI, it will be 30% slower than it need be. If you plan to run this mirror weekly, it is best to script it, so exactly the same options, exactly the same source and exactly the same target are used. Over the network, rsync does to block comparisons by default. If you want that, you'll need the -no-whole-file option and you'll need to understand the caveats in using it. Rsync between storage on the same computer doesn't do differentials by default. If you want a backup, there are better choices with options similar to rsync, but that handle the versioning, permissions, Put me in the "use rsync, not grsync" group, but only if you want a quick and dirty mirror. Last edited by rbmorse May 1st, 2019 at 04:17 PM. It would be embarrassing if I worried about such things. However, by the time of the day I get around to thinking about backup, I seldom meet all the prerequisite conditions. This method induces fewer errors for me than any other.Īnd yes, if I know what I'm doing, have time to concentrate, not distracted by intractable problems forced upon me by dim, lazy and untalented supervisors, not suffering from chronic lack of sleep or amusement and not particularly drunk, using rsync via the command line is a much more efficient way. It usually ends up being one directory above or below where I really want it to go, but I've also specified the wrong hardware device on more than one occasion.īest practice for me is to set the source and destination directories using grsync's GUI.check the little block at the end of the source and destination lines and use the file browser to navigate to the correct places. What you describe happens to me when I don't properly specify the destination directory and grsync goes where I tell it and finds no prior backup, so it ends up copying the entire source directory. Only a few dozen files have been changed or added, I expected the process to skip existing files and only update or add the changed files I expected maybe 20 minutes to complete at most.Īny ideas where I should place check marks? Ignore Existing, Skip Newer, Show Transfer Progress,Įvery file on the source media was copied to the destination, this backup took over an hour to copy 68 Gb Preserve time, Preserve owner, Preserve permissions, Preserve Group Grsync options I've selected (placed a check mark): I tried to back up one device last night, I thought I selected sensible options, but I had a surprise. Local to local backup is what I've done and will be the norm for me.Ī few weeks ago, I succeeded in backing up several USB 2.0 based storage to an external USB 3 external hard disk. Just starting to get familiar wth Grsync.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |