Hasleo Backup Suite V5.4.2.0 Released!

[admin]

It is smart and will guarantee that the backup chain will not be broken. For example, if you choose to delete a differential backup, all incremental backups that depend on that differential backup are automatically selected.

I would make the following suggestion... when you CHECK (for deletion), currently all "children" associated with that selection (FULL or DIFF) are selected as well AND when unselected, all associated children as unselected as well... very good implementation!  BUT when this is done by selecting an INCREMENTAL, all incrementals that are "children" of the selection are also selected... that's good.  But when the original selected INCREMENTAL is unselected, all automatically selected "children" of that image remain selected.  Now I understand your logic here..,. automatically selected "children" of the originally selected INCREMENTAL remain selected because they don't get affected by the original unCHECK operation, but their cleanup from reversing the original selection is basically a mess... all originally automatic selected "children" remain selected and can only be unselected with manual unCHECKs on the automatically children.  This is truly messy if your INC chains are of any real length (mine are 7-day by 12-hourly).

What should be done is any action that's automatically added by a selected DELETE operation, should be removed when that selected DELETE operation is unCHECKed.  This produces a clean SETUP when a single image is selected for deletion, and a complete reversal if that decision is reversed (which it will be if the user accidentally selected the wrong image like I did  ).  Sure would save a lot of unCHECKing operations.

Thanks for the suggestion, we will improve it in future releases.