similar to: Differential backup

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

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

Hi All, I am writing a backup program for my computer. brief outline is as follows. Running ubuntu 10.04 2 main partitions, / and /home, both ext3. 1 external usb hdd, ext3, mounted to /backups/main. once every couple of days, rsync backs up, using following command, everything worth backing up in / and /home partitions to a folder /backups/main/Full. command: "rsync -vrhRupElog

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

Am 19.06.2016 um 19:27 schrieb Simon Hobson: > Dennis Steinkamp <dennis at lightandshadow.tv> wrote: > >> i tried to create a simple rsync script that should create daily backups from a ZFS storage and put them into a timestamp folder. >> After creating the initial full backup, the following backups should only contain "new data" and the rest will be referenced

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

rsync folks, Henri Shustak <henri.shustak at gmail.com> wrote: > LBackup always starts a new backup snapshot with an empty directory. I > have been looking at extending --link-dest options to scan beyond just > the previous successful backup to (failed backups / older backups). > However, there are all kinds of edge cases which are worth considering > with such a changes. At

is there anything special to do this from the daemon server. I've setup the /etc/rsyncd.conf with some filesystems and I would rather originate (control) my rsyncs from this server and not from the hosts that have the data I want. ie. I want to pull not push. for instance my rsyncd.conf [www] comment = www path = /snaps/www numeric ids = true log file = /snaps/rsync/logs/www.log pid file

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

Brandysnap is an rsync-based script with a difference. Unlike dirvish, it does not assign importance to snapshots when they are created. All snapshots are created equal, and then they are managed so that the required number of old snapshots is maintained. Unlike rsnapshot, brandysnap does not get its snapshots out of sync if runs are missed, and it is very easy to configure. The link between

Sorry to do this .... AGAIN Every year or two I get stuck on this same problem involving excluding. Seems I learn how its done then 2yrs later I've totally forgotten and when I look up my notes ... this new need is just different enough that they don't apply. Here's the problem. (Simplified... and I've skipped some of the repetitive output) On remote ls A/ a/ b/ c/ d e on

Is there a way to know from the rsync logs how long it took to do a backup? The only timing info,. I see is this at the end: sent 3067328 bytes received 7853035429 bytes 1187888.83 bytes/sec total size is 1559866450336 speedup is 198.55 Can I use it to figure out how long the operation took? Does the above mean it took 2.5 secs of send time and 1.8 hours of recieve time so (roughly) the

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

I'm using rsync to do an incremental backup of my desktop here, to a remote server as follows: #/usr/bin/bash old=$(date -d 'now - 1 week' +%Y-%m-%d) new=$(date +%Y-%m-%d) rsync -avP --delete --link-dest=../$dir /home/bakers bakers at perturb.org:/home/bakers/backup/$new/ This is actually working GREAT! The only problem is that sometimes the cronjob won't complete (internet is

I am involved with the development of lbackup. This message to the rsync mailing list is related to the following thread on the lbackup-disccussion mailing list : http://tinyurl.com/lbackup-discussion-diskfull Essentially, I am curious to if any one using rsync 3.0.7 on Mac OS (10.6) Server has experienced an out of disk space error and not had a message similar to the following reported : >

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

Hi everybody! Since two months I tested a lot with rsync, and found out great things. But I still have a question, maybe two. 1. Was it possible in earlier rsync versions (below version 2.7 I thing, where the ssh option was not set as default) to read out the packets rsync sent? I mean could you read data out of the blocks in clear text, or do you get only ASCII code? 2. How can I get a status

I have a volume at 192.168.0.2 on my local network. I'd like to rsync the entire volume to a backup volume, skip all files already present on the backup volume (same name and the same or earlier timestamp), and include all flags, dates, etc. as applicable to Mac OS X 10.6.x. Can someone tell me the proper command to do this.

Hello, We have strange issue with rsync and backup-dir option. In case of having empty directories and deleting them, those directories are not backed up in backup-dir directory. Directories are backed up only if contains files. Scenario: # mkdir -p source/b # rsync -a --backup --backup-dir=../backup source/ destination/ # rm -rf source/b # rsync -a --backup --backup-dir=../backup source/

Hi, Been using rsync for many years but I'm stuck with this problem. I'ts a simplistic backup using rsync from a Windows 2k3 machine to a Linux box out on the 'net, using pre-shared ssh keys. In this case I'm saving, files belonging to various users, using the administrator account on the windows machine and the destination is a normal user account and its home file area.