Re: [rdiff-backup-users] rdiff-backup fails, no gzipped file
On 12/08/2010 11:01 AM, Dominic Raferd wrote: On 07/12/2010 22:40, ~D wrote: On 12/07/2010 09:33 PM, Dominic Raferd wrote: On 07/12/10 18:54, ~D wrote: On 12/07/2010 05:09 PM, Dominic Raferd wrote: On 07/12/2010 14:42, ~D wrote: On 12/07/2010 03:26 PM, D. Kriesel wrote: Do you prevent a shutdown or reboot when rdiff-backup is running? How? Since rdiff-backup does not like backup interruptions (and therefore is not usable on slow or unreliable connections) I rdiff to a local repository on the server (the server usually doesn't reboot) and rsync the entire repository to the remote destination. My backup only runs when there is a internet connection. I use my laptop at home most of the time. I have to find a way to check wether rdiff-backup is running and to reboot after it shutdown. I can use htop of course, but I am not sure if rdiff-backup is runnin also local on my laptop or only on my server. Maybe there is a more advanced way to do this? You can test for running rdiff-backup locally thus: [ -n `ps -o pid --no-heading -C rdiff-backup` ] echo running || echo not running and you can query remote server thus: [ -n `ssh u...@remote.server ps -o pid --no-heading -C rdiff-backup 2/dev/null` ] echo running || echo not running . Ah Thanks! So it should be possible to make some script which checks if it's is running, if no, shutdown, if yes, wait 15 minuts and check again etc... right? ~D yes you could write a bash script and put it as a job in your crontab to run every 15 minutes, say... My mirror backup server (not my primary) is updated from my primary by a script which uses rdiff. The script runs on the primary and starts by waking up the mirror server (over the internet), then runs rsync, then after checking all is well, powers down the mirror. Hmm I just have a small NAS server (qnap 109), no 'mirror backup server' here. What do you mean by 'waking up the mirror server'? ~D ___ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
Re: [rdiff-backup-users] rdiff-backup fails, no gzipped file
yes you could write a bash script and put it as a job in your crontab to run every 15 minutes, say... My mirror backup server (not my primary) is updated from my primary by a script which uses rdiff. The script runs on the primary and starts by waking up the mirror server (over the internet), then runs rsync, then after checking all is well, powers down the mirror. Hmm I just have a small NAS server (qnap 109), no 'mirror backup server' here. What do you mean by 'waking up the mirror server'? ~D Wiki Well our main backup is done by all our machines to a server on our LAN using rdiff-backup - this I call the 'primary' backup server. Then each night this primary machine runs a script which uses rsync to copy its contents to an offsite machine, which therefore is maintained as a 'mirror' of the primary. The mirror machine is normally switched off. To switch it on, the script sends a 'magic packet' to the mirror machine, thus turning it on. Then the script runs rsync, and when that is over, it shuts the mirror machine down again. In a simple case, you can use the wakonlan utility to wake the remote machine: see http://gsd.di.uminho.pt/jpo/software/wakeonlan/. If it isn't already available on your machine and you use Debian or Ubuntu you can add it with apt-get I think. If the remote machine is behind another router then waking it may be more complicated: I have a special script to pass through Netgear DG834G router, for example (see http://www.timedicer.co.uk/dg834g.) Dominic ___ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
Re: [rdiff-backup-users] rdiff-backup fails, no gzipped file
On 12/11/2010 01:37 PM, Dominic Raferd wrote: yes you could write a bash script and put it as a job in your crontab to run every 15 minutes, say... My mirror backup server (not my primary) is updated from my primary by a script which uses rdiff. The script runs on the primary and starts by waking up the mirror server (over the internet), then runs rsync, then after checking all is well, powers down the mirror. Hmm I just have a small NAS server (qnap 109), no 'mirror backup server' here. What do you mean by 'waking up the mirror server'? ~D Wiki Well our main backup is done by all our machines to a server on our LAN using rdiff-backup - this I call the 'primary' backup server. Then each night this primary machine runs a script which uses rsync to copy its contents to an offsite machine, which therefore is maintained as a 'mirror' of the primary. The mirror machine is normally switched off. To switch it on, the script sends a 'magic packet' to the mirror machine, thus turning it on. Then the script runs rsync, and when that is over, it shuts the mirror machine down again. In a simple case, you can use the wakonlan utility to wake the remote machine: see http://gsd.di.uminho.pt/jpo/software/wakeonlan/. If it isn't already available on your machine and you use Debian or Ubuntu you can add it with apt-get I think. If the remote machine is behind another router then waking it may be more complicated: I have a special script to pass through Netgear DG834G router, for example (see http://www.timedicer.co.uk/dg834g.) Sounds like a professional setup, advanced and interesting, thanks for info. For now I keep it the way I have :) ~D ___ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
Re: [rdiff-backup-users] rdiff-backup fails, no gzipped file
On 12/08/2010 11:01 AM, Dominic Raferd wrote: On 07/12/2010 22:40, ~D wrote: On 12/07/2010 09:33 PM, Dominic Raferd wrote: On 07/12/10 18:54, ~D wrote: On 12/07/2010 05:09 PM, Dominic Raferd wrote: On 07/12/2010 14:42, ~D wrote: On 12/07/2010 03:26 PM, D. Kriesel wrote: Do you prevent a shutdown or reboot when rdiff-backup is running? How? Since rdiff-backup does not like backup interruptions (and therefore is not usable on slow or unreliable connections) I rdiff to a local repository on the server (the server usually doesn't reboot) and rsync the entire repository to the remote destination. My backup only runs when there is a internet connection. I use my laptop at home most of the time. I have to find a way to check wether rdiff-backup is running and to reboot after it shutdown. I can use htop of course, but I am not sure if rdiff-backup is runnin also local on my laptop or only on my server. Maybe there is a more advanced way to do this? You can test for running rdiff-backup locally thus: [ -n `ps -o pid --no-heading -C rdiff-backup` ] echo running || echo not running and you can query remote server thus: [ -n `ssh u...@remote.server ps -o pid --no-heading -C rdiff-backup 2/dev/null` ] echo running || echo not running . Ah Thanks! So it should be possible to make some script which checks if it's is running, if no, shutdown, if yes, wait 15 minuts and check again etc... right? ~D yes you could write a bash script and put it as a job in your crontab to run every 15 minutes, say... My mirror backup server (not my primary) is updated from my primary by a script which uses rdiff. The script runs on the primary and starts by waking up the mirror server (over the internet), then runs rsync, then after checking all is well, powers down the mirror. Works well with rsync - as David pointed out earlier, it is not a good idea to run rdiff-backup over an unstable connection. I was thinking about a script on my laptop for shutdown my machine, instead of running sudo shutdown -h now, run a script which only make the laptop shutdown when rdiff-backup is not runnning. I'm using fluxbox, so I'm used to shutdown my machine via terminal. ~D Here's a script 'auto-shutdown.sh' I use which shuts down a machine if there is no ssh connection and certain other programs are not running: if [ -z `netstat -t|grep :ssh.*ESTABLISHED$` ]; then [ `ps -A|grep -Ec cp$|rsync$|mv$|rm$` = 0 ] shutdown -h now fi add a line to /etc/crontab thus, to run the script hourly: 01 ** * * root/opt/auto-shutdown.sh I made this script to be sure it only shuts down when rdiff-backup isn't running: #!/bin/bash while true; do if pgrep rdiff-backup /dev/null; then sleep 10; else shutdown -h now; fi; done ___ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
Re: [rdiff-backup-users] rdiff-backup fails, no gzipped file
On 07/12/2010 22:40, ~D wrote: On 12/07/2010 09:33 PM, Dominic Raferd wrote: On 07/12/10 18:54, ~D wrote: On 12/07/2010 05:09 PM, Dominic Raferd wrote: On 07/12/2010 14:42, ~D wrote: On 12/07/2010 03:26 PM, D. Kriesel wrote: Do you prevent a shutdown or reboot when rdiff-backup is running? How? Since rdiff-backup does not like backup interruptions (and therefore is not usable on slow or unreliable connections) I rdiff to a local repository on the server (the server usually doesn't reboot) and rsync the entire repository to the remote destination. My backup only runs when there is a internet connection. I use my laptop at home most of the time. I have to find a way to check wether rdiff-backup is running and to reboot after it shutdown. I can use htop of course, but I am not sure if rdiff-backup is runnin also local on my laptop or only on my server. Maybe there is a more advanced way to do this? You can test for running rdiff-backup locally thus: [ -n `ps -o pid --no-heading -C rdiff-backup` ] echo running || echo not running and you can query remote server thus: [ -n `ssh u...@remote.server ps -o pid --no-heading -C rdiff-backup 2/dev/null` ] echo running || echo not running . Ah Thanks! So it should be possible to make some script which checks if it's is running, if no, shutdown, if yes, wait 15 minuts and check again etc... right? ~D yes you could write a bash script and put it as a job in your crontab to run every 15 minutes, say... My mirror backup server (not my primary) is updated from my primary by a script which uses rdiff. The script runs on the primary and starts by waking up the mirror server (over the internet), then runs rsync, then after checking all is well, powers down the mirror. Works well with rsync - as David pointed out earlier, it is not a good idea to run rdiff-backup over an unstable connection. I was thinking about a script on my laptop for shutdown my machine, instead of running sudo shutdown -h now, run a script which only make the laptop shutdown when rdiff-backup is not runnning. I'm using fluxbox, so I'm used to shutdown my machine via terminal. ~D Here's a script 'auto-shutdown.sh' I use which shuts down a machine if there is no ssh connection and certain other programs are not running: if [ -z `netstat -t|grep :ssh.*ESTABLISHED$` ]; then [ `ps -A|grep -Ec cp$|rsync$|mv$|rm$` = 0 ] shutdown -h now fi add a line to /etc/crontab thus, to run the script hourly: 01 ** * * root/opt/auto-shutdown.sh ___ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
Re: [rdiff-backup-users] rdiff-backup fails, no gzipped file
On 07/12/2010 14:42, ~D wrote: On 12/07/2010 03:26 PM, D. Kriesel wrote: Do you prevent a shutdown or reboot when rdiff-backup is running? How? Since rdiff-backup does not like backup interruptions (and therefore is not usable on slow or unreliable connections) I rdiff to a local repository on the server (the server usually doesn't reboot) and rsync the entire repository to the remote destination. My backup only runs when there is a internet connection. I use my laptop at home most of the time. I have to find a way to check wether rdiff-backup is running and to reboot after it shutdown. I can use htop of course, but I am not sure if rdiff-backup is runnin also local on my laptop or only on my server. Maybe there is a more advanced way to do this? You can test for running rdiff-backup locally thus: [ -n `ps -o pid --no-heading -C rdiff-backup` ] echo running || echo not running and you can query remote server thus: [ -n `ssh u...@remote.server ps -o pid --no-heading -C rdiff-backup 2/dev/null` ] echo running || echo not running ___ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
Re: [rdiff-backup-users] rdiff-backup fails, no gzipped file
On 12/07/2010 05:09 PM, Dominic Raferd wrote: On 07/12/2010 14:42, ~D wrote: On 12/07/2010 03:26 PM, D. Kriesel wrote: Do you prevent a shutdown or reboot when rdiff-backup is running? How? Since rdiff-backup does not like backup interruptions (and therefore is not usable on slow or unreliable connections) I rdiff to a local repository on the server (the server usually doesn't reboot) and rsync the entire repository to the remote destination. My backup only runs when there is a internet connection. I use my laptop at home most of the time. I have to find a way to check wether rdiff-backup is running and to reboot after it shutdown. I can use htop of course, but I am not sure if rdiff-backup is runnin also local on my laptop or only on my server. Maybe there is a more advanced way to do this? You can test for running rdiff-backup locally thus: [ -n `ps -o pid --no-heading -C rdiff-backup` ] echo running || echo not running and you can query remote server thus: [ -n `ssh u...@remote.server ps -o pid --no-heading -C rdiff-backup 2/dev/null` ] echo running || echo not running Ah Thanks! So it should be possible to make some script which checks if it's is running, if no, shutdown, if yes, wait 15 minuts and check again etc... right? ~D ___ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
Re: [rdiff-backup-users] rdiff-backup fails, no gzipped file
I'm having what seems like exactly the same problem. Any ideas how to fix this yet? /usr/local/bin/rdiff-backup -v8 --exclude-filelist /.cpignore --exclude- other-filesystems --remove-older-than 1M --force /2nd Using rdiff-backup version 1.3.3 Using mirror root directory /2nd Making directory /2nd/rdiff-backup-data/rdiff-backup.tmp.0 Touching /2nd/rdiff-backup-data/rdiff-backup.tmp.0/5-_ a.snapshot.gz Deleting /2nd/rdiff-backup-data/rdiff-backup.tmp.0/5-_ a.snapshot.gz Touching /2nd/rdiff-backup-data/rdiff-backup.tmp.0/uniá Deleting /2nd/rdiff-backup-data/rdiff-backup.tmp.0/uniá Touching /2nd/rdiff-backup-data/rdiff-backup.tmp.0/:\ Deleting /2nd/rdiff-backup-data/rdiff-backup.tmp.0/:\ Touching /2nd/rdiff-backup-data/rdiff-backup.tmp.0/A Deleting /2nd/rdiff-backup-data/rdiff-backup.tmp.0/A Touching /2nd/rdiff-backup-data/rdiff-backup.tmp.0/foo Deleting /2nd/rdiff-backup-data/rdiff-backup.tmp.0/foo Making directory /2nd/rdiff-backup-data/rdiff-backup.tmp.0/hl Touching /2nd/rdiff-backup-data/rdiff-backup.tmp.0/hardlinked_file1 Hard linking /2nd/rdiff-backup-data/rdiff-backup.tmp.0/hl/hardlinked_file2 to /2nd/rdiff-backup-data/rdiff-backup.tmp.0/hardlinked_file1 Unable to import module xattr. Extended attributes not supported on filesystem at /2nd/rdiff-backup-data/rdiff-backup.tmp.0 Unable to import module posix1e from pylibacl package. POSIX ACLs not supported on filesystem at /2nd/rdiff-backup-data/rdiff-backup.tmp.0 Unable to import win32security module. Windows ACLs not supported by filesystem at /2nd/rdiff-backup-data/rdiff-backup.tmp.0 Touching /2nd/rdiff-backup-data/rdiff-backup.tmp.0/dir_inc_check Deleting /2nd/rdiff-backup-data/rdiff-backup.tmp.0/dir_inc_check Touching /2nd/rdiff-backup-data/rdiff-backup.tmp.0/regfile Deleting /2nd/rdiff-backup-data/rdiff-backup.tmp.0/regfile Touching /2nd/rdiff-backup-data/rdiff-backup.tmp.0/high_perms_file Touching /2nd/rdiff-backup-data/rdiff-backup.tmp.0/high_perms_dir Deleting /2nd/rdiff-backup-data/rdiff-backup.tmp.0/high_perms_file Deleting /2nd/rdiff-backup-data/rdiff-backup.tmp.0/high_perms_dir Touching /2nd/rdiff-backup-data/rdiff-backup.tmp.0/symlinked_file1 Deleting /2nd/rdiff-backup-data/rdiff-backup.tmp.0/symlinked_file2 Deleting /2nd/rdiff-backup-data/rdiff-backup.tmp.0/symlinked_file1 Touching /2nd/rdiff-backup-data/rdiff-backup.tmp.0/foo Deleting /2nd/rdiff-backup-data/rdiff-backup.tmp.0/foo Deleting /2nd/rdiff-backup-data/rdiff-backup.tmp.0 Removing directory /2nd/rdiff-backup-data/rdiff-backup.tmp.0 - Detected abilities for /2nd/rdiff-backup-data (read/write) file system: Ownership changing On Hard linking On fsync() directories On Directory inc permissionsOn High-bit permissions On Symlink permissions On Extended filenames On Windows reserved filenames Off Access control lists Off Extended attributes Off Windows access control lists Off Case sensitivity On Escape DOS devices Off Escape trailing spaces Off Mac OS X style resource forksOff Mac OS X Finder information Off - Backup: escape_dos_devices = 0 Backup: escape_trailing_spaces = 0 No increments older than Sun Nov 7 14:28:14 2010 found, exiting. Cleaning up Previous backup seems to have failed, regressing destination now. Exception 'CRC check failed' raised of class 'exceptions.IOError': File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 306, in error_check_Main try: Main(arglist) File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 326, in Main take_action(rps) File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 282, in take_action elif action == backup: Backup(rps[0], rps[1]) File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 339, in Backup backup_final_init(rpout) File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 504, in backup_final_init checkdest_if_necessary(rpout) File /usr/local/lib/python2.4/site-packages/rdiff_backup/Main.py, line 938, in checkdest_if_necessary dest_rp.conn.regress.Regress(dest_rp) File /usr/local/lib/python2.4/site-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/local/lib/python2.4/site-packages/rdiff_backup/regress.py, line 197, in iterate_meta_rfs for raw_rf, metadata_rorp in collated: File /usr/local/lib/python2.4/site-packages/rdiff_backup/rorpiter.py, line 100, in Collate2Iters try: relem2 =
Re: [rdiff-backup-users] rdiff-backup fails, no gzipped file
On 07/12/10 18:54, ~D wrote: On 12/07/2010 05:09 PM, Dominic Raferd wrote: On 07/12/2010 14:42, ~D wrote: On 12/07/2010 03:26 PM, D. Kriesel wrote: Do you prevent a shutdown or reboot when rdiff-backup is running? How? Since rdiff-backup does not like backup interruptions (and therefore is not usable on slow or unreliable connections) I rdiff to a local repository on the server (the server usually doesn't reboot) and rsync the entire repository to the remote destination. My backup only runs when there is a internet connection. I use my laptop at home most of the time. I have to find a way to check wether rdiff-backup is running and to reboot after it shutdown. I can use htop of course, but I am not sure if rdiff-backup is runnin also local on my laptop or only on my server. Maybe there is a more advanced way to do this? You can test for running rdiff-backup locally thus: [ -n `ps -o pid --no-heading -C rdiff-backup` ] echo running || echo not running and you can query remote server thus: [ -n `ssh u...@remote.server ps -o pid --no-heading -C rdiff-backup 2/dev/null` ] echo running || echo not running . Ah Thanks! So it should be possible to make some script which checks if it's is running, if no, shutdown, if yes, wait 15 minuts and check again etc... right? ~D yes you could write a bash script and put it as a job in your crontab to run every 15 minutes, say... My mirror backup server (not my primary) is updated from my primary by a script which uses rdiff. The script runs on the primary and starts by waking up the mirror server (over the internet), then runs rsync, then after checking all is well, powers down the mirror. Works well with rsync - as David pointed out earlier, it is not a good idea to run rdiff-backup over an unstable connection. Dominic ___ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
Re: [rdiff-backup-users] rdiff-backup fails, no gzipped file
On 12/07/2010 09:33 PM, Dominic Raferd wrote: On 07/12/10 18:54, ~D wrote: On 12/07/2010 05:09 PM, Dominic Raferd wrote: On 07/12/2010 14:42, ~D wrote: On 12/07/2010 03:26 PM, D. Kriesel wrote: Do you prevent a shutdown or reboot when rdiff-backup is running? How? Since rdiff-backup does not like backup interruptions (and therefore is not usable on slow or unreliable connections) I rdiff to a local repository on the server (the server usually doesn't reboot) and rsync the entire repository to the remote destination. My backup only runs when there is a internet connection. I use my laptop at home most of the time. I have to find a way to check wether rdiff-backup is running and to reboot after it shutdown. I can use htop of course, but I am not sure if rdiff-backup is runnin also local on my laptop or only on my server. Maybe there is a more advanced way to do this? You can test for running rdiff-backup locally thus: [ -n `ps -o pid --no-heading -C rdiff-backup` ] echo running || echo not running and you can query remote server thus: [ -n `ssh u...@remote.server ps -o pid --no-heading -C rdiff-backup 2/dev/null` ] echo running || echo not running . Ah Thanks! So it should be possible to make some script which checks if it's is running, if no, shutdown, if yes, wait 15 minuts and check again etc... right? ~D yes you could write a bash script and put it as a job in your crontab to run every 15 minutes, say... My mirror backup server (not my primary) is updated from my primary by a script which uses rdiff. The script runs on the primary and starts by waking up the mirror server (over the internet), then runs rsync, then after checking all is well, powers down the mirror. Works well with rsync - as David pointed out earlier, it is not a good idea to run rdiff-backup over an unstable connection. I was thinking about a script on my laptop for shutdown my machine, instead of running sudo shutdown -h now, run a script which only make the laptop shutdown when rdiff-backup is not runnning. I'm using fluxbox, so I'm used to shutdown my machine via terminal. ~D ___ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
Re: [rdiff-backup-users] rdiff-backup fails, no gzipped file
See Andrew Ferguson's response regarding this error message here: http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/rdiff-backup-23/regression-fails-ioerror-not-a-gzipped-file-93222/ Andrew is the current maintainer of rdiff-backup so his word is law! What version of rdiff-backup are you using? 2.8-6 is not a valid version number, the current stable version is 1.2.8. Check with: rdiff-backup -V Dominic On 05/12/10 17:12, ~D wrote: Hi, I did setup a backup system like here, but then the other way around, backup my desktop to the server. http://www.howtoforge.com/linux_rdiff_backup I have two scripts on my server. The first one seems to run fine, the second not atm (till a week ago it went well, I didn't change a thing on a the server side) ... I have version 2.8-6 on both sides. On the server I installed the version of Debian testing on Lenny (Stable), which is on the server. I do run Debian testing on my desktop. See the messages below. Thanks in advance, ~D $ ./laptop_backup Previous backup seems to have failed, regressing destination now. * Exception 'Not a gzipped file' raised of class 'type 'exceptions.IOError'': ... File /usr/lib/python2.5/gzip.py, line 263, in _read self._read_gzip_header() File /usr/lib/python2.5/gzip.py, line 164, in _read_gzip_header raise IOError, 'Not a gzipped file' IOError: Not a gzipped file Fatal Error: Lost connection to the remote system ___ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
Re: [rdiff-backup-users] rdiff-backup fails, no gzipped file
On 12/05/2010 06:42 PM, Dominic Raferd wrote: rdiff-backup -V 1.2.8-6 ___ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
Re: [rdiff-backup-users] rdiff-backup fails, no gzipped file
On 12/05/2010 06:42 PM, Dominic Raferd wrote: See Andrew Ferguson's response regarding this error message here: http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/rdiff-backup-23/regression-fails-ioerror-not-a-gzipped-file-93222/ Andrew is the current maintainer of rdiff-backup so his word is law! It's not exactly clear which file I have to remove and how. Regards, ~D ___ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
