[Duplicity-talk] Duplicity using 1.5 TB storage and loosing incremental backups?

[Remy van Elst]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Duplicity seems to loose it's status when trying to do a incremental
backup set over 14 days. The backup has been running for a while now
but it is using about 1.5 TB of backend storage since 2 weeks. It is
going to an Openstack swift object store as backend.

This is the command line:

     duplicity --asynchronous-upload --verbosity 9 --log-file
/var/log/duplicity.log --volsize 25 --tempdir="/tmp"
- --file-prefix="vps1.sparklingclouds.nl."
- --name="vps1.sparklingclouds.nl." --exclude-device-files
- --exclude-globbing-filelist=/etc/duplicity-backup/exclude.conf
- --full-if-older-than="14D" --no-encryption  / swift://duplicity-backup

This is what caught my eye in the verbose log file:

    File
vps1.sparklingclouds.nl.duplicity-full.20150430T034939Z.vol166.difftar.g
z
is part of known set
    File
vps1.sparklingclouds.nl.duplicity-full.20150430T034939Z.vol1660.difftar.
gz
is part of known set
    Found backup chain [Tue Mar 24 14:42:44 2015]-[Tue Mar 24 14:42:44
2015]
    Last full backup is too old, forcing full backup


The last full backup is from yesterday, and it should only do a full
backup every 14 days.

When I do a collection status it seems all the incremental backups are
gone:

Do note that I've got a wrapper script around duplicity which outputs
the status, storage used and config settings:


    # Hostname: vps1.sparklingclouds.nl
    # IP: 192.0.2.10
    # Storage used: 1.5T
    # Full backups to keep: 4
    # Create full backup if last full backup is older than: 14D
    -----------------------------------------
    # Duplicity collection status:
    # Local and Remote metadata are synchronized, no sync needed.
    # Last full backup date: Mon May 25 10:48:16 2015
    # Collection Status
    # -----------------
    # Connecting with backend: BackendWrapper
    # Archive dir: /root/.cache/duplicity/vps1.sparklingclouds.nl.
    # Found 4 secondary backup chains.
    # Secondary chain 1 of 4:
    # -------------------------
    # Chain start time: Tue Mar 24 14:42:44 2015
    # Chain end time: Tue Mar 24 14:42:44 2015
    # Number of contained backup sets: 1
    # Total number of contained volumes: 3009
    #  Type of backup set:                            Time:      Num
volumes:
    #                 Full         Tue Mar 24 14:42:44 2015
   3009
    # -------------------------
    # Secondary chain 2 of 4:
    # -------------------------
    # Chain start time: Wed Apr  8 05:49:18 2015
    # Chain end time: Wed Apr  8 05:49:18 2015
    # Number of contained backup sets: 1
    # Total number of contained volumes: 3104
    #  Type of backup set:                            Time:      Num
volumes:
    #                 Full         Wed Apr  8 05:49:18 2015
   3104
    # -------------------------
    # Secondary chain 3 of 4:
    # -------------------------
    # Chain start time: Thu Apr 16 05:49:37 2015
    # Chain end time: Thu Apr 16 05:49:37 2015
    # Number of contained backup sets: 1
    # Total number of contained volumes: 3128
    #  Type of backup set:                            Time:      Num
volumes:
    #                 Full         Thu Apr 16 05:49:37 2015
   3128
    # -------------------------
    # Secondary chain 4 of 4:
    # -------------------------
    # Chain start time: Thu Apr 30 05:49:39 2015
    # Chain end time: Thu Apr 30 05:49:39 2015
    # Number of contained backup sets: 1
    # Total number of contained volumes: 736
    #  Type of backup set:                            Time:      Num
volumes:
    #                 Full         Thu Apr 30 05:49:39 2015
    736
    # -------------------------
    # Found primary backup chain with matching signature chain:
    # -------------------------
    # Chain start time: Mon May 25 10:48:16 2015
    # Chain end time: Mon May 25 10:48:16 2015
    # Number of contained backup sets: 1
    # Total number of contained volumes: 0
    #  Type of backup set:                            Time:      Num
volumes:
    # -------------------------
    # No orphaned or incomplete backup sets found.


Why does this happen and how can I get this back to normal?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCAAGBQJVYuW4AAoJECtnVb0bf4jcIzAIAPJRikn6IUQpDb3xaXBk8JMM
9YT+DCknj3U74Z927NI6UhuM2CJVmdhnZgQZxg50oDVyqt7Yynsf5HTPH4sSq9YZ
19vQ5CDieAFlqiKTYY5d2E1rp+Ivy4ZrYAu7B1RzIz2ySI56slmttjlV1uMg5MGk
PKm2jOYtmuj+3l1EyF6LIwETfwEnmXJ1+sdIc7x2V9+jEdjyFQNY3vku86eiCtkz
h/YEsTtH9/ibwRVfvhGbgeoRqVDkR7GjqAGMbm8pQsMfYfXLVgENhxQUn0NUeSt7
3DGaYe1Cz4rNsXBAjgWEcaxu9kSDPckwwkpEmoFEnz2v2xjJy87wCG1VzXLD530=
=u9Y/
-----END PGP SIGNATURE-----

0x1B7F88DC.asc
Description: application/pgp-keys

0x1B7F88DC.asc.sig
Description: PGP signature