similar to: originate sync from the daemon server

Normally I would use the --link-dest option to do this but I can't since I'm rsyncing from a Mac to a Samba share on a Linux box and hard links don't work. What I want to do is create a 10 day rotating incremental backup. I used the first script example on the rsync examples page as a template. The only thing I changed was the destination to be a local directory and paths for

Hello, I have got three folders: - /home/backup/2008-10-20 - place for differential backup - /mnt/for_backup - folder with files for backup - /home/backup/2008-10-01 - place where the last full backup is My question: is below command prepared correctly to make differential backup? rsync -avPbn --backup-dir=/home/backup/2008-10-20/ --exclude "System Volume Information" --exclude

well, when I tell rsync to compare my home directory with itself, it reports many differences. I'm using rsync version 3.0.7 protocol version 30. I was hoping to use it to verify my backup.

Hi All, I am aware that rsync can be run to just list the files that have changed between the source and destination. I would like to capitalize on that feature to monitor some development that is going on in order to get a complete list of files that have been changed on a server. I realize that I can create an initial rsync of the files to some other location and then sometime later run

We use rsync to copy files and directories from one server to the other. What options should I give to rsync so that it only copies the modified files? For example server1 may contain a dir which contains just one file that has been modified, how do I get rsync to copy just that one file over? I would like rsync to copy over the files which have been modified on the server1 to server2. This is

Am 09.02.2017 um 11:05 schrieb Ben RUBSON: >> On 09 Feb 2017, at 10:05, Thomas Güttler <guettliml at thomas-guettler.de> wrote: >> >> Hi, >> >> we have a huge directory tree. >> >> >> * 17M files (number of files) >> * 2.2TBytes of data. >> * Only 0.1% changes per day >> >> Current pain: rsyncs directory tree traversal

Hi, I have few questions that could not find answers to in documentation. Different filesystems: Lets say I want to keep all extended attributes and everything else, so I use -A, -X, --perms etc., together with --fake-super. Now, lets say source FS supports some attributes not supported on target FS (for example, XFS extended attributes). Would this work as expected (ie. extended attributes are

Hi list, I have been reading MAN pages and listarchives, but not found the answer to my question though I am sure it must be possible to acheive my wish. I wish to use rsync to create a backup BUT only keep the files for a limited period of time, EG two weeks. I have not yet been able to figure out how to do this inside rsync (while the backup is being performed) and my understanding of the

Hello all, I have a strange problem where rsync is copying over all files instead of just the ones that have changed. My setup: -------------- Backup server runs a script that calls rsync in more or less this form: "rsync --rsh=ssh user at remote.server.com:/backups/stuff /localbackup" Of course, I use a # of options, but the main ones are "-axS" Just in case, here are

Feature request: allow --link-dest dir to be linked to even if file exists in target. This statement from the man page is adhered to too strongly IMHO: "This option works best when copying into an empty destination hierarchy, as rsync treats existing files as definitive (so it never looks in the link-dest dirs when a destination file already exists)". I was suprised by this behaviour

As Ben mentioned, ZFS snapshots is one possible approach. Another approach is to have a faster storage system. I have seen considerable speed improvements with rsync on similar data sets by say upgrading the storage sub system. -------------------------------------------------------------------- This email is protected by LBackup, an open source backup solution http://www.lbackup.org

Does anyone have a good distributed backup strategy? I've been revising mine for a year or so now and always realize there's some hole or another in it. I get the feeling to do it exactly the way I want it needs to be complex, but I'm looking for something elegant. My data consists of some of these representative folders: .mozilla Documents Pictures .ssh Music bin And these

How do you handle snapshotting? or do you leave that to the block/fs virtualization layer? /kc On Fri, Apr 17, 2015 at 01:35:27PM +1200, Henri Shustak said: >> Our backup procudures have provision for looking back at previous directories, but there is not much to be gained with recycled directories. Without recycling, and after a failure, the latest available backup may not have much

Dear rsync-guru's, here's a user question: I want to make sure the files transferred to rsync daemon (running on a linux kernel) are written to media I assume if rsync command returns (with 0) all data has been tranferred to rsync daemon, but it depends on the rsync daemon priority and linux pdflush daemon before the data is truly written to physical media (whatever that is). Is there

Hi All, I am presently doing a small POC with rsync for incremental backup and restore starategies. I have come up with certain question down the line, can anyone help me with the explanation. Used the config and ideas from: http://www.mikerubel.org/computers/rsync_snapshots/ The commands executed on two machines in sequence Machine 1: root at Andruil:~# vim testfile root at Andruil:~# ls

I'm using rsync 3.0.7 on Mac OS X 10.6, compiled according to Mike Bombich's instructions at http://www.bombich.com/rsync.html. Rsync repeatedly exits with a protocol data stream error when trying to copy some com.apple.FinderInfo extended attributes. While testing this issue, I found that rsync is not actually copying all extended attributes even when there is no error message. I'm

On Sun 02 Jun 2024, Chris Green via rsync wrote: > I have an rsync daemon running on a 64-bit (x86_64) system which I > successfully use for backups from several other 64-bit systems on my > LAN. > > I want to use it for backups from a BeagleBone Black (32-bit, armv7l) > but it fails as follows:- > > root at bbb:~# rsync -a /etc chris at backup::bbb >

I am a developer on the LBackup project. An LBackup user recently posted a question to the mailing list asking about the following error. > "rsync: unpack_smb_acl: sys_acl_get_info(): Unknown error: 0 (0)" Link to thread : <http://www.mail-archive.com/lbackup-discussion at lists.connect.homeunix.com/msg00040.html> My understanding of this error is that when copying files via

Hi there, I am running rsync-3.0.6-12.el6.x86_64 on a centos 6.6 box. Am trying to get files from a remote server (centos 6.5) to my local machine. It appears to connect fine, but does not transfer any file. this is what I am seeing [youcantoo at testbox home]# rsync -avvvzh -P --stats --delete servername::backupdir/ /home/findmoore opening tcp connection to servername port 873 sending daemon

I'm really confused with all the examples out there and all different types of incremental backups. I tried several scripts but cannot reduce the size of my backup folders. What I want is to backup my documents to my external drive every month and save as much disk space as possible. Lets say I have 3 backup directories in the external drive, backup03.10, backup04.10 and backup05.10. I want