search for: rsyncability

...; rsyncing the entire package file. The only possible > > amelioration of this would be the use of the gzip > > --rsyncable option (which requires a patched gzip) by the > > package builders--assuming they use gzip for package > > compression. Given the effect of improving rsyncability and > > thereby reducing bandwidth requirements such a change to > > their package build scripts could well be to their > > advantage. > > BTW, is there patch for bzip2 that adds --rsyncable option? Or may bw > someone working on it? I don't expect so. The --rsynca...

Hi, I currently create large (500MB-2.5GB) tar.gz files that I am trying to get to rsync better. After doing some research by reading a lecture presented by the original author of rsync and googling the list archives, I have concluded that the gzip-rsyncable.diff is the best way to get gzipped files to rsync nicely. The only version I could find of this patch is available here:

Hi all- My test results so far indicate a pretty decent improvement in overall rsync performance when using a slightly more sophisticated checksum calculation. The attached patch has the required changes (in hindsight, I should have compressed this using zlib with the new algorithm :-) ). Some things to know about the patch: First, it is against the zlib library - NOT the gzip application. By

Hello group, I'm having a very hard time rsyncing efficiently a MySQL database which contains very large binary blobs. (Actually, it's the database of Mantis bug tracker [http://www.mantisbt.org/], with file attachments stored directly in the table rows. I know it's a bad idea from many other reasons, but let's say it was given to me as such.) First, I was dumping the

Hello All, I have been using rsync to backup several filesystems by using Mike Rubel's hard link method (http://www.mikerubel.org/computers/rsync_snapshots/). The problem is, I am backing up a lot of ASCII .log, csv, and .txt files. These files are large and can range anywhere from 1GB to 30GB. I was wondering if on the target side (the backup side), if I can use some sort of compression. I

Hi folks, Are there any tricks known to let rsync operate on huge tar files? I've got a local tar file (e.g. 2GByte uncompressed) that is rebuilt each night (with just some tiny changes, of course), and I would like to update the remote copies of this file without extracting the tar files into temporary directories. Any ideas? Regards Harri

Hi, Recently We've upgraded some KVM hosts from Fedora 29 to Fedora 30 and now experience broken VM configurations on filesystem after virsh blockcommit. Commands "virsh dumpxml ..." and "virsh dumpxml --inactive ..." is showing diffrent configuration than the one on filesystem. In case of restart libvirtd or system reboot, there are broken VM xml configurations on

Hi, Recently We've upgraded some KVM hosts from Fedora 29 to Fedora 30 and now experience broken VM configurations on filesystem after virsh blockcommit. Commands "virsh dumpxml ..." and "virsh dumpxml --inactive ..." is showing diffrent configuration than the one on filesystem. In case of restart libvirtd or system reboot, there are broken VM xml configurations on

Hi I'm having issues sendig a lot of tar.gz backup files to a ZFS remote filesystem server. This files are compressed with the --rsyncable option. Sending without --inplace option rsync works well and send only the differences, but to create a temporary file and rewrite the file destination, zfs snapshots contain the full size of the backup, not only differences block. I've tried

Hi All, I have a 1.8GB PST file that is backed up every night from a cygwin install) and every night rsync transfers about 1.8GB of data for that file. It changes a bit, but for all intents and purposes the entire file is transferred. There are other files on this system that rsync more typically, so I'm fairly certain this isn't a switch or command error on the calling end. I have also

Suppose I have a particular version of a largish compressed archive, most likely a .tgz or .tbz2, and that a remote machine has a newer, and only slightly different, version of the same archive, where most of the content hasn't actually changed much. I might attempt to obtain a copy of the newer archive by first copying my local older copy to the newer name as a file to update from. My

I noticed with rsync and compressed files or package files the transfer efficiency drops considerably. Eg. rsync an ISO image of a distribution will give you between 30% and 60% of the original transfer although from Beta1-Beta2 the change could not have been that great. The same thing happens with ZIP files for obvious reasons. My question or feature request if you want to call it is. Is it

Hello folks! I've been thinking about adding the capability to store files compressed and/or encrypted on either side of the rsync transfer. Let's say there's a storage space provider. I want to store my files on that server compressed (so I don't use more paid space than I need), and encrypted (so they can't read my data). I don't know much about encryption, but I

Hello All, I have searched for this error and found similiar errors, but everything seems to indicate that this should be fixed in the 2.5.5 version. rsync version 2.5.5 protocol version 26 I am running rsync with -axz, trying to sync up a large gz file : Source machine: -rw-r--r-- 1 root other 175214792 Dec 22 00:17

Mike, As it stands right now, we use xz for our compression, so if rsync had a similar option for xz that would probably be an improvement. However, I think being able to decompress directly to the remote system would save more; elsewise I don't see how I'm going to be able to avoid untarring and uncompressing the whole xz file on the other end. thanks much, ed On Tue, Dec 6, 2016 at

Hi, all - I've been digging into the question of using rsync to sync up compressed data, and read with interest the conversations regarding the rsync friendly patch available for gzip (I belive Rusty provided this patch). For anyone interested, the message thread is archived at http://lists.samba.org/archive/rsync/2002-June/thread.html. The broad outline of this approach were mentioned in

Hi, all. This is my first post to the list, so please forgive me if this is an old issue. I scoured the mailing list archives by hand and could find no mention of it, and the official FAQ-o-matic mentions it, but doesn't offer a fix that works for me. I've set up an rsync daemon on Windows NT4 by installing the latest cygwin. Using the cygwin1.dll and rsync.exe, I'm able to connect

At $work I have an odd situation involving incomplete file transfers, but I am unsure where the issue may be occurring. Here is the scenario. Problem: Sometimes the file transfer seems to have completed, but the file size does not match that on the remote system. Details: I transfer a number of large (>1GB) Tar-Gzipped (.tgz) files via SSH tunnels from $customer. Because of some previous

https://bugzilla.samba.org/show_bug.cgi?id=6916 Summary: Avoid bundling a modified zlib Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: matt at mattmccutchen.net

Dear all, I am implementing a backup system, where thousands of postgreSQL databases (max 1 Gb in size) on as much clients need to be backed up nightly across ISDN lines. Because of the limited bandwidth, rsync is the prime candidate of course. Potential problems I see are server load (I/O and CPU), and filesystem limits. Does anyone have experience with such setups? Ron Arts -- NeoNova BV