vorta icon indicating copy to clipboard operation
vorta copied to clipboard

Switching between profiles sometimes starts a new backup that is not yet due according to schedule

Open tvogel opened this issue 8 months ago • 3 comments

Description

Sometimes, when vorta is idle and I switch between the four profiles that I have set up, suddenly a backup run starts that I did not expect to run yet and which has a recent completed archive.

For context: Three of my four profiles use the same repo and the fourth uses a separate repo. They all use different schedules:

  • one uses "every three hours"
  • one uses "every four weeks"
  • one uses "every three days"
  • one uses "every week"

In the latest occurrence of this problem, the backup that is supposed to run every four weeks and has run today at 12:40 and had completed successfully, was started again when I switched to it at 13:57 which actually would be too early for any schedule, I have configured, so a mere mix-up of schedule information when switching profiles is unlikely.

Could it be that "last run" information is reset to "never" during profile switch and can happen to be used before it is retrieved from the repo in a race condition?

Reproduction

  • [x] I tried to reproduce the issue.
  • [x] I was able to reproduce the issue.

OS

openSUSE Tumbleweed 20250329, KDE 6.3.3

Version of Vorta

0.10.3

What did you install Vorta with?

Distribution package

Version of Borg

1.4.0

Logs


tvogel avatar Apr 17 '25 12:04 tvogel

I have changed my timer several times. Now it makes backups whenever it wants. Where can I reset the timer configuration or change it manually in which file?

Satlinker avatar Apr 22 '25 06:04 Satlinker

@tvogel Keep in mind that without the detailed log-files it is close to impossible to understand what was going on in your case. Is the "Run missed backups on startup or wakeup" option enabled? Did you change the scheduler settings recently? You say that you can reproduce - could you please describe how exactly? (I had some unexpected scheduling myself, recently - but could not reproduce)

The "run missed backups" uses the date of the last successful backup (from the logs) in combination with the Backup period - and compares this with current time. This can lead to unexpected results, if you change the backup schedule.

goebbe avatar May 11 '25 08:05 goebbe

I have changed my timer several times. Now it makes backups whenever it wants. Where can I reset the timer configuration or change it manually in which file?

@Satlinker Your question is not directly related to this bug report. Please repost your question under "Discussions"

goebbe avatar May 11 '25 08:05 goebbe

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Aug 25 '25 02:08 github-actions[bot]

This issue was closed because it has been stalled for 7 days with no activity.

github-actions[bot] avatar Sep 01 '25 02:09 github-actions[bot]