DO NOT REPLY [Bug 6996] New: syncing backups - autodetect older variants already existing on receiver

[samba-bugs at samba.org]

https://bugzilla.samba.org/show_bug.cgi?id=6996

           Summary: syncing backups - autodetect older variants already
                    existing on receiver
           Product: rsync
           Version: 3.1.0
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P3
         Component: core
        AssignedTo: wayned at samba.org
        ReportedBy: bugzilla.samba.org at zmi.at
         QAContact: rsync-qa at samba.org


We use virtualization, each server makes it's backup to a central backup
server. That backup server rsyncs every day the diffs to another site.

Many of the servers make a "backup.tar.bz2", and keep the older version as
"backup.tar.bz2.old" or "backup_old.tar.bz2". These files tend to be large, so
it would be nice not to sync them, just rename them on the receiver site.

rsync currently transfers the "*old*" version despite it exists already on the
receiver, it's just still named "backup.tar.bz2" and would need to be renamed
to "backup_old.tar.bz2" (or backup.tar.bz2.old depending on how it is named
now).

It would be very interesting to have a feature to search
- within the same dir for files with "similar" names and autodetect if they are
the same
- within the same dir for subdirs which have the same content and have just
been renamed. This is for backups that do "backup/0", "backup/1", and so on,
just renaming the dirs each day.

That should result in just a rename on the receiver side. It could reduce the
backup traffic a lot. Maybe name that options "--search-similar"

I think nearly everybody uses "generations" of backups, just renaming them on
the original server. So this would free the Internet of unneccessary traffic
during the night.


-- 
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.