similar to: Rsync Runs Out of Space Because of Temp File

A large file (2+ GB) needs to be transfered, but I see more than one temp file for it. One temp file is larger than the other, but this morning I tried to rsync again, and it DID NOT resume the largest temp file - it resumed the smaller one. Is there an explanation of this behaviour? I didn't want --inplace because I don't need it (I have the disk space). - -rw-r--r-- 1 felipe users

I use rsync on an SSD which is slow at writing, but very fast at reading, so it is important to me to avoid writing data. I had hoped rsync would only write changes in files when using --inplace, but it seems not: # Make a 1 GB file $ perl -e 'print "x"x1000000000' > 1g # rsync it (as expected this costs 1 GB writes) $ ./rsync-3.1.0/rsync --progress --inplace -cva 1g 1g.copy

Hi all. I once tried to rsync around 100 GB (10 million files), but version 2.6.6 needed too much RAM and was too slow. Is one of the snapshots stable enough to try this again? Greetings Sven -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url :

I am using rsync 2.6.9 in daemon mode under Cygwin, and having trouble reconciling its --append behavior with that described in the man page: The man page says that when you use --append, it will update a file by appending, which presumes the existing data on the receiving side matches. But when I run rsync with append mode when the existing file on the receiving side is shorter than on the

https://bugzilla.samba.org/show_bug.cgi?id=13820 Bug ID: 13820 Summary: rsync is not preserving ACLs Product: rsync Version: 3.1.3 Hardware: x64 OS: Linux Status: NEW Severity: major Priority: P5 Component: core Assignee: wayne at opencoder.net Reporter: dinesh.k at

Hello, I have a Debian Etch server (Server A) running Rsync 2.6.9. In Server A I have a second hard drive mounted where I rsync data (about 400 GB) from server B. Server A needs to be rebuilt because I didnt partition it correctly and for other reasons I wont get into. My question is how can I maintain my rsync(ed) data on the second hard drive in the new Server A without having to re-rsync

This is the case - mounted Inetpub's windows-webserver on /mnt/web1 /mnt/web2, etc. - rsync this to local dir: rsync -av --delete /mnt/web1 /mass/kuurne/day rsync -av --delete /mnt/web2 /mass/kuurne/day etc.. - when logged in, everything works (I do see some errors about non-existing files, but rsync won't stop. When used this command in cron 00 01 * * * rsync -av --delete

Hello together, I have a question about using rsync with many files. We are using rsync via rsnapshot, but this is not elementary. It is used to backup many (above 100 servers) and works very well. Now there is one server with many (several millions) files. The files are not very big, so the complete backup is about 500 GB. Now my problem is, that the backup needs about 14 hours - the most time

On Mon, 13 Jul 2015 15:40:51 +0100, Simon Hobson wrote: > The think here is that you are into "backup" tools rather than the > general purpose tool that rsync is intended to be. Yes, that is true. Rsync serves so well as a core component to backup, I can be blind about "something other than rsync". I'll look at the tools you suggest. However, you've made be

Hi All, My using rsync command to backup my mail server mailbox to backup server. I am using following command for backup. rsync -avzu -e ssh root at 192.168.1.12:/mail_home /mail_backup I configured daily cron for this command in backup server. In mail server /mail_home folder having all user's mailbox and size of mail_home is 345 GB and in backup server I have assign 450 GB for

Hello, anybody has a clue why this happens? The scenario: Each night I create LVM snapshot of my volume which contains some virtual disk images (VirtualBox VDIs). Then I rsync the content of one of the snapshot directories to a backup server. Each file size is between 1.3 GB and 6GB. I run the following commmand: sudo -u rsyncbackup rsync -avzP --exclude-from /home/rsyncbackup/excludefile -e

We have nearly 200 GB of data in a production Oracle database broken up into about 100 files of 2 GB. The database incurrs a 5% change per week in the form of new data, no modification nor deletions. I need to copy this data from one mount point to another then bring up the new database on the new mount point in place of the original. The high availability and production nature of this system

Hello, Today I succesfully transfered some testfile on my local computer with the following command: rsync -e "ssh" testfile.txt localhost:receive I can also succesfully connect with SSH to a remote server through an http proxy with the following command: ssh -o "ProxyCommand corkscrew myhttpProxy 8080 targetcomputer.domain 22" targetcomputer.domain But I'm so far

Hi, i have to tranfer large files each 5-100 GB (mo-fri) over dsl line. unfortunately dsl lines are often not very stable and i got a broken pipe error. (dsl lines are getting a new ip if they are broken or at least after a reconnect every 24 hours) i had a script which detect the rsync error and restart the transmission. this means that if a file has transfered e.g. 80 % i start again from

I just tried to copy several million files with rsync. Unfortunately, it seems to freeze: # rsync --delete-before -a -H -v --progress --stats /srv/backuppc-data/ /mnt/iscsi_backup/backuppc/ building file list ... 7891370 files to consider And it waits here. It was already copied once sussessfully, and this time, I just wanted to do an update. Destination filesystem is iSCSI, on another device

Hello. Recently, I started using rsync to backup files in my root partition on an Ensim box over to a remote machine. The remote machine 'pulls' from the Ensim box using the following: rsync -arvzx --exclude=/proc --exclude=/tmp --exclude=/mnt --delete --delete-excluded -e ssh 192.168.0.1:/ /bkup/rootpart/ The problem is, if I 'df' the Ensim box, it reports that the entire

https://bugzilla.samba.org/show_bug.cgi?id=3358 Summary: rsync chokes on large files Product: rsync Version: 2.6.6 Platform: PPC OS/Version: Mac OS X Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: david-bo@dsv.su.se QAContact:

Hi, When I send this command, I get a timeout almost every time... --- this is the client side --- rsync -av --timeout 120 /home/bat/20070205_0501/log/sync_dns29_log /home/bat/20070205_0501/log/sync_dns29_serial /home/bat/20070205_0501/log/sync_dns29_tcpdump_log.gz --port 5873 fileserver::test/20070205_0501/log sending incremental file list sync_dns29_log sync_dns29_serial

I have been doing some experiments with rsync on btrfs, a copy-on-write file system that is approaching or having just achieved production-ready status depending on your requirements. For my purposes the reliability appears by almost all accounts to be there, and the compression alone makes it very compelling. However the following two experiments show rsync behaviors that are disappointing to

Hello, I have two production servers which house large drive arrays storing digitized music for our webradio. They are used in a 'failover' configuration so that if one goes down the other remains available. New music is added all of the time to this library and it is a pain to have to add it to both machines as the files are large (.wav). I am thinking to setup rsync to keep the drives