[Feature Request] sinple shedule option to update previous backups

[FreezyExp]

Is your feature request related to a problem? Please describe it. I would like to have a simple and clear way to ensure daily updates of backups, it should skip apps that have not run since the last backup.

Describe the primary solution The filter in shedule should also have the "apps without backups" option, so that it is consistent with the other screens.

Making the first backup manually for new apps (or using a different shedule entry for automation) The daily update eill ipdate the exact same type of backup as that specifi app already had.

Describe alternative solutions, if any A basic set of shedule options, to reduce percieved complexity, keeping the current options as an advanced view.

[hg42]

I think this could be seen as multiple feature requests in one...

I agree that "doing the same backup again" could be useful. It avoids duplicating the manual actions in a schedule.

Despite the same name, the "Backup Types" in schedule are not the same as in the filter. In the schedule it means which parts to backup. So "without" doesn't make sense here.

I think we should probably rename the section. And I think, the "App type" needs to be put below the "Backup types", because it's a filter. The sort section, and the filter section should be separated by a line or something from the rest.

I think, the "without backup" part could be covered by "new backups", but I'm not sure if it's designed like this (@machiav3lli ?). What exactly does "new" mean? if it would mean "existing but not old", it wouldn't be very useful. I wouldn't even expect a recent backup to be included in "new". From my POV it would only mean "non-existent backups".

[machiav3lli]

Here are some notes/answers:

• without backups doesn't make sense here as its the instances to get backed up, so "without backup" is nothing meaningful
• filtering apps based on data being changed, has been discussed many times in the group and the result is: that nowdays contrary to 10 years earlier (when TiB was on work) app data (in all those different directories) isn't static and dynamically changing even when the user doesn't open the app. Plus there's no API to get this info easily so NB will have to scan the storage fully, which isn't efficient, that's why we decided against this.
• a strategy to cover your different needs would be to create multiple schedules with different intervals and filters e.g. daily for updated apps, bi-weekly for old backups (old can be defined in the app settings).
• the only FR I see here is the "backing up based on latest backup"

@hg42 I agree on resorting the sections. And as pointed out by you and I, "without nackup" have isn't logical here". With the new filtering system there's multiple "new"s, and those should be clear considering each category…

• new for apps mean newly installed
• new for backups mean, backups that aren't old (allows loop-repeatation of backup of certain apps)