The word public, in brackets, is the given name to the module, the area(s) that will be available to reach from the rsync client. I will focus on what is strictly necessary to change in order for my “share” or module to be accessible and functional. If you’d like to read about the several options in detail, please read this article. The file is divided, largely, in two sections, the global section, the first four lines and the modules section, where each rsync module, or “share” is defined.īelow is an example of a nf file: To create the file, replace nano with your text editor of choice, type: sudo nano /etc/nf To install rsync, on a terminal window type: sudo apt-get install rsyncĬonfiguring rsync editing the necessary files – nfĪfter installing rsync, it is needed to create and edit a pair of files, the first one being the configuration file as it is not created automatically upon installation. Install and configure rsync Installing rsync If you do not have yet a machine installed with a Debian based Linux distro, I’ll leave you the links for two of the most popular ones: The configuration part should also be valid for other main Linux distributions, such as Fedora.Ī machine with a Debian based Linux distro installed and updated, that will function as the rsync server, and another Linux machine with rsync installed, which will be the rsync client to test connectivity. I will focus on installing rsync on Debian based Linux distributions, such as Ubuntu. Want to read more answers from other tech-savvy Stack Exchange users? Check out the full discussion thread here.In this article I will look at how to install and configure rsync, “an utility for efficiently transferring and synchronizing files between a computer and an external hard drive and across networked computers by comparing the modification times and sizes of files.” in Wikipedia Have something to add to the explanation? Sound off in the comments. If you can, strongly consider remounting the source file system as read-only before starting the second rsync run (something like mount -o ro,remount /media/source should do). Thus, you can feel free to use the computer normally during the first run, but should avoid making any changes as much as possible to the source during the second run. The second run should transfer only differences that happened during the previous rsync run, and as such, will be completed much faster. Doing so will cause rsync to re-scan the source and transfer any differences that were not picked up during the original run. Once rsync has finished, run it again with the same parameters (unless you have some funky deletion parameter if you do, then be a bit more careful). There is an easy way around that, however. That depends on the type of change, whether rsync has scanned that particular directory yet, and whether rsync has copied the file or directory in question yet. “Write” is anything that modifies the content of the source directory or any subdirectory thereof, so that includes file updates, deletions, creation, etc.ĭoing so will not actually break anything, but the change may or may not actually get picked up by rsync for copying to the target location. What is not generally safe, however, is to write within the source directory while rsync is running. It is also safe to read within the target directory, especially if the target directory is being populated exclusively by the rsync run. SuperUser contributor Michael Kjorling has the answer for us:Īs others have already pointed out, it is safe to read from the source disk or use the target disk outside of the target directory while rsync is running. Is it safe to use a hard drive while rsync is running? The Answer
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |