Bug 468242

Summary:	[WISH] Add conditional start option for scheduled backups
Product:	[Applications] kup	Reporter:	pumaelbusta
Component:	general	Assignee:	Simon Persson <simon.persson>
Status:	RESOLVED WORKSFORME
Severity:	wishlist	CC:	daniel
Priority:	NOR
Version First Reported In:	0.9.1
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description pumaelbusta 2023-04-07 13:12:39 UTC

SUMMARY
It's a feature request for Kup for conditional run of scheduled backup. The point is that if we are doing backups to network drives mounted. We should be able to ensure the drive is actually mounted, preventing backing up to and filling our root fs.


STEPS TO REPRODUCE
N/A

OBSERVED RESULT
No chance (apart from manual starting) to make sure all prerequisites are in place.

EXPECTED RESULT
Deciding if backup can be started based on e.g. script exit code or mount is in place

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE neon 5.27
(available in About System)
KDE Plasma Version:  5.27.4
KDE Frameworks Version:  5.104.0
Qt Version: 5.15.8

Comment 1 Daniel M 2023-11-14 18:12:16 UTC

In my use of Kup with network mounts in fstab, this feature is already there and works as expected. When you Specify the backup schedule, both Interval and Active Usage Time schedules support this and specifically note the backups being "triggered when backup destination becomes available."

Comment 2 Simon Persson 2024-05-10 12:55:00 UTC

Thanks for the report!

This is already supposed to work, like Daniel M commented. When there is a change in file system mounts kup will check if the filesystem destination is available. This can fail to work if your local filesystem has the destination folder and it just gets shadowed (hidden) by mounting a networked filesystem, in that case the destination folder always exists.

Please reopen this bug report if kup fails to notice changes in filesystem mounts or if I have misunderstood something. Thanks again!