Re: using rsync for backups - want to run only if changes from last backup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 7/11/25 5:09 PM, Samuel Sieb wrote:
On 7/11/25 1:59 PM, Go Canes wrote:
On Fri, Jul 11, 2025 at 4:29 PM Robert Moskowitz via users
<users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
rsync -tvz rsync.ietf.org::id-archive/*.txt /home/common/ietf/drafts

So you are rsyncing off the internet?  In that case I think your main
option is the suggestion to use rsync with --dry-run, but in that case
if there are new files, you are doing all the non-download work twice
(unless you capture and process the output and then rsync individual
files).  I'm not sure it is worth the effort....

The original message didn't say anything about it being over the internet.  In that case, there is no way to do what you want.  The only way to know if there are changes is to run the rsync.  And if you have to run it anyway, what's the point of checking for changes first?

I have downloaded, over the Internet from IETF, using their rsync service for lots of years.   I had a small hand in setting this up.

But here I am working with a few servers on my local net, going to my local NAS.  All Linux.

I naturally fell to rsync as I have been using it for lots of decades for lots of things.  This is the first time, though I am am running rsyncd (on the NAS).  I trust all systems involved.

Some cases there are just a few files to copy (BIND zone files) that change, well, once in a while. Some cases there are a lot of files that are updated every week, but not every day.

So I wonder, can I do this smarter with rsync, and it appears it is not worth the candle.  rsync handles that very large Internet Draft download every night.

But a chance to maybe learn a bit more.


--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux