rdiff-backup-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[rdiff-backup-users] Error recovering from failed backup


From: Keith Edmunds
Subject: [rdiff-backup-users] Error recovering from failed backup
Date: Thu, 08 Sep 2005 08:46:28 +0100
User-agent: Debian Thunderbird 1.0.2 (X11/20050817)

I have a server being backed up by rdiff-backup, and occasionally the backup fails for network or other reasons. The problem I am experiencing happens on the _next_ backup. The command issued is:

--------------------------------------------------------------
        rdiff-backup --print-statistics --create-full-path \
                /home/xxx \
                backup::/backups/yyy/xxx \
--------------------------------------------------------------

Then I get, as expected:

--------------------------------------------------------------
Previous backup seems to have failed, regressing destination now.
--------------------------------------------------------------

Followed by:

--------------------------------------------------------------
Warning: Could not restore file /backups/yyy/xxx/02LaidOut/.DS_Store!

A regular file was indicated by the metadata, but could not be
constructed from existing increments because last increment had type
None.  Instead of the actual file's data, an empty length file will be
created.  This error is probably caused by data loss in the
rdiff-backup destination directory, or a bug in rdiff-backup
-----------------------------------------------------------------

Note that the source directory name is '02 Laid Out' but that the spaces have disappeared in the error message (but the spaces do exist on the backup:: machine). The exclamation mark at the end of the error message is part of the message rather than part of the filename. Both source and destination machines are running Linux with rdiff-backup 0.13.4. The files being backed up are created by Apple Macs and saved in an Appletalk share.

Any clues as to how to proceed?

Thanks,
Keith




reply via email to

[Prev in Thread] Current Thread [Next in Thread]