duplicity-talk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Duplicity-talk] duply not recognizing backup chains after upgrade


From: Scott Classen
Subject: [Duplicity-talk] duply not recognizing backup chains after upgrade
Date: Mon, 30 Jan 2017 12:22:00 -0800

Hello

I just swapped in the new duply (2.01 for 1.11.1) and the existing backup chain 
is not being recognized.

BTW I'm pretty sure that duplicity is actually version 7.11. I just upgraded 
it, but it still is reporting itself as 0.7.05

any advice on what I may have forgotten to configure?

Thanks,
Scott


# duply home_a status
Start duply v2.0.1, time is 2017-01-30 12:14:51.
Using profile '/etc/duply/home_a'.
Using installed duplicity version 0.7.05, python 2.7.11, gpg 2.0.14 (Home: 
~/.gnupg), awk 'GNU Awk 3.1.7', grep 'grep (GNU grep) 2.20', bash 
'4.1.2(2)-release (x86_64-redhat-linux-gnu)'.
Autoset found secret key of first GPG_KEY entry 'xxxxxxxx' for signing.
Checking TEMP_DIR '/duplicity' is a folder and writable (OK)
Test - Encrypt to 'xxxxxxxx' & Sign with 'xxxxxxxx' (OK)
Test - Decrypt (OK)
Test - Compare (OK)
Cleanup - Delete '/duplicity/duply.26802.1485807291_*'(OK)

--- Start running command STATUS at 12:14:52.745 ---
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: none
Collection Status
-----------------
Connecting with backend: BackendWrapper
Archive dir: /duplicity/.duply-cache/duply_home_a

Found 0 secondary backup chains.
No backup chains with active signatures found
No orphaned or incomplete backup sets found.
--- Finished state OK at 12:14:53.193 - Runtime 00:00:00.448 ---







# duply-old home_a status
Start duply-old v1.11.1, time is 2017-01-30 12:16:59.
Using profile '/etc/duply/home_a'.
Using installed duplicity version 0.7.05, python 2.7.11, gpg 2.0.14 (Home: 
~/.gnupg), awk 'GNU Awk 3.1.7', grep 'grep (GNU grep) 2.20', bash 
'4.1.2(2)-release (x86_64-redhat-linux-gnu)'.
Autoset found secret key of first GPG_KEY entry 'xxxxxxxx' for signing.
Checking TEMP_DIR '/duplicity' is a folder and writable (OK)
Test - Encrypt to 'xxxxxxxx' & Sign with 'xxxxxxxx' (OK)
Test - Decrypt (OK)
Test - Compare (OK)
Cleanup - Delete '/duplicity/duply-old.27279.1485807419_*'(OK)

--- Start running command STATUS at 12:17:00.706 ---
Synchronizing remote metadata to local cache...
Last full backup date: Sun Jan  1 01:00:02 2017
Collection Status
-----------------
Connecting with backend: BackendWrapper
Archive dir: /duplicity/.duply-cache/duply_home_a

Found 2 secondary backup chains.
Secondary chain 1 of 2:
-------------------------
Chain start time: Tue Nov  1 01:00:03 2016
Chain end time: Tue Nov  1 01:00:03 2016
Number of contained backup sets: 1
Total number of contained volumes: 41
 Type of backup set:                            Time:      Num volumes:
                Full         Tue Nov  1 01:00:03 2016                41
-------------------------

Secondary chain 2 of 2:
-------------------------
Chain start time: Thu Dec  1 01:00:03 2016
Chain end time: Thu Dec  1 01:00:03 2016
Number of contained backup sets: 1
Total number of contained volumes: 41
 Type of backup set:                            Time:      Num volumes:
                Full         Thu Dec  1 01:00:03 2016                41
-------------------------


Found primary backup chain with matching signature chain:
-------------------------
Chain start time: Sun Jan  1 01:00:02 2017
Chain end time: Mon Jan 30 01:00:03 2017
Number of contained backup sets: 13
Total number of contained volumes: 53
 Type of backup set:                            Time:      Num volumes:
                Full         Sun Jan  1 01:00:02 2017                41
         Incremental         Mon Jan  2 01:00:03 2017                 1
         Incremental         Tue Jan  3 01:00:03 2017                 1
         Incremental         Wed Jan  4 01:00:03 2017                 1
         Incremental         Thu Jan  5 01:00:03 2017                 1
         Incremental         Fri Jan  6 01:00:03 2017                 1
         Incremental         Sat Jan  7 01:00:03 2017                 1
         Incremental         Sun Jan  8 01:00:02 2017                 1
         Incremental         Mon Jan  9 01:00:03 2017                 1
         Incremental         Fri Jan 27 11:05:07 2017                 1
         Incremental         Sat Jan 28 01:00:03 2017                 1
         Incremental         Sun Jan 29 01:00:03 2017                 1
         Incremental         Mon Jan 30 01:00:03 2017                 1
-------------------------
No orphaned or incomplete backup sets found.
--- Finished state OK at 12:17:01.368 - Runtime 00:00:00.661 ---


reply via email to

[Prev in Thread] Current Thread [Next in Thread]