Changes between Version 19 and Version 20 of backup

Timestamp:

Nov 28, 2014, 9:17:55 AM (10 years ago)

Author:

dac

Comment:

--

backup

@@ -33 +33 @@
 Occasionally there is a problem overnight and the rsync doesn't run until late. This can mean it is still running when the next rsync begins. This leads to a piling up of multiple instances of the script which just gets worse. It is good practice every now and then to log onto gridmaster3 as arsf and check that there aren't a stupid number of rsync/rdiff processes running (a few concurrent is normal). If so, just kill all instances you can find and let the cron start again as normal the following night. You could automatically check for this problem by modifying repos_back_up_rsync_rdiff.sh to check for rsync/rdiff processes and to fail if they are over a threshold.
 
+rdiff-backup can also produce the following error "Found too many current_mirror incs!". A description of this error is available [http://lists.gnu.org/archive/html/rdiff-backup-users/2003-11/msg00047.html here], you can check using:
+
+
+{{{
+rdiff-backup -l GB08_19-2010_154a_London_day
+}}}
+
+There is a script to fix this problem by moving the duplicate files (/tools/backup/fix_rdiff_multiple_incs.py), if you think this needs running check with mark1 first.
+
 Other problems can be found by checking the cron log above.