Forum: 
Tags: 

duplicity collection-status

David McNeill's picture

So I'm still wrangling monster backups, trying to get this server to behave nicely, and get restorable backups.

So, duplicity collection-status looks useful, but there is no tklbam-collection-status utility (yet).

Based on this incredibly useful post by developer Liraz Siri, I can get the status

export NTPSERVER=ntp.local
tklbam-backup --simulate --debug

The --debug option has dropped you into an interactive shell

duplicity collection-status --archive-dir=/var/cache/duplicity --s3-unencrypted-connection s3://s3-ap-southeast-2.amazonaws.com/tklbam-ap-southeast-2-e9...

Some useful output,

    Local and Remote metadata are synchronized, no sync needed.
    Last full backup date: Sat Apr  8 12:16:44 2017
    Collection Status
    -----------------
    Connecting with backend: BotoBackend
    ...
    Found 2 secondary backup chains.
    Found primary backup chain with matching signature chain:
    ...
    No orphaned or incomplete backup sets found.

So that machine is all clean and tidy. Method checked, onto the next one.


 

David McNeill's picture

And on my problem machine...

Also found 0 backup sets not part of any chain,
and 1 incomplete backup set.
These may be deleted by running duplicity with the "cleanup" command.

 

So copy and paste the cleanup command shown in the --debug output into the tklbam shell...

duplicity --verbosity=5 --archive-dir=/var/cache/duplicity cleanup --force s3://s3-ap-southeast-2.amazonaws.com/tklbam-ap-s
outheast-2-e9...
 

Warning, found incomplete backup sets, probably left from aborted session
Deleting this file from backend:

So now the nasty incomplete full backup is kicked for touch, and we can get going again on a regular process.

Post new comment