similar to: sudo / --link-dest combination problem.

I have been trying to use rsyncx to generate a script for rotating backups but it seems to me that the --link-dest option doesn't work properly in my configuration. Instead of creating hard links for all unchanged files it seems that rsync copies everything, as if --link-dest hasn't been specificed. Can somebody clarify what's going on? My script is ptovided below: #rotating backup

Hi there, I'm using this version of rsync: localhost:~ mzehetle$ /usr/local/bin/rsync --version rsync version 2.6.0 protocol version 27 Copyright (C) 1996-2004 by Andrew Tridgell and others HFS+ filesystem support for OSX (C)2004 Kevin A. Boyd <http://rsync.samba.org/> Basically incremental backup (--link-dest option) works with a destination on my local volume but not with a

On Mon, Jun 02, 2003 at 03:32:04PM -0700, Michael Rubel wrote: > Hi J.W., > > Please pardon this intrusion on your private address; the rsync list seems > to be down (no messages since yesterday), so I'm forwarding this directly > to you. If you'd rather wait until the list restarts, that's fine too. I'm CCing the list. > > Best regards, > Mike >

Way back: > > ---------- Forwarded message ---------- Date: Mon, 2 Jun 2003 > > 09:56:50 -0700 (PDT) From: Michael Rubel <mrubel at > > galcit.caltech.edu> To: rsync at lists.samba.org Subject: > > --link-dest when target and compare_dir both have file > > > > Hi J.W. et al, > > > > Kevin Everets was kind enough to inform me about some

Hi I am a rsync (on Mac OS X, RsyncX version with extended HFS+/-eahfs forks) beginner (I merely use it for backing up my desktop machine to a bootable external firewire volume, so that I can resume work in case of a harddrive disaster) and I got these messages: mknod "/Volumes/backup/Applications/Plone2/Sites/Default/var/zopectlsock" failed: Invalid argument mknod

Hello fellas, Firstly, I would like to apologize for the post being long, but I would appreciate if someone with a good knowledge of the subject gave his opinion. I am working on a backup solution for a series of old and very specialized host computers in aviation industry. I need to do monthly backups of one or two logical volumes (non-OS) on each of the computers and keep the last 12 monthly

> Hi-- > > I just tried my first rsync operation. I got a couple of errors I don?t > understand. Could someone explain what might be happening here? > > Please know that I am working in rsync for Mac OS 10.4, which includes a few > odd options discussed in previous posts. > > The original command was: > > time rsync -a -v -e ssh /'Applications'

I'm getting a "bad address" error which is causing my rsync process to bomb out. I'm running RsyncX 2.1, in daemon mode on the source machine, with a script to pull the information to the backup server. Both servers are Xserves running OS X Server 10.2.8. Rsync target is on an Xserve RAID. The RAID has 350GB free, so I'm not running into a disk full situation. My command

Hi, I am using --link-dest for my rotating backups. Noticing the "--detect-renamed-lax" patch to rsync 3.0.0. I was hoping to make use of the --detect-moved. Unfortunately, "--detect-moved" does not seem to recognize the --linkdest option. A moved file is getting transferred again and a new file is created at the receiving end instead of linking to the moved

Hello, (I found a post in the archives titled "link_dest checks perms despite no -p -o or -g" on April 7th, which might be related - not sure...) I'm trying to get a rotating daily backup going with previous days kept as hard links to save on network transfer and disk space. The plan: on day N, rsync to blah/N/, using --link-dest=../<N-1> (modulo 7 or whatever). My test

Alright guys, you're my last hope. Currently I am trying to create a rotating backup system. I have a remote server which I've patched to work with the -E option. Anyhow, the remote server has the backup and I'm trying to use --link-dest against it. Here is the command I'm running. sudo rsync --dry-run -e 'ssh -l root' --delete -auE \ --link-dest=../backup.0 \

I am attempting to backup the Users directory on my desktop running OS X 10.3.6. I am backing up to Jaguar Server 10.2.8. I am using RsyncX version 2.1 on both systems. RsyncX Server is set up to run on both systems however in this instance the Rsync client is my desktop and server is Panther Server. When I kick off an RsyncX session, RsyncX will run for a while, then stop part of the way

Folks, Thinking again about the issue of changed attributes for a file in source that is identical in content to a file in destination that is hard linked get propagated to the --link-dest directories I would like to suggest a new flag, (perhaps called something like --preserve-linked-attributes), to allow callers to get the behaviour that is needed to allow the use of recycled

OS X 10.4.6 (BSD) I was using the 'standard' versions (i.e. non-HFS supporting) of rsync with the backup -b option so that I could do nightly incrementals. This seemed to be running fine. Changes to existing backed up files got copied to the appropriate path(s) on the target. BUDIR=myDirectoryName time /usr/local/bin/rsync -a -b --suffix=# --backup-dir=$BUDIR / Users

I have the following as a line in a script kicked off from cron: sudo rsync -e ssh -avz /Times_QPS/ 192.168.22.72:/Times_QPS/ --eahfs It logs the output to a log file, however rsync caused the log file to go to an 80gb file and fill up my disk because it threw a mental when a file it went to sync was no longer there! Is there some way to get the sync to ignore errors? -Jason

I am having a problem with implementing a slight modification of the "backup to a central backup server with 7 day incremental" example from <http://rsync.samba.org/examples.html>. When rsync runs, I end up getting stat errors that the file doesn't exist in the backup-dir location. The backup server is running rsyncd, and without the --backup and --backup-dir options set, I

Hi guys, I've been struggling with getting --link-dest working for a couple of hours now. I'm using rsync 2.6.9 (protocol 29), on Gentoo Linux. For some strange reason, whenever I recreate the source file, even though it's identical to the old source file --link-dest simply does not create the link. Point in case (starting from a blank directory tmp in my home directory):

this email is to Sean M. Kaiser skaiser at northmont.k12.oh.us post was: Tue Feb 24 23:38:32 GMT 200 hi, did you get a solution for the --backup-dir problem (stat error messages)? I ran into the same thing... Thanks Christian the original message was: > > > I am having a problem with implementing a slight modification of the > "backup to a central backup

The following backup script works fine for test cases but for doing a backup of 750 MB, the directory daily.1 has a subdirectory daily.0, that is, there is daily.1/daily.0 daily.2/daily.1 daily.3/daily.2 The directory daily.0 has nothing strange, no unusual links at the top level neither hard or soft. Also, the original directory has not unusual links. All directories are in the same

> Here's the deal... I have a filesystem that I have populated by > rsyncing from a filer (over NFS) using the --link-dest option to create > incremental "snapshots" of the live data. This part is working > fine... lots of links, much fewer blocks represented. Now it is time > to migrate to > a larger filesystem and, during the rsync, the links are not being