I am trying to exclude a "bulk" folder in each home directory from the backup. For this purpose, I have a line - /data/home/*/bulk in my exclude-filelist file. However, this doesn't seem to be recognised: Warning: file specification '/data/home/*/bulk' in filelist exclude-list-test.txt doesn't start with correct prefix /data/home/kay/bulk. Ignoring. Is there a way? BTW: is the format in general compatible with rsync's exclude-from? I have a working exclude list for that, where this wildcard expression works.

I would like to locally attach an NTFS volume to my unix (Ubuntu) machine, and copy (replicate) some unix directories to it, using rsync, in a way that the result is readable under Windows. I do not care about ownership and permissions. It would be nice if modification dates would be preserved. I only need directories and files (symbolic links would be nice, too; but not a problem if they cannot be copied). Two obvious problems are: case (in)sensitivity, and characters that are illegal in Windows filenames. For example, in Linux I can have two files "a" and "A"; I can copy them to the NTFS volume, but in Windows I will be able to access (at most?) one of them. But I am happy to ignore that problem. What I am interested about are illegal characters in Windows filenames, which are ,:,",/,\\,|,?, and * (well, actually also ascii 0-31, but I do not care about that. There might also be problems with files ending in a "."?). I would like rsync to automatically "rename", e.g., a file called "a:" to, say a(COLON), to end up with a legal name (and, ideally, translate a(COLON) back to a:) **Is this possible to have rsync automatically rename files to avoid characters forbidden in Windows?** - As far as I understand rsync can use **iconv** to do such tasks; is there a standard iconv module for windows-filenames? (I briefly looked into programming an own gconv module, but lacking C knowlege this seems too complicated). - I have been told that **rdiff-backup** can do some conversions like that, but the homepage just mentions something being done "automatically", and I am not sure whether a locally mounted NTFS vomlume would trigger a renaming in a reliable way? - I am aware that there is **fuse-posixovl**, but this seems an overkill for my purpose, and also it doesn't seem to be well documented (which characters will be translated in which way? Will all filenames be truncated to 8.3 or whatever? Can I avoid the additional files carrying owner/permission information, which I will not need, etc etc.) - I am aware that I could avoid all these problems by using, e.g., a **tar** file; but this is not what I want. (In particular, I would like in Windows to further replicate from the NTFS volume to another backup partition, copying only the changed files) - I am aware of the "**windows_names**" option when mounting NTFS; but this will prevent creating offending files, not rename them. **Update:** As it seems my question was not quite clear, let me give a more explicit example: For example, WINDOWS-1251 is of no use for me. iconv -f utf-8 -t WINDOWS-1251//TRANSLIT transforms 123 abc ABC äö &::*"\\|?][^/]*' # find stuff containing dot as last character (supposedly bad for windows) find $MYDIR -regex '.*\.' # find stuff that is identical case insensitive find $MYDIR -print0 | sort -z | uniq -diz | tr '\0' '\n' (the last line is from https://unix.stackexchange.com/questions/22870/case-insensitive-search-of-duplicate-file-names/ )

