>>>>> Kevin Horton <[EMAIL PROTECTED]> >>>>> wrote the following on Wed, 2 Nov 2005 06:01:12 -0500 > I made a fresh backup with rdiff-backup 1.1.0, then did an > incremental backup. It failed, complaining about not being able to > read a 13M xml file.
Not sure what would cause that. > The file was quite readable, and I couldn't see any reason for the > failure, so I tried again. This time the backup failed complaining > about corrupt mirror_metadata. Did it try to regress at the beginning of the session after the failed one? > I checked the last mirror_metadata file, and it was corrupt. > > 1. Is this corruption a result of the earlier failure to backup? > Should I need to do anything special to recover from an error, or can > I just try again. It's normal for the mirror_metadata and other things to be corrupt after a failed session (since they're only partially written) but they should all be cleaned up during the beginning "regress" period of the next session. > 3. I note that many of the file names in the rdiff-backup-data > directory have strange encoding in the file names. Why? See: If the repository is already quoted then rdiff-backup will maintain the quoting for backwards compatibility. But if you start a new repository with a new version (maybe just 1.1.1/ maybe 1.1.0) then it should be (and stay) unquoted. -- Ben Escoto
pgpqgkdaTWGUS.pgp
Description: PGP signature
_______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
