vorta icon indicating copy to clipboard operation
vorta copied to clipboard

A daily backup should be performed as soon as the appropriate backup location has been mounted

Open sudwhiwdh opened this issue 3 years ago • 6 comments
trafficstars

In version 0.8.4. I am currently experiencing the following: I have set a daily backup to 6pm. The external hard disk is not mounted at 6pm. Vorta gives me notifications that the backup location was not found. When I mount the external hard drive and the Borg app is open, the backup to be made does not start automatically. If I briefly change the switch from daily backup at 6pm to manual backup and back again, the backup starts. I would expect the backup to start as soon as Vorta recognises the mounting of the target location.

sudwhiwdh avatar May 17 '22 16:05 sudwhiwdh

How can Vorta know about new mounts?

m3nu avatar May 17 '22 16:05 m3nu

How does Vorta know about existing or unmounted devices?

sudwhiwdh avatar May 17 '22 16:05 sudwhiwdh

Currently it doesn't. But if you know of a cross-platform way to implement it, we would probably add it.

m3nu avatar May 17 '22 18:05 m3nu

Currently it doesn't. But if you know of a cross-platform way to implement it, we would probably add it.

There probably won't be an event-driven way of implementing this, so simply trying to run the backup after a short period of time would do the job similarly well.

real-yfprojects avatar May 18 '22 13:05 real-yfprojects

Currently it doesn't.

How does the option "Run missed backup on startup or wakeup" work then? Doesn't Vorta need to know if the target device is mounted or not? Otherwise, how could it just start backing up or throw the following notification: "Repo folder not mounted or moved."

sudwhiwdh avatar May 22 '22 10:05 sudwhiwdh

How does the option "Run missed backup on startup or wakeup" work then?

If you shutdown you computer or terminate vorta, it isn't able to run a backup. When vorta is started or on every other triggering of the scheduler, vorta determines whether the last scheduled backup was run. If it wasn't vorta will try to catch up.

Doesn't Vorta need to know if the target device is mounted or not? Otherwise, how could it just start backing up or throw the following notification: "Repo folder not mounted or moved."

You can easily check whether a path exists in the filesystem. If a folder isn't mounted the corresponding path does not exist. So when starting a backup vorta/borg checks whether the repo still exists.

real-yfprojects avatar May 22 '22 10:05 real-yfprojects