When scheduling a daily backup at an exact time, the selected minutes are not preserved when calculating the next backup. For example, a backup scheduled for 18-08-2026 at 22:15 correctly triggers at 22:15, but the next backup is incorrectly scheduled for 19-08-2026 at 22:00. This prevents users from reliably scheduling backups at a specific minute within an hour.
Additionally, while users can specify an exact minute when creating a backup, editing an existing backup only allows selecting minutes in 5-minute increments. The scheduling logic should preserve the originally configured minute, and the edit flow should ideally support the same minute-level precision as the creation flow.
