On 22/01/13 13:51, Russell Coker wrote:
> I've got an archive of 30G+ of video files that needs to be synchronised
> occasionally with a system that has limited quota. I want to get a list of
> new/changed files that I can pass as parameters to tar and then take a tar
> file
> on a USB stick with the new files.
Missed the significance of what you were saying here first of all,
these rsync options might also be handy to you:
--write-batch=FILE
Record a file that can later be applied to another identical
destination with --read-batch.
See the "BATCH MODE" section for details, and also the
--only-write-batch option.
--only-write-batch=FILE
Works like --write-batch, except that no updates are made on the
destination system when cre‐
ating the batch. This lets you transport the changes to the
destination system via some
other means and then apply the changes via --read-batch.
Note that you can feel free to write the batch directly to some
portable media: if this media
fills to capacity before the end of the transfer, you can just
apply that partial transfer to
the destination and repeat the whole process to get the rest of
the changes (as long as you
don’t mind a partially updated destination system while the
multi-update cycle is happening).
Also note that you only save bandwidth when pushing changes to
a remote system because this
allows the batched data to be diverted from the sender into the
batch file without having to
flow over the wire to the receiver (when pulling, the sender is
remote, and thus can’t write
the batch).
--read-batch=FILE
Apply all of the changes stored in FILE, a file previously
generated by --write-batch. If
FILE is -, the batch data will be read from standard input. See
the "BATCH MODE" section for
details.
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
_______________________________________________
luv-main mailing list
[email protected]
http://lists.luv.asn.au/listinfo/luv-main
