Incremental backups should not appear incremental when restoring

Bug #176838 reported by Ryan Thompson
8
Affects Status Importance Assigned to Milestone
nssbackup
Fix Released
Medium
Oumar Aziz OUATTARA
sbackup
Fix Released
Undecided
Unassigned
sbackup (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

When restoring, the user shouldn't have to think about whether a particular date's backup was full or incremental. In both cases, the full file list should be shown. Currently, when restoring from an incremental backup, only the files that were updated in that increment are shown.

Basically, when I restore from the Feb. 20 backup, I want to restore the full state of the filesystem on that date, not the diff between that backup and the previous one. Incremental backup should not mean incremental restore.

Revision history for this message
Francesco Potortì (pot) wrote :

For what it's worth, I wholeheartedly second this comment.
This is a misfeature of sbackup, which I hope will be corrected in the long run, and which is only excusable because of the young age of this software.

Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :

@francesco: One would say : "This is why the source code is open. If you want to add something to the software, just do it (or find someone who can do it for you".

I really hate this kind of comment. "and which is only excusable because of " !!!
This software is made by developers on their free time, they earn nothing from it, they don't sell it. Moreover they open the code. Would you take some of your free time to do that ? If the answer is yes, then please fix this "misfeature" and submit your patch to the developers or to this bug report.

This said, I would like both of you to know that the main developer of Sbackup is currently busy and he will most likely not take the time to answer this kind of comment.

Revision history for this message
Francesco Potortì (pot) wrote : Re: [Bug 176838] Re: Incremental backups should not appear incremental when restoring

>@francesco: One would say : "This is why the source code is open. If you
>want to add something to the software, just do it (or find someone who
>can do it for you".

You are perfectly right. I myself contribute to some free projects, and
I am well aware of what you mean.

In this case I had the impression that this particular issue was
understated, and I added my comment to stress its importance.

>I really hate this kind of comment. "and which is only excusable
>because of " !!!

Yes, I admit that my wording was badly chosen. I apologise...

>This said, I would like both of you to know that the main developer of
>Sbackup is currently busy and he will most likely not take the time to
>answer this kind of comment.

Yes, I was aware of that. However, one of the roles of bug tracking
systems is to, well, keep track of issues, so that it is plain what are
the problems with one particular package.

Thank you for giving me the opportunity to set things straight.

Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :

Sorry if I was quite rude.

According to your answer, I understand that you're not the kind of users I were talking about. You are also able to admit your mistakes and I am really impressed. This was really a wording issue. And I also apologize as I over reacted.

As for this Bug report, I think it's fixed in NSsbackup (which will be in version 0.3 the new version of Sbackup : sbackup 1.1). I will add NSsbackup as an impacted software.Then you can check if you still find this bug or if you want some improvements.

https://edge.launchpad.net/nssbackup

You should test it with version 0.2 beta . There is a ppa available for NSsbackup which is NSsbackup team PPA.

I need to take time to work on NSsbackup 0.3/Sbackup 1.1 ...

Changed in nssbackup:
assignee: nobody → wattazoum
milestone: none → release0.2
Revision history for this message
Francesco Potortì (pot) wrote :

>I need to take time to work on NSsbackup 0.3/Sbackup 1.1 ...

I am really happy that you and the others on the team took this into your hands. It was a pity to let sbackup starve. Thanks a lot for your work on NSsbackup!

Daniel T Chen (crimsun)
Changed in sbackup:
importance: Undecided → Wishlist
Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Indeed, this issue is still present in latest NSsbackup (0.2RC1).

Changed in nssbackup:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :

I really don't think this problem is still present on 0.2 RC 6.

Currently, the full file list is shown from an incremental snapshot with the precision is the file is included or not.
Then on can restore a non-included file using the "revert" and "revert as" button, which will get the latest version of this file (starting from the selected snapshot)
I believe this solves the issue.

However, an improvement can be added by disabling the "restore" and "restore as" button, when a non included file is selected.

Changed in nssbackup:
status: Confirmed → In Progress
Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :

Fixed on 0.2 branch.

Changed in nssbackup:
status: In Progress → Fix Committed
Revision history for this message
Oumar Aziz OUATTARA (wattazoum) wrote :

Fixed in 0.2rc 7

Changed in nssbackup:
status: Fix Committed → Fix Released
Changed in sbackup:
status: New → Fix Committed
Changed in sbackup:
status: Fix Committed → Fix Released
Changed in sbackup (Ubuntu):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sbackup - 0.11.2ubuntu1

---------------
sbackup (0.11.2ubuntu1) maverick; urgency=low

  * New upstream release. LP: #620384
  * [Fix] LP: #638072 Exclude rules not working on some dirs
  * [Fix] LP: #634356 Exception on reading snapshots in restore ui
  * [Fix] LP: #634031 Default behavior incorrectly set to `Cancel` instead
                      of `Retry`
  * [Fix] LP: #632605 catch error while closing snapshot file over FTP
  * [Fix] LP: #642087 Log. purge not working under certain circumstances
  * Workaround for LP #640034 Setting status to attention does not change
                              to specified icon (indicator-application)
  * Fix: don't block restore gui on long running tasks
  * Fix: don't touch snapshots being upgraded from backup process

sbackup (0.11.1ubuntu1) UNRELEASED; urgency=low

  * [Fix] LP: #587911 Logarithmic purge does not work
  * [Fix] LP: #622095 catch error when listing directory contents fails
  * [Fix]: revamped packaging: use distutils and pysupport

sbackup (0.11.0ubuntu1) UNRELEASED; urgency=low

  * [Fix] LP: #618730 Merge sbackup and nssbackup (see enclosed file
                      nssbackup.ChangeLog for further information)
  * [Fix] LP: #604558 'abort backup' on exernal drives not possible
  * [Fix] LP: #412934 sbackup/nssbackup fails if exclude-path contains an
                      equal-sign
  * [Fix] LP: #277137 crashed with NoSpaceError: No space left on device
  * [Fix] LP: #328902 Spelling and wording errors
  * [Fix] LP: #130856 Show remaining time till backup is finished in UI
  * [Fix] LP: #267759 Simple Backup should display a progress bar
  * [Fix] LP: #137293 empty dialog when restoring with sbackup
  * [Fix] LP: #176838 Incremental backups should not appear incremental when
                      restoring
  * [Fix] LP: #254464 Password for SSH Do Not URI Encode
  * [Fix] LP: #489107 sbackup crahses: stop_if_no_target is not an option in
                      general
  * [Fix] LP: #504990 Mb used instead of MB in the application dialogs
  * [Fix] LP: #507175 libgnomevfs2-extra required for FTP backups
  * [Fix] LP: #310306 Error: no space left
  * [Fix] LP: #383383 restore crashes when the destination path or file is non
                      existent
  * [Fix] LP: #331551 Wrong original English text in sbackup po-file
  * [Fix] LP: #585769 default backup directory doesn't exist in ubuntu
  * translations updated
 -- Jean-Peer Lorenz <email address hidden> Sat, 18 Sep 2010 18:44:57 +0200

Changed in sbackup (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.