This does mean that this option is only looking at the existing files in the destination hierarchy itself.
transfer all files in a directory that have changed or have been created?
So wondering how can I modify the rsync command to send out only newly added files. It goes a lot faster if it doesn't have to juggle tens of thousands of files.
Thanks This forces rsync to skip any files which exist on the destination and have a modified time that is newer than the source file. Another option is to just unzip and if you are using a modern version of the tool it seems it will give you an interactive mode.
(If an existing destination file has a modification time equal to the source file's, it will be updated if the sizes are different.) --update does skip files when the mtimes are identical (which is not what the wording implies). I believe the wording would be better understood if it said "only source files which are newer than destination will be copied"[email protected] "only source files which are newer than destination will be copied" ..source files that have same modification time as their destination file counterparts, but have different sizes. (Chris already covered that, thanks) From my experience with rsync, a 1TB partition copying is too large to be efficient. This is nice because you can see what it's trying do.
At any point you select "A" it will essentially perform the -o option. [y]es, [n]o, [A]ll, [N]one, [r]ename: y inflating: .htaccess replace 50/images/2011-Press-Kit.jpg?
The following command will recursively copy all files from the local filesystem from /var/www to the remote system at 10.1.1.1.
However you may want to copy files over the have been updated more recently on the local filesystem which is done with the --update flag.
[y]es, [n]o, [A]ll, [N]one, [r]ename: y inflating: 50/images/2011replace 50/images/60-years.jpg?
[y]es, [n]o, [A]ll, [N]one, [r]ename: A (continues overwriting) inflating: template/bootstrap/js/tests/visual/inflating: template/bootstrap/js/...
This option can be useful for those doing backups using the --link-dest option when they need to continue a backup run that got interrupted.
Since a --link-dest run is copied into a new directory hierarchy (when it is used properly), using --ignore existing will ensure that the already-handled files don't get tweaked (which avoids a change in permissions on the hard-linked files).