Re: [rdiff-backup-users] restore do not work
Hi Dmitriy Try with rdiff-backup 1.2.4, version 1.2.3 is broken on restoring. (1.2.4 also seems to have some problems with restoring but you should try it first...) Dominic DK wrote: Hi, It looks like an ssh error because locally restore is working ssh setup systems ate Cent OS 5.2 Any ideas? thx, Dmitriy testbac...@nagios-monitor ~]$ rdiff-backup -v9 -r now r...@wcmisdlin01::/files/test22/ test1 Mon Jan 5 14:52:50 2009 Using rdiff-backup version 1.2.3... ___ 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] Backing up remote db's
Hi Peter, on Mon, 05 Jan 2009 17:43:33 +1100 you wrote: I am running rdiff-backup on a linux box and have a mysql database server running on another windows box. Can I set up a rdiff-backup config to log in remotely to the mysql on the other box and do a dump of all databases so it gets backed up? I suppose I could run rdiff on the windows box but my linux one is a more stable runner. If I can, how do I configure a username and password so it can connect? Peter rdiff-backup itself does not do specific Mysql-tasks, but I think AutoMySQLBackup does exactly what you need. If you remove in the script the appended timestamp-string from the created filename, you can also benefit from storing only the actual changes with rdiff-backup, not full dumps each time. It supports remote backups from Windows MySQL to Linux (script runs on Linux-server e.g. via cron) or other way 'round (requires CygWin) and also doing local backups on a host (for Windows CygWin is required), e.g. for later fetching via rsync. ## AutoMySQLBackup Script Features ## * Backup mutiple MySQL databases with one script. (Now able to backup ALL databases on a server easily. no longer need to specify each database seperately) * Backup all databases to a single backup file or to a seperate directory and file for each database. * Automatically compress the backup files to save disk space using either gzip or bzip2 compression. * Can backup remote MySQL servers to a central server. * Runs automatically using cron or can be run manually. * Can e-mail the backup log to any specified e-mail address instead of root. (Great for hosted websites and databases). * Can email the compressed database backup files to the specified email address. * Can specify maximun size backup to email. * Can be set to run PRE and POST backup commands. - to interface with rdiff-backup nicely * Choose which day of the week to run weekly backups. Full feature description: http://members.lycos.co.uk/wipe_out/automysqlbackup/ Project site: http://sourceforge.net/projects/automysqlbackup/ Cheers, Oliver ___ 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
[rdiff-backup-users] Graphical User Interfaces (GUIs) for rdiff-backup - Later as Wiki-Entry - Request for comments now
Hi *, most will use rdiff-backup via commandline, but some users don't feel comfortable with/are used to graphical interfaces, so the below list might help. Especially pyBackPack looks interesting, although it is not found in a Google-search for rdiff-backup GUI. ## pyBackPack - sponsored 2005 Google Summer of Code project ## ## PythonGTK2+ GUI for RDB ## http://andrewprice.me.uk/projects/pybackpack/ http://projects.sucs.org/projects/pybackpack/ http://andrewprice.me.uk/weblog/all/pybackpack Should work in CygWin under windows, too: http://lists.sucs.org/pipermail/pybackpack/2007-May/33.html A graphical backup utility based on rdiff-backup. The latest version is 0.5.6, released on September 25 2008. ## FlyBack ## http://code.google.com/p/flyback/ http://code.google.com/p/flyback/downloads/list + PyGTK, so mostly cross-platform - only several releases in Nov 2007 ## rdiffweb ## http://www.rdiffweb.org/wiki/index.php?title=Main_Page + requires only Python, PySQLite, CherryPy (for local webserver) ## rdiffbackupweb ## http://rdiffbackupweb.sourceforge.net/ - requires php + mysql backend ## Keep ## - only working in Linux KDE: http://jr.falleri.free.fr/keep/wiki/Home http://jr.falleri.free.fr/keep/wiki/Screenshots --- If I have forgotten other working + maintained GUIs, please post to the list, so I can create a RDB Wiki-Page for GUIs. Since I do not require a GUI, I haven't tested any of the above, so feedback on this is also welcome. Cheers, Oliver ___ 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
[rdiff-backup-users] --override-chars-to-quote bug fixed and default behaviour change
On 2009-01-05 Oliver Mulatz wrote:
Another issue: there's a bug (RDB aborts) in '--override-chars-to-quote'
functionality, (I require for cross-platform filesystem compatibility).
It hits each time --override-chars-to-quote is used, even with empty
set ('') for keeping capital chars from being escaped.
The exact error including trace was also posted to the ML on Oct'08 by EliW:
http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/rdiff-backup-23/probleme-with-rdiff-on-smbfs-92963/#287692
I fixed it, but would like to go deeper.
Now is a good time to discuss a default behaviour change, since the
'--override-char-to-quote' (= OCTQ) option *never* worked, so users
will not be surprised and no scripts need to be changed.
Currently, and what I have read on the mailing-list, the OCTQ-option must
be provided ON EACH commandline issued when used initially to create a backup
mirror, also for restores. This is non-intuitive IMO, a more sensible approach
would be:
1. if no commandline OCTQ option is provided when a backup mirror is created,
use FS auto-detected chars to quote (already doing so now)
2. if a backup mirror was started with OCTQ, this is assumed valid unless
otherwise notice/overridden (default behaviour needs to be changed for this,
but breaks nothing AFAICT)
3. if the OCTQ really must be changed after creation of backup mirror with
initial OCTQ set, coupling with '--force' option would be naturally most
intuitive, otherwise shows error-message hinting about this
= so anybody knows this is a potential 'risky/deep' change, along the line
of overwriting already existing directories when doing a RDB restore, ...
This has the benefit of being more intuitive, it's no problem to forget
about the required char-set once a mirror is set up and not required
for each action/restore.
When there are no objections to this change, I create the patches for this
against the 1.3 development-release.
Cheers,
Oliver
___
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] Graphical User Interfaces (GUIs) for rdiff-backup - Later as Wiki-Entry - Request for comments now
On Tue, Jan 6, 2009 at 6:58 AM, Oliver Mulatz sira...@arcor.de wrote: Hi *, most will use rdiff-backup via commandline, but some users don't feel comfortable with/are used to graphical interfaces, so the below list might help. Especially pyBackPack looks interesting, although it is not found in a Google-search for rdiff-backup GUI. ## pyBackPack - sponsored 2005 Google Summer of Code project ## ## PythonGTK2+ GUI for RDB ## http://andrewprice.me.uk/projects/pybackpack/ http://projects.sucs.org/projects/pybackpack/ http://andrewprice.me.uk/weblog/all/pybackpack Should work in CygWin under windows, too: http://lists.sucs.org/pipermail/pybackpack/2007-May/33.html A graphical backup utility based on rdiff-backup. The latest version is 0.5.6, released on September 25 2008. ## FlyBack ## http://code.google.com/p/flyback/ http://code.google.com/p/flyback/downloads/list + PyGTK, so mostly cross-platform - only several releases in Nov 2007 ## rdiffweb ## http://www.rdiffweb.org/wiki/index.php?title=Main_Page + requires only Python, PySQLite, CherryPy (for local webserver) ## rdiffbackupweb ## http://rdiffbackupweb.sourceforge.net/ - requires php + mysql backend ## Keep ## - only working in Linux KDE: http://jr.falleri.free.fr/keep/wiki/Home http://jr.falleri.free.fr/keep/wiki/Screenshots --- If I have forgotten other working + maintained GUIs, please post to the list, so I can create a RDB Wiki-Page for GUIs. Since I do not require a GUI, I haven't tested any of the above, so feedback on this is also welcome. Cheers, Oliver Oliver, I have not used any of the GUI tools either. Personally I run rdiff-backup on a few different fileservers. It would be nice to give the users a HTTP interface to the backups, etc. So if you do document whats out there, please organize them by user interface: X / KDE / HTTP / Windows native / etc. Thanks Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence Technology http://www.norcrossgroup.com ___ 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] Graphical User Interfaces (GUIs) forrdiff-backup - Later as Wiki-Entry - Request for comments now
I've had pretty good success with RdiffWeb. It's quite easy to set up and fast. The newest version (0.6.3) is able to use SSL as well for secure connections. I cannot comment on the others however. Lucas Burdick -Original Message- From: rdiff-backup-users-bounces+lucas=progressive-sealing@nongnu.org [mailto:rdiff-backup-users-bounces+lucas=progressive-sealing@nongnu.org] On Behalf Of Greg Freemyer Sent: January-06-09 9:57 AM To: Oliver Mulatz Cc: rdiff-backup-users@nongnu.org Subject: Re: [rdiff-backup-users] Graphical User Interfaces (GUIs) forrdiff-backup - Later as Wiki-Entry - Request for comments now On Tue, Jan 6, 2009 at 6:58 AM, Oliver Mulatz sira...@arcor.de wrote: Hi *, most will use rdiff-backup via commandline, but some users don't feel comfortable with/are used to graphical interfaces, so the below list might help. Especially pyBackPack looks interesting, although it is not found in a Google-search for rdiff-backup GUI. ## pyBackPack - sponsored 2005 Google Summer of Code project ## ## PythonGTK2+ GUI for RDB ## http://andrewprice.me.uk/projects/pybackpack/ http://projects.sucs.org/projects/pybackpack/ http://andrewprice.me.uk/weblog/all/pybackpack Should work in CygWin under windows, too: http://lists.sucs.org/pipermail/pybackpack/2007-May/33.html A graphical backup utility based on rdiff-backup. The latest version is 0.5.6, released on September 25 2008. ## FlyBack ## http://code.google.com/p/flyback/ http://code.google.com/p/flyback/downloads/list + PyGTK, so mostly cross-platform - only several releases in Nov 2007 ## rdiffweb ## http://www.rdiffweb.org/wiki/index.php?title=Main_Page + requires only Python, PySQLite, CherryPy (for local webserver) ## rdiffbackupweb ## http://rdiffbackupweb.sourceforge.net/ - requires php + mysql backend ## Keep ## - only working in Linux KDE: http://jr.falleri.free.fr/keep/wiki/Home http://jr.falleri.free.fr/keep/wiki/Screenshots --- If I have forgotten other working + maintained GUIs, please post to the list, so I can create a RDB Wiki-Page for GUIs. Since I do not require a GUI, I haven't tested any of the above, so feedback on this is also welcome. Cheers, Oliver Oliver, I have not used any of the GUI tools either. Personally I run rdiff-backup on a few different fileservers. It would be nice to give the users a HTTP interface to the backups, etc. So if you do document whats out there, please organize them by user interface: X / KDE / HTTP / Windows native / etc. Thanks Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence Technology http://www.norcrossgroup.com ___ 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 ___ 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
[rdiff-backup-users] Re: Graphical User Interfaces (GUIs) for rdiff-backup - Later as Wiki-Entry - Request for comments now
Hi, On 06/01/09 11:58, Oliver Mulatz wrote: Especially pyBackPack looks interesting, although it is not found in a Google-search for rdiff-backup GUI. I'm the maintainer of pybackpack and I follow the rdiff-backup list so thanks for mentioning it. I'd like to clarify some points: ## PythonGTK2+ GUI for RDB ## It requires some GNOME specific widgets to work at the moment. I'm planning on stripping these and using GTK+ widgets only. Should work in CygWin under windows, too: It should do in theory but I've yet to hear from anyone who has managed it (and I don't have a Windows machine to test it on), so it probably doesn't :-) Also, I'm not sure if the switch has happened but Sivan Greenberg mentioned something about switching HUBackup to use rdiff-backup: http://sivang.blogspot.com/2007/10/hubackup-and-rdiff-backup-or-how-i.html There are some things I'd like to see changed in rdiff-backup to make writing a UI for it easier (e.g. progress callbacks, no sys.exit() calls). I'll probably start a new thread or submit some patches about these points when I've done more research into them. My thanks go to Andrew Ferguson and the other contributors for keeping rdiff-backup ticking. It's much appreciated. Cheers, -- Andy Price ___ 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] long filename error
On Jan 4, 2009, at 4:11 AM, Ryan wrote: Under Windows XP with version 1.3.0, if I try to back up the following file, C:\important stuff \111 I get: Traceback (most recent call last): File rdiff-backup, line 30, in module File rdiff_backup\Main.pyc, line 309, in error_check_Main File rdiff_backup\robust.pyc, line 77, in is_routine_fatal NameError: global name 'e' is not defined Hi Ryan, Thanks for reporting this error. The error message is unhelpful because of a typo. I am fixing that in the next release. The next release will also allow rdiff-backup to ignore (some? all?) of the errors caused by too-long filenames on Windows. It does not yet backup such files. See this thread on the mailing list for the explanation: http://lists.nongnu.org/archive/html/rdiff-backup-users/2008-10/msg00117.html Basically, rdiff-backup will need to move to Unicode file handling and prepend ?\\ to each Windows path in order to support long paths filenames ( 255 characters, or so). That is something for the development branch, possibly even for the next one. Andrew ___ 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] Error on remote restore (1.2.3)
On Jan 5, 2009, at 6:06 AM, Dominic wrote:
... but I do get an error with rdiff-backup 1.2.4 when running from
a *Windows* client (to Linux-based rdiff-backup server) thus:
C:\rdiff-backup -r 0D dominic-pcchi...@192.168.100.125::archives/
mydocs/myfile.docx myfile.docx
Traceback (most recent call last):
File rdiff-backup, line 30, in module
File rdiff_backup\Main.pyc, line 307, in error_check_Main
File rdiff_backup\robust.pyc, line 77, in is_routine_fatal
NameError: global name 'e' is not defined
Is this the known bug with Windows escaping (Savannah #25041) or
something different? If it is, is the only solution to move to
1.3.0? (Strangely the last line of my error messages is the same as
Ryan reported in 1.3.0 ('long filename error' thread))
Hi Dominic,
Due to the typo in robust.py on line 77 (e.errno should be
exc.errno) we don't know what error is causing your restore to fail.
I will release 1.2.5 shortly so that we see better error messages.
After that, feel free to try again, and we can see what went wrong.
Andrew___
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] long filename error
I hope you at least give a warning so people will know the file was not backed up. on Tuesday 01/06/2009 Andrew Ferguson(adfergu...@gmail.com) wrote On Jan 4, 2009, at 4:11 AM, Ryan wrote: Under Windows XP with version 1.3.0, if I try to back up the following file, C:\important stuff \111 I get: Traceback (most recent call last): File rdiff-backup, line 30, in module File rdiff_backup\Main.pyc, line 309, in error_check_Main File rdiff_backup\robust.pyc, line 77, in is_routine_fatal NameError: global name 'e' is not defined Hi Ryan, Thanks for reporting this error. The error message is unhelpful because of a typo. I am fixing that in the next release. The next release will also allow rdiff-backup to ignore (some? all?) of the errors caused by too-long filenames on Windows. It does not yet backup such files. See this thread on the mailing list for the explanation: http://lists.nongnu.org/archive/html/rdiff-backup-users/2008-10/msg00117.html Basically, rdiff-backup will need to move to Unicode file handling and prepend ?\\ to each Windows path in order to support long paths filenames ( 255 characters, or so). That is something for the development branch, possibly even for the next one. Andrew ___ 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 -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici cov...@ccs.covici.com ___ 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] OverflowError: signed integer is greater than maximum
On Jan 5, 2009, at 4:00 PM, Brad Beyenhof wrote: First of all, I really like rdiff-backup. In most cases (all but the one I'll detail below), it's been great for me. Searching in the mailing-list archives has led me to believe that either the operating system version (64- versus 32-bit) or the python version may be to blame here. The server I'm using as a backup repository runs 64-bit CentOS 5. I'm using rdiff-backup *from* two other servers, one with the same OS and one with 32-bit CentOS 4. The 64-bit machines run python 2.4.3, and the 32-bit has python 2.3.4, which is the highest version in the Cent4 repos. Backing up from the 64-bit system works fine, and two of the directories I'm backing up from the 32-bit system are fine as well. However, one directory reports OverflowError: signed integer is greater than maximum and quits partway through the backup. The terminal output with the default verbosity is below; I can attach a log with a higher verbosity if requested. Hi Brad, This is a known problem that is due to a bug in Python. The Python bug has been fixed in their SVN, and was slated to be a part of 2.5.3, so it should be included in the latest Python releases: 2.5.4, 2.6.1, and 3.0. Try upgrading your Python to 2.5.4 or 2.6.1. Here is some more information about the problem: https://bugs.launchpad.net/ubuntu/+source/rdiff-backup/+bug/245844 http://bugs.python.org/issue1747858 Andrew ___ 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] long filename error
On Jan 6, 2009, at 4:01 PM, John covici wrote: I hope you at least give a warning so people will know the file was not backed up. It gives rdiff-backup's standard UpdateError, just like other errors which cause an individual file to fail, without taking the whole backup with them: OSError while renaming Test-dest/dest/rdiff-backup.tmp.1 to Test-dest/ dest/1 111 .txt UpdateError dest/rdiff-backup.tmp.1 [Error 3] The system cannot find the path sp ecified Andrew ___ 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
[rdiff-backup-users] Probleme with rdiff on smbfs
having the same exact issue here as well - i am going from a case-sensitive filesystem to one that is not. the first backup went fine with the option: --override-chars-to-quote '' but subsequent backups fail. i have to choose to ignore case because i need a useable mirror on the other system. any further info on this issue? i am running python 2.4.3 on the source and 2.5.1 on dest -- both on rdiff-backup 1.2.4 +-- |This was sent by sbo...@techrvealed.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ 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
[rdiff-backup-users] Does rdiff implement kernel specific optimizations?
Devels, I just came across tee() and splice(). They were introduced in 2.6.17, so relatively new, but not that new. http://linux.die.net/man/2/tee http://linux.die.net/man/2/splice They allow data to be copied from one file descriptor to another without the data coming into userspace. If I was still an active developer, I think about modifying rdiff-backup to use them if there available. I doubt it would really impact the speed of rdiff-backup, but it seems like a fun project and I always liked learning new system calls. Greg -- Greg Freemyer Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence Technology http://www.norcrossgroup.com ___ 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] Probleme with rdiff on smbfs
On Jan 6, 2009, at 3:33 PM, sphen wrote: having the same exact issue here as well - i am going from a case- sensitive filesystem to one that is not. the first backup went fine with the option: --override-chars-to-quote '' but subsequent backups fail. i have to choose to ignore case because i need a useable mirror on the other system. any further info on this issue? i am running python 2.4.3 on the source and 2.5.1 on dest -- both on rdiff-backup 1.2.4 How do the backups fail? Please include your error messages. Also, it is important that you understand that if you override chars- to-quote there is the distinct possibility for dataloss either due to filename collisions or the change-case bug: http://savannah.nongnu.org/bugs/?21253 Andrew ___ 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] Probleme with rdiff on smbfs
On Jan 6, 2009, at 3:33 PM, sphen wrote: having the same exact issue here as well - i am going from a case- sensitive filesystem to one that is not. the first backup went fine with the option: --override-chars-to-quote '' but subsequent backups fail. i have to choose to ignore case because i need a useable mirror on the other system. any further info on this issue? i am running python 2.4.3 on the source and 2.5.1 on dest -- both on rdiff-backup 1.2.4 Spoke too soon ... I believe I've fixed --override-chars-to-quote to work again. Instead of releasing a 1.2.6 so quickly, I'll explain how to get the fix. All you need to do is replace your fs_abilities.py file with this one: http://cvs.savannah.gnu.org/viewvc/*checkout*/rdiff-backup/rdiff_backup/fs_abilities.py?revision=1.61.2.1root=rdiff-backup When I added the functionality last fall to automatically-requote a repository, I didn't notice that one of the functions had a subtle return condition. Andrew ___ 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] --override-chars-to-quote bug fixed and default behaviour change
On Jan 6, 2009, at 12:01 PM, Oliver Mulatz wrote:
On 2009-01-05 Oliver Mulatz wrote:
Another issue: there's a bug (RDB aborts) in '--override-chars-to-
quote'
functionality, (I require for cross-platform filesystem
compatibility).
It hits each time --override-chars-to-quote is used, even with
empty
set ('') for keeping capital chars from being escaped.
The exact error including trace was also posted to the ML on
Oct'08 by EliW:
http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/rdiff-backup-23/probleme-with-rdiff-on-smbfs-92963/#287692
I fixed it, but would like to go deeper.
Did you send the patch to me? (If so, I apologize for not noticing
yet) ... I hope we wrote the same fix to compare_ctq_file()
Now is a good time to discuss a default behaviour change, since the
'--override-char-to-quote' (= OCTQ) option *never* worked, so users
will not be surprised and no scripts need to be changed.
It worked until a year ago with release 1.1.15.
Currently, and what I have read on the mailing-list, the OCTQ-option
must
be provided ON EACH commandline issued when used initially to create
a backup
mirror, also for restores. This is non-intuitive IMO, a more
sensible approach
would be:
1. if no commandline OCTQ option is provided when a backup mirror is
created,
use FS auto-detected chars to quote (already doing so now)
2. if a backup mirror was started with OCTQ, this is assumed valid
unless
otherwise notice/overridden (default behaviour needs to be changed
for this,
but breaks nothing AFAICT)
After reading over the code, it looks like this is actually the case.
Now that I think --override-chars-to-quote is fixed, please test it.
The relevant function is compare_ctq_file() in fs_abilities.py. In it,
we see:
ctq_rp = rbdir.append(chars_to_quote)
if not ctq_rp.lstat():
...
return (actual_ctq, None)
if Globals.chars_to_quote is None: actual_ctq =
ctq_rp.get_data()
else: actual_ctq = Globals.chars_to_quote # Globals override
So, it definitely takes the data from the chars_to_quote file.
3. if the OCTQ really must be changed after creation of backup
mirror with
initial OCTQ set, coupling with '--force' option would be
naturally most
intuitive, otherwise shows error-message hinting about this
= so anybody knows this is a potential 'risky/deep' change, along
the line
of overwriting already existing directories when doing a RDB
restore, ...
I think a small logic change in that function would make this
possible, since the requoting logic is already there. It's a good
suggestion.
Andrew
___
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
[rdiff-backup-users] Rdiff-backup 1.30
Hi all, I just upgraded a couple of machines to 1.3.0 Below is a traceback when running on a standard script of mine: (Used to work with 1.1.15) It's backing up from a Windows server to a unix box. The script runs on the unix box. Any thoughts? (The first line is output from my script, the rest is from rdiff-backup) Cheers, Craig 2009-01-07 11:54:36 Backing up plsbs_backup::d:/users to /mnt/backup/serverbackup/plsbs/users with args: Traceback (most recent call last): File /usr/bin/rdiff-backup, line 30, in module rdiff_backup.Main.error_check_Main(sys.argv[1:]) File /usr/lib/python2.5/site-packages/rdiff_backup/Main.py, line 309, in error_check_Main errmsg = robust.is_routine_fatal(exc) File /usr/lib/python2.5/site-packages/rdiff_backup/robust.py, line 77, in is_routine_fatal elif isinstance(exc, EnvironmentError) and e.errno == errno.ENOTCONN: NameError: global name 'e' is not defined ___ 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
