On full drive, backup directory got deleted
Bug #1665327 reported by
Anes Lihovac
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
New
|
Undecided
|
Unassigned |
Bug Description
The other day, my harddrive containing my backups, was full, and of course the backup triggered via dejadup would fail, which is configured to run daily. So the next day when the backup started again, I cancled it, only to find out later that the directory containing my backups was empty. All my backups were gone.
To post a comment you must log in.
What version of duplicity? Which OS? Do you run clean automatically?
On Thu, Feb 16, 2017 at 6:25 AM, Anes Lihovac <email address hidden>
wrote:
> Public bug reported: /bugs.launchpad .net/bugs/ 1665327 /bugs.launchpad .net/duplicity/ +bug/1665327/ +subscriptions
>
> The other day, my harddrive containing my backups, was full, and of
> course the backup triggered via dejadup would fail, which is configured
> to run daily. So the next day when the backup started again, I cancled
> it, only to find out later that the directory containing my backups was
> empty. All my backups were gone.
>
> ** Affects: duplicity
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https:/
>
> Title:
> On full drive, backup directory got deleted
>
> Status in Duplicity:
> New
>
> Bug description:
> The other day, my harddrive containing my backups, was full, and of
> course the backup triggered via dejadup would fail, which is
> configured to run daily. So the next day when the backup started
> again, I cancled it, only to find out later that the directory
> containing my backups was empty. All my backups were gone.
>
> To manage notifications about this bug go to:
> https:/
>