similar to: How to delete files older than X on backup during sync?

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

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'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

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

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

Hi, Presently I have the latest full backup in a 'current' directory and 30 day incrementals in 'YYYY-MM-DD' format directories. Without changing that directory structure I'd like the 'YYYY-DD-MM' directories to contain the full system hardlinked (when applicable) to 'current'. What rsync command-line options could provide me with this? Thanks,

The current man text for rsync is rather sparse in what it tells you about backup-dir This is from my debian installation - which appears to have come from the source here --backup-dir=DIR In combination with the --backup option, this tells rsync to store all backups in the specified directory on the receiving side. This can be used for incremental backups. You can addi? tionally specify a

Hi, I am using rsync to backup files. Is it possible to specify an option not to delete files from backup directory if the files are deleted from source? In that way, I can always keep something I may or may not need in the backup disk, but remove it from a work computer. Thank you. Kind Regards. hce

Hey all, I'm writing a tool: http://www.subspacefield.org/security/hdb/ It is very similar in some ways to rsync, except it's meant for backing up locally to removable HDDs, and it keeps metadata around when the HDD is removed. I figured I'd ping people here to see if they are interested in participating in the brainstorming sessions. I figure you know a lot more than me about this

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 everyone, I have been using rsync for years to perform off-site backups, and have recently come up with a problem that is starting to hurt my head. I am at the point where I am starting to think that there is a method to achieve my desired outcome that I cannot see. First, a bit of history. I usually just set up a script that runs many rsync commands in sequence to perform the desired

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

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

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

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

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/

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

Subject should be enough: are hardlinks supported when rsyncing over ssh? I know that I cannot do anything with hardlinks if I'm using SSHFS over FUSE, I was wondering if rsync is plagued by the same problem. Matt

Hi List, I am very close to migrating from Cyrus to Dovecot (to be more precise from Mac OS X Server 10.5.8 to 10.6.4). The latter is reporting the dovecotd version to be 1.1.20apple0.5. All I have read about dovecot is extremely positive so I am exited to make the switch. BACKUP: BUT I would like to be sure that I can make a sound backup strategy. For Cyrus i used topicdesk's mailbfr (a

Just chiming in slightly off topic. As a first step if you are going to be backing up files to some media with a computer it would be a really good idea to ensure, that the hardware being used is not faulty. I am not saying that your hardware is faulty. However, it would be worth checking this somehow. Check the drive media for bad blocks, check that all the cables are working well. Ensure the