I have quite a lot of free space (and inodes) on this filesystem, but rdiff-backup apparently runs out of space. And hence my backups are not working at the moment :-(. Why? (I wonder how much space I should be reserving for this in future!) My rdiff-backup is version 1.2.8-7. My OS is Debian 9 "stretch". # df -h /d/backup Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_brick-lv_backup 139G 95G 38G 72% /d/backup # df -i /d/backup Filesystem Inodes IUsed IFree IUse% Mounted on /dev/mapper/vg_brick-lv_backup 9240576 413341 8827235 5% /d/backup # df -h Filesystem Size Used Avail Use% Mounted on udev 244M 0 244M 0% /dev tmpfs 51M 1.9M 49M 4% /run /dev/sda7 15G 4.1G 9.8G 30% / tmpfs 251M 0 251M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 251M 0 251M 0% /sys/fs/cgroup /dev/ubi0_0 462M 225M 233M 50% /d/ubi tmpfs 251M 4.0K 251M 1% /tmp /dev/mapper/vg_brick-lv_attic 44G 21G 21G 50% /d/attic /dev/mapper/vg_brick-lv_backup 139G 95G 38G 72% /d/backup /dev/sda6 2.0G 81M 1.8G 5% /boot /dev/mapper/vg_brick-lv_home 134G 91G 37G 71% /home /dev/sda10 9.8G 2.9G 6.9G 30% /d/xfer tmpfs 51M 0 51M 0% /run/user/1003 root@brick:/d/backup/jenkins-desktop# du -sh mike 5.7G mike root@brick:/d/backup/jenkins-desktop# du -sh ../jenkins-desktop.rdiff/mike 8.2G ../jenkins-desktop.rdiff/mike root@brick:/d/backup/jenkins-desktop# rdiff-backup mike ../jenkins-desktop.rdiff/mike Previous backup seems to have failed, regressing destination now. Exception '[Errno 28] No space left on device' raised of class '': File "/usr/lib/python2.7/dist-packages/rdiff_backup/robust.py", line 32, in check_common_error try: return function(*args) File "/usr/lib/python2.7/dist-packages/rdiff_backup/restore.py", line 468, in get_fp Rdiff.write_patched_fp(current_fp, delta_fp, new_fp) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Rdiff.py", line 73, in write_patched_fp rpath.copyfileobj(librsync.PatchedFile(basis_fp, delta_fp), out_fp) File "/usr/lib/python2.7/dist-packages/rdiff_backup/rpath.py", line 64, in copyfileobj outputfp.write(inbuf) Exception '[Errno 28] No space left on device' raised of class '': File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 304, in error_check_Main try: Main(arglist) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 324, in Main take_action(rps) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 280, in take_action elif action == "backup": Backup(rps, rps) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 337, in Backup backup_final_init(rpout) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 501, in backup_final_init checkdest_if_necessary(rpout) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 920, in checkdest_if_necessary dest_rp.conn.regress.Regress(dest_rp) File "/usr/lib/python2.7/dist-packages/rdiff_backup/regress.py", line 71, in Regress for rf in iterate_meta_rfs(mirror_rp, inc_rpath): ITR(rf.index, rf) File "/usr/lib/python2.7/dist-packages/rdiff_backup/rorpiter.py", line 281, in __call__ last_branch.fast_process(*args) File "/usr/lib/python2.7/dist-packages/rdiff_backup/regress.py", line 268, in fast_process if rf.metadata_rorp.isreg(): self.restore_orig_regfile(rf) File "/usr/lib/python2.7/dist-packages/rdiff_backup/regress.py", line 290, in restore_orig_regfile tf.write_from_fileobj(rf.get_restore_fp()) File "/usr/lib/python2.7/dist-packages/rdiff_backup/restore.py", line 488, in get_restore_fp return robust.check_common_error(error_handler, get_fp) File "/usr/lib/python2.7/dist-packages/rdiff_backup/robust.py", line 32, in check_common_error try: return function(*args) File "/usr/lib/python2.7/dist-packages/rdiff_backup/restore.py", line 468, in get_fp Rdiff.write_patched_fp(current_fp, delta_fp, new_fp) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Rdiff.py", line 73, in write_patched_fp rpath.copyfileobj(librsync.PatchedFile(basis_fp, delta_fp), out_fp) File "/usr/lib/python2.7/dist-packages/rdiff_backup/rpath.py", line 64, in copyfileobj outputfp.write(inbuf) Traceback (most recent call last): File "/usr/bin/rdiff-backup", line 30, in rdiff_backup.Main.error_check_Main(sys.argv[1:]) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 304, in error_check_Main File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 324, in Main take_action(rps) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 280, in take_action elif action == "backup": Backup(rps, rps) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 337, in Backup backup_final_init(rpout) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 501, in backup_final_init checkdest_if_necessary(rpout) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Main.py", line 920, in checkdest_if_necessary dest_rp.conn.regress.Regress(dest_rp) File "/usr/lib/python2.7/dist-packages/rdiff_backup/regress.py", line 71, in Regress for rf in iterate_meta_rfs(mirror_rp, inc_rpath): ITR(rf.index, rf) File "/usr/lib/python2.7/dist-packages/rdiff_backup/rorpiter.py", line 281, in __call__ last_branch.fast_process(*args) File "/usr/lib/python2.7/dist-packages/rdiff_backup/regress.py", line 268, in fast_process if rf.metadata_rorp.isreg(): self.restore_orig_regfile(rf) File "/usr/lib/python2.7/dist-packages/rdiff_backup/regress.py", line 290, in restore_orig_regfile tf.write_from_fileobj(rf.get_restore_fp()) File "/usr/lib/python2.7/dist-packages/rdiff_backup/restore.py", line 488, in get_restore_fp return robust.check_common_error(error_handler, get_fp) File "/usr/lib/python2.7/dist-packages/rdiff_backup/robust.py", line 32, in check_common_error try: return function(*args) File "/usr/lib/python2.7/dist-packages/rdiff_backup/restore.py", line 468, in get_fp Rdiff.write_patched_fp(current_fp, delta_fp, new_fp) File "/usr/lib/python2.7/dist-packages/rdiff_backup/Rdiff.py", line 73, in write_patched_fp rpath.copyfileobj(librsync.PatchedFile(basis_fp, delta_fp), out_fp) File "/usr/lib/python2.7/dist-packages/rdiff_backup/rpath.py", line 64, in copyfileobj outputfp.write(inbuf) IOError: [Errno 28] No space left on device

I am looking for a way to check if files were added/deleted/updated on a network shared HDD without spinning it up if possible. First I will start with my set up. I have an Asus Router (running Merlin) with a 3.0 usb port connected to a HDD (call it HDD1) shared using the build in Samba share. I then have a raspberry pi 3 (only with usb 2.0 ports) connected to the router through ethernet. The pi also has its own HDD (call it HDD2) connected to it. I have HDD2 as a backup of HDD1 using rdiff-backup and the HDD1 mounted to a folder within the pi. Using a cronjob, I have weekly backups made. I noticed though when calling rdiff-backup to do a check, it has to spin up both drives even if there is no change. May not be much but to strive for the most life long drive, I would like it to spin up less, especially if I have not touched the shared drive in say weeks. My initial thoughts were to use something like inotify to make the calls to rdiff-backup only when files change but reading the man page, it does not work over the network and has to do "polling" to check. Doesn't really solve the issue and the derivatives to inotify all seem to build off of it, which entails still not working over network. My second idea is to add some script to the router that makes some call to the pi when the hard drive has any file changes and then the pi would know to maybe later that night to do a rdiff-backup sync, but I feel that is over complicating the situation and I don't yet have a full plan of how I would do that. Third option is to have both hard drives connected to the pi, but then I am limited to 2.0 usb speeds. Does anyone have any idea's/suggestions?

I wrote my backup script to automatically combine two external drives into one with mergerfs so I could use the whole thing as a destination directory for rdiff-backup. However, when I tried to run it recently I get the error: fuse: unknown option `threads=2' The "threads" option appears in the man pages so I'm not sure what I'm missing here. For reference this is my current mergerfs command that's failing: mergerfs -o use_ino,category.create=mfs,threads=2 ...

I used the following rdiff-backup command to backup my home directory onto a mounted drive /run/media/me/bku. rdiff-backup -v 9 --force --include /home/me/ --exclude '**' / /run/media/me/bku At the destination there were other directories and files present: ls /run/media/me/bku dir1 dir2 Upon completion, I noticed that all the files I had at the destination have been removed entirely. 2020-11-04 16:19:01.560098 -0500 Removing directory /run/media/me/bku/dir1 Is this a normal behavior for rdiff-backup? Also, is there a way to recover those deleted files?

My latest backup attempt with rdiff-backup failed due to "[Errno 28] No space left on device". And it's true, according to du there are 0 bytes available on the backup device. When I now try to revert the directory to the state before the unsuccessful session by simply starting another backup attempt, I also get [Errno 28]. The next idea I had was to get rid of some old backup increments to gain some fresh disk space. To see the list of backup increments, I invoked rdiff-backup -l mirror_dir which results in Fatal Error: Previous backup to mirror_dir seems to have failed. Rerun rdiff-backup with --check-destination-dir option to revert directory to state before unsuccessful session. Then I did what the message told me and ran rdiff-backup --check-destination-dir mirror_dir which again gives me the now already famous [Errno 28]. It seems like I am in a dead end, where I cannot do *anything* anymore, not even free some disk space which action seems to be the only solution to this problem. Is there a way out of this situation?

I installed rsnapshot and configured it to make backup every hour. But the issue is all backups that are made not working. Let me explain to you, I made 3 backups hourly.0, hourly.1 and hourly.2. - hourly.0 : there are 15 files - hourly.1 : there are 14 files (I removed one file) - hourly.2 : there are 15 files (I recreated an other file) The problem is when I went to backup of hourly.1 I found the file that I created in hourly.2, so I tried to remove it again but unfortunately the file that I removed ended up being removed in all my folders (hourly.0, hourly.1 and hourly.3), which means the all of those folders are just a symbolic links not more. This is my file configuration: #rsnapshot config_version 1.2 snapshot_root /var/Majjane-Save/ cmd_cp /bin/cp cmd_rm /bin/rm cmd_rsync /usr/bin/rsync cmd_logger /usr/bin/logger cmd_du /usr/bin/du cmd_rsnapshot_diff /usr/bin/rsnapshot-diff retain hourly 24 verbose 2 loglevel 3 logfile /var/log/rsnapshot.log lockfile /var/run/rsnapshot.pid exclude /var/www/clients/ exclude /var/www/apps/ backup /var/www/ localhost/var/Majjane-Save/ Note : i solved the issue , in the fact it was about the symbolic links. i were run the backup just the symbolic links no more. now its work well.

I'm running the following command: rdiff-backup --remote-schema '%s' 'sudo /usr/bin/rdiff-backup --server \ --restrict-read-only /'::/etc /var/backups/hosts/derp It's backing up /etc from localhost and putting it in /var/backups/hosts/derp just fine. I have no idea how to get this to run and pull the files from another host.

After upgrading my rdiff backup rdiff-backup --version rdiff-backup 1.2.8 i get the following error message: Exception 'Found too many current_mirror incs!' raised of class '': **How would i find out which directory is having the issue?**

I'm having trouble installing rdiff backup on Centos 7. Every google search is telling to get this https://dl.fedoraproject.org/pub/epel/7/x86_64/r/rdiff-backup-1.2.8-11.el7.x86_64.rpm one way or the other but it yields a 404. So I tried installing development tools and building it from source. python --version Python 2.7.5 python setup.py install running install running build running build_py creating build creating build/lib.linux-x86_64-2.7 creating build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/backup.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/robust.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/iterfile.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/user_group.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/lazy.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/increment.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/log.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/FilenameMapping.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/fs_abilities.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/regress.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/statistics.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/rpath.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/manage.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/metadata.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/TempFile.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/Rdiff.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/restore.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/static.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/Main.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/Time.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/hash.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/eas_acls.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/rorpiter.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/Hardlink.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/Globals.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/SetConnections.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/selection.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/Security.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/connection.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/__init__.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/librsync.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/win_acls.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/compare.py -> build/lib.linux-x86_64-2.7/rdiff_backup copying rdiff_backup/longname.py -> build/lib.linux-x86_64-2.7/rdiff_backup running build_ext building 'rdiff_backup.C' extension creating build/temp.linux-x86_64-2.7 gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python2.7 -c cmodule.c -o build/temp.linux-x86_64-2.7/cmodule.o cmodule.c:24:20: fatal error: Python.h: No such file or directory #include ^ compilation terminated. error: command 'gcc' failed with exit status 1 The build fails. No idea if it has something to do with 2009 or something else, but man this is annoying. This worked a few months ago on my old box.

I'm testing rdiff-backup and I thought maybe someone could help me out. 1: Why is my backup smaller than the original folder? In my remote server I have 36G and in my backup server it's only 29G. 2: I was trying to restore some files but I got this error: Exception '[Errno 13] Permission denied: '/home/brt/backups2/rdiff-backup.tmp.0'' raised of class '': File "/usr/local/lib/python2.7/site-packages/rdiff_backup/Main.py", line 304, in error_check_Main try: Main(arglist) File "/usr/local/lib/python2.7/site-packages/rdiff_backup/Main.py", line 324, in Main take_action(rps) File "/usr/local/lib/python2.7/site-packages/rdiff_backup/Main.py", line 290, in take_action elif action == "restore-as-of": Restore(rps, rps, 1) File "/usr/local/lib/python2.7/site-packages/rdiff_backup/Main.py", line 554, in Restore dest_rp.conn.fs_abilities.restore_set_globals(dest_rp) File "/usr/local/lib/python2.7/site-packages/rdiff_backup/connection.py", line 450, in __call__ return apply(self.connection.reval, (self.name,) + args) File "/usr/local/lib/python2.7/site-packages/rdiff_backup/connection.py", line 370, in reval if isinstance(result, Exception): raise result Traceback (most recent call last): File "/usr/local/bin/rdiff-backup", line 30, in rdiff_backup.Main.error_check_Main(sys.argv[1:]) File "/usr/local/lib/python2.7/site-packages/rdiff_backup/Main.py", line 304, in error_check_Main try: Main(arglist) File "/usr/local/lib/python2.7/site-packages/rdiff_backup/Main.py", line 324, in Main take_action(rps) File "/usr/local/lib/python2.7/site-packages/rdiff_backup/Main.py", line 290, in take_action elif action == "restore-as-of": Restore(rps, rps, 1) File "/usr/local/lib/python2.7/site-packages/rdiff_backup/Main.py", line 554, in Restore dest_rp.conn.fs_abilities.restore_set_globals(dest_rp) File "/usr/local/lib/python2.7/site-packages/rdiff_backup/connection.py", line 450, in __call__ return apply(self.connection.reval, (self.name,) + args) File "/usr/local/lib/python2.7/site-packages/rdiff_backup/connection.py", line 370, in reval if isinstance(result, Exception): raise result OSError: [Errno 13] Permission denied: '/home/brt/backups2/rdiff-backup.tmp.0' Fatal Error: Lost connection to the remote system What happened and how can I fix it? Thank you.

I have a xfs filesystem with many small and a couple very large files (~100GB), its on a lvm2 volume. I want to do incremental backups from it. Is there any computational overhead when using a tool like for example duplicity/rdiff versus xfsdump for the backups ? In short will xfsdump reuse some fs internal information to significantly reduce the work it has to do to get the deltas or can I as well use something with nice features without significant performance penalties ?

#Objective# I'm trying to execute the following command in my Python script: > rdiff-backup --terminal-verbosity=5 --remote-schema "ssh %s -p1019 -i > C:/Users/Adam/.ssh/private-passphrase rdiff-backup --server" > C:/Users/Adam/Desktop pi@192.168.0.125::/media/exthdd1/backup My source directory is from a Windows OS and my target directory is a Debian based system. #Problem# I get this output: `Using rdiff-backup version 1.2.8 Executing ssh pi@192.168.0.125 -p1019 -i C:/Users/Adam/.ssh/private-passphrase r diff-backup --server Enter passphrase for key 'C:/Users/Adam/.ssh/private-passphrase': Found interrupted initial backup. Removing... Hardlinks disabled by default on Windows Unable to import module xattr. Extended attributes not supported on filesystem at C:/Users/Adam/Desktop Unable to import module posix1e from pylibacl package. POSIX ACLs not supported on filesystem at C:/Users/Adam/Desktop escape_dos_devices not required by filesystem at C:/Users/Adam/Desktop ----------------------------------------------------------------- Detected abilities for source (read only) file system: Access control lists Off Extended attributes Off Windows access control lists On Case sensitivity Off Escape DOS devices Off Escape trailing spaces Off Mac OS X style resource forks Off Mac OS X Finder information Off ----------------------------------------------------------------- POSIX ACLs not supported by filesystem at /media/exthdd1/backup/rdiff-backup-dat a/rdiff-backup.tmp.0 Unable to import win32security module. Windows ACLs not supported by filesystem at /media/exthdd1/backup/rdiff-backup-data/rdiff-bac kup.tmp.0 escape_dos_devices not required by filesystem at /media/exthdd1/backup/rdiff-bac kup-data/rdiff-backup.tmp.0 ----------------------------------------------------------------- Detected abilities for destination (read/write) file system: Ownership changing Off Hard linking On fsync() directories On Directory inc permissions Off High-bit permissions Off Symlink permissions Off Extended filenames On Windows reserved filenames Off Access control lists Off Extended attributes On Windows access control lists Off Case sensitivity On Escape DOS devices Off Escape trailing spaces Off Mac OS X style resource forks Off Mac OS X Finder information Off ----------------------------------------------------------------- Backup: must_escape_dos_devices = 0 Symbolic links excluded by default on Windows Starting mirror C:/Users/Adam/Desktop to /media/exthdd1/backup Processing changed file . Processing changed file Git Shell.lnk Sending back exception [Errno 1] Operation not permitted: '/media/exthdd1/backup /rdiff-backup.tmp.4' of type : E File "/usr/lib/python2.7/dist-packages/rdiff_backup/connection.py", line 335, in answer_requestxception '[Errno 1] Operation not permitted: '/media/exthdd1/b result = apply(eval(request.function_string), argument_list)Traceback (most recent call last):up\Main.pyc", line 304, in error_check_Main File "rdiff_backup\Main.pyc", line 324, in Main File "rdiff-backup", line 30, in n take_action File "/usr/lib/python2.7/dist-packages/rdiff_backup/backup.py", line 232, in p atchle "rdiff_backup\backup.pyc", line 38, in Mirror File "rdiff_backup\Main.pyc", line 304, in error_check_Main ITR(diff.index, diff)ection.pyc", line 370, in reval File "/usr/lib/python2.7/dist-packages/rdiff_backup/rorpiter.py", line 281, in __call__ File "rdiff_backup\Main.pyc", line 324, in Main last_branch.fast_process(*args) File "rdiff_backup\Main.pyc", line 280, in File "/usr/lib/python2.7/dist-packages/rdiff_backup/backup.py", line 529, in f ast_process File "rdiff_backup\Main.pyc", line 346, in Backup if self.patch_to_temp(mirror_rp, diff_rorp, tf): File "/usr/lib/python2.7/dist-packages/rdiff_backup/backup.py", line 559, in p atch_to_temp File "rdiff_backup\connection.pyc", line 450, in __call__ rpath.copy_attribs(diff_rorp, new)OSError0, in reval File "/usr/lib/python2.7/dist-packages/rdiff_backup/rpath.py", line 189, in co py_attribs: rpout.chmod(rpin.getperms())Errno 1] Operation not permitted: '/media/exthdd File "/usr/lib/python2.7/dist-packages/rdiff_backup/rpath.py", line 927, in ch mod self.conn.os.chmod(self.path, permissions & Globals.permission_mask) Fatal Error: Lost connection to the remote system` #Attempts to resolve# - I thought it was permissions but my target directory is 777 - I've tried running CMD as admin - Adding my Windows user account to the user group Users - Got half way through setting up Cygwin to have sshd service but kept getting "Error 1053: Could not start service" so gave up. I tried to do this because I thought SSH aliases would simplify the command and to see if it got me anywhere, something about the placeholder %s makes me feel sick so I thought if I could get around using it then I might get somewhere. Does anyone think SSH aliases is even worth still pursuing?

