Bug report: Areca deletes all backups when only 1 should be deleted
Brought to you by:
aventin
Menu
▾
▴
#567 Bug report: Areca deletes all backups when only 1 should be deleted
I love Areca. Been using it for a long time. I just wanted to point out 1 small bug so Areca can become even better.
Ex: Lets say a user has 2 Full backups: one made 5 days ago, and one made today. If they want to delete Only the old full backup made 5 days ago, Areca won't allow it. Because it deleted all backups made after that date. So even the new full backup made today will be deleted if the user wants to get rid of the oldest full backup.
I understand this behavior is appropriate if the backups are partial/incremental. But it makes no sense when they are full backups, which should be "self-sufficient" and independent from any other backups before or after them.
Hope this helps!
.
This is not really a bug, it is just a bit unintuitive. If you want to remove the old backup you have to merge them into one which in your case will simply delete the older full backup and keep the newer one.
There is a hint in the warning message when you try to delete the older backup that tells you that you probably want to do a merge.
We programmers should really start to look wider.
Making software is not just making basic functionality - this was maybe enough in 1980-is.
* Unintuitive things in programs ARE bags !!! *
Really bad bugs ! Bugs in design. Bugs in thinking. Bugs in quality. Bugs in quality control. Bugs in user relationship. And could lead to bugs in functionality when user use it as intuitively expected, and program function different (unintuitive).
It could be right in same cases (maybe also in this case?) to DECEIDE to leave particular bugs unresolved (ie. because of lack of resources for that product, or decision to make lower quality product), but is not right to minimize its importance (just unintuitive, this is a feature not a bug, ...).
Thanks you !