[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [rdiff-backup-users] How to cope with missing 'rdiff-backup-data' in
Re: [rdiff-backup-users] How to cope with missing 'rdiff-backup-data' in destination directory
Thu, 21 Jan 2016 20:26:43 +0000 (UTC)
> The message I see in the same situation is:
Ah, now I understand. My script was doing a first sweep with "--force", but
also with "--remove-older-than", which of course will fail in this scenario. I
wrote the thing some time ago. Thanks for your help.
> Fatal Error: Destination directory [dir]
> exists, but does not look like a rdiff-backup directory. Running
> rdiff-backup like this could mess up what is currently in it. If you
> want to update or overwrite it, run rdiff-backup with the --force
> Fatal Error: Lost connection to the remote system
> If you do as it suggests and run rdiff-backup with
> --force option, it should complete successfully and
> convert the destination directory in an rdiff-backup repository.
By the way, the wording in the rdiff-backup message above is probably well
meaning, but it does inflict some fear, especially if you have a huge backup on
a slow USB drive. I would suggest mentioning in the documentation that --force
is fine in this scenario. It is not untypical to migrate from other backup
systems to rdiff-backup, so mentioning that this regenerates
'rdiff-backup-data' would help.