I have a server web based Linux and i want to make backup every hour using rsnapshot. this is my rsnapshot file configuration : config_version 1.2 snapshot_root /var/Majjane-Save/ cmd_cp /bin/cp cmd_rm /bin/rm cmd_rsync /usr/bin/rsync cmd_logger /usr/bin/logger cmd_du /usr/bin/du cmd_rsnapshot_diff /usr/bin/rsnapshot-diff retain hourly 24 verbose 2 loglevel 3 logfile /var/log/rsnapshot.log lockfile /var/run/rsnapshot.pid exclude /var/www/clients/ exclude /var/www/apps/ backup /var/www/ localhost/var/Majjane-Save/ The problem is when i make 3 backups for example : * hourly.0 : the folder backuped has 15 files * hourly.1 : the folder backuped has 14 files ( i removed one file from the folder /var/www/ ) * hourly.2 : the folder backuped has 15 files ( i created an other file different from the first one) when i try to restore the first removed file from my backup hourly.0 i didn't find it, you can say that all of hourly.x folders are just a symbolic links no more.

I am currently doing a backup of my system on an external hard disk using rdiff-backup. This kind of backup is good when the disk dies. However, I was also wondering if I can extend this method to do a 3 way backup? For example, instead of just backing up to one hard disk, I can back up to two hard disks. And everytime, before doing the backup, the program checks for integrity of files by comparing all the three copies, and then chooses the version which agrees on at least two hard disks. This way, I can take care of on disk corruption of my files too. Is it possible with rdiff-backup? If not, does there exist some similar kind of utility?

