On 10.04.2014 23:41, Carlos Chavez wrote:
I seem to be having a problem. I have several servers backing up to a
single server. All except one are working perfectly and I have been able to
restore files from all of them. All servers do a FULL backup on Sunday and
incremental backups the rest of the week. One of the servers (used for email)
misses the FULL backup on Sunday some of the times and keeps going with
incremental backups. Here is the listing:
Last full backup date: Sun Mar 30 04:39:30 2014
Collection Status
-----------------
Connecting with backend: SSHBackend
Archive dir: /root/.cache/duplicity/d0e2f4f0aec36ed03a5b14adcbd2eec4
Found 3 secondary backup chains.
Secondary chain 1 of 3:
-------------------------
Chain start time: Sat Feb 8 04:03:08 2014
Chain end time: Sat Feb 22 04:02:59 2014
Number of contained backup sets: 6
Total number of contained volumes: 28522
Type of backup set: Time: Num volumes:
Full Sat Feb 8 04:03:08 2014 28350
Incremental Tue Feb 18 22:15:42 2014 110
Incremental Wed Feb 19 04:09:47 2014 2
Incremental Thu Feb 20 04:03:01 2014 20
Incremental Fri Feb 21 04:04:13 2014 28
Incremental Sat Feb 22 04:02:59 2014 12
-------------------------
Secondary chain 2 of 3:
-------------------------
Chain start time: Tue Mar 25 13:42:25 2014
Chain end time: Tue Mar 25 13:42:25 2014
Number of contained backup sets: 1
Total number of contained volumes: 5852
Type of backup set: Time: Num volumes:
Full Tue Mar 25 13:42:25 2014 5852
-------------------------
Secondary chain 3 of 3:
-------------------------
Chain start time: Sun Feb 23 04:24:34 2014
Chain end time: Sun Mar 30 04:03:49 2014
Number of contained backup sets: 32
Total number of contained volumes: 6214
Type of backup set: Time: Num volumes:
Full Sun Feb 23 04:24:34 2014 5717
Incremental Mon Feb 24 04:03:25 2014 5
Incremental Tue Feb 25 04:03:01 2014 17
Incremental Wed Feb 26 04:03:03 2014 17
Incremental Thu Feb 27 04:03:01 2014 20
Incremental Fri Feb 28 04:02:58 2014 20
Incremental Sat Mar 1 04:03:55 2014 17
Incremental Sun Mar 2 04:03:01 2014 6
Incremental Sun Mar 2 04:38:44 2014 1
Incremental Mon Mar 3 04:02:49 2014 4
Incremental Tue Mar 4 04:03:07 2014 12
Incremental Wed Mar 5 04:03:13 2014 30
Incremental Thu Mar 6 04:02:56 2014 15
Incremental Fri Mar 7 04:02:56 2014 14
Incremental Sat Mar 8 04:04:09 2014 16
Incremental Sun Mar 9 04:03:09 2014 5
Incremental Sun Mar 9 04:41:11 2014 1
Incremental Mon Mar 10 04:03:11 2014 7
Incremental Tue Mar 11 04:03:09 2014 18
Incremental Wed Mar 12 04:03:32 2014 25
Incremental Thu Mar 13 04:03:06 2014 39
Incremental Fri Mar 14 04:03:02 2014 17
Incremental Sat Mar 15 04:02:59 2014 21
Incremental Sun Mar 16 04:03:31 2014 5
Incremental Sun Mar 16 04:41:58 2014 1
Incremental Mon Mar 17 04:03:00 2014 4
Incremental Tue Mar 18 04:03:13 2014 10
Incremental Wed Mar 26 04:08:34 2014 87
Incremental Thu Mar 27 04:03:14 2014 14
Incremental Fri Mar 28 04:03:01 2014 28
Incremental Sat Mar 29 04:03:02 2014 14
Incremental Sun Mar 30 04:03:49 2014 7
-------------------------
Found primary backup chain with matching signature chain:
-------------------------
Chain start time: Sun Mar 30 04:39:30 2014
Chain end time: Thu Apr 10 04:03:30 2014
Number of contained backup sets: 13
Total number of contained volumes: 6018
Type of backup set: Time: Num volumes:
Full Sun Mar 30 04:39:30 2014 5848
Incremental Mon Mar 31 04:03:03 2014 4
Incremental Tue Apr 1 04:04:00 2014 22
Incremental Wed Apr 2 04:03:54 2014 14
Incremental Thu Apr 3 04:04:20 2014 26
Incremental Fri Apr 4 04:03:03 2014 16
Incremental Sat Apr 5 04:05:03 2014 18
Incremental Sun Apr 6 04:03:39 2014 5
Incremental Sun Apr 6 04:43:11 2014 1
Incremental Mon Apr 7 04:03:14 2014 5
Incremental Tue Apr 8 04:03:22 2014 13
Incremental Wed Apr 9 04:03:32 2014 18
Incremental Thu Apr 10 04:03:30 2014 28
-------------------------
No orphaned or incomplete backup sets found.
I have no idea why this particular server will sometimes fail to do the
FULL backup on Sunday. There seem to be two incremental backups for Sunday.
try to use parameter --full-if-older-than as described on the manpage
http://duplicity.nongnu.org/duplicity.1.html
this way duplicity determines when to do full or incr and you don't run into
the possibility of cron starting more than one duplicity instance for on backuü
I run the incremental backup from cron.daily and the full backup from
cron.weekly. All servers have exactly the same cron jobs. We are using
Duplicity 0.6.13 which is the latest version we can compile on out CentOS 5.10
servers.
why can't you compile latest stable? did you try to 'python setup.py' the
tarball from the website manually already?