I just upgraded one of my test systems (client and server) from
rdiff-backup 1.0.0 to 1.0.4 (both with my --force-path-prefix patch
applied; perhaps at some point I'll try to reopen the discussion on
merging it upstream). While I can run new backups and increment them,
rollbacks are failing on an
Listing the increments in a backup directory while an other backup is in
progress give the following error:
rdiff-backup -l host::/path/to/backup
Fatal Error: Previous backup to /path/to/backup seems to have failed.
Rerun rdiff-backup with --check-destination-dir option to revert directory to
--- rdiff-backup-1.0.4/rdiff_backup/Security.py.orig2006-01-26
12:21:30.980533559 -0600
+++ rdiff-backup-1.0.4/rdiff_backup/Security.py 2006-01-26
12:21:57.997097214 -0600
@@ -140,6 +140,7 @@
if sec_level == read-only or sec_level == all:
I've validated (via running pdb and looking at the actual file handle
the call is being made on) that it's a directory being fsync'd. However,
this still happens even if I munge Globals.py and force
Globals.fsync_directories to 0.
___
Eww -- sorry 'bout that formatting, all; didn't realize it would do
that. As an attachment, this time.
(Lacking this patch, btw, I was receiving security violations on the
specified method doing a simple restore of a backup specified with
--restore-as-of 0B).
---
On Wed, 25 Jan 2006, Troels Arvin wrote:
I'm backing up a Red Hat Enterprise Linux 4 with enabled SELinux support.
It seems that SELinux security contexts for files aren't backed up by
rdiff-backup.
I tought that SELinux's security contexts were implemented by extended
attributes (and that
On Thu, 26 Jan 2006 16:48:42 -0800, dean gaudet wrote:
you probably need to install pyxattr package... i don't know the redhat
package name. install pylibacl while you're at it...
I already have the python-xattr and python-libacl packages installed
on both the production and backup servers.
