3 Commits

Author	SHA1	Message	Date
dillard	e58b86fc48	A schedule per location, and locations backed up one after the other ... Off, once a day or every N hours from a time, each in its own time zone. Existing locations keep the time that held for all of them. A backup that has to wait shows as queued, and its restore point has the time it really began.	2026-11-07 00:04:00 +01:00
dillard	133f5f9d34	Schedule: say why a server zone of UTC is passed over	2026-10-22 19:47:30 +02:00
dillard	67cc350b8c	Daily backup time in the administrator's time zone (#19); a time saved before is converted once so it shows as it ran	2026-10-22 16:38:54 +02:00