10

Use another backup solution. rdiff-backup got its last update in 2009. Also their website clearly states Many users seem to use rdiff-backup on MS Windows but this configuration is less well tested. That's not what you want.


5

It didn't kill rdiff-backup, it should have but its oom_score_adj is -1000. This is caused by a bug in sshd. The bug is fixed but wont be available until the next release which is openssh 6.5. sshd fails to set the oom_score_adj of new shells it creates back to 0 if you reload it, causing all child processes you spawn via SSH (so your bash shell and any ...


5

Assuming that the modification timestamps on your source files are legitimate (and are being updated when the files are modified) I think it makes sense for you to add the -t argument to synchronize times. Quoth the rsync man page: -t, --times This tells rsync to transfer modification times along with the files and update them on the remote system. Note ...


4

You're making the assumption that your backup is only ever going to be the same size as the source; if you only ever want that then just use cp or rsync, rdiff-backup doesn't seem the right tool for you. rdiff-backup maintains multiple backups (both full and incremental) so that you can rollback your data to a particular point in time instead of only being ...


3

You may want to go one layer down, using lvm snapshots and lvmsync. In this solution the snapshots will know what has been changed, no scanning is needed. The downside is that this solution doesn't understand files, it will just transfer blocks. The other solution would be a daemon that uses inotify and stores information which files have been changed. ...


2

The official github repository for rdiff-backup now has a script to do this: https://github.com/rdiff-backup/rdiff-backup/blob/master/src/rdiff-backup-delete The script referenced in the other answers does not seem to be available any more.


2

it appears somebody made a script doing the above steps https://www.eugenemakerspace.com/wiki/Sites/Rdiff-backup-delete I didn't test it, but choose a 'saver' way by deleting all files which are already gone voor 2 weeks, by running rdiff-backup --remove-older-than 2W host.net::/remote-dir more example http://www.nongnu.org/rdiff-backup/examples.html


2

I strongly suggest you to use rsnapshot, configuring it to retry multiple times if a connection problem is detected. For example, to enable the multi-tries approach with 3 max tries, please add the following line to your rsnapshot.conf file: rsync_numtries 3


2

The thing is that you want to backup 1 TB of data. This means that even after your first initial backup getting done, the incremental updates can be quite large, since all the tools you mentioned are working on the file system level, and transfer the whole new file if you changed it to the VPS. Also some of those tools are definitely not being made for ...


1

Per your post you are generating every hour unique sql dump YYYYMMDDHHMM.sql This is every time new file with unique file name. If you was changing files on the source (instead of generating new files) - then this feature would apply.Otherwise it looks at the source, discovers entirely new file YYYYMMDDHH+1MM.sql, it has no idea that on the destination file ...


1

The error message seems to be fully misleading. This is probably no memory issue at all. If I try to do an ssh to the user on the machine I get "This account is currently not available". The Ubuntu updated removed the shell entry for the backup user (which is a systems user and therefore it might not have been good idea to use this one in the first place .....


1

Have a look at Watchman. It's a tool created by Facebook for the purposes of watching file changes and triggering an action. Have it trigger a script which records what files changed before triggering an rsync.


1

I use duplicity instead of rdiff-backup but from my understanding your problem is here: My idea was to transfer data initially on physical media to remote server. After that transfer I synchronized the data by rync to make sure they are identical. Now I want to do intial rdiff-backup. Solution that works The simplest solution is to rdiff-backup to ...


Only top voted, non community-wiki answers of a minimum length are eligible