summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Wilson <chris+github@qwirx.com>2014-04-17 20:57:11 +0000
committerChris Wilson <chris+github@qwirx.com>2014-04-17 20:57:11 +0000
commitba441abfb7c1de0ef0622cee5d0d61abd379efa0 (patch)
treea48227ecd52b7ec4aad158426111096c15170f66
parentc39b8cc631c74abefcb8981d4925103013fb5dfd (diff)
Don't consider inode database errors enough reason to run the next backup
immediately after the end of the current one.
-rw-r--r--bin/bbackupd/BackupDaemon.cpp10
1 files changed, 5 insertions, 5 deletions
diff --git a/bin/bbackupd/BackupDaemon.cpp b/bin/bbackupd/BackupDaemon.cpp
index 6dc877b0..47d1174f 100644
--- a/bin/bbackupd/BackupDaemon.cpp
+++ b/bin/bbackupd/BackupDaemon.cpp
@@ -729,13 +729,13 @@ void BackupDaemon::RunSyncNowWithExceptionHandling()
// do not retry immediately without a good reason
mDoSyncForcedByPreviousSyncError = false;
-
+
+ // Is it a berkely db failure?
+ bool isBerkelyDbFailure = false;
+
// Notify system administrator about the final state of the backup
if(errorOccurred)
{
- // Is it a berkely db failure?
- bool isBerkelyDbFailure = false;
-
if (errorCode == BackupStoreException::ExceptionType
&& errorSubCode == BackupStoreException::BerkelyDBFailure)
{
@@ -806,7 +806,7 @@ void BackupDaemon::RunSyncNowWithExceptionHandling()
// If we were retrying after an error, and this backup succeeded,
// then now would be a good time to stop :-)
- mDoSyncForcedByPreviousSyncError = errorOccurred;
+ mDoSyncForcedByPreviousSyncError = errorOccurred && !isBerkelyDbFailure;
OnBackupFinish();
}