I have an archive_interval of 300s, the database is usually updated within the first 20s after each 5th minute. The cron jobs that backup my sdb files run at minute 1 of every hour/day/week. I've never came across any problems, which doesn't mean this way to work will work always that smoothly. But: having an hourly backup, a daily backup, and a weekly backup done this way, chances are, I'll find a working copy anywhere :)
Jonathan Ryshpan schrieb am Montag, 13. März 2023 um 08:29:00 UTC+1: > My weewx database, which is on OaklandWeather, is shared via nfs with my > main system, on which key files and folders are backed up daily using > rsnapshot. The files being backed up include weewx.sdb. I have just noted > this in the WeeWx User Manual: > Do not make the copy of the SQLite database while in the middle of a > transaction! Schedule the backup for immediately after an archive record is > written, and then make sure the backup completes before the next archive > record arrives. Alternatively, stop WeeWX, perform the backup, then restart > WeeWX. > > What are the bad consequences of backing up during a transaction? Is there > just one corrupt entry, or is the whole backup corrupt? Does anyone know a > way to control the backup process so that this particular file in not > copied during a transaction? > > -- > > Many Thanks - Jonathan Ryshpan <[email protected]> > > The best is the enemy of the good -- Voltaire > > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/2be69d2d-c287-449a-aaa4-825b998118edn%40googlegroups.com.