I use rdiff-backup for my backups. My disk runs out of space. I would like to clean some rdiff-backup data by removing either: * the backup data of small files with a large number of different versions * the backup data of very large files which have been deleted In order to free space, how to identify those files?

While _creating_ incremental backups is relatively simple (and can be automated, e.g. via [rdiff-backup](http://www.nongnu.org/rdiff-backup/)) , in order to access a specific state of a file one first has to manually restore the backup, which is both not-simple and tedious if you need to browse through multiple states. So is there a [FUSE](https://en.wikipedia.org/wiki/Filesystem_in_Userspace "filesystem in userspace, so asking for a FUSE filesystem would be redundant") which allows to transparently access previous states e.g. via some filename@2013-01-23 (the backup made at that date, if existing) or filename@{-2} (two backups ago) syntax while the current and backup files reside on arbitrary filesystems (including remote ones, e.g. nfs backups while the current state is on a local ext3)?

I've been reading about using rsync and rdiff-backup to make incremental backups of my entire Linux system. I am planning to practise that by setting up a Linux system, making some changes to it, erasing everything and restoring the system (all with the convenience of doing it in a virtual machine). But I want to clarify a few things before taking the plunge: 1. How do I get fine control about what gets included in and excluded from the backup? i.e. by default would everything (including invisible "." files, trash, etc.) be backed up? If so, how can I exclude some of them? 2. The rdiff-backup tutorial tells you how to retrieve a file from an arbitrary time in the past (as long as you still have the backup). What if I want to restore the complete system on a new computer? How do I do that? 3. Suppose I make backups of my system on machine A. A few years later I buy a new computer B, and want to restore my system from the backup of machine A. Since the hardware might be totally different, will my new system work when I try to start it up after the restore? How can I ensure a smooth restore onto a new machine? Thanks for your answers.