Comment 8 for bug 445346

I can't add a thing at the moment I don't know much about the feature
--
Philippe Delodder
<email address hidden>
http://www.delodder.be

2009/10/8 Rob Oakes <email address hidden>

> Hi Stan,
>
> Can you elaborate on this a little more? I didn't even release there
> was an "auto-remove" pop up. (Can you add anything Philippe?) Though
> that particular feature is important, it's still highly on the
> experimental side (as is the Delete Backup Set feature).
>
> Cheers,
>
> Rob
>
> -----Original Message-----
> From: <email address hidden> [mailto:<email address hidden>] On Behalf Of
> Stan Armstrong
> Sent: Thursday, October 08, 2009 4:08 AM
> To: <email address hidden>
> Subject: Re: [Bug 445346] Re: smart remove is deleting all earlier
> snapshots
>
> Rob and Philippe,
>
> That's it! The button that you call "Delete Backup Set" is called in the
> pop-up "Run Auto-remove." I'm almost positive that, at some point having
> noticed that setting Smart remove hadn't done anything, I pressed "Run
> Auto-remove." It seemed logical.
>
> May all the problems be so easy to fix.
>
> Warmest regards,
>
> Stan
>
>
> Rob Oakes wrote:
> > Hi Stan and Philippe,
> >
> > I went through and took a look at the app, duplicity_interface and utils
> > classes that deal with snapshot deletion and the autoremove methods. In
> > 0.2, autoremove buttons don't actually do anything; which is to say,
> > there isn't any way to activate those methods except by modifying the
> > source code.
> >
> > I'm afraid we may be dealing with something else here. Stan, by chance,
> > did you happen to press the "Delete Backup Set" button? If you have
> > more than a single complete backup set, it's possible that one of the
> > sets was deleted and you are seeing the remaining files of the other
> > sets. The way that we list out backup sets in Time Drive isn't as
> > robust as it could be.
> >
> > An alternative theory is that one of the links in you backup chain
> > somehow got corrupted. This has been known to happen with duplicity.
> > If that is the case, it would produce the same sort of behavior that you
> > describe. To test for corruption, could you run the following command
> > on the broken backup:
> >
> > duplicity verify /path/to/archive
> >
> > Regardless of the cause, I consider this to be a serious bug and would
> > like to correct it.
> >
> > Cheers,
> >
> > Rob
> >
> > ** Changed in: time-drive
> > Importance: Undecided => Critical
> >
> >
>
> --
> smart remove is deleting all earlier snapshots
> https://bugs.launchpad.net/bugs/445346
> You received this bug notification because you are a member of Time
> Drive - Devel, which is subscribed to Time Drive.
>
> Status in Time Drive: Incomplete
>
> Bug description:
> I lost all my snapshots except the current one when I chose smart remove. I
> set it up yesterday. I ran refresh. Nothing appeared to happen. My list of
> snapshots remained the same. This morning I discovered that all but two
> entries for last night's snapshot had been removed from the list. The list
> now contains entries marked Tue Oct 6 00:32:48 2009 and Tue Oct 6 00:00:02
> 2009. Both entries are tagged with the blue circle.
>
> I had had several incrementals and three full backups. It is now
> impossible to restore to a state earlier than last night's backup. When
> I looked at the actual backup folder, all the earlier duplicity files
> appeared to still be there. The latest backup (a full) seems to have
> started at midnight, as usual, and finished with a manifest file at
> 12:24:43. There are no files corresponding to the snapshot entry marked
> 00:32:48.
>
> I am running Time-Drive 0.2 on Ubuntu 9.04 64-bit.
>
> --
> smart remove is deleting all earlier snapshots
> https://bugs.launchpad.net/bugs/445346
> You received this bug notification because you are a member of Time
> Drive - Devel, which is subscribed to Time Drive.
>
> Status in Time Drive: Incomplete
>
> Bug description:
> I lost all my snapshots except the current one when I chose smart remove. I
> set it up yesterday. I ran refresh. Nothing appeared to happen. My list of
> snapshots remained the same. This morning I discovered that all but two
> entries for last night's snapshot had been removed from the list. The list
> now contains entries marked Tue Oct 6 00:32:48 2009 and Tue Oct 6 00:00:02
> 2009. Both entries are tagged with the blue circle.
>
> I had had several incrementals and three full backups. It is now impossible
> to restore to a state earlier than last night's backup. When I looked at the
> actual backup folder, all the earlier duplicity files appeared to still be
> there. The latest backup (a full) seems to have started at midnight, as
> usual, and finished with a manifest file at 12:24:43. There are no files
> corresponding to the snapshot entry marked 00:32:48.
>
> I am running Time-Drive 0.2 on Ubuntu 9.04 64-bit.
>