|Subject:||[rdiff-backup-users] Resuming rdiff-backup after crash|
|Date:||Sun, 04 May 2003 22:22:46 -0500|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313|
I had this experience today when I had started rdiff-backup in an xterm and was browsing the web with Mozilla. Apparently the browser made a bad function call and the X display crashed, which crashed the xterm, which crashed rdiff-backup. When I got an xterm back and restarted rdiff-backup (with the exact same parameters), I saw this message:
"Last backup dated Sun May 4 13:08:14 2003 was aborted, but we aren't resuming it."
What does this mean? Is rdiff-backup trying to resume the backup cleanly? That would be great if it is, but then again, if you do Ctrl-C, you get a nasty-looking Python stacktrace, so I really don't know how rdiff-backup is designed to handle crashes. (I'm using 0.10.2.)
It would really be cool if rdiff-backup were fault-tolerant and could pick up a backup job no matter when it dies. That would also allow a pause-resume feature, which I don't think exists now. (e.g. pressing Ctrl-C halts the current backup, then doing, say, "rdiff-backup --resume" picks up where it left off.) Not exactly a high-priority feature, but something that would be nice to have.
|[Prev in Thread]||Current Thread||[Next in Thread]|