2

I have setup a Google Cloud Storage bucket for my Duplicity backups. The bucket has a retention policy of 1 year. Today Duplicity got interrupted while doing the backups, and now, every time I want to run a backup, it tries to delete the aborted backup:

Attempt of _do_delete Nr. 2 failed. ClientError: An error occurred (AccessDenied) when calling the DeleteObject operation: Access denied.

How can I just leave the aborted file stub (can't be deleted due to retention) and let Duplicity start a new backup anyways?

Workaround if the bucket retention is not locked

  • Remove bucket retention and let Duplicity have "Storage Object Admin" access to the bucket.
  • Rerun Duplicity.

But I'd prefer a solution that works even if the destination is read only / WORM.

Improve this question
9
  • 1
    Why do you want to keep an aborted backup? Can you not delete the file manually? Commented Apr 25 at 20:15
  • 1
    Please refer to my question and you will see why this is. BTW manually deleting a file in a Duplicity backup set is not so good, since Duplicity then will not recognise the repository, and will start a full backup even if this isn’t really needed. Commented Apr 26 at 5:19
  • If the backup is corrupt as you have alluded to by having an incomplete file, then you DO NEED A NEW BACKUP. Having a cherrypicked backup is not a complete backup. This is just an opinion mind you... Commented Apr 28 at 18:03
  • @eyoung100 Well, let's say I have a complete backup from 2025-01-01. The incremental of 2025-01-02 is incomplete due to error. If I do an incremental instead of a full on the 2025-01-03 doesn't matter. I still have the same data. I can't get back to the state of 2025-01-02 whatever way, so I can't really see why it would be better to start anew with a full backup, but please correct me if I'm wrong ... Commented Apr 28 at 19:29
  • All an incremental backup is is a file comparison using the following logic: What files changed between todays new backup and yesterdays backup?; If a file exist in yesterday's backup, it's marked as not new and not added. Each previous incremental backup becomes the starting point for each new incremental backup, like so Full + Incremental + Incremental + i^n incrementals You currently have Full + incremental + incremental + broken You cant restart an incremental backup with a broken segment therefore you need to skip the broken days incremental and do a full Commented Apr 28 at 19:49

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.