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 Fri, 2025-07-11 at 16:29 -0400, Robert Moskowitz via users wrote:
> 
> On 7/11/25 11:00 AM, Joe Average wrote:
> > Robert Moskowitz wrote:
> > ...
> > > But is there some way to evaluate the source and see if any changes have
> > > occurred since the last rsync (or some time) and only trigger rsync
> > > accordingly?
> > filtering/investigating the output of rsync's "--dry-run" option ?
> The whole point is to reduce rsync activity.  Dry run is a complete 
> compare of the source and destination.
> 
> It may just be a mental exercise and not worth it.  Every night I have 
> an rsync job that downloads the latest Internet Drafts.  There is 
> currently 168694 files in my download directory.  So every night rsync 
> is comparing that to what is in the IETF repo with:
> 
> rsync -tvz rsync.ietf.org::id-archive/*.txt /home/common/ietf/drafts
> 
> So what am I concerned about backing up a dir tree with a couple 
> thousand files?

Is this a passive download or is the server end collaborating with its
own rsync instance? If it's the former, rsync may not be gaining you
anything as it has to download everything anyway for comparison
purposes, unless you just trust the mod times of the server end files.
Even if you do trust them, any modified files will have to be
downloaded in their entirety. If OTOH there *is* a collaborating rsync
server at the other end, that makes all the difference.

You might also want to consider rclone, which can work with rsync and a
lot of other cloud storage options.

poc
-- 
_______________________________________________
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