search for: dynamic_hash

We're having a performance issue when attempting to rsync a very large file. Transfer rate is only 1.5MB/sec. My issue looks very similar to this one: http://www.mail-archive.com/rsync at lists.samba.org/msg17812.html In that thread, a 'dynamic_hash.diff' patch was developed to work around this issue. I applied the 'dynamic_hash' patch included in the 2.6.7 src, but it didn't help. We are trying to evaluate the possibility of using rsync as an alternative to IBM's FlashCopy, which only works within the storage pool con...

I need to rsync 4 TB datafiles to remote server and clone to a new oracle database..I have about 40 drives that contains this 4 TB data. I would like to do rsync from a directory level by using --files-from=FILE option. But the problem is what will happen if the network connection fails the whole rsync will fail right. rsync -a srchost:/ / --files-from=dbf-list and dbf-list would contain this:

...a non-predetermined hash table size, so that the hash cell load (alpha) is never more than 80%. As far as my understanding of rsync goes, this requires no change in the rsync protocol. Comments welcome, Shachar -------------- next part -------------- A non-text attachment was scrubbed... Name: dynamic_hash.patch Type: text/x-patch Size: 1454 bytes Desc: not available Url : http://lists.samba.org/archive/rsync/attachments/20060225/62f748cc/dynamic_hash.bin

Hello, I have inherited a setup where there are 2 AIX 5.1 systems in 2 separate sites. There are large database files that are backed from each site to the other via rsync. Currently, it is using rsync version 2.5.4. It does it via ssh with the options -avz. This has all been merrily plodding along for some time. There is one file that is over 45 GB, and it started having trouble with that

This is my situation and I am running into dead ends. We have a server with about 400GB of data that we are trying to backup with rsync. On the content1 server we had rsyncd.conf as: [content1] path = / comment = Backup list = no read only = yes hosts allow = 192.168.22.181 hosts deny = * uid = root gid = root and on the backup server we had a crontab entry as follows:

I've been playing with rsync and very large files approaching and surpassing 100GB, and have found that rsync has excessively very poor performance on these very large files, and the performance appears to degrade the larger the file gets. The problem only appears to happen when the file is being "updated", that is, when it already exists on the receiving side. For instance,