similar to: link-dest or cp -al?

Hi, I'm having some strange issues when using cp in my rsync script. It seems there may be links breaking or something. Before running the actual rsync I run the following command in my script: cp -al /backup/Current /backup/$prevday Then I rsync from the source to /Current So shouldn't all my previous days have hard links back to the original /backup directory? Sometimes the

I want to use rsync to backup a couple of Windows systems to a central point. To this end I installed the "DeltaCopy" implementation of an rsync server on the Windows boxes. On the central server I have rsync 3.0.7 running on a Debian GNU/Linux distribution. (I also have a similar configuration but with a QNAP - a NAS with bells on - as the central backup point. Since both exhibit

Clearly I'm missing something about --link-dest; I know it works because rsnapshot is doing the right thing on this system, but it's not on another system, and I'm trying to troubleshoot that. The first step is to be able to verify that --link-dest works on it, but I can't even get it to work in an known-good environment --- no matter how I specify the args to it, it's

Has anyone else had problems using the --link-dest flag? I do what it says in the example rsync -a --delete --link-dest=/home/chamberl/oldbk/ /home/chamberl/source/ /home/chamberl/backup/ I make sure that /home/chamberl/source has some files exactly the same as in /home/chamberl/oldbk/ but evertything gets copiued, and no hard links are done (though they should be). Anyone know the problem?

Hi, To do incremental backups I am presently using --backup-dir=/backup/host/$TODAY and the full backup is written to /backup/host/current. With this system incremental directories only contain deleted files and "current" contains the full backup. Would it be more efficient to use --link-dest=/backup/host/$YESTERDAY and write the main backup to /backup/host/$TODAY ? That way each

I'm using version 2.6.3 on OS X. I'm trying to use --link-dest to keep some rolling backups of production websites. There is about 2GB of data in 60,000 total files. I do an initial rsync to get an initial copy of the data, and each day thereafter I run rsync again with --link-dest to create a new daily backup. For some reason, in the subsequent runs, rsync updates a whole lot of files

I'm wondering if I can use link-dest to compare rsync to a remote directory. rsync -aCHh --stats --link-dest=akane::backup/ranma.daily.1 / myserver::akane/ranma.daily.0 Something like that? Is it going to work like it does when doing a local rsync with a local link-dest directory? Is it going to chew massive amounts of bandwidth? Is there something else I should be doing

Hello, This is my first post to the list. Is it possible to specify the --link-dest option server-side in the rsyncd.conf file? What I'd like to do is implement incremental snapshot backups without having to change the clients which all just do regular dumps to the rsync server. I'd like to specifiy this option on the server rather than on the client because I don't want to

I currently do incremental backups using --link-dest. Unchanged files are hard links to the previous snapshot; changed files are new copies. Where this "fails" is for large files that have received small changes. The directory containing my main IMAP account, for example, typically generates between 1 and 2 G of daily backup data as I file messages in my inbox. Yesterday, though,

Hi, Just a quick question. I am looking for a replacement for the command "cp -al" which has problems dealing with a massive amount of files (http://mail.gnu.org/archive/html/bug-coreutils/2003-12/msg00028.html). Could I use "rsync -aHr" to do _exactly_ the same thing as "cp -al"? I just want to make sure before trying it. Thanks for your help. Charles --

Hello rsync people I thought I knew how to use rsync, but I can't work out how to use it to do the equivalent of cp -al dir1 dir2 where dir1 and dir2 are both local and on the same disk. In other words I want to make dir2 a copy of dir1, with every file hard-linked to its counterpart in dir1. Why not just use cp? Because I want to be able to do it as a user who has sudo

https://bugzilla.samba.org/show_bug.cgi?id=3693 Summary: rsync can use same --link-dest file several times, leading to incorrect hard links Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

I've got a problem for which the combination of -R and --link-dest doesn't seem to be quite enough---and I may have discovered a few small bugs as well; test cases are below. [And if someone has a scheme for doing this that doesn't involve rsync at all, but works okay, I'm all ears as well---I'm not the first with this problem.] Here's my problem: I unfortunately need to

Hi, New to this list, but long-time (appreciative) user of rsync. Grateful for any help with my problem here... In particular, I've been having long-standing issues (just now getting around to trying to resolve them) when I use rsync with '--copy-unsafe-links' alongside the '--delete' parameter. If I use either of these two parameters in isolation (along with other shared

Hi all, Recently I do some jobs based on llvm-link tool. I wonder why link '@llvm.global_ctors' into dest file, even it's not used in dest file? And how can I remove it? Thank you all in advance! Fangqing Xilinx Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugzilla.samba.org/show_bug.cgi?id=12036 Bug ID: 12036 Summary: Multiple --link-dest, --copy-dest, or --compare-dest flags produce incorrect behavior Product: rsync Version: 3.1.2 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component:

Hi all, I have just migrated my tooling from version 2.6.9 to 3.0.0. Unfortunately my script generated an error message during the execution. Because this command was working perfectly in the previous version I suspect this could be a bug. This is the command that I am executing: rsync -av --link-dest=20080313/ --compare-dest=/data/20080313/ 20080313/ /data/20080314/ It just

https://bugzilla.samba.org/show_bug.cgi?id=2947 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2005-08-03 16:45 ------- Keep in mind that --link-dest only hard-links regular

Hello everyone: I keeps using rsync to backup my files on my laptop from one folder to another, and to reduce disk usage, so I use "--link-dest" option for incremental backup like this: *rsync -a --link-dest=/local/old /tmp/myfile /local/new* And "/local/old" is backuped some days ago, I use "--link-dest" option to keep unchanged files as links to new destination

I notice that devices are not hardlinked when using the --link-dest option, for instance: rsync -aH --link-dest=../bar/ foo/ baz/ When foo/zero is a device, baz/zero is not a hardlink to bar/zero. How come? $ rsync --version rsync version 2.5.6 protocol version 26 on linux 2.4.x -- Russell Senior ``I have nine fingers; you have ten.'' seniorr@aracnet.com