|
From: | Andrew Ferguson |
Subject: | Re: [rdiff-backup-users] Re: Keyerror strikes again |
Date: | Fri, 27 Jun 2008 18:30:45 -0400 |
On Jun 26, 2008, at 11:08 PM, Kingsley G. Morse Jr. wrote:
Hi Andrew, Version 1.1.15-2+b1 of rdiff-backup is failing withKeyError: ('mnt', 'backup', 'palace', 'rdiff-backup-data', 'increments', 'dev', '.static')Evidently it's failing because a certain directory is missing from rdiff-backup's mirror. I find myself wondering what to do when a directory is missing. Should I a.) manually copy the directory to rdiff-backup's mirror? b.) delete all backed up data, and start over?
Hi Kingsley,I'm really not all that familiar with this part of rdiff-backup's code, so I can't give you any definitive advice.
I don't see any harm in copying the directory to the mirror, do you? It seems like it would be worth a shot. What type of directory is / dev/.static anyway? Maybe it's the kind of auto-mounted or auto- generated directory which really doesn't matter in the long run.
If you reach the point where you plan to delete data, you probably would want to delete the rdiff-backup-data dir on the destination (not the current backed-up files). Rdiff-backup will then prompt you for the --force option, just as with the various suggestions on this list to initialize a repository with rsync, and then use rdiff-backup -- force on the first run.
But, before you delete data, I would appreciate it if you could try rdiff-backup 1.1.16 and see if that makes any difference.
good luck, Andrew
[Prev in Thread] | Current Thread | [Next in Thread] |