On 07/11/2016 07:06 AM, Laurent De Buyst wrote:
"Fatal Error: It appears that a previous rdiff-backup session with
process id 17597 is still running. If two different rdiff-backup
processes write the same repository simultaneously, data corruption will
probably result. To proceed with regress anyway, rerun rdiff-backup
with the --force option."
While your backup session is running, the repository is in an
inconsistent state with _two_ current_mirror files in the
rdiff-backup-data directory. That is also the state when a backup
session has failed. rdiff-backup needs to regress the "failed" backup to
put the repository back into a clean state. Doing that while a backup
session is still running would probably be fatal to your repository and
could never be repaired.
If all you are interested in is the most recent version of the files,
you can always just copy those from the mirror without running
rdiff-backup at all. With a backup session still running, you could of
course get some mix of new and old files depending on just where the
current backup session was currently working.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
_______________________________________________
rdiff-backup-users mailing list at [email protected]
